hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5862) Line records longer than 2x split size aren't handled correctly
Date Thu, 01 May 2014 14:00:54 GMT

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

Hadoop QA commented on MAPREDUCE-5862:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core:


    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4572//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4572//console

This message is automatically generated.

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

View raw message