[
https://issues.apache.org/jira/browse/HADOOP-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675132#action_12675132
]
Koji Noguchi commented on HADOOP-5259:
--------------------------------------
bq. I think the only way you can get this is if you set fs.default.name to
hdfs://aaa.bbb.ccc:8020/ in your site config file.
That's exactly what I have.
bq. if so, the workaround is to instead use just hdfs://aaa.bbb.ccc/ there.
Thanks.
But can we have this fixed on hadoop side also?
I think application that worked on 0.17 started failing on 0.18 because of this.
> 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
> Assignee: Doug Cutting
>
> 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.
