[
https://issues.apache.org/jira/browse/HBASE-28406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-28406:
------------------------------
Fix Version/s: (was: 3.0.0-beta-2)
> Move namespace to RS group can support multiple options to move tables under
> it
> -------------------------------------------------------------------------------
>
> Key: HBASE-28406
> URL: https://issues.apache.org/jira/browse/HBASE-28406
> Project: HBase
> Issue Type: Improvement
> Components: rsgroup
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Priority: Major
> Fix For: 4.0.0-alpha-1
>
>
> As discussed here
> [https://github.com/apache/hbase/pull/5661#issuecomment-1949090826]
> Move namespaces to rsgroup can have multiple options like:
> # *Move All Tables:* This option involves moving all tables within a
> namespace to the new RS group, regardless of the current RS group they belong
> to. This would effectively consolidate all tables of the namespace into the
> new RS group. This is the same as the current implementation so it can be
> default behavior.
> # {*}Move Tables present in current RS group{*}: With this option, only
> tables belonging to the current RS group of the namespace would be moved to
> the new RS group. This provides more granular control, allowing users to
> choose specific tables to move based on their needs. If the namespace does
> not belong to any RS group, the namespace tables in the default RS group
> would be moved to the new RS group.
> # *Move No Tables:* This option involves changing the RS group of the
> namespace without moving any tables. Existing tables would remain in their
> current RS group. This could be useful if there's a desire to separate the
> namespaces by RS group but without immediately moving the tables.
> With this options we can give control to user choose proper option based on
> the requirements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
