[
https://issues.apache.org/jira/browse/HADOOP-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756877#comment-13756877
]
Jason Lowe commented on HADOOP-9912:
------------------------------------
Thanks for chiming in, Eli. I understand that there are going to be times when
we can't avoid exposing symlinks to older clients, but we should try to avoid
that when reasonable to do so. I believe the common use-case for symlinks will
be links within the same filesystem, and if listStatus proceeds to resolve
symlinks that it can resolve then existing directory walkers should work as-is.
Using a symlink in HDFS to another directory in the same filesystem should
"just work," but that's not going to be the case if listStatus behaves as it
does today.
Is it unreasonable to have listStatus resolve symlinks and provide a separate
API or flag for symlink-aware clients? Understandably listStatus will still
have to expose symlinks that cannot be resolved (e.g.: dangling links or links
to permission-restricted areas), but that seems preferable to breaking most of
the directory walking code built for FileSystem.
> 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
