hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3671) ByteRangeInputStream shouldn't require the content length header be present
Date Mon, 20 Aug 2012 17:49:38 GMT

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

Eli Collins commented on HDFS-3671:
-----------------------------------

Yes, you can't distcp from 20.x to v2 because in ByteRangeInputStream we still fail if the
content length header is not present but 20.x releases don't set it, eg distcp using hftp
from 0.20.2 to 2.0.0-alpha1 fails.
                
> 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: h3671_20120717.patch, h3671_20120719.patch, h3671_20120812.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

        

Mime
View raw message