[
https://issues.apache.org/jira/browse/HADOOP-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440453#comment-13440453
]
Hudson commented on HADOOP-8655:
--------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2691 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2691/])
HADOOP-8655. Fix TextInputFormat for large deliminators. (Gelesh via
bobby) (Revision 1376592)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1376592
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/LineReader.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestLineReader.java
> In TextInputFormat, while specifying textinputformat.record.delimiter the
> character/character sequences in data file similar to starting
> character/starting character sequence in delimiter were found missing in
> certain cases in the Map Output
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8655
> URL: https://issues.apache.org/jira/browse/HADOOP-8655
> Project: Hadoop Common
> Issue Type: Bug
> Components: util
> Affects Versions: 0.20.2
> Environment: Linux- Ubuntu 10.04
> Reporter: Arun A K
> Labels: hadoop, mapreduce, textinputformat,
> textinputformat.record.delimiter
> Fix For: 3.0.0, 2.2.0-alpha
>
> Attachments: HADOOP-8655 (2).patch, HADOOP-8655.patch,
> HADOOP-8655.patch, HADOOP-8655.patch, MAPREDUCE-4519.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Set textinputformat.record.delimiter as "</entity>"
> Suppose the input is a text file with the following content
> <entity><id>1</id><name>User1</name></entity><entity><id>2</id><name>User2</name></entity><entity><id>3</id><name>User3</name></entity><entity><id>4</id><name>User4</name></entity><entity><id>5</id><name>User5</name></entity>
> Mapper was expected to get value as
> Value 1 - <entity><id>1</id><name>User1</name>
> Value 2 - <entity><id>2</id><name>User2</name>
> Value 3 - <entity><id>3</id><name>User3</name>
> Value 4 - <entity><id>4</id><name>User4</name>
> Value 5 - <entity><id>5</id><name>User5</name>
> According to this bug Mapper gets value
> Value 1 - entity><id>1</id><name>User1</name>
> Value 2 - <entity>id>2</id><name>User2</name>
> Value 3 - <entity><id>3id><name>User3</name>
> Value 4 - <entity><id>4</id><name>User4name>
> Value 5 - <entity><id>5</id><name>User5</name>
> The pattern shown above need not occur for value 1,2,3 necessarily. The bug
> occurs at some random positions in the map input.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
