[
https://issues.apache.org/jira/browse/HBASE-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906023#comment-13906023
]
Hudson commented on HBASE-10534:
--------------------------------
SUCCESS: Integrated in hbase-0.96 #303 (See
[https://builds.apache.org/job/hbase-0.96/303/])
HBASE-10534 Rowkey in TsvImporterTextMapper initializing with wrong
length(Rajesh) (rajeshbabu: rev 1569840)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/ImportTsv.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsvParser.java
> Rowkey in TsvImporterTextMapper initializing with wrong length
> --------------------------------------------------------------
>
> Key: HBASE-10534
> URL: https://issues.apache.org/jira/browse/HBASE-10534
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.96.0
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Fix For: 0.96.2, 0.98.1, 0.99.0
>
> Attachments: HBASE-10534.patch
>
>
> In TsvImporterTextMapper rowkey initializing with wrong length.
> parser.parseRowKey give pair of start and end positions, so the rowkey length
> initialized with rowkey end position instead of length.
> {code}
> Pair<Integer,Integer> rowKeyOffests =
> parser.parseRowKey(value.getBytes(), value.getLength());
> ImmutableBytesWritable rowKey = new ImmutableBytesWritable(
> value.getBytes(), rowKeyOffests.getFirst(),
> rowKeyOffests.getSecond());
> {code}
> Its better to change TsvParser#parseRowKey to return starting position and
> length of rowkey.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
