You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/06/09 19:55:18 UTC
[jira] [Resolved] (HBASE-18107) [AMv2] Rename
DispatchMergingRegionsRequest & DispatchMergingRegions
[ https://issues.apache.org/jira/browse/HBASE-18107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-18107.
---------------------------
Resolution: Won't Fix
Resolving as won't fix. This is old stuff that came in long time ago. It will be replaced before we release hbase2. See HBASE-18105.
> [AMv2] Rename DispatchMergingRegionsRequest & DispatchMergingRegions
> --------------------------------------------------------------------
>
> Key: HBASE-18107
> URL: https://issues.apache.org/jira/browse/HBASE-18107
> Project: HBase
> Issue Type: Sub-task
> Components: Region Assignment
> Affects Versions: 2.0.0
> Reporter: stack
> Fix For: 2.0.0
>
>
> They don't align with how we have named the Split equivalents; i.e. SplitRegion (so should be MergeRegion...). They probably have these awkward names because the obvious slots are occupied... so this may not be fixable but filing issue anyways.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)