[jira] Commented: (HADOOP-2842) NameNode should throw FileNotFoundException for nonexistent files

["Hairong Kuang (JIRA)" <ji...@apache.org>]

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

Hairong Kuang commented on HADOOP-2842:
---------------------------------------

The problem described in this issue was fixed as part of HADOOP-2841. This patch fixed the javadoc. Thanks Edward. Here are a few comments:
1. Although FSNamesystem.exists deprecated, could you please fix it so it returns true only when getFileInfo throws a FileNotFoundException?
2. In TestDFSMkdirs, the mini dfs cluster is brought up with the format flag true. So the check of the non-existent directory is unnecessary.

> NameNode should throw FileNotFoundException for nonexistent files
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2842
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2842
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.16.0
>            Reporter: Hairong Kuang
>            Assignee: Edward J. Yoon
>             Fix For: 0.18.0
>
>         Attachments: 2842_v01.patch
>
>
> Currently namenode throws an IOException with a "File does not exist" message for nonexistent files. It would be better to throw FileNotFound exception. So the client does not need to parse the error message to find out the real cause of the I/O error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.