[
https://issues.apache.org/jira/browse/HBASE-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488838#comment-13488838
]
Francis Liu commented on HBASE-7042:
------------------------------------
{quote}
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.
{quote}
Don't we already have a precedent for this with MasterObserver? From a use case
perspective it would seem to me that Master Coprocessors are cluster owner
decisions and are prolly fewer and slower moving than region coprocessors which
are owned by table owners. In the former case updating and restarting the
master should be acceptable?
> 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
