[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16121534#comment-16121534 ] Reid Chan edited comment on HBASE-15511 at 8/10/17 12:27 PM: - Rebase master branch, and add more detailed info on the deprecated method. was (Author: reidchan): Rebase master branch, and add more detailed info on the deprecation method. > 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, > HBASE-15511.master.012.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)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[
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 6:07 AM:
---
Thanks for reviews [~chia7712].
Most of the codes are 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 to reset defaults{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)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[
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)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115454#comment-16115454 ] Reid Chan edited comment on HBASE-15511 at 8/5/17 5:06 PM: --- Re-write most of the codes, also updates it on review board, [Reviewboard|https://reviews.apache.org/r/51212/] ping [~chia7712] was (Author: reidchan): Re-write most of the codes, also updates it on review board, [Reviewboard|https://reviews.apache.org/r/51212/] > 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 > > > 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)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115454#comment-16115454 ] Reid Chan edited comment on HBASE-15511 at 8/5/17 5:03 PM: --- Re-write most of the codes, also updates it on review board, [Reviewboard|https://reviews.apache.org/r/51212/] was (Author: reidchan): Re-write most of the codes. > 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 > > > 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)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15441425#comment-15441425 ] Reid Chan edited comment on HBASE-15511 at 8/30/16 4:00 AM: failed tests are not related to 007 patch. review board is updated. [~esteban] [~mbertozzi] [~anoop.hbase] apologize for interruption, would you mind giving a review? https://reviews.apache.org/r/51212/ thanks. was (Author: reidchan): failed tests are not related to 007 patch. review board is updated. [~esteban] [~mbertozzi] [~anoop.hbase] apologize for interruption would you mind giving a review? https://reviews.apache.org/r/51212/ thanks. > 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 > > > 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.3.4#6332)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15441425#comment-15441425 ] Reid Chan edited comment on HBASE-15511 at 8/30/16 3:56 AM: failed tests are not related to 007 patch. review board is updated. [~esteban] [~mbertozzi] [~anoop.hbase] apologize for interruption would you mind giving a review? https://reviews.apache.org/r/51212/ thanks. was (Author: reidchan): failed tests are not related to 007 patch. review board is updated. [~esteban] would you mind giving a review? https://reviews.apache.org/r/51212/ thank you~. > 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 > > > 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.3.4#6332)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15441425#comment-15441425 ] Reid Chan edited comment on HBASE-15511 at 8/27/16 12:37 PM: - failed tests are not related to 007 patch. review board is updated. [~esteban] would you mind giving a review? https://reviews.apache.org/r/51212/ thank you~. was (Author: reidchan): failed tests are not related to 007 patch. review board is updated. [~esteban] would you mind giving a review? thank you~. > 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 > > > 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.3.4#6332)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427612#comment-15427612 ] Reid Chan edited comment on HBASE-15511 at 8/19/16 4:37 AM: findbugs, javac and TestInterfaceAudienceAnnotations seem to be unrelated to patch? needs some time to fix TestClientClusterStatus was (Author: reidchan): findbugs, javac and `TestInterfaceAudienceAnnotations` seem to be unrelated to patch? needs some time to fix `TestClientClusterStatus` > 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 > > > 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.3.4#6332)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427612#comment-15427612 ] Reid Chan edited comment on HBASE-15511 at 8/19/16 4:38 AM: findbugs, javac and TestInterfaceAudienceAnnotations seem to be unrelated to patch? need some time to fix TestClientClusterStatus was (Author: reidchan): findbugs, javac and TestInterfaceAudienceAnnotations seem to be unrelated to patch? needs some time to fix TestClientClusterStatus > 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 > > > 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.3.4#6332)
[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
[ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426834#comment-15426834 ] Reid Chan edited comment on HBASE-15511 at 8/18/16 5:41 PM: A client can retrieve desired information of ClusterStatus by providing a scope named ClusterInfo. If ClusterInfo is not provided, all information will be retrieved as original version. It can be applied to cluster wide, but only after reviewed and with permissions. was (Author: reidchan): A client can retrieve desired information of ClusterStatus by providing a scope named ClusterInfo. If ClusterInfo is not provided, all information will be retrieved as original version. It can be applied to cluster wide, but only after being reviewed and with permissions. > 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 > > > 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.3.4#6332)
