[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155957#comment-16155957
]
Ajay Jadhav commented on HBASE-18444:
-------------------------------------
[~stack] The reason for keeping those methods public was because the
TestTableName.java is in hbase-server module (and TableName.java in
hbase-common) where I'm using
these methods for unit testing.
I'm not sure why the TestTableName.java should be in hbase-server module as it
is entirely testing the TableName class. Should I move this to hbase-common?
For HBaseConfiguration.create(): Yes, since the META_TABLE_NAME is static, it
will be initialized only during startup once.
> Add support for specifying custom meta table suffix
> ---------------------------------------------------
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0, 1.3.1
> Reporter: Ajay Jadhav
> Assignee: Ajay Jadhav
> Labels: patch
> Attachments: HBASE-18444.branch-1.001.patch,
> HBASE-18444.master.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
