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 Fri, 02 Nov 2012 23:18:12 GMT

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

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

bq. Apart from being a bit clunky I made them separate so that each class can evolve without
master/region usages stepping/confusing on each other. If you think this is ok I'm fine with
reusing the Exec and ExecResult.

Sounds great.

bq. I believe your concern can be addressed by making system coprocessors reloadable. Which
I think we should do for both master and region coprocessors anyway. This we can address in
a separate jira?

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

Mime
View raw message