[
https://issues.apache.org/jira/browse/HADOOP-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795718#action_12795718
]
Eli Collins commented on HADOOP-6427:
-------------------------------------
If I understand correctly we:
# Drop support links that are relative to the file context's default file
system from the current patch, ie the client's default file system will never
be used when resolving links. Defer this to a future change, if needed.
# Leave the behavior of partially qualified link targets up to file system of
the path that refers to the link. Examples:
** file:///link -> file:///file is ok because LocalFs only supports partially
qualfied URIs (does not support URIs with an authority)
** file:///link -> file://localhost/file is an error, same rationale
** hdfs://hostx/link -> hdfs:///file is an error because Hdfs URIs must be
fully qualified
** hdfs://hostx/link -> //hosty/file is an error, same rationale
** foo://hostx/link -> //hosty/file is ok if file system foo supports paths of
form //hosty/file
This sounds good to me. Sanjay, and others, does this sound reasonable to you?
> 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.
