Support retreiving ConsumedCapacity on DDB mapper interactions

[baumand-amazon]

Describe the feature

This was reported for V1 and closed because no more changes were being made as V2 was released. I don't think this was ever addressed in V2.
aws/aws-sdk-java#1170

Use Case

Users of the mapper who need ConsumedCapacity stats to handle performance and scaling operations for their databases are stuck if they have already invested in using the mapper. There's no way to get that information without migrating away from the mapper.

It's operationally important for users to be able to track the sizes of their read/write requests for capacity planning.

Proposed Solution

No response

Other Information

One option to resolve it is to add mapper method alternatives like saveWithStats which returns a DynamoDBResultWithStats<Item, Stats>. This provides a relatively simple migration path for users already invested in the mapper to get the stats they need.

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Java SDK version used

any

JDK version used

any

Operating System and version

any

[debora-ito]

Hi @baumand-amazon

ConsumedCapacity is already supported in the DynamoDbTable *WithResponse APIs in their respective return types - e.g. see
PutItemEnhancedResponse, DeleteItemEnhancedResponse.

Is this what you are looking for?

[baumand-amazon]

Thanks @debora-ito it looks like that's what I was looking for.

I got thrown off - we use the V1 mapper which doesn't have this support.

When I checked I thought we were using V2 because of the dynamodbv2 in the package name.
https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/dynamodbv2/datamodeling/DynamoDBMapper.html - see the package com.amazonaws.services.dynamodbv2.datamodeling.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.