[
https://issues.apache.org/jira/browse/PHOENIX-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866293#comment-15866293
]
James Taylor commented on PHOENIX-3639:
---------------------------------------
+1. Thanks, [~gjacoby] - this looks very clean to me already. I'll get this
committed shortly. If you have a few spare cycles, it would be most appreciated
if you could right up a paragraph or two documenting how best to configure
replication in Phoenix (and the config options that should be set). We get
asked this frequently on the mailing list. Maybe a new Replication page in the
Using menu after Tuning?
> WALEntryFilter to block System.Catalog replication
> --------------------------------------------------
>
> Key: PHOENIX-3639
> URL: https://issues.apache.org/jira/browse/PHOENIX-3639
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.8.0, 4.9.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Labels: replication
> Attachments: PHOENIX-3639.patch, PHOENIX-3639.v2.patch
>
>
> As a stopgap before PHOENIX-3520, we can create an HBase WALEntryFilter to
> filter out non-tenant rows of SYSTEM.CATALOG from replication while allowing
> tenant-owned rows such as tenant views to proceed with replication.
> This would have to be incorporated into a ReplicationEndpoint subclass to be
> useful, though HBASE-17543 would make that much simpler by doing it via
> configuration rather than code (and avoiding the need for a new peer to be
> created).
> If PHOENIX-3520 is on the near-future roadmap, however, that would be the
> better solution to the "replication corrupts SYSTEM.CATALOG" problem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
