[
https://issues.apache.org/jira/browse/HBASE-29082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933449#comment-17933449
]
Andor Molnar commented on HBASE-29082:
--------------------------------------
[~ndimiduk] I shared the link to the design doc of feature on the parent.
Why would having a second meta on the same filesytem be a problem?
System namespace would look something like this:
* hbase:meta
* hbase:meta_second
* hbase:meta_third
* hbase:namespace
* hbase:replication
* hbase:acl
Where's the conflict?
> Add custom meta table name suffix
> ---------------------------------
>
> Key: HBASE-29082
> URL: https://issues.apache.org/jira/browse/HBASE-29082
> Project: HBase
> Issue Type: Sub-task
> Components: master, meta
> Reporter: Andor Molnar
> Assignee: Abhishek Kothalikar
> Priority: Major
> Labels: pull-request-available
>
> Add support for custom meta table name and ability to start cluster on the
> same storage location.
> New config setting:
> |*Config*|*Default* |*Explanation*|
> |hbase.meta.table.suffix|“”|Adds a suffix to the meta table name:
> value=’test’ -> ‘hbase:meta_test’|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
