[
https://issues.apache.org/jira/browse/HDFS-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415844#comment-13415844
]
Tsz Wo (Nicholas), SZE commented on HDFS-3670:
----------------------------------------------
> ... Currently you get eg a file not found if webhdfs is not enabled which
> isn't intuitive.
More precisely, it is "resource not found" but not "file not found". The
reason is that when WebHDFS is disabled, the servlets are not added and the web
server returns "resource not found" by default. Note that when WebHDFS is
enabled, "HDFS file not found" is a JSON FileNotFoundException response.
BTW, I think there is no standard HTTP response for "not-enabled".
> 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
