You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hernan Gelaf-Romer (Jira)" <ji...@apache.org> on 2024/04/10 12:41:00 UTC
[jira] [Updated] (HBASE-28484) Allow replication to different target table
[ https://issues.apache.org/jira/browse/HBASE-28484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hernan Gelaf-Romer updated HBASE-28484:
---------------------------------------
Summary: Allow replication to different target table (was: Allow replication to different table)
> 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)