[HDFS-5802] NameNode does not check for inode type before traversing down a path

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha
• Fix Version/s: 2.8.0, 2.7.4, 3.0.0-alpha1
• Component/s: namenode
• Labels: supportability
• Hadoop Flags: Reviewed
• Assignee: Xiao Chen
• Reporter: Harsh J
• Created: 21/Jan/14 05:22
• Updated: 12/Sep/16 20:08
• Resolved: 18/Sep/15 14:39

Description

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-rr- 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.

Issue Links

• is related to: HDFS-10276 HDFS should not expose path info that user has no permission to see.