hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12260) MasterServices - remove from coprocessor API (Discuss)
Date Sat, 09 Sep 2017 07:22:00 GMT

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

Anoop Sam John commented on HBASE-12260:

We are doing all the CP clean up for the 2.0.  Let me make this jira a subtask of that.  
MasterServices some of the methods might be useful for the general CPs.  But we should NOT
expose the internal stuff for the CPs.  (Same the case with even RS side also which is tracked
as another issue).  So ya may be we should make a new interface for CPs and expose only the
needed things there.  AccessController is our internal CP and we may have to do type casting

> 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

View raw message