hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9853) Edit the CP API: Make 'plugin's Interfaces for admending behaviors
Date Mon, 28 Oct 2013 21:54:31 GMT

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

Andrew Purtell commented on HBASE-9853:

We can encourage changes to compaction and flush behavior via plugins even while retaining
the Observer views over those activities for a while. If there are users of these interfaces,
this is evidence of the utility of observing (and occasionally changing) what flush and compaction
scanners are iterating over. 

Some Observer APIs are deprecated and will be removed, that will pare back the number of such
APIs in the CP interface. We should not add new ones. 

The WALObserver stands apart from the master and region observer APIs in my opinion and so
is a good candidate for deprecation and removal in favor of a plugin approach.

> Edit the CP API: Make 'plugin's Interfaces for admending behaviors
> ------------------------------------------------------------------
>                 Key: HBASE-9853
>                 URL: https://issues.apache.org/jira/browse/HBASE-9853
>             Project: HBase
>          Issue Type: Umbrella
>          Components: Coprocessors
>            Reporter: stack
> Current CP API has deviated from original intent allowing Observers observe (and on occasion
amend data) and Endpoints for adding custom query handling over hbase data.  CP API has evolved
to include a raft of APIs that allow modifying base behaviors -- how we do compactions, flushes,
etc -- that are not 'coprocessor'-type functions.
> This issue came of devs discussing figuring how to stabilize the CP API.  The thought
is to return its scope to that of the original intent and to add new plugins Interfaces whereever
we want to allow changing base behaviors (WAL writing, etc.).
> This is an umbrellas issue.  The redo would happen as subtasks.

This message was sent by Atlassian JIRA

View raw message