hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4782) NLineInputFormat skips first line of last InputSplit
Date Thu, 08 Nov 2012 21:32:17 GMT

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

Robert Joseph Evans updated MAPREDUCE-4782:

     Target Version/s: 0.23.5
    Affects Version/s: 0.23.0
               Status: Patch Available  (was: Open)
> NLineInputFormat skips first line of last InputSplit
> ----------------------------------------------------
>                 Key: MAPREDUCE-4782
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4782
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.0.0-alpha, 1.0.0, 0.23.0, 0.22.0, trunk
>         Environment: job.setMapperClass(Mapper.class);  // just pass text lines through
to output
> job.setInputFormatClass(NLineInputFormat.class);
> NLineInputFormat.setNumLinesPerSplit(job, 100);
> NLineInputFormat.setInputPaths(job, "/path/to/a_file_with_many_lines.txt");
>            Reporter: Mark Fuhs
>            Priority: Critical
>         Attachments: MAPREDUCE-4782.patch, MR-4782.txt
> NLineInputFormat creates FileSplits that are then used by LineRecordReader to generate
Text values. To deal with an idiosyncrasy of LineRecordReader, the begin and length fields
of the FileSplit are constructed differently for the first FileSplit vs. the rest.
> After looping through all lines of a file, the final FileSplit is created, but the creation
does not respect the difference of how the first vs. the rest of the FileSplits are created.
> This results in the first line of the final InputSplit being skipped. I've created a
patch to NLineInputFormat, and this fixes the problem.

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

View raw message