hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13823) s3a rename: fail if dest file exists; throw FNFE if source is missing
Date Thu, 24 Nov 2016 14:30:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693418#comment-15693418

Steve Loughran commented on HADOOP-13823:

Also: s3a doesn't raise an exception if the source isn't there. That's at odds with the FS

> s3a rename: fail if dest file exists; throw FNFE if source is missing
> ---------------------------------------------------------------------
>                 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message