hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12260) MasterServices needs a short-back-and-sides; pare-back exposure of internals and IA.Private classes
Date Thu, 12 Oct 2017 22:48:01 GMT

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

stack commented on HBASE-12260:

.013 fix tests (except one I can't figure that comes of our using mocks over HMaster than
over RegionServer around the crptic wal splitting engine). Lets see what hadoopqa says. Will
look at rb in meantime. I think patch ready to go. Can address the TODOs above in follow-ons.

> MasterServices needs a short-back-and-sides; pare-back exposure of internals and IA.Private
> ---------------------------------------------------------------------------------------------------
>                 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,
HBASE-12260.master.012.patch, HBASE-12260.master.013.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

View raw message