Hudson commented on HBASE-20361:

Results for branch HBASE-20046-branch-2
        [build #7 on 
 (x) *{color:red}-1 overall{color}*
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 

(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 

(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 

(/) {color:green}+1 source release artifact{color}
-- See build output for details.

> Non-successive TableInputSplits may wrongly be merged by auto balancing 
> feature
> -------------------------------------------------------------------------------
>                 Key: HBASE-20361
>                 URL: https://issues.apache.org/jira/browse/HBASE-20361
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>            Reporter: Yuki Tawara
>            Assignee: Yuki Tawara
>            Priority: Major
>             Fix For: 2.1.0
>         Attachments: HBASE-20361.master.001.patch, 
> HBASE-20361.master.002.patch
> TableInputFormatBase class offers users a mechanism to exclude specific 
> splits from returned list of TableInputFormatBase#getSplits through 
> TableInputFormatBase#includeRegionInSplit.
> It also offers users a feature called "auto balancing" to mitigate data skew 
> by splitting large splits and merging small splits.
> If a user overrides TableInputFormatBase#includeRegionInSplit, i th split and 
> i+1 th split may not be successive(i th split's end key is smaller than i+1 
> th split's start key).
> If he or she further enable auto balancing feature, non-successive splits can 
> be merged, which means excluded splits between merged non-successive splits 
> "revive".
> To avoid such cases, we should not merge non-successive splits.

This message was sent by Atlassian JIRA

Reply via email to