[
https://issues.apache.org/jira/browse/HBASE-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847729#comment-15847729
]
Geoffrey Jacoby commented on HBASE-17543:
-----------------------------------------
Uploaded backport to branch-1
> Create additional ReplicationEndpoint WALEntryFilters by configuration
> ----------------------------------------------------------------------
>
> Key: HBASE-17543
> URL: https://issues.apache.org/jira/browse/HBASE-17543
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-17543-branch-1.patch, HBASE-17543.patch,
> HBASE-17543.v2.patch, HBASE-17543.v3.patch
>
>
> The existing BaseReplicationEndpoint creates a ChainWALEntryFilter containing
> a NamespaceTableCfWALEntryFilter and a ScopeWALEntryFilter. Adding a custom
> WALEntryFilter type to this chain requires creating an entirely new
> ReplicationEndpoint subclass and creating a new peer on the running cluster,
> which can be operationally complex to transition to without data loss in
> cases such as master/master.
> For WALEntryFilters without constructor parameters, it would be
> straightforward to have a Configuration option to list additional
> WALEntryFilter classes the operator wants to include in the filter chain in
> the default endpoint, and then have the endpoint instantiate the filters via
> reflection. Then filter logic could be added (or removed) with only a
> hbase-site.xml change and a rolling restart.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
