Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D938B200C0D for ; Tue, 31 Jan 2017 19:59:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D8090160B36; Tue, 31 Jan 2017 18:59:57 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2EF06160B62 for ; Tue, 31 Jan 2017 19:59:57 +0100 (CET) Received: (qmail 20967 invoked by uid 500); 31 Jan 2017 18:59:55 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 20668 invoked by uid 99); 31 Jan 2017 18:59:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2017 18:59:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 71F0D189F70 for ; Tue, 31 Jan 2017 18:59:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id QsMFGeTeHgZ9 for ; Tue, 31 Jan 2017 18:59:54 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 69E3B60DD5 for ; Tue, 31 Jan 2017 18:59:54 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7803DE034F for ; Tue, 31 Jan 2017 18:59:53 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8E6C525299 for ; Tue, 31 Jan 2017 18:59:52 +0000 (UTC) Date: Tue, 31 Jan 2017 18:59:52 +0000 (UTC) From: "Geoffrey Jacoby (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] (HBASE-17543) Create additional ReplicationEndpoint WALEntryFilters by configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 31 Jan 2017 18:59:58 -0000 [ https://issues.apache.org/jira/browse/HBASE-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated HBASE-17543: ------------------------------------ Status: Patch Available (was: Open) > 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 > Attachments: 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)