[
https://issues.apache.org/jira/browse/HADOOP-9929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771522#comment-13771522
]
Hudson commented on HADOOP-9929:
--------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4439 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4439/])
HADOOP-9929. Insufficient permission for a path reported as file not found.
(Contributed by Colin Patrick McCabe) (cmccabe:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1524611)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/Globber.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/fs/TestGlobPaths.java
> Insufficient permissions for a path reported as file not found
> --------------------------------------------------------------
>
> Key: HADOOP-9929
> URL: https://issues.apache.org/jira/browse/HADOOP-9929
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.3.0
> Reporter: Jason Lowe
> Assignee: Colin Patrick McCabe
> Fix For: 2.3.0
>
> Attachments: HADOOP-9929.001.patch, HADOOP-9929.002.patch
>
>
> Using "hadoop fs -ls" to list a path where the permissions of a parent
> directory are insufficient ends up reporting "no such file or directory" on
> the full path rather than reporting the permission issue. For example:
> {noformat}
> $ hadoop fs -ls /user/abc/tests/data
> ls: `/user/abc/tests/data': No such file or directory
> $ hadoop fs -ls /user/abc
> ls: Permission denied: user=somebody, access=READ_EXECUTE,
> inode="/user/abc":abc:hdfs:drwx------
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
