DynamoDBMapperConfig.DefaultBatchWriteRetryStrategy equivalent in DynamoDB SDK for Java v2

Open
#6,536 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
aws, java
Domain
api, databases

Research direction

Start with the V1 DynamoDBMapper#batchSave behavior and compare it with the V2 DynamoDB batch-write APIs. Investigate how retries for unprocessed items and splitting requests above 25 items or 1 MB could be exposed, then verify that both requested behaviors are covered.

Written by the indexing model from the issue text.

Description

dynamodb-enhanced feature-request p2
Describe the feature

I'd like to request features which were available in the V1 SDK but missing in the V2 SDK below:

  • Automatic retries for unprocessedItems: DynamoDBMapper#batchSave in the V1 SDK was capable of handling retries of unprocessedItems. However, in the V2 SDK, there seems to be no out of the box equivalent.
  • Automatic breaking down of a large batch into smaller batches: DynamoDBMapper#batchSave in the V1 SDK was capable of breaking a large batch which contains more than 25 items or exceeds the request size limit of 1MB into smaller chunks. The V2 SDK doesn't seem to be capable of this.

More details can be found in: https://stackoverflow.com/questions/78495172/dynamodb-java-sdk-v2-client-batchwrite-retries

Use Case

It was available in the V1 SDK. I have to implement these myself after migrating to the V2 SDK otherwise.

Proposed Solution

No response

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.29.6

JDK version used

any

Operating System and version

any

Dominant language
Java
Stars
2.6k
Forks
1k
Avg merge
2d 17h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-sdk-java-v2

All issues in aws/aws-sdk-java-v2

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.