hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9780) Filesystem and FileContext methods that follow symlinks should return unresolved paths
Date Tue, 08 Oct 2013 15:19:43 GMT

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

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

bq. I think server-side resolution is problematic. How would this work with a chroot or viewfs?

The same way it works now.  If the scheme of the absolute symlink is {{viewfs://}}, it's a
cross-filesystem symlink, and we throw it back to the client.  If it's {{hdfs://}}, it's ours
and we handle it.

> 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)

Mime
View raw message