hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-13823) s3a rename onto existing file must fail
Date Thu, 17 Nov 2016 10:13:58 GMT
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

To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

View raw message