Adds count, scanned count and consumed capacity to DDB Enhanced Page #4444
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.
Motivation and Context
This PR addresses the issue of missing metadata fields in the response of DDB Enhanced Scan and Query operations, as described in
In addition, this PR adds
Count
andScannedCount
to the response to aid users who want to understand the results of their queries.Scan and Query are paginated operations where each page is represented by a backend call to DDB. The consumed capacity and count metric metadata is specific per page; therefore this metadata is exposed to the user per page. The new response values are available on both table and index operations.
Modifications
EnhancedScanRequest
andEnhancedQueryRequest
ConsumedCapacity
to thePage
classCount
andScannedCount
to thePage
classTesting
Functional testing, integration testing
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License