Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Tue, 21 Jan 2014 05:23:22 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12689950.1390281766179.38172.1390281802761@arcas>
In-Reply-To: <JIRA.12689950.1390281766179@arcas>
References: <JIRA.12689950.1390281766179@arcas>
Subject: [jira] [Created] (HDFS-5802) NameNode does not check for inode type
 before traversing down a path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Harsh J created HDFS-5802:
-----------------------------

             Summary: NameNode does not check for inode type before travers=
ing 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-ge=
tting-the-status-of-a-file/m-p/5049#M162 surrounding an fs.exists(=E2=80=A6=
) check running on a path /foo/bar, where /foo is a file and not a director=
y.

In such a case, NameNode yields a user-confusing message of {{Permission de=
nied: user=3Dfoo, access=3DEXECUTE, inode=3D"/foo":foo:foo:-rw-r--r--}} ins=
tead of clearly saying (and realising) "/foo is not a directory" or "/foo i=
s 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)