[
https://issues.apache.org/jira/browse/HBASE-18873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203710#comment-16203710
]
Josh Elser commented on HBASE-18873:
------------------------------------
bq. Approach wise it is ok though that naming of new class is bit odd.
Suggestions instead? :)
bq. 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?
Let me double check, we might have some API already to convert most of the
internal protobufs back to some sort of POJOs. We could expose them on the
visible GlobalQuotaSettings with a caveat that the methods are expensive and
users shouldn't call them repeatedly.
> 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)
