[
https://issues.apache.org/jira/browse/HADOOP-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793731#action_12793731
]
Sanjay Radia commented on HADOOP-6427:
--------------------------------------
Absolute paths:
Agree with Eli's comment on absolute links. It is consistent with the "symlinks
are resolved relative to their source" is consistent with
"volume root relative". I was thrown off by Doug's comment in HDFS-245 where he
said "Links should be resolved against the client's context."; this seems to be
in conflict with his "symlinks are resolved relative to their source".
Also thanks for the "hdfs://host1/dir/foo" I had missed that case. I agree with
your analysis.
Partially qualified syntax (The partially qualified syntax (a scheme but no
host, eg hdfs:///foo)).
I agree that the syntax is goofy if the scheme is ignored. Not sure if everyone
will buy into the "%" syntax (it was inspired by the "~" syntax but such
special character get messy after a while.) Can we use a special scheme such as
"clientContext:///foo"?
So is your proposal to mark partially qualified syntax as invalid or to allow
them with the somewhat "goofy" interpretation.
> 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.
