[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404338#comment-15404338
]
Andras Bokor commented on HDFS-6262:
------------------------------------
[~ajisakaa],
Any update on this ticket? Will it be closed or fixed?
My thoughts:
Based on my previous experience with rename related issues (HADOOP-13082) it
seems the ecosystem strongly based on the current behavior of rename methods
even they are not consistent. Changing in rename behavior can definitely break
compatibility (another discussion is HDFS-10385, I have just close it as
Later). Please check the linked issues.
I am asking because I am going through the points of HDFS-303 and the 3rd point
is covered by this ticket.
Thanks in advance.
> 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
> Labels: BB2015-05-TBR
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
