You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2013/07/19 19:12:49 UTC
[jira] [Commented] (HDFS-3794) WebHDFS Open used with Offset
returns the original (and incorrect) Content Length in the HTTP Header.
[ https://issues.apache.org/jira/browse/HDFS-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713855#comment-13713855 ]
Jing Zhao commented on HDFS-3794:
---------------------------------
+1 for the branch-1 patch.
> 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
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Fix For: 0.23.3, 2.0.2-alpha
>
> Attachments: HDFS-3794_branch-1.patch, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira