[
https://issues.apache.org/jira/browse/HBASE-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172524#comment-14172524
]
Andrew Purtell commented on HBASE-12260:
----------------------------------------
If you want to see real world usage of MasterServices, see the
AccessController.
We do have an issue open for building a higher level coprocessor API on top of
the current one, HBASE-11125 might be a useful vehicle. Not exposing
MasterServices and RegionServerServices there totally makes sense. However
HBASE-11125 specifically does not eliminate what would become the lower level
API for power uses or propose abandoning current users.
> MasterServices - remove from coprocessor API (Discuss)
> ------------------------------------------------------
>
> Key: HBASE-12260
> URL: https://issues.apache.org/jira/browse/HBASE-12260
> Project: HBase
> Issue Type: Bug
> Components: master
> Reporter: ryan rawson
> Priority: Minor
>
> A major issue with MasterServices is the MasterCoprocessorEnvironment exposes
> this class even though MasterServices is tagged with
> @InterfaceAudience.Private
> This means that the entire internals of the HMaster is essentially part of
> the coprocessor API. Many of the classes returned by the MasterServices API
> are highly internal, extremely powerful, and subject to constant change.
> Perhaps a new API to replace MasterServices that is use-case focused, and
> justified based on real world co-processors would suit things better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
