You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2014/01/21 06:23:22 UTC
[jira] [Created] (HDFS-5802) NameNode does not check for inode type
before traversing down a path
Harsh J created HDFS-5802:
-----------------------------
Summary: NameNode does not check for inode type before traversing down a path
Key: HDFS-5802
URL: https://issues.apache.org/jira/browse/HDFS-5802
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.0.0-alpha
Reporter: Harsh J
Priority: Trivial
This came up during the discussion on a forum at http://community.cloudera.com/t5/Batch-Processing-and-Workflow/Permission-denied-access-EXECUTE-on-getting-the-status-of-a-file/m-p/5049#M162 surrounding an fs.exists(…) check running on a path /foo/bar, where /foo is a file and not a directory.
In such a case, NameNode yields a user-confusing message of {{Permission denied: user=foo, access=EXECUTE, inode="/foo":foo:foo:-rw-r--r--}} instead of clearly saying (and realising) "/foo is not a directory" or "/foo is a file" before it tries to traverse further down to locate the requested path.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)