[
https://issues.apache.org/jira/browse/HBASE-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003049#comment-14003049
]
Nick Dimiduk commented on HBASE-9507:
-------------------------------------
You folks think we should keep this one opened then? Can we not support the two
different semantics with the same API, just noting the a/sync registration? The
async operation still must be queued and pushing the operation to the queue
happens inline.
Perhaps wanting to support the two semantics with the same API is overly
optimistic.
> 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)
