You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/05/19 18:11:39 UTC

[jira] [Commented] (HBASE-9507) Promote methods of WALActionsListener to WALObserver

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

stack commented on HBASE-9507:
------------------------------

[~ndimiduk] This is a good idea.  Lets make sure we don't drop it (it is kinda crazy that per edit we call two different sets of 'listeners' -- CPs and WAL.

> 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
>             Fix For: 0.99.0
>
>
> 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.2#6252)