[
https://issues.apache.org/jira/browse/HADOOP-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788851#action_12788851
]
Eli Collins commented on HADOOP-6427:
-------------------------------------
I special cased the file scheme because it is special cased in RFC 1738:
{quote}
As a special case, <host> can be the string "localhost" or the empty string;
this is interpreted as `the machine from which the URL is being interpreted'.
{quote}
ie the non-file schemes in the RFC require an authority because they require a
fully qualified host. My rationale is that since other file systems use a
different scheme (eg the RFC reserves the "afs" scheme) and non-local files in
Hadoop have their own scheme (hdfs, s3, s3n etc) they would not be considered
"fully qualified" without an authority, so the "file" scheme is a special case.
Ie even if accessing remote files via the file scheme from Hadoop's perspective
the file is local in that LocalFs is still used (even if the underlying host
provides this file via a network file system). Reasonable?
> 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.
