[
https://issues.apache.org/jira/browse/HADOOP-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772588#comment-13772588
]
Arun C Murthy commented on HADOOP-9912:
---------------------------------------
bq. At this point we think the best choice for the existing listStatus API is
to follow symlinks when it can but throw an exception when it cannot.
Makes sense to me.
I agree it's unfortunate that "bad" symlinks, but also that this is
significantly better than the alternative of silently missing them since apps
might follow the hadoop-1.x semantics of isDir.
----
Another crazy thought I'd like to throw out - what if we just returned false
for isDir if we cannot resolve the symlink rather than throw an exception?
This has the benefit of treating the unresolved symlink as a 'file' which means
apps can still move them etc. while not blowing them up.
Is it too crazy? :)
> 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.1.0-beta
> 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
