[ 
https://issues.apache.org/jira/browse/PHOENIX-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas D'Silva updated PHOENIX-3939:
------------------------------------
    Fix Version/s:     (was: 4.15.0)

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Reply via email to