Redirecting a bug report on behalf of @drshriveer , who informed the DynamoDB SSA team in this issue about a bug:
Hi, apologies for filing an issue here, but I [@drshriveer] have found no other place to file this bug that makes sense. I'm hoping someone on the AWS team can direct this bug to the right place or otherwise let me know where that place is.
Issue:
I have found two instances where DynamoDBLocal fails to return the correct/expected Consumed Capacity. Both when using BatchAPIs against records that do not exist.
When attempting to delete a single record that does not exist via the BatchWrite API, DDBLocal returns 2.0 consumed capacity units. This should be 1.0, as verified against production DynamoDB as well as using the DeleteItem (non-batch) API.
When attempting to Get a single record that does not exist via the BatchGet API, DDBLocal returns 0.0 consumed capacity units. This should be 0.5 (eventually consistent reads) or 1.0 (strongly consistent reads). Again, I verified this against production DynamoDB and tested DDBLocal via the GetItem API which behaves as expected.
Redirecting a bug report on behalf of @drshriveer , who informed the DynamoDB SSA team in this issue about a bug:
Hi, apologies for filing an issue here, but I [@drshriveer] have found no other place to file this bug that makes sense. I'm hoping someone on the AWS team can direct this bug to the right place or otherwise let me know where that place is.
Issue:
I have found two instances where DynamoDBLocal fails to return the correct/expected Consumed Capacity. Both when using BatchAPIs against records that do not exist.
When attempting to delete a single record that does not exist via the BatchWrite API, DDBLocal returns 2.0 consumed capacity units. This should be 1.0, as verified against production DynamoDB as well as using the DeleteItem (non-batch) API.
When attempting to Get a single record that does not exist via the BatchGet API, DDBLocal returns 0.0 consumed capacity units. This should be 0.5 (eventually consistent reads) or 1.0 (strongly consistent reads). Again, I verified this against production DynamoDB and tested DDBLocal via the GetItem API which behaves as expected.