Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 11 Nov 2013 21:01:19 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12668123.1378928810165.53605.1384203679807@arcas>
In-Reply-To: <JIRA.12668123.1378928810165@arcas>
References: <JIRA.12668123.1378928810165@arcas>
Subject: [jira] [Commented] (HBASE-9507) Promote methods of
 WALActionsListener to WALObserver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819383#comment-13819383 ] 

Andrew Purtell commented on HBASE-9507:
---------------------------------------

bq. Deprecate in 0.96. Remove in 0.98?

+1

> Promote methods of WALActionsListener to WALObserver
> ----------------------------------------------------
>
>                 Key: HBASE-9507
>                 URL: https://issues.apache.org/jira/browse/HBASE-9507
>             Project: HBase
>          Issue Type: Brainstorming
>          Components: Coprocessors, wal
>            Reporter: Nick Dimiduk
>            Priority: Minor
>
> The interface exposed by WALObserver is quite minimal. To implement anything of significance based on WAL events, WALActionsListener (at a minimum) is required. This is demonstrated by the implementation of the replication feature (not currently possible with coprocessors) and the corresponding interface exploitation that is the [Side-Effect Processor|https://github.com/NGDATA/hbase-indexer/tree/master/hbase-sep]. Consider promoting the interface of WALActionsListener into WALObserver. This goes a long way to being able refactor replication into a coprocessor. This also removes the duplicate code path for listeners because they're already available via coprocessor hook.


--
This message was sent by Atlassian JIRA
(v6.1#6144)