Steve Loughran created HADOOP-13823:
---------------------------------------
Summary: s3a rename onto existing file must fail
Key: HADOOP-13823
URL: https://issues.apache.org/jira/browse/HADOOP-13823
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/s3
Affects Versions: 2.7.3
Reporter: Steve Loughran
Assignee: Steve Loughran
Priority: Critical
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
