Allow a conditional write on put - #51
Open
toots wants to merge 1 commit into
Open
Conversation
Several writers racing for one key currently all succeed, each overwriting the last, and nothing in the API can express "only if nobody got here first"; meta_headers cannot, since it emits x-amz-meta- user metadata rather than request headers. A precondition of `If_none_match or `If_match etag sends the matching header on both put entry points, letting s3 evaluate it and answer 412 rather than replace the object.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Several writers racing for one key currently all succeed, each overwriting the last, and nothing in the API can express "only if nobody got here first" --
meta_headerscannot, since it emitsx-amz-meta-user metadata rather than request headers.A
preconditionof`If_none_matchor`If_match etagsends the matching header on both put entry points, letting S3 evaluate it and answer 412 rather than replace the object.