[
https://issues.apache.org/jira/browse/PHOENIX-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918423#comment-16918423
]
István Tóth commented on PHOENIX-5457:
--------------------------------------
Yes we could.
However
# Phoenix doesn't even compile with the affected HBASE versions, as there is
no apache hbase-2.2 branch yet.
# The fix has already already been approved (soon to be merged) in HBase. It's
extremely likely to be in 2.2.1, and 2.2.0 is not affected, so it won't affect
any released version.
So think we should keep relying on HBASE returning a sane list to us.
BTW the HBASE ticket is HBASE-22941.
> MetaTableAccessor.getMergeRegions() returns parent regions in random order
> --------------------------------------------------------------------------
>
> Key: PHOENIX-5457
> URL: https://issues.apache.org/jira/browse/PHOENIX-5457
> Project: Phoenix
> Issue Type: Bug
> Reporter: István Tóth
> Priority: Major
>
> The multi-region merge patch has changed the behaviour of the
> MetaTableAccessor.getMergeRegions() method. Earlier, the parent regions were
> returned in the same order that they were passed to mergeRegion().
> The patch has changed this to return the regions in random order. To be more
> precise, the parent regions are stored in random order in Meta.
> I propose storing and returning the parent regions in ascending order.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
