DynamoDB: document retry configuration #1986
Merged
Conversation
This file contains 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
|
This will make #1924 obsolete. |
seglo
approved these changes
Oct 15, 2019
There was a problem hiding this comment.
LGTM. You could consider adding a direct link to the DynamoDB javadocs for RetryPolicy, https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/core/retry/RetryPolicy.html
11 tasks
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.
Purpose
Instead of wrapping the DynamoDB calls with retrying in Akka Streams, the AWS SDK 2 built-in "retry with backoff" logic should be used.
References
This seems to be the answer to #767 (which was suggested when Alpakka used AWS SDK 1).
The AWS documentation is not up-to-date right now but indicates that this is a recommended approach.
Changes
RetryFlowadded in DynamoDb: AWS SDK2; Add tryFlow to be used with RetryFlow #1896overrideConfiguration