Persist-only property support for DynamoDB Enhanced client

Describe the feature

The Enhanced client should identify JavaBeans properties based on getter methods. When a setter method is not present, the client should persist the property into DynamoDB but should not attempt to set the property on read. (If necessary, an explicit directive to do this such as Jackson's @JsonProperty(access) would be okay.)

Use Case

I have a table with a large number of derived properties for indexing. Currently, the Enhanced client fails to correctly identify properties that have only getter methods and not setter methods. As the use of derived properties to paste together main properties is the standard method of creating indexes for DDB, it would be helpful not to have to include dummy setters.

Proposed Solution

Modify BeanTableSchema#isMappableProperty not to exclude properties without setters, and allow missing setters to be interpreted as "no-op".

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Java SDK version used

2.19.25

JDK version used

openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode)

Operating System and version

Gentoo Linux

Comience leyendo BeanTableSchema#isMappableProperty para entender cómo se excluyen actualmente las propiedades de JavaBeans sin setters. Siga cómo el Enhanced client gestiona la lectura y escritura de esas propiedades y, a continuación, verifique que las propiedades que solo tienen getter se persisten, mientras que las lecturas tratan sus setters inexistentes como no-ops.