HADOOP-19256. S3A: Support S3 Conditional Writes: rename builder() #7033
+292
−0
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.
Not for merging
Feature
Outline of a RenameOperation class which creates a builder which would ultimately initiate a rename.
It's not that complex an operation API-wise.
The pain will be in implementing it consistently, especially if we make that non-posix rename into empty dir feature optional with an withLegacyPathFixup() flag.
HDFS would need to implement this server side.
Without that, it could be done for hdfs on the client.
ABFS and S3A could both benefit
Change-Id: I030842543dc60cb4cba3716a6f9d87dd986dffc0
ABFS: etag/file status for better file rename, saved HEAD
S3A: save on HEAD/LIST, progress callbacks (hello distCp!),
How was this patch tested?
wasn't
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?