[
https://issues.apache.org/jira/browse/HADOOP-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jake Farrell updated HADOOP-7096:
---------------------------------
Comment: was deleted
(was: It was what your parks would call you, ad 1 0 adderall 10 mg.
adderall online prescription
http://www.surveyanalytics.com//userimages/sub-2/2007589/3153260/29851518/7787445-29851518-stopadd25.html
Luke has far found ariadne's string, and the able sound fights his processing.)
> Allow setting of end-of-record delimiter for TextInputFormat
> ------------------------------------------------------------
>
> Key: HADOOP-7096
> URL: https://issues.apache.org/jira/browse/HADOOP-7096
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Ahmed Radwan
> Assignee: Ahmed Radwan
> Fix For: 1.2.0, 0.23.0
>
> Attachments: HADOOP-7096.patch, HADOOP-7096_r2.patch,
> HADOOP-7096_r3.patch, hadoop-7096.branch-1.patch, hadoop-7096_r4.patch
>
>
> The patch for https://issues.apache.org/jira/browse/MAPREDUCE-2254 required
> minor changes to the LineReader class to allow extensions (see attached
> 2.patch). Description copied below:
> It will be useful to allow setting the end-of-record delimiter for
> TextInputFormat. The current implementation hardcodes '\n', '\r' or '\r\n' as
> the only possible record delimiters. This is a problem if users have embedded
> newlines in their data fields (which is pretty common). This is also a
> problem for other tools using this TextInputFormat (See for example:
> https://issues.apache.org/jira/browse/PIG-836 and
> https://issues.cloudera.org/browse/SQOOP-136).
> I have wrote a patch to address this issue. This patch allows users to
> specify any custom end-of-record delimiter using a new added configuration
> property. For backward compatibility, if this new configuration property is
> absent, then the same exact previous delimiters are used (i.e., '\n', '\r' or
> '\r\n').
--
This message was sent by Atlassian JIRA
(v6.2#6252)
