[
https://issues.apache.org/jira/browse/HADOOP-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673416#action_12673416
]
Koji Noguchi commented on HADOOP-5259:
--------------------------------------
Looking at FileSystem.java:checkapth()
{noformat}
if (thatAuthority == null && // path's authority is null
thisAuthority != null) { // fs has an authority
URI defaultUri = getDefaultUri(getConf()); // & is the default fs
if (thisScheme.equalsIgnoreCase(defaultUri.getScheme()) &&
thisAuthority.equalsIgnoreCase(defaultUri.getAuthority()))
return;
}
{noformat}
With output of hdfs:/user/knoguchi/outputpath
that Authority is null
this Authority is aaa.bbb.ccc
this Scheme is hdfs
default Scheme is hdfs
default Authority is aaa.bbb.ccc:8020
FileSystem.getDefaultUri simply takes "fs.default.name" and don't know about
NameNode.DEFAULT_PORT.
> Job with output hdfs:/user/<username>/outputpath (no authority) fails with
> Wrong FS
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-5259
> URL: https://issues.apache.org/jira/browse/HADOOP-5259
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs, fs
> Affects Versions: 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.19.0
> Reporter: Koji Noguchi
>
> Using namenode with default port of 8020.
> When starting a job with output hdfs:/user/knoguchi/outputpath, my job fails
> with
> Wrong FS: hdfs:/user/knoguchi/outputpath, expected: hdfs://aaa.bbb.cc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
