[jira] [Commented] (HADOOP-8087) Paths that start with a double slash cause "No filesystem for scheme: null" errors

["Colin Patrick McCabe (JIRA)" <ji...@apache.org>]

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

Colin Patrick McCabe commented on HADOOP-8087:
----------------------------------------------

I did some tests and this bug is still present:

{code}
cmccabe@keter:~> /h/bin/hadoop fs -ls /alpha/beta                                                                                                                                
Found 1 items
drwxr-xr-x   - cmccabe supergroup          0 2013-07-17 11:51 /alpha/beta/gamma
cmccabe@keter:~> /h/bin/hadoop fs -ls /alpha/////beta
Found 1 items
drwxr-xr-x   - cmccabe supergroup          0 2013-07-17 11:51 /alpha/beta/gamma
cmccabe@keter:~> /h/bin/hadoop fs -ls //alpha/beta
ls: No FileSystem for scheme: null
{code}

For consistency's sake, I think we should interpret {{//alpha/beta}} as the path {{/alpha/beta}} in the default scheme.

It's also worth pointing out that in shell scripts, it's a lot simpler to just do this:
{code}
./bin/hadoop fs -touchz /${FOO}/${BAR}/${BAZ}
{code}

without having to special-case the scenario where FOO is empty.  If you have do something different when FOO is empty (like omit a slash) the script gets complex.  This is the real win behind handling multiple slashes as a path separator, as we currently do.
                
> Paths that start with a double slash cause "No filesystem for scheme: null" errors
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-8087
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8087
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>
> {{Path}} is incorrectly parsing {{//dir/path}} in a very unexpected way.  While it should translate to the directory {{$fs.default.name}/dir/path}}, it instead discards the {{//dir}} and returns
> {{$fs.default.name/path}}.  The problem is {{Path}} is trying to parsing an authority even when a scheme is not present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira