feat(dynamodb): add batch get item paginators for low level and document client #7713
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.
Description
This pull request adds paginators for the DynamoDB BatchGetItemCommand (low level client) and BatchGetCommand (document client). Similar to the implementation in other AWS SDKs (Java, .Net, Go), these paginators work by repeatedly issuing batch get commands until the returned UnprocessedKeys object is missing (or empty), or a service error is returned.
Unlike the other paginators (paginateQuery and paginateScan), these batch get paginators do not mutate the received input.
Testing
This change was tested using a DynamoDB table with 100 items, each 400kb in size. The first test was with a provisioned capacity of 5 RCUs, and the second with 10,000 RCUs . In both tests, the paginators returned the 100 items in 7 pages of maximum 17 items each.
Checklist
*.integ.spec.ts).@publictag and enable doc generation on the package?By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.