[
https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117863#comment-16117863
]
Reid Chan edited comment on HBASE-15511 at 8/8/17 5:11 AM:
-----------------------------------------------------------
Thanks for reviews [~chia7712].
Most of the codes is modified as suggestions, the getter/setter i reserves for
literal comprehensive, but you remind me of the reusability of the Options, so
i add a method to reset defaults{code} public Options reset() {code}
was (Author: reidchan):
Thanks for reviews [~chia7712].
Most of the codes is modified as suggestions, the getter/setter i reserves for
literal comprehensive, but you remind me of the reusability of the Options, so
i add a method {code} public Options reset() {code}
> ClusterStatus should be able to return responses by scope
> ---------------------------------------------------------
>
> Key: HBASE-15511
> URL: https://issues.apache.org/jira/browse/HBASE-15511
> Project: HBase
> Issue Type: Improvement
> Reporter: Esteban Gutierrez
> Assignee: Reid Chan
> Attachments: HBASE-15511.master.001.patch,
> HBASE-15511.master.002.patch, HBASE-15511.master.003.patch,
> HBASE-15511.master.004.patch, HBASE-15511.master.005.patch,
> HBASE-15511.master.006.patch, HBASE-15511.master.007.patch,
> HBASE-15511.master.008.patch, HBASE-15511.master.009.patch,
> HBASE-15511.master.010.patch
>
>
> The current ClusterStatus response returns too much information about the
> load per region and replication cluster wide. Sometimes that response can be
> quite large (10s or 100s of MBs) and methods like getServerSize() or
> getRegionsCount() don't really need the full response. One possibility is to
> provide a scope (or filter) for the ClusterStatus requests to limit the
> response back to the client.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
