Wellington Chevreuil created HBASE-25955:
--------------------------------------------
Summary: Setting NAMESPACES when adding a replication peer doesn't
have any effect
Key: HBASE-25955
URL: https://issues.apache.org/jira/browse/HBASE-25955
Project: HBase
Issue Type: Bug
Components: Replication
Reporter: Wellington Chevreuil
Assignee: Wellington Chevreuil
A common ask from our customers is for an easy way to enable replication for
all tables within a namespace, but we had noticed that setting *NAMESPACES*
option when adding a peer has no effect on enabling replication for the defined
namespaces tables, it still replicates only entries where the *CF
REPLICATION_SCOPE* is set to '1'.
The problem is due to the chaining of *ScopeWALEntryFilter* and
*NamespaceTableCfWALEntryFilter* together. This is currently done on
*BaseReplicationEndpoint* class, but these two filters are not compatible, as
*ScopeWALEntryFilter.filterCells* logic filters out cells from CFs where
REPLICATION_SCOPE property is set to 0, before
*NamespaceTableCfWALEntryFilter.filterCells* can have a chance to apply it's
own logic, based on namespace definition.
This PR changes the logic described above, making *ScopeWALEntryFilter* and
*NamespaceTableCfWALEntryFilter* mutual exclusive, allowing for entries from
all tables within the defined namespaces to be replicated without needing to
have *REPLICATION_SCOPE* set to true.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
