Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dynamoDB reads are not fully consisten by default #16483

Merged
merged 1 commit into from
Oct 27, 2017

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Oct 27, 2017

Use fully consistent reads for backend operations.

Use fully consistent reads for backend operations.
@jbardin jbardin merged commit c34265a into master Oct 27, 2017
@jbardin jbardin deleted the jbardin/consistent-s3 branch October 27, 2017 21:22
@ghost
Copy link

ghost commented Apr 6, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants