[
https://issues.apache.org/jira/browse/HADOOP-9929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe updated HADOOP-9929:
-----------------------------------------
Attachment: HADOOP-9929.001.patch
Here's a patch which lets all exceptions except FileNotFound propagate,
effectively restoring the old behavior. This means that, as before, your glob
will fail if you encounter permission issues. It's probably best to keep it
this way for compatibility reasons.
I also added a unit test for this.
> 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.1.0-beta, 2.0.4-alpha
> Reporter: Jason Lowe
> Attachments: HADOOP-9929.001.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
