[
https://issues.apache.org/jira/browse/HBASE-28484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901053#comment-17901053
]
Duo Zhang commented on HBASE-28484:
-----------------------------------
What I mean in the previous PR is that, we'd better provide a design doc first.
The difficulty here is the mapping patterns can be very flexible, it is not
likely that we can support them all, so we need to discuss which patterns we
want to support now, which patterns we want to support in the future, and which
patterns we do not consider.
And we also need to discuss where to put the mapping config. Putting it in
ReplicationPeerConfig seems to be stright forward, but we can also put it in
the target cluster.
So let's put up a google doc to discuss all these things first?
Thanks.
> 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)
