[
https://issues.apache.org/jira/browse/HADOOP-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760425#comment-13760425
]
Andrew Wang commented on HADOOP-9912:
-------------------------------------
Hi all,
I'm all in favor of a compatibility mode for listStatus and not breaking
existing programs, but I'm not sure there actually is a compatible solution.
Specifically, there are three cases I'm wondering about:
- Symlink loops. If we're auto-resolving, does our directory walker infinite
loop?
- Dangling symlinks. What happens when we hit one of these? An exception? Prune
it from the results?
- Symlink to another FileSystem. An HDFS symlink could link to another HDFS, or
the local filesystem, or theoretically any implementing filesystem (e.g. S3,
Swift). Would you really want to walk across filesystems transparently?
Please prove me wrong :)
> 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, new-hdfs.txt, new-local.txt,
> old-hdfs.txt, old-local.txt
>
>
> 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
