[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=13713996#comment-13713996 ] Chris Nauroth commented on HDFS-3794: - I committed this to branch-1 and branch-1-win. Thanks, Nicholas and Jing! 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, 1-win, 1.3.0 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
[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-tabpanelfocusedCommentId=13435931#comment-13435931 ] Hudson commented on HDFS-3794: -- Integrated in Hadoop-Hdfs-0.23-Build #345 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/345/]) svn merge -c 1373193 FIXES: 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 1373399) Result = SUCCESS daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1373399 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/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: 0.23.3, 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
[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-tabpanelfocusedCommentId=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-SVNview=revrev=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
[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-tabpanelfocusedCommentId=13435077#comment-13435077 ] Hudson commented on HDFS-3794: -- Integrated in Hadoop-Mapreduce-trunk #1167 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1167/]) 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-SVNview=revrev=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
[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-tabpanelfocusedCommentId=13434102#comment-13434102 ] Daryn Sharp commented on HDFS-3794: --- Shouldn't it check if length - offset goes negative? Or is that checked elsewhere? 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 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
[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-tabpanelfocusedCommentId=13434193#comment-13434193 ] Ravi Prakash commented on HDFS-3794: I tested the modified patch and it too worked in all three previous cases. 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
[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-tabpanelfocusedCommentId=13434754#comment-13434754 ] Hadoop QA commented on HDFS-3794: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12540891/HDFS-3794.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3007//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3007//console This message is automatically generated. 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
[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-tabpanelfocusedCommentId=13434768#comment-13434768 ] Hudson commented on HDFS-3794: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2604 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2604/]) 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-SVNview=revrev=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
[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-tabpanelfocusedCommentId=13434776#comment-13434776 ] Hudson commented on HDFS-3794: -- Integrated in Hadoop-Common-trunk-Commit #2578 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2578/]) 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 = SUCCESS szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=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
[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-tabpanelfocusedCommentId=13434780#comment-13434780 ] Hudson commented on HDFS-3794: -- Integrated in Hadoop-Hdfs-trunk-Commit #2643 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2643/]) 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 = SUCCESS szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=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
[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-tabpanelfocusedCommentId=13433603#comment-13433603
]
Ravi Prakash commented on HDFS-3794:
{noformat}
e.g. $ curl -L
http://HOST:PORT/webhdfs/v1/somePath/someFile?op=OPENoffset=10;
curl: (18) transfer closed with 10 bytes remaining to read
{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
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
[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-tabpanelfocusedCommentId=13433609#comment-13433609 ] Ravi Prakash commented on HDFS-3794: The same patch applies to branch 0.23, 2, and trunk. 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 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
[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-tabpanelfocusedCommentId=13433710#comment-13433710 ] Tsz Wo (Nicholas), SZE commented on HDFS-3794: -- +1 on the patch. Good catch! 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 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
[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-tabpanelfocusedCommentId=13433839#comment-13433839 ] Hadoop QA commented on HDFS-3794: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12540778/HDFS-3794.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. -1 findbugs. The patch appears to introduce 2 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.ha.TestStandbyCheckpoints +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2997//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/2997//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2997//console This message is automatically generated. 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 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
[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-tabpanelfocusedCommentId=13433875#comment-13433875 ] Tsz Wo (Nicholas), SZE commented on HDFS-3794: -- The findbugs warnings and the failed tests are not related. 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 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
[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-tabpanelfocusedCommentId=13433878#comment-13433878 ] Ravi Prakash commented on HDFS-3794: Thanks a lot Nicholas! Could you please commit the patch? Credit goes to Phil Su for filing the issue! :) 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 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
[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-tabpanelfocusedCommentId=13433881#comment-13433881
]
Tsz Wo (Nicholas), SZE commented on HDFS-3794:
--
Took a second look at the patch. The length HTTP query parameter means The
number of bytes to be processed according to the
[API|hadoop.apache.org/common/docs/r1.0.0/webhdfs.html#length]. So it does not
need to minus offset and the code should be
{code}
final long n = length.getValue() != null? length.getValue()
: in.getVisibleLength() - offset.getValue();
{code}
What do you think?
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
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
