hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5862) Line records longer than 2x split size aren't handled correctly
Date Wed, 28 May 2014 19:57:06 GMT

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

Sandy Ryza commented on MAPREDUCE-5862:
---------------------------------------

Thanks Jason!

> Line records longer than 2x split size aren't handled correctly
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-5862
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5862
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: bc Wong
>            Assignee: bc Wong
>            Priority: Critical
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: 0001-Handle-records-larger-than-2x-split-size.1.patch, 0001-Handle-records-larger-than-2x-split-size.patch,
0001-Handle-records-larger-than-2x-split-size.patch, 0001-MAPREDUCE-5862.-Line-records-longer-than-2x-split-si.patch,
recordSpanningMultipleSplits.txt.bz2
>
>
> Suppose this split (100-200) is in the middle of a record (90-240):
> {noformat}
>    0              100            200             300
>    |---- split ----|---- curr ----|---- split ----|
>                  <------- record ------->
>                  90                     240
> {noformat}
>       
> Currently, the first split would read the entire record, up to offset 240, which is good.
But the 2nd split has a bug in producing a phantom record of (200, 240).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message