[
https://issues.apache.org/jira/browse/HADOOP-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754132#comment-13754132
]
Daryn Sharp commented on HADOOP-9912:
-------------------------------------
I need to look at this further but if {{DFS.listStatus}} isn't resolving, then
we've got to think hard about the semantics of symlinks. 99% of the time, the
user expects a symlink to be transparent.
Lots of code uses {{listStatus}} or {{globStatus}} and expects to perform
file/dir checks. Now that code will be required to check if the path is a
symlink, if yes, re-stat. This will greatly inhibit the use of symlinks which
is why I think a new api is required.
Either way we go, we can't have the inconsistency I cited for how globbing is
now returning different results based on whether the symlink was matched by a
static or globbed path component. It must always be a resolved status or an
unresolved status.
> 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
