hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3794) WebHDFS Open used with Offset returns the original (and incorrect) Content Length in the HTTP Header.
Date Wed, 15 Aug 2012 13:01:39 GMT

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

Hudson commented on HDFS-3794:
------------------------------

Integrated in Hadoop-Hdfs-trunk #1135 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1135/])
    HDFS-3794. WebHDFS OPEN returns the incorrect Content-Length in the HTTP header when offset
is specified and length is omitted.  Contributed by Ravi Prakash (Revision 1373193)

     Result = FAILURE
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1373193
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/web/resources/DatanodeWebHdfsMethods.java

                
> WebHDFS Open used with Offset returns the original (and incorrect) Content Length in
the HTTP Header.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3794
>                 URL: https://issues.apache.org/jira/browse/HDFS-3794
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 0.23.3, 2.0.0-alpha, 2.1.0-alpha
>            Reporter: Ravi Prakash
>            Assignee: Ravi Prakash
>             Fix For: 2.2.0-alpha
>
>         Attachments: HDFS-3794.patch, HDFS-3794.patch
>
>
> When an offset is specified, the HTTP header Content Length still contains the original
file size. e.g. if the original file is 100 bytes, and the offset specified it 10, then HTTP
Content Length ought to be 90. Currently it is still returned as 100.
> This causes curl to give error 18, and JAVA to throw ConnectionClosedException

--
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