[
https://issues.apache.org/jira/browse/HADOOP-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754807#comment-13754807
]
Binglin Chang commented on HADOOP-9912:
---------------------------------------
bq. If the NN resolves links it allows the user to unexpectedly access stuff
outside the mount point.
Your comments reminds me another potential issue about permission checking.
How to handle permission denied in listStatus if some(not all) of its entry is
permission denied? getFileStatus doesn't have this issue because it is either
success or failed.
I did a check and found out, it just simply skip the symlink, I think it is not
the right.
{code}
decster:~/hadoop> ll test/
total 8
drwxr-xr-x 2 decster staff 68 Aug 30 23:29 aa
drwx------ 3 root staff 102 Aug 30 23:30 bb
lrwxr-xr-x 1 decster staff 5 Aug 30 23:32 cc -> bb/cc
decster:~/hadoop> ll test/cc
lrwxr-xr-x 1 decster staff 5 Aug 30 23:32 test/cc -> bb/cc
decster:~/hadoop> ll test/cc/bb
ls: test/cc/bb: Permission denied
decster:~/hadoop> bin/hadoop fs -ls file:///Users/decster/hadoop/test/
13/08/30 23:38:59 WARN util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
Found 2 items
drwxr-xr-x - decster staff 68 2013-08-30 23:29
file:///Users/decster/hadoop/test/aa
drwx------ - root staff 102 2013-08-30 23:30
file:///Users/decster/hadoop/test/bb
{code}
> globStatus of a symlink to a directory does not report symlink as a directory
> -----------------------------------------------------------------------------
>
> Key: HADOOP-9912
> URL: https://issues.apache.org/jira/browse/HADOOP-9912
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.3.0
> Reporter: Jason Lowe
> Priority: Blocker
> Attachments: HADOOP-9912-testcase.patch
>
>
> globStatus for a path that is a symlink to a directory used to report the
> resulting FileStatus as a directory but recently this has changed.
--
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