[
https://issues.apache.org/jira/browse/HBASE-29082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940435#comment-17940435
]
Nick Dimiduk commented on HBASE-29082:
--------------------------------------
bq. Where's the conflict?
My objection is that the source cluster stores data pertaining to the read
replica. The only information I would expect the source cluster to have about
the replica cluster would be a replication peer configuration. The read replica
should have its own filesystem with its own hbase:meta, own hbase:acl, &c.
bq. Did you have a chance to review the design doc?
I have not read the doc yet; I've not read the blog post in many years. I will
take a look.
> 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)
