[
https://issues.apache.org/jira/browse/PHOENIX-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866512#comment-15866512
]
Geoffrey Jacoby commented on PHOENIX-3639:
------------------------------------------
Replication in 0.98 is significantly different than in 1.x. I can make a
0.98-based patch, though the companion HBase JIRA to this (HBASE-17543) is not
in 0.98 due to the recent EOLing of 0.98. An 0.98-based patch of PHOENIX-3639
would still be potentially useful, but require users of 0.98.x clusters to
write their own custom ReplicationEndpoint implementations to make use of the
new WALEntryFilter introduced here. Users of the upcoming HBase 1.4 and up can
make use of it just by changing some config on their existing replication peers
and doing a rolling restart.
> WALEntryFilter to replicate only multi-tenant views from SYSTEM.CATALOG
> -----------------------------------------------------------------------
>
> 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
> Fix For: 4.10.0
>
> 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)
