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

Daryn Sharp commented on HADOOP-9984:
-------------------------------------

bq.  Daryn, the discussion about resolved paths versus unresolved ones belongs 
on HADOOP-9780, not here. The current patch here has nothing to do with that 
issue.

HADOOP-9780 is different.  It's regarding whether the +symlink target+ in the 
file status is (un)resolved, which is indeed a different but important topic, 
whereas this jira's discussion is whether the +actual path+ itself in the file 
status is (un)resolved.

The issue's importance is relevant to this jira because it's not an issue 
unless symlinks are automatically resolved (this jira's goal).  The serious 
ramifications of returning a resolved path need to be considered.  Most notably 
the behavior of operating directly on the symlink target's path.  Data loss 
from a delete of the target, rather than the link itself, is a major concern.

> FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by 
> default
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-9984
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9984
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 2.1.0-beta
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Blocker
>         Attachments: HADOOP-9984.001.patch, HADOOP-9984.003.patch, 
> HADOOP-9984.005.patch, HADOOP-9984.007.patch, HADOOP-9984.009.patch, 
> HADOOP-9984.010.patch, HADOOP-9984.011.patch, HADOOP-9984.012.patch, 
> HADOOP-9984.013.patch, HADOOP-9984.014.patch, HADOOP-9984.015.patch
>
>
> During the process of adding symlink support to FileSystem, we realized that 
> many existing HDFS clients would be broken by listStatus and globStatus 
> returning symlinks.  One example is applications that assume that 
> !FileStatus#isFile implies that the inode is a directory.  As we discussed in 
> HADOOP-9972 and HADOOP-9912, we should default these APIs to returning 
> resolved paths.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to