hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Kumar M R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7418) support for multiple slashes in the path separator
Date Fri, 08 May 2015 09:48:00 GMT

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

Kiran Kumar M R commented on HADOOP-7418:
-----------------------------------------

Current behavior of trunk and 7.2 is if {{//}} appears in the beginning of path, it is expected
to have scheme: before that. So restriction is that  {{//}} is not supported only in beginning
of path as its used to identify scheme.

Samples:
{code}
>hadoop fs -ls //wc-out//_temporary
ls: No FileSystem for scheme: null
{code}

{{//}} is allowed later in path. Below path is valid
{code}
>hadoop fs -ls /wc-out//_temporary
Found 1 items
drwxr-xr-x   - KiranKumar supergroup          0 2015-05-04 02:41 /wc-out/_temporary/1
{code}

{{//}} is also valid if path has proper scheme
{code}
>hadoop fs -ls hdfs://kiran-hpenvy//wc-out//_temporary
Found 1 items
drwxr-xr-x   - KiranKumar supergroup          0 2015-05-04 02:41 hdfs://kiran-hpenvy/wc-out/_temporary/1
{code}


I think existing path behavior is fine. This issue can be closed.
Others please comment.

> support for multiple slashes in the path separator
> --------------------------------------------------
>
>                 Key: HADOOP-7418
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7418
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>         Environment: Linux running JDK 1.6
>            Reporter: Sudharsan Sampath
>            Assignee: Andrew Look
>            Priority: Minor
>              Labels: BB2015-05-TBR, newbie
>         Attachments: HADOOP-7418--20110719.txt, HADOOP-7418.txt, HADOOP-7418.txt, HDFS-1460.txt,
HDFS-1460.txt
>
>
> the parsing of the input path string to identify the uri authority conflicts with the
file system paths. For instance the following is a valid path in both the linux file system
and the hdfs.
> //user/directory1//directory2.
> While this works perfectly fine in the command line for manipulating hdfs, the same fails
when specified as the input path for a mapper class with the following expcetion.
> Exception in thread "main" java.net.UnknownHostException: unknown host: user
>         at org.apache.hadoop.ipc.Client$Connection.<init>(Client.java:195)
> as the org.apache.hadoop.fs.Path class assumes the string that follows the '//' to be
an uri authority



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message