[
https://issues.apache.org/jira/browse/HDFS-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159705#comment-13159705
]
Hadoop QA commented on HDFS-2606:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505560/HDFS-2606.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1614//console
This message is automatically generated.
> webhdfs client filesystem impl must set the content-type header for
> create/append
> ---------------------------------------------------------------------------------
>
> Key: HDFS-2606
> URL: https://issues.apache.org/jira/browse/HDFS-2606
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.24.0, 0.23.1
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 0.24.0, 0.23.1
>
> Attachments: HDFS-2606.patch
>
>
> Currently the content-type header is not being set and for some reason for
> append it is being set to the form encoded content type making jersey
> parameter parsing fail.
> For this and to avoid any kind of proxy transcoding the content-type should
> be set to binary.
> {code}
> conn.setRequestProperty("Content-Type", "application/octet-stream");
> {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
