Adding unprocessedKeysForTable to BatchGetItem results object #2425
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
DynamoDB returns keys that could not be processed in a BatchGetItem result, however there was no way to get at these values
through the enhanced client. Inferring which keys were not processed by subtracting the results list from the inputs was not
sufficient because if any of the items were missing from the results, it would be impossible to know if they were not included in
the result set because they were not processed or if they were actually missing.
Motivation and Context
At least one customer has asked for this functionality. DynamoDbMapper provides this functionality by throwing an exception and providing the partial results and the unprocessed keys in that exception, so this is also a feature parity issue.
Testing
Unit tests.
Types of changes
Checklist
mvn install
succeedsLicense