Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 10658 invoked from network); 14 Feb 2009 00:23:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2009 00:23:30 -0000 Received: (qmail 75979 invoked by uid 500); 14 Feb 2009 00:23:27 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 75969 invoked by uid 500); 14 Feb 2009 00:23:27 -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 75958 invoked by uid 99); 14 Feb 2009 00:23:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2009 16:23:27 -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; Sat, 14 Feb 2009 00:23:19 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 958AC234C495 for ; Fri, 13 Feb 2009 16:22:59 -0800 (PST) Message-ID: <1903609273.1234570979611.JavaMail.jira@brutus> Date: Fri, 13 Feb 2009 16:22:59 -0800 (PST) From: "Hairong Kuang (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=12673434#action_12673434 ] Hairong Kuang commented on HADOOP-5259: --------------------------------------- Is it possible that this is related to HADOOP-3317? Doug, could you please take a look? Is it better if HADOOP-3317 does not remove default port number in namenode URI but adds the default port number to a URL without a port number during normalization? This would be more backwards compatible. > 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 > > 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.