hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2602) Allow setting of end-of-record delimiter for TextInputFormat (for the old API)
Date Sun, 26 Jun 2011 17:41:47 GMT

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

Harsh J commented on MAPREDUCE-2602:

The changes include constructor changes to LineReader class. Is that OK to go in without an
Incompat mark? Its an internal class, but its been public so far.

Rest of the changes appear all good :)

> Allow setting of end-of-record delimiter for TextInputFormat (for the old API)
> ------------------------------------------------------------------------------
>                 Key: MAPREDUCE-2602
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2602
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Ahmed Radwan
>            Assignee: Ahmed Radwan
>         Attachments: MAPREDUCE-2602.patch
> Since there are users who are still using the old MR API, it will be useful to modify
the org.apache.hadoop.mapred.LineRecordReader and org.apache.hadoop.mapred.TextInputFormat
to be able to use custom (user-specified) end-of-record delimiters. This will make use of
the LineReader improvement introduced in HADOOP-7096 that enables the LineReader to break
lines at user-specified delimiters. 
> Note: MAPREDUCE-2254 already added this improvement to the new API (but not the old API).

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message