hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6427) Add Path isQualified
Date Fri, 01 Jan 2010 01:42:29 GMT

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

Eli Collins commented on HADOOP-6427:

Hm, seems like we should first check if the target can be resolved with the file system of
the target, if one is specified, before trying to resolve using the file system of the link.
* hdfs://hostx/link -> file:///file is ok even though Hdfs doesn't support URIs w/o authorities
* foo://host/link -> //host/file is only ok if file system foo supports URIs with just
an authority 

I should also mention that even in the /link -> /file case we know the file system of the
link since FileContext uses the default file system to make the paths it creates fully qualified,
ie the default file system is never used when resolving a link target, but _is_ still used
when creating paths.

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

View raw message