Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05273913B for ; Mon, 16 Jul 2012 16:48:36 +0000 (UTC) Received: (qmail 84256 invoked by uid 500); 16 Jul 2012 16:48:35 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 84162 invoked by uid 500); 16 Jul 2012 16:48:35 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 83917 invoked by uid 99); 16 Jul 2012 16:48:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jul 2012 16:48:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 2B86514285A for ; Mon, 16 Jul 2012 16:48:35 +0000 (UTC) Date: Mon, 16 Jul 2012 16:48:35 +0000 (UTC) From: "Eli Collins (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1294611250.58640.1342457315180.JavaMail.jiratomcat@issues-vm> In-Reply-To: <144370839.58633.1342457314869.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3670: ------------------------------ Description: 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} was: 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. {shell} 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 {shell} > 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: 2.0.0-alpha > Reporter: Eli Collins > > 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