[jira] [Comment Edited] (HBASE-12260) MasterServices needs a short-back-and-sides; pare-back exposure of internals and IA.Private classes

["stack (JIRA)" <ji...@apache.org>]

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

stack edited comment on HBASE-12260 at 10/9/17 10:37 PM:
---------------------------------------------------------

TODO:

* Schedule and wait on flush/compaction
* Creating system tables (Done via Admin. Testing)
* Review of RSGroups to see what functionality need to add back into MasterServices
* Metrics/by-pass
* Only Master process can make system tables (while at it, only Master can write hbase:meta)


was (Author: stack):
TODO:

* Schedule and wait on flush/compaction
* Creating system tables (Done via Admin. Testing)
* Review of RSGroups to see what functionality need to add back into MasterServices
* Metrics/by-pass

> MasterServices needs a short-back-and-sides; pare-back exposure of internals and IA.Private classes
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-12260
>                 URL: https://issues.apache.org/jira/browse/HBASE-12260
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master
>            Reporter: ryan rawson
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0-alpha-4
>
>         Attachments: HBASE-12260.master.001.patch, HBASE-12260.master.002.patch, HBASE-12260.master.003.patch, HBASE-12260.master.004.patch, HBASE-12260.master.005.patch, HBASE-12260.master.006.patch, HBASE-12260.master.007.patch, HBASE-12260.master.008.patch, HBASE-12260.master.009.patch, HBASE-12260.master.010.patch, HBASE-12260.master.011.patch, HBASE-12260.master.011.patch
>
>
> 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.4.14#64029)