hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira AJISAKA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
Date Tue, 22 Apr 2014 10:10:15 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976606#comment-13976606
] 

Akira AJISAKA commented on HDFS-6262:
-------------------------------------

I'm thinking the problem is rename(src, dst) calls deprecated FSDirectory.renameTo(src, dst),
which doesn't throw FileNotFoundException even if src does not exist.
I suggest rename(src, dst) to call FSDirectory.renameTo(src, dst, Rename.NONE).

> 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)

Mime
View raw message