[
https://issues.apache.org/jira/browse/HDFS-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124771#comment-13124771
]
Praveen Kumar K J V S commented on HDFS-2432:
---------------------------------------------
Its better to return HTTP Status code 403 (Forbidden), because setting a
replication factor on a directory is not a bad request per se, just that its
not allowed in HDFS. (probably in future this might be a feature in future
where replication factors can be defined for directories, there are definite
use-cases though)
As per the specification:
400 Bad Request -
The request could not be understood by the server due to malformed syntax. The
client SHOULD NOT repeat the request without modifications.
403 Forbidden -
The server understood the request, but is refusing to fulfill it. ...
> webhdfs setreplication api should return a 400 when called on a directory
> -------------------------------------------------------------------------
>
> Key: HDFS-2432
> URL: https://issues.apache.org/jira/browse/HDFS-2432
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.20.205.0
> Reporter: Arpit Gupta
>
> Currently the set replication api on a directory leads to a 200.
> Request URI
> http://NN:50070/webhdfs/tmp/webhdfs_data/dir_replication_tests?op=SETREPLICATION&replication=5
> Request Method: PUT
> Status Line: HTTP/1.1 200 OK
> Response Content: {"boolean":false}
> Since we can determine that this call did not succeed (boolean=false) we
> should rather just return a 400 (Bad Request)
--
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
