[
https://issues.apache.org/jira/browse/HBASE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161299#comment-13161299
]
Jimmy Xiang commented on HBASE-4927:
------------------------------------
SplitParentFirstComparator is used to sort split parents so that parent is
before its daughters.
Suppose parent P split into F1 and F2, and F1 is split into D1 and D2, F2 is
split into E1 and E2.
Now we have split parents: P, F1 and F2. The expected order should be P, F1,
and F2 so that
CatalogJanior can clean up P before F1 (HBASE-4238). If The endkey of P is
empty, due to this bug,
the order will be F1, P and F2. So F1 will be removed before P. That's not
what we want, right?
> CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the
> last region when the endkey is empty
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4927
> URL: https://issues.apache.org/jira/browse/HBASE-4927
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.92.0, 0.94.0
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
>
> When reviewing HBASE-4238 backporting, Jon found this issue.
> What happens if the split points are (empty end key is the last key, empty
> start key is the first key)
> Parent [A,)
> L daughter [A,B),
> R daughter [B,)
> When sorted, we gets to end key comparision which results in this incorrector
> order:
> [A,B), [A,), [B,)
> we wanted:
> [A,), [A,B), [B,)
--
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
