hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (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 19:48:31 GMT

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

stack commented on HBASE-9853:
------------------------------

Suggestion:

triggers /get/put /endpoints == coproc, (augmenting stuff) (mixins)
internals flush/compact/wal/storage engines (?) == plugin (replacing stuff / losing delegation
model)


> 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
(v6.1#6144)

Mime
View raw message