Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- depends upon
-
PHOENIX-5249 Implicit multi-tenancy by naming convention
- Open