[
https://issues.apache.org/jira/browse/HBASE-28484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901298#comment-17901298
]
Evelyn Boland commented on HBASE-28484:
---------------------------------------
Hi [~zhangduo], you can find my [design document
here|https://docs.google.com/document/d/1h6G55j3B4vKxHliw6Wx9tXezNDhod7dY1EiHkhcKFDI/edit?tab=t.0].
Happy to field any questions or tweak the design to unlock this feature. Thank
you!
> Allow replication to different target table
> -------------------------------------------
>
> Key: HBASE-28484
> URL: https://issues.apache.org/jira/browse/HBASE-28484
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Hernan Gelaf-Romer
> Assignee: Hernan Gelaf-Romer
> Priority: Major
> Labels: pull-request-available
>
> At the moment, HBase replication assumes the source and target table have the
> same name. Our company is looking into a use case that would require
> replicating to an arbitrary target table.
>
> *Potential Solution:*
> It seems that the WALKey stores the table name of it's corresponding edit
> should be applied to.
> We can add a setting to ReplicationPeerConfig that allows users to specify a
> source to target table mapping. This mapping can then be used to overwrite
> the WALKey's table before shipping the edit to the target cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
