[
https://issues.apache.org/jira/browse/HADOOP-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792761#action_12792761
]
Sanjay Radia commented on HADOOP-6427:
--------------------------------------
If you look at my comments on the symlink jira, I pointed out that the
/dir/link could be resolved relative to the root of the volume (NN) or
resolved relative to the client's context.
(https://issues.apache.org/jira/browse/HDFS-245?focusedCommentId=12629524&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12629524)
I list 4 kinds of symlinks in that comment.
There are use cases for both volume-root-relative and client-root-relative.
I had assumed that /dir/link was a volume-relative symlink (but I don't think
that was called out explicitly in the rather long jira).
I think NFS resolves symlink like "/dir/foo" to the root of the volume (ie NN)
rather than the root of the client. (Need to verify this).
The only way to support both use cases is to have a different character(s) to
distinguish the two.
There was an earlier system I worked on that used / and % to distinguish
between the two (yes ugly).
I would use NFS to guide us here. But regardless of the answer, we need a way
to represent the other use case.
> Add Path isQualified
> --------------------
>
> Key: HADOOP-6427
> URL: https://issues.apache.org/jira/browse/HADOOP-6427
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hadoop-6427-1.patch
>
>
> The Path class has a method to make a path qualified but not to query if the
> path is qualified. This is needed for HADOOP-64221. In addition this patch
> adds tests to TestPath that cover the file scheme. Note that "fully
> qualified" applies to domain names not URIs so this function and it tests
> also serve to define what we mean by a fully qualified path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
