[ 
https://issues.apache.org/jira/browse/HADOOP-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760476#comment-13760476
 ] 

Colin Patrick McCabe commented on HADOOP-9912:
----------------------------------------------

HDFS symlinks support in FileContext has been in many official releases of 
Hadoop 2.  "I doubt they're being used" is not really a good reason to break 
the existing behavior.  That's why we have been trying to keep as close as 
possible to the FileContext behavior in our port of symlinks to FileSystem.

As Andrew mentioned, it is not always possible to resolve symlinks.  There can 
be infinite symlink loops, or dangling symlinks.  "Just make them go away, I 
don't want to see them at all" is not a viable strategy.  Symlinks exist and 
their semantics are different than directories or files.

There may be an occasional program that needs a tiny change to be compatible 
with symlinks.  I think this is likely to be extremely rare, since 
getFileStatus resolves symlinks fully, and symlinks are mostly transparent to 
the application.  If system administrators don't want to change anything, they 
don't have to-- they can just continue not using symlinks on their clusters.
                
> 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

Reply via email to