[
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
