You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current /_changes/ allows full document retrieval using the param include_docs=true, but sometimes such documents contain extra data, that make downloading such sequences unnecessary costly.
I have been reading about the available filters and views and seems like there is no way to achieve what I'm trying to do. Please let me know if this is already doable!
Example
For instance, the following sequences with their file sizes:
5524439: 36M
5524449: 23M
5526384: 45M
5527795: 45M
How
Current Behaviour
You can quickly test this by downloading a few files:
Upon closer inspection of those sequences, the bloat was never caused by a document's property that we were looking for, but rather on many different properties which sometimes are not even part of the package standard.
The desired behavior would be to been able to download only the pieces of the document that we need.
I'm not sure about what is the best way to express but one idea could be to follow the selector api
This discussion was converted from issue #109 on May 08, 2020 14:31.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Motivation ("The Why")
The current
/_changes/
allows full document retrieval using the paraminclude_docs=true
, but sometimes such documents contain extra data, that make downloading such sequences unnecessary costly.I have been reading about the available filters and views and seems like there is no way to achieve what I'm trying to do. Please let me know if this is already doable!
Example
For instance, the following sequences with their file sizes:
How
Current Behaviour
You can quickly test this by downloading a few files:
Desired Behaviour
Upon closer inspection of those sequences, the bloat was never caused by a document's property that we were looking for, but rather on many different properties which sometimes are not even part of the package standard.
The desired behavior would be to been able to download only the pieces of the document that we need.
I'm not sure about what is the best way to express but one idea could be to follow the selector api
References
Beta Was this translation helpful? Give feedback.
All reactions