[jira] [Commented] (HBASE-26351) Implement a table-based region grouping strategy for RegionGroupingProvider
[ https://issues.apache.org/jira/browse/HBASE-26351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427783#comment-17427783 ] fengxianjing commented on HBASE-26351: -- [~zhangduo] I have created a github PR, please review it. Thanks. > Implement a table-based region grouping strategy for RegionGroupingProvider > --- > > Key: HBASE-26351 > URL: https://issues.apache.org/jira/browse/HBASE-26351 > Project: HBase > Issue Type: New Feature >Reporter: fengxianjing >Priority: Major > > In our company, we create only one namespace for each RegionServer group, but > we have about 1000 region per regionserver. Neither _identity_ nor _bounded > are good choices, So we need to a_ WAL grouping strategy based on table name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-26351) Implement a table-based region grouping strategy for RegionGroupingProvider
[ https://issues.apache.org/jira/browse/HBASE-26351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427452#comment-17427452 ] Duo Zhang commented on HBASE-26351: --- [~fengxianjing] HBase now uses github PR for reviewing patch, so please create a github PR for your patch? And please make the patch against master branch, every patch should be landed on master first, unless it is only a bug for a specific branch. Thanks. > Implement a table-based region grouping strategy for RegionGroupingProvider > --- > > Key: HBASE-26351 > URL: https://issues.apache.org/jira/browse/HBASE-26351 > Project: HBase > Issue Type: New Feature >Reporter: fengxianjing >Priority: Major > > In our company, we create only one namespace for each RegionServer group, but > we have about 1000 region per regionserver. Neither _identity_ nor _bounded > are good choices, So we need to a_ WAL grouping strategy based on table name -- This message was sent by Atlassian Jira (v8.3.4#803005)
