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-7042) Master Coprocessor Endpoint
Date Thu, 01 Nov 2012 15:21:14 GMT

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

Andrew Purtell commented on HBASE-7042:

It is possible to reuse Exec and ExecResult. Just ignore / don't set the row fields etc. Having
separate classes for master exec only is not a clean API in my opinion. 

The issue I see with supporting only system coprocessors is it requires deployment by way
of XML config update as the sole option, which requires a process restart. Table CPs can be
deployed to HDFS and then loaded dynamically with a schema update without needing to stop
any process. Not supporting this latter option on the master seems a shortcut and limiting. 
> 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

View raw message