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

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Won't Fix
• Fix Version/s: 2.0.0-alpha-4, 2.0.0
• Component/s: master

Release Note

TODO:

Reason for large amount of code movement explained here: http://apache-hbase.679495.n3.nabble.com/Looking-for-input-on-an-alpha-4-thorny-item-td4090953.html

• Assignee: Unassigned
• Reporter: ryan rawson
• Created: 15/Oct/14 00:27
• Updated: 17/Jun/22 05:20
• Resolved: 18/Oct/17 04:55

Description

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.

Issue Links

• relates to: HBASE-18298 RegionServerServices Interface cleanup for CP expose
• relates to: HBASE-11125 Introduce a higher level interface for registering interest in coprocessor upcalls
• links to: Review Board (master)