-
Notifications
You must be signed in to change notification settings - Fork 864
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return ConsumedCapacityUnits from DynamoDB Enhanced GetItem calls #4372
Comments
If accepted, I can raise a pull request with required changes. |
@psnilesh PRs are welcome! |
Submitted PR #4375 |
* feat: add GetItemEnhancedResponse with consumedCapacity units to DynamoDb enhanced client This addressing feature request #4372 * Fix dependency error in DynamoDB Enhanced Client Related to issue #4372 * More unit and functional tests for DynamoDbTable#getItemWithResponse() api * Add unit tests for DynamoDB GetItemEnhancedResponse --------- Co-authored-by: Nilesh <[email protected]>
Changes for retrieving read units consumed by GetItem and BatchGetItem operations have been merged and will be available in the next minor version release. |
|
Describe the feature
DynamoDB can return capacity units consumed by GetItem call if requested, but it is not supported by DynamoDbTable interface. Following are all the methods for loading data,
However, this is already supported by Put, Update and Delete methods,
I propose we add ConsumedCapacity and ItemCollectionMetrics to for read operations as well in a backwards compatible manner.
Related to #1918
Use Case
We have a requirement where we need to accurately calculate capacity consumed by multiple DynamoDB requests made in succession. Having the metrics from DynamoDB would greatly simplify this work.
Proposed Solution
(Better names are welcome)
I propose we add and implement following new methods, similar to how Put, Update and Delete is implemented.
Other Information
No response
Acknowledgements
AWS Java SDK version used
2.x
JDK version used
Java8 or newer
Operating System and version
ALL
The text was updated successfully, but these errors were encountered: