Fix BatchGetItem paginated request data format. #205
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
1 participant
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.
This fixes the format of paginated BatchGetItem request using
Table.getItems.Without this change, the first request would succeed, but subsequent paginated requests would fail with
MissingRequiredParameter: Missing required key 'RequestItems' in params. This is because the requested keys were sent as the request, rather than being placed onrequest.RequestItems.Note that a large number of items must be requested in order for BatchGetItem requests to be paginated. Even with 5000 items requested DynamoDB would sometimes return them all in one response.