Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 92881 invoked from network); 19 Feb 2009 20:12:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Feb 2009 20:12:33 -0000 Received: (qmail 82751 invoked by uid 500); 19 Feb 2009 20:12:31 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 82500 invoked by uid 500); 19 Feb 2009 20:12:30 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 82489 invoked by uid 99); 19 Feb 2009 20:12:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2009 12:12:30 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2009 20:12:22 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id EAD75234C4AA for ; Thu, 19 Feb 2009 12:12:01 -0800 (PST) Message-ID: <1822531733.1235074321958.JavaMail.jira@brutus> Date: Thu, 19 Feb 2009 12:12:01 -0800 (PST) From: "Doug Cutting (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-5259) Job with output hdfs:/user//outputpath (no authority) fails with Wrong FS In-Reply-To: <1617792345.1234565939536.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675114#action_12675114 ] Doug Cutting commented on HADOOP-5259: -------------------------------------- I'm having trouble reproducing this in a unit test. 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. Is that what you've done? If so, the workaround is to instead use just hdfs://aaa.bbb.ccc/ there. The problem is that the port-defaulting is filesystem specific, but the setting of the default FS is generic, and hence knows nothing about port defaulting. > Job with output hdfs:/user//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.