hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5802) NameNode does not check for inode type before traversing down a path
Date Fri, 18 Sep 2015 19:52:05 GMT

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

Hudson commented on HDFS-5802:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk #2330 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2330/])
HDFS-5802. NameNode does not check for inode type before traversing down a path. (Xiao Chen
via Yongjun Zhang) (yzhang: rev 2ff6faf954eb0f1ab2b339d589edb30040087669)
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSPermissionChecker.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSPermission.java


> 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
>            Assignee: Xiao Chen
>            Priority: Trivial
>              Labels: supportability
>             Fix For: 2.8.0
>
>         Attachments: HDFS-5802.001.patch, HDFS-5802.002.patch, HDFS-5802.003.patch, HDFS-5802.004.patch,
HDFS-5802.005.patch, HDFS-5802.006.patch
>
>
> 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.3.4#6332)

Mime
View raw message