Atomic s3 snapshots #7162
Draft
Atomic s3 snapshots #7162
Conversation
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
- Add FileIOTest.testConditionalWriteDefaults for tryToWriteAtomicIfAbsent - Add RenamingSnapshotCommitTest for conditional vs lock-based commit paths Co-Authored-By: Claude <[email protected]>
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.
Purpose
The latest hadoop s3a libraries expose conditional writes https://issues.apache.org/jira/browse/HADOOP-19256.
We can utilise this in order to avoid potential data loss with snapshots being overwritten.
Tests
Added coverage
API and Format
No changes to the physical storage or APIs
Documentation
TODO - update docs