Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 31 Oct 2012 19:06:11 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <796373740.52406.1351710371929.JavaMail.jiratomcat@arcas>
In-Reply-To: <1742975981.20707.1351063332966.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-7042) Master Coprocessor Endpoint
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-7042:
---------------------------------------

Seems reasonable.

On the current patch:

- Can we use the same Exec and ExecResponse classes for both master and RS endpoint invocations? (I.e. get rid of MasterExec and MasterExecResult?) 

- The patch handles system coprocessors, those registered by Configuration, but what about table coprocessors? Table coprocessors are loaded as dictated by table attributes. Should the master load those when creating or updating table schema and discovers that coprocessor load directives now exist in the schema? We wouldn't need to load a table coprocessor into the master if the table is disabled, but once the table is enabled, then we would?

                
> Master Coprocessor Endpoint
> ---------------------------
>
>                 Key: HBASE-7042
>                 URL: https://issues.apache.org/jira/browse/HBASE-7042
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Francis Liu
>            Assignee: Francis Liu
>             Fix For: 0.96.0
>
>         Attachments: HBASE-7042_94.patch
>
>
> Having support for a master coprocessor endpoint would enable developers to easily extended HMaster functionality/features. As is the case for region server grouping.

--
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