hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7042) Master Coprocessor Endpoint
Date Thu, 01 Nov 2012 00:57:12 GMT

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

Francis Liu commented on HBASE-7042:

Can we use the same Exec and ExecResponse classes for both master and RS endpoint invocations?
(I.e. get rid of MasterExec and MasterExecResult?)
It's not possible since the region classes contains relations to regions/row/etc.

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?
Do we really need a table specific MasterEndpoint? For Region's it was really useful since
it'd enable you to do distributed computation across regions apart from being able to extend
Region/RegionServer functionality. In the master's case, most use cases would be to extend
the master's functionality?
> 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