EfficientDynamoDb
EfficientDynamoDb copied to clipboard
AllocZero
High-performance C# DynamoDb library
`ItemCollectionMetrics` is completely ignored in high-level API deserialization. The class structure varies from what is returned in JSON and requires custom ddb converters.
The builders for `BatchGet` and `BatchWrite` operations for some reason don't support requesting `ReturnConsumedCapacity` and get the `ConsumedCapacity` in the response (no `ToResponseAsync` for the builders). Although it is supported...
**Additions:** 1. Exposed consumed capacity high-level API for batch requests. Addresses #222. **Bugfixes:** 1. `ConsumedCapacity` was not parsed at all for `DeleteItem` operation due to incorrect JSON name mapping. 2....
This change allows the use of PascalCase for enum values instead of UPPER_SNAKE_CASE used in DynamoDB API. This is a breaking change for [DescribeTable](https://github.com/AllocZero/EfficientDynamoDb/blob/e3e672f120d1a6f1365176da309413ad514cafd8/src/EfficientDynamoDb/DynamoDbManagementContext.cs#L20) call. But since it's the only...
This PR enables using different endpoints for different DynamoDB services. E.g. DynamoDB Streams API endpoints [use different convention](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html#Streams.Endpoints) `streams.dynamodb..amazonaws.com` instead of regular `dynamodb..amazonaws.com`.
is there any way to see what is being produced? I tried mess about with IUpdateEntityRequestBuilder but could not work it out. The main reason I have three requests below...
It would be great if this library were to provide support for emitting OpenTelemetry metrics and traces in accordance with the [semantic conventions for DynamoDB](https://opentelemetry.io/docs/specs/semconv/database/dynamodb/). Note that the AWS SDK...
