You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Rajeshbabu Chintaguntla (Jira)" <ji...@apache.org> on 2019/08/29 07:48:00 UTC

[jira] [Commented] (PHOENIX-5457) MetaTableAccessor.getMergeRegions() returns parent regions in random order

    [ https://issues.apache.org/jira/browse/PHOENIX-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918364#comment-16918364 ] 

Rajeshbabu Chintaguntla commented on PHOENIX-5457:
--------------------------------------------------

[~stoty] Instead of depending on the HBase changes, we can sort the regions returned by the API with the region start key comparison.

> 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)