You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/06/04 22:25:00 UTC

[jira] [Commented] (PHOENIX-5315) Cross cluster replication of the base table only should be sufficient

    [ https://issues.apache.org/jira/browse/PHOENIX-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856161#comment-16856161 ] 

Andrew Purtell commented on PHOENIX-5315:
-----------------------------------------

[~kozdemir] [~vincentpoon] [~gjacoby]

> Cross cluster replication of the base table only should be sufficient
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-5315
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5315
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Priority: Major
>
> When replicating Phoenix tables using the HBase cross cluster replication facility, it should be sufficient (and must, for correctness and avoidance of race conditions and inconsistencies) to replicate the base table only. On the sink cluster the replication client's application of mutations from the replication stream to the local base table should trigger all necessary index update operations. To the extent that won't happen now due to implementation details, those details should be reworked. 
> This also has important efficiency benefits: no matter how many indexes are defined for a base table, only the base table updates need be replicated (presuming Phoenix schema is synchronized over all sites by some other external means). 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)