[
https://issues.apache.org/jira/browse/HADOOP-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789481#comment-13789481
]
Chris Nauroth commented on HADOOP-9780:
---------------------------------------
bq. There is no client context-sensitivity unless different clients are using
inconsistent DNS servers.
In the current code, there could still be an issue of client
context-sensitivity if different clients map the schemes to entirely different
filesystem implementations in their configuration. Colin has suggested that we
drop support for this kind of remapping, perhaps by freezing the definitions of
the schemes that ship in hadoop-common, like hdfs and viewfs. (Some amount of
mapping configuration support needs to remain though to support plugging in
alternative filesystem implementations that ship outside the Hadoop code.)
> 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)
