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 2012/12/21 01:29:13 UTC

[jira] [Updated] (HBASE-6895) Remove CoprocessorProtocol support and implementations

     [ https://issues.apache.org/jira/browse/HBASE-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-6895:
-------------------------

    Attachment: 6895.txt

First cut (I get a tingling sensation when I remove lots of code from hbase -- this patch brought it on).

Removes CoprocoessorProtocol, its support in protobufs, HTableInterface, HConnection, and on serverside in HRegionServer, etc.

Removed Exec, ExecResult, BaseEndpointCoprocessor, ExecPRCInvoker,

                
> Remove CoprocessorProtocol support and implementations
> ------------------------------------------------------
>
>                 Key: HBASE-6895
>                 URL: https://issues.apache.org/jira/browse/HBASE-6895
>             Project: HBase
>          Issue Type: Task
>          Components: Coprocessors
>    Affects Versions: 0.96.0
>            Reporter: Gary Helmling
>            Priority: Blocker
>             Fix For: 0.96.0
>
>         Attachments: 6895.txt
>
>
> The CoprocessorProtocol mechanism for registering and calling coprocessor endpoints has been supplanted by protocol buffer based service registrations in HBASE-5448.  This means the Writable-based CoprocessorProtocol mechanism will need to be removed at some point.
> In discussion on the dev list, general consensus was that it is better to remove the CoprocessorProtocol mechanism completely in 0.96, where other backwards-incompatible changes are being made, and before it is adopted by more clients:
> http://mail-archives.apache.org/mod_mbox/hbase-dev/201209.mbox/%3CCADfYSXTvqEu3SifyWdZCi9kKPw1Hf9EoaKVGFOCbwRpSkdaCng%40mail.gmail.com%3E
> This is an umbrella issue to track what changes are required to completely remove the CoprocessorProtocol support.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira