Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 16 Aug 2012 10:28:38 +1100 (NCT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <2097316065.16780.1345073318198.JavaMail.jiratomcat@arcas>
In-Reply-To: <1420166651.58632.1342457314819.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Resolved] (HDFS-3670) WebHDFS have a "not-enabled" return
 code instead of using file not found
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE resolved HDFS-3670.
------------------------------------------

    Resolution: Not A Problem

Let's close this as not-a-problem.
                
> WebHDFS have a "not-enabled" return code instead of using file not found  
> --------------------------------------------------------------------------
>
>                 Key: HDFS-3670
>                 URL: https://issues.apache.org/jira/browse/HDFS-3670
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 1.0.0, 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Tsz Wo (Nicholas), SZE
>
> WebHDFS (and HttpFs if it doesn't already) should have a return code indicating they are not enabled. Currently you get eg a file not found if webhdfs is not enabled which isn't intuitive.  
> {code}
> hadoop-3.0.0-SNAPSHOT $ ./bin/hadoop fs -get webhdfs://localhost:50070/user/eli/temp.json
> get: Unexpected HTTP response: code=404 != 200, op=GETFILESTATUS, message=Not Found
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira