Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Thu, 19 Jun 2014 13:14:26 +0000 (UTC)
From: "jay vyas (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12722496.1403183639375.8634.1403183666195@arcas>
In-Reply-To: <JIRA.12722496.1403183639375@arcas>
References: <JIRA.12722496.1403183639375@arcas>
Subject: [jira] [Created] (HADOOP-10723) FileSystem deprecated filesystem
 name warning : Make error message HCFS compliant
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

jay vyas created HADOOP-10723:
---------------------------------

             Summary: FileSystem deprecated filesystem name warning : Make error message HCFS compliant
                 Key: HADOOP-10723
                 URL: https://issues.apache.org/jira/browse/HADOOP-10723
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs
            Reporter: jay vyas


We've found that if we have an alternative filesystem (i.e. xyz://) and we enter it without slashes, we get an hdfs specific error message: 

{{hadoop fs -fs xyz: -mkdir -p /foo/bar}} 

Yields an error message which suggests an hdfs URI.  

{noformat}
# hadoop fs -fs xyzfs: -mkdir -p /foo/bar
14/06/12 17:57:24 WARN fs.FileSystem: "xyz:" is a deprecated filesystem name. Use "hdfs://xyz:/" instead.
{noformat}

Would be better if the error message threw an Exception (as suggested in the comments) and was something that didnt hardcode the hdfs uri to the beggining, as its very confusing when running on any alternative filesystem.


--
This message was sent by Atlassian JIRA
(v6.2#6252)