[
https://issues.apache.org/jira/browse/HBASE-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172519#comment-14172519
]
Andrew Purtell commented on HBASE-12260:
----------------------------------------
No, we expose MasterServices and RegionServerServices as a way for coprocessors
to get useful access to server internals. I'd be -1 on the proposed change.
What we probably should do is tag them LimitedPrivate(COPROC)
> 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)
