You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2017/06/14 21:58:00 UTC

[jira] [Created] (PHOENIX-3939) Tenant-based Replication

Geoffrey Jacoby created PHOENIX-3939:
----------------------------------------

             Summary: Tenant-based Replication
                 Key: PHOENIX-3939
                 URL: https://issues.apache.org/jira/browse/PHOENIX-3939
             Project: Phoenix
          Issue Type: New Feature
            Reporter: Geoffrey Jacoby
            Assignee: Geoffrey Jacoby
             Fix For: 4.12.0


Standard HBase replication offers a few ways to control what subset of a cluster's data gets replicated to a replication peer, generally by table and column family. However, there's no way for a multi-tenant cluster to say "these tenants will replicate to this peer, and these other tenants will be replicated to a different peer, and this third group will not be replicated at all." 

Phoenix's first-class multi-tenant and composite key support makes this possible. This feature will create a new optional replication plugin, "TenantReplicationEndpoint", and a new optional Phoenix system table to store tenant/target cluster mappings.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)