[ 
https://issues.apache.org/jira/browse/HBASE-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sakthi updated HBASE-23826:
---------------------------
    Description: 
HBase Master can do multi-region merge from: 2.0.6,2.1.6,2.2.1,2.3.0,3.0.0

HBASE-22827 aims at exposing the feature via shell from: 2.3.0 & 3.0.0

Let's use this Jira to track, exposing the access to the multi-region merge 
feature from hbck2 for the versions where shell feature isn't available but the 
master supports the multi merge feature & hbck service supports mergeRegions 
api: i.e. 2.1.9+, 2.2.4+ and of course 2.3.0+,3.0.0+ where both shell/hbck2 
would be able to do the task for us.

  was:
HBase Master can do multi-region merge from: 2.0.6,2.1.6,2.2.1,2.3.0,3.0.0

HBASE-22827 aims at exposing the feature via shell from: 2.3.0 & 3.0.0

Let's use this Jira to track, exposing the access to the multi-region merge 
feature from hbck2 for the versions where shell feature isn't available but the 
master supports the feature: i.e. 2.0.6+,2.1.6+, 2.2.1+


> [HBCK2] Expose Multi-Region merge feature via hbck2
> ---------------------------------------------------
>
>                 Key: HBASE-23826
>                 URL: https://issues.apache.org/jira/browse/HBASE-23826
>             Project: HBase
>          Issue Type: Task
>          Components: hbase-operator-tools
>            Reporter: Sakthi
>            Assignee: Sakthi
>            Priority: Major
>             Fix For: hbase-operator-tools-1.1.0
>
>
> HBase Master can do multi-region merge from: 2.0.6,2.1.6,2.2.1,2.3.0,3.0.0
> HBASE-22827 aims at exposing the feature via shell from: 2.3.0 & 3.0.0
> Let's use this Jira to track, exposing the access to the multi-region merge 
> feature from hbck2 for the versions where shell feature isn't available but 
> the master supports the multi merge feature & hbck service supports 
> mergeRegions api: i.e. 2.1.9+, 2.2.4+ and of course 2.3.0+,3.0.0+ where both 
> shell/hbck2 would be able to do the task for us.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to