Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 20 Jul 2012 06:43:35 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1641774390.80883.1342766615730.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1987133318.59121.1342461274950.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HDFS-3671) ByteRangeInputStream shouldn't require
 the content length header be present
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HDFS-3671:
-----------------------------------------

    Attachment: h3667_20120718.patch

h3667_20120718.patch: updated the test with trunk.

Tested read/write a 3GB file using WebHDFS with trunk and branch-1.  It worked fine and the content-length check is unnecessary.
                
> ByteRangeInputStream shouldn't require the content length header be present
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-3671
>                 URL: https://issues.apache.org/jira/browse/HDFS-3671
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Priority: Blocker
>         Attachments: h3667_20120718.patch, h3671_20120717.patch
>
>
> Per HDFS-3318 the content length header check breaks distcp compatibility with previous releases (0.20.2 and earlier, and 0.21). Like branch-1 this check should be lenient.

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