Aws-sdk-java-v2: DynamoDB Document API

[millems]

Review the inherited state of V1 Dynamo DB document API and determine which changes are necessary for V2.

(Feel free to comment on this issue with desired changes).

[jaymell]

Hi. I'm hoping it goes without saying, but it would be wonderful if this API would be updated to support the use of the async client and CompletableFutures.

[dagnir]

Feedback from v1: https://github.com/aws/aws-sdk-java/issues/1528

[bamapookie]

Any progress on this?

[martel]

"Feel free to comment on this issue with desired changes"

Document API had its downsides (like no Java 8 streams support, etc) but at this point I would rather have it with all the downsides than not have it at all. Is there an ETA for it?

[arashbi]

The state of documentation on dynamo, at least on java lang side, is very confusing.

[millems]

In 2.x, we're thinking of combining the Document APIs and DynamoDB Mapper. We're created prototype APIs we're interested in feedback on. See https://github.com/aws/aws-sdk-java-v2/issues/35#issuecomment-468435660 for how you can check our these prototypes and help us deliver the right thing for you.

[mwfpope]

I appreciated that the Document API in v1.11 had methods for converting from json to AttributeValue & vice versa because it made it possible to use DynamoDB for complicated data models without having to use DynamoDB Mapper.

Whatever happens in the new SDK, I would like to see a similar capability so that customers like me who don't want to use DynamoDB Mapper don't have to do all the heavy lifting of converting a complex data model.

[gibbonsj]

Is there a status on this now the DDB enhanced client is released?

I plus'd 1 on @mwfpope comment... item to/from json was a greatly appreciated feature in DDB.

[millems]

@gibbonsj The document client is high on our priority list. We should probably to a to/from json API as a separate feature request. I don't think our plans for the document client currently include a to/from JSON API in scope.