[
https://issues.apache.org/jira/browse/HDFS-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744873#comment-13744873
]
Hadoop QA commented on HDFS-4594:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598907/HDFS-4594.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.datanode.TestBlockRecovery
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4858//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4858//console
This message is automatically generated.
> WebHDFS open sets Content-Length header to what is specified by length
> parameter rather than how much data is actually returned.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4594
> URL: https://issues.apache.org/jira/browse/HDFS-4594
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 2.0.3-alpha
> Reporter: Arpit Gupta
> Assignee: Chris Nauroth
> Attachments: HDFS-4594.1.patch
>
>
> This was noticed on 2.0.3 alpha
> Lets say we have a file of length x
> We make an webhdfs open call specifying length=x+1
> The response of the call redirected to the datanode sets the content length
> header to value x+1 rather than x.
> Now this causes an error when the client tries to read the data.
> For the test i was using HttpResponse.getEntity().getContent()
> This failed with message "Premature end of Content-Length delimited message
> body (expected: 71898; received: 71897"
> This was not seen in hadoop 1 as we did not set the content length header.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
