Details
-
Sub-task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.7.3
-
None
-
Reviewed
Description
HIVE-15199 shows that s3a allows rename onto an existing file, which is something HDFS, azure and s3n do not permit (though file:// does). This is breaking bits of Hive, is an inconsistency with HDFS and a regression compared to s3n semantics.
I propose: rejecting the rename on a file -> file rename if the destination exists (easy) and changing the s3a.xml contract file to declare the behavior change; this is needed for AbstractContractRenameTest.testRenameFileOverExistingFile to handle the changed semantics.
Attachments
Attachments
Issue Links
- is depended upon by
-
HADOOP-13600 S3a rename() to copy files in a directory in parallel
- Resolved
- is related to
-
HIVE-15199 INSERT INTO data on S3 is replacing the old rows with the new ones
- Resolved