issue #5039 - added support for fluent setters in dynamodb enhanced client #5856
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.
Adding support for Fluent Setters in the DynamoDBEnhancedClient #5039.
Description
Some consumers of DynamoDbMapper (v1) configured their bean classes with fluent setters. While this is working in v1, it is not supported in v2 as it was not considered in the original design. This feature aims to introduce support for Fluent Setters in the
DynamoDBEnhancedClient
.Motivation and Context
The issue was raised in #5039. Adding support for fluent setters will help achieve feature parity between DynamoDbMapper (v1) and DynamoDBEnhancedClient (v2), making it easier for consumers to migrate to v2.
Modifications
The
BeanInfo
is now obtained usingIntrospector.getBeanInfo(beanClass)
, which identifies bean property descriptors based on regular setters and getters. TheBeanTableSchema -> StaticTableSchema<T> createStaticTableSchema(Class<T> beanClass, MetaTableSchemaCache metaTableSchemaCache)
logic has been updated to invoke a new method that enhances the descriptors to support fluent setters.Testing
Unit tests added.
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License