[
https://issues.apache.org/jira/browse/PHOENIX-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866651#comment-15866651
]
Hudson commented on PHOENIX-3639:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-master #1552 (See
[https://builds.apache.org/job/Phoenix-master/1552/])
PHOENIX-3639 WALEntryFilter to replicate only multi-tenant views from
(jamestaylor: rev d1e80e3b161628af4d58443b87d42fa4af256486)
* (add)
phoenix-core/src/main/java/org/apache/phoenix/replication/SystemCatalogWALEntryFilter.java
* (add)
phoenix-core/src/it/java/org/apache/phoenix/replication/TestSystemCatalogWALEntryFilter.java
> 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)
