[
https://issues.apache.org/jira/browse/HBASE-15357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265174#comment-15265174
]
Hudson commented on HBASE-15357:
--------------------------------
FAILURE: Integrated in HBase-1.4 #127 (See
[https://builds.apache.org/job/HBase-1.4/127/])
HBASE-15357 TableInputFormatBase getSplitKey does not handle signed (tedyu: rev
57ca428c542b8bdb56e1b14d8e4fea533c12710a)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormatBase.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableInputFormatScan1.java
> TableInputFormatBase getSplitKey does not handle signed bytes correctly
> -----------------------------------------------------------------------
>
> Key: HBASE-15357
> URL: https://issues.apache.org/jira/browse/HBASE-15357
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Reporter: Nathan Schile
> Assignee: Nathan Schile
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
> Attachments: 15357-branch-1.v2.txt, 15357-branch-1.v3.txt,
> 15357.v2.txt, HBASE-15357.patch
>
>
> When auto-balance is enabled in TableInputFormatBase and the table key is a
> binary key, the getSplitKey method does not function correctly for signed
> bytes. The proposed solution it to utilize
> org.apache.hadoop.hbase.util.Bytes#split method to find the split key.
> org.apache.hadoop.hbase.util.Bytes#split is stated to be a expensive
> operation, so if another solution is preferred, that is fine. In addition,
> handling of a split key that is equal to the TableSplit end key is added to
> calculateRebalancedSplits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
