Chia-Ping Tsai commented on HBASE-15511:

+  /**
+   * Use {@link ClusterStatus.Builder} to construct a ClusterStatus instead.
+   * It will be removed in the future, see HBASE-15511 for more information.
+   * TODO: make it private.
+   */
+  @Deprecated
Could you add the comment to indicate the version in which this construction 
should be removed. For instance: "@deprecated since x version and will be 
removed in y version."

> 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, HBASE-15511.master.011.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

Reply via email to