[
https://issues.apache.org/jira/browse/HDFS-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Prakash updated HDFS-3794:
-------------------------------
Attachment: HDFS-3794.patch
Thanks a lot Nicholas! I'm afraid I don't know enough about the code. I'll
defer to you on this! I'm attaching the modified patch with the change you
suggested.
Thanks Daryn. It discovers an out of range offset and throws an exception
before reaching this method.
{noformat}
$ curl -L
"http://HOST:PORT/webhdfs/v1/somePath/someFile?op=OPEN&offset=457236547";
{"RemoteException":{"exception":"IOException","javaClassName":"java.io.IOException","message":"Offset=457236547
out of the range [0, 457236477); OPEN, path=/somePath/someFile"}}
{noformat}
> 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
> 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
