Projection support in Transactional Gets at the DynamoDBContext level#4395
Draft
aanton-git wants to merge 2 commits intoaws:developmentfrom
Draft
Projection support in Transactional Gets at the DynamoDBContext level#4395aanton-git wants to merge 2 commits intoaws:developmentfrom
aanton-git wants to merge 2 commits intoaws:developmentfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Add projection support for DynamoDB transactional get operations exposed through DynamoDBContext in the AWS SDK for .NET.
When using DynamoDBContext to perform transactional get operations, it is currently not possible to specify a projection to retrieve only a subset of item attributes. All attributes are always returned.
This capability is supported by DynamoDB and exposed in other SDKs, but is missing from the high-level DynamoDBContext transactional APIs.
Motivation and Context
I need this feature to reduce payload size and improve efficiency when performing transactional reads via DynamoDBContext.
Without projection support:
Transactional gets always return full items, even when only a few attributes are required
Network transfer and deserialization costs are higher than necessary
Transactional reads are less efficient than non-transactional DynamoDBContext reads, which already support projections
This makes it harder to optimize read-heavy transactional workflows.
Testing
Dry-runs
Breaking Changes Assessment
Screenshots (if appropriate)
Types of changes
Checklist