Skip to content

Transactional and PartiQL ConsumedCapacity under-reported / omitted #37

@hicksy

Description

@hicksy

Summary

ConsumedCapacity reporting differs from real DynamoDB, surfaced by the dynamodb-conformance suite (Dynoxide 0.9.13). All four are under-reporting or omission against ReturnConsumedCapacity.

  1. TransactWriteItems reports 1 WCU per item; AWS charges 2 WCU per item for transactional writes (so a 2-item transaction is CapacityUnits: 4, not 2).
  2. TransactGetItems reports 1 RCU per item; AWS charges 2 RCU per item, including items that are missing.
  3. TransactGetItems with ReturnConsumedCapacity: INDEXES omits Table.ReadCapacityUnits from the breakdown; AWS populates it.
  4. PartiQL ExecuteStatement omits the ConsumedCapacity block entirely when ReturnConsumedCapacity is requested; AWS always returns it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions