Feature/issue 334 bulk requests nobundle #377
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following David's suggestion in the chat today
13:54:35 From David Glazer to Everyone:
semi-radical proposal: do NOT support bundles; do support bulk requests for a long list of ids; implement pagination on the return for the bulk request then do some object-semantics-specific way to get the list of object ids that you want to retrieve.
The proposal, as stated above, has been around for some time. Surfacing it as a PR for formal consideration.
This branch was created from the issue-334-drs-bulk-requests branch. It should preserve all existing bulk request functions:
Removed the Contents object.
Removed expand parameter