hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2606) webhdfs client filesystem impl must set the content-type header for create/append
Date Wed, 30 Nov 2011 13:17:40 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160026#comment-13160026
] 

Hudson commented on HDFS-2606:
------------------------------

Integrated in Hadoop-Mapreduce-0.23-Build #109 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/109/])
    Merge -r 1208156:1208157 from trunk to branch. FIXES: HDFS-2606

tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208158
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/web/WebHdfsFileSystem.java

                
> 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

        

Mime
View raw message