[
https://issues.apache.org/jira/browse/HBASE-18107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18107:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 3.0.0)
2.0.0
Release Note:
Incompatible change. Removes merge code no longer supported in branch-2 most of
which had already been made redundant unused even in branch-1.
Removed:
# dispatchMergingRegions from Connection (was superceded long ago in branch-1).
# mergeRegions from RsRpcServices (was not used).
Status: Resolved (was: Patch Available)
I pushed this to master and branch-2. Excellent cleanup [~easyliangjob]. Great
job.
> [AMv2] Remove 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: 3.0.0
> Reporter: stack
> Assignee: Yi Liang
> Fix For: 2.0.0
>
> Attachments: draft.patch, hbase-18107-master.v1.patch,
> HBASE-18107-master-v2.patch
>
>
> 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.4.14#64029)
