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 73854200C17 for ; Fri, 27 Jan 2017 02:42:28 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7214C160B50; Fri, 27 Jan 2017 01:42:28 +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 BA22B160B4C for ; Fri, 27 Jan 2017 02:42:27 +0100 (CET) Received: (qmail 52823 invoked by uid 500); 27 Jan 2017 01:42:26 -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 52812 invoked by uid 99); 27 Jan 2017 01:42:26 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jan 2017 01:42:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 70CDEC18AC for ; Fri, 27 Jan 2017 01:42:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id MH-6RGvlMV1u for ; Fri, 27 Jan 2017 01:42:25 +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 54B215FDC3 for ; Fri, 27 Jan 2017 01:42:25 +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 D09A2E02A9 for ; Fri, 27 Jan 2017 01:42:24 +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 5F2962528A for ; Fri, 27 Jan 2017 01:42:24 +0000 (UTC) Date: Fri, 27 Jan 2017 01:42:24 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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: Fri, 27 Jan 2017 01:42:28 -0000 [ https://issues.apache.org/jira/browse/HBASE-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840816#comment-15840816 ] Ted Yu commented on HBASE-17543: -------------------------------- {code} 42 public static final String REPLICATION_WALENTRYFILTER_CONFIG_KEY = "replication.source.custom.walentryfilters"; {code} Please add "hbase." prefix to the above config parameter. > 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 > > > 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.4#6332)