[ https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979105#comment-13979105 ]
Suresh Srinivas commented on HDFS-6262: --------------------------------------- [~ste...@apache.org], given rename had different behaviors on different file systems, we did not want to change it and leave it alone (as discussed in HADOOP-6240). That way applications that are dealing with or dependent different behaviors of the file systems continue to work. I think we should deprecate old rename and and not test it for consistent behavior. Lets only test the new rename for consistency across FileSystems. > HDFS doesn't raise FileNotFoundException if the source of a rename() is > missing > ------------------------------------------------------------------------------- > > Key: HDFS-6262 > URL: https://issues.apache.org/jira/browse/HDFS-6262 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.4.0 > Reporter: Steve Loughran > Assignee: Akira AJISAKA > Attachments: HDFS-6262.2.patch, HDFS-6262.patch > > > HDFS's {{rename(src, dest)}} returns false if src does not exist -all the > other filesystems raise {{FileNotFoundException}} > This behaviour is defined in {{FSDirectory.unprotectedRenameTo()}} -the > attempt is logged, but the operation then just returns false. > I propose changing the behaviour of {{DistributedFileSystem}} to be the same > as that of the others -and of {{FileContext}}, which does reject renames with > nonexistent sources -- This message was sent by Atlassian JIRA (v6.2#6252)