[
https://issues.apache.org/jira/browse/HBASE-18873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203361#comment-16203361
]
Anoop Sam John commented on HBASE-18873:
----------------------------------------
So here hiding the proto obj returning functions by adding a new class
extension. The CP user can still get all the Quota related info what he would
ideally see? I mean if this is a ThrottleSettings they can get the details
like for which user on which table and what is the throttle etc? We should
make sure that they can get all such details or else there is no point in
passing the object in CP hook. Approach wise it is ok though that naming of
new class is bit odd.
> Hide protobufs in GlobalQuotaSettings
> -------------------------------------
>
> Key: HBASE-18873
> URL: https://issues.apache.org/jira/browse/HBASE-18873
> Project: HBase
> Issue Type: Sub-task
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18873.001.branch-2.patch
>
>
> HBASE-18807 cleaned up direct protobuf use in the Coprocessor APIs for
> quota-related functions. However, one new POJO introduced to hide these
> protocol buffers still exposes PBs via some methods.
> We should try to hide those as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
