[
https://issues.apache.org/jira/browse/HADOOP-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789795#comment-13789795
]
Colin Patrick McCabe commented on HADOOP-9780:
----------------------------------------------
I filed HADOOP-10034 to discuss optimizations for same-filesystem symlinks. On
this JIRA, we can make FS and FC return unresolved paths rather than resolved
ones. I think the consensus that we're coming to is that we would like to do
this.
bq. Some amount of mapping configuration support needs to remain though to
support plugging in alternative filesystem implementations that ship outside
the Hadoop code
The HDFS NN just needs to know "is this scheme hdfs or not?" No configuration
is needed. Anyway, we should probably discuss this on HADOOP-10034.
> Filesystem and FileContext methods that follow symlinks should return
> unresolved paths
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-9780
> URL: https://issues.apache.org/jira/browse/HADOOP-9780
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Colin Patrick McCabe
> Priority: Minor
>
> Currently, when you follow a symlink, you get back the resolved path, with
> all symlinks removed. For compatibility reasons, we might want to have the
> returned path be an unresolved path.
> Example: if you have:
> {code}
> /a -> b
> /b
> /b/c
> {code}
> {{getFileStatus("/a/c")}} will return a {{FileStatus}} object with a {{Path}}
> of {{"/b/c"}}.
> If we returned the unresolved path, that would be {{"/a/c"}}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
