[jira] [Commented] (HBASE-25002) Create simple pattern matching query for retrieving metrics matching the pattern
[ https://issues.apache.org/jira/browse/HBASE-25002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196252#comment-17196252 ] Hudson commented on HBASE-25002: Results for branch branch-2 [build #41 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/41/]: (x) *{color:red}-1 overall{color}* details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/41/General_20Nightly_20Build_20Report/] (/) {color:green}+1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/41/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/41/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/41/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (x) {color:red}-1 client integration test{color} --Failed when running client tests on top of Hadoop 2. [see log for details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/41//artifact/output-integration/hadoop-2.log]. (note that this means we didn't run on Hadoop 3) > Create simple pattern matching query for retrieving metrics matching the > pattern > > > Key: HBASE-25002 > URL: https://issues.apache.org/jira/browse/HBASE-25002 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.2.5 >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > Currently we allow querying a metric with a specific metric name. But > generally say under the MBean sub=Tables under a server we might have 'n' > number of tables and we might be interested in a specific metric across all > tables. > So in such cases giving a simple pattern based query will help so that we can > retrieve all metrics that follow that pattern. > The other side effect is that we can also reduce the size of the json we pull > from the server to the querying client. Which are generally smaller scripts > which might not be able to process the big sized response JSON. > Thanks [~anoopsamjohn] for the suggestion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25002) Create simple pattern matching query for retrieving metrics matching the pattern
[ https://issues.apache.org/jira/browse/HBASE-25002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195786#comment-17195786 ] Hudson commented on HBASE-25002: Results for branch master [build #47 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/47/]: (x) *{color:red}-1 overall{color}* details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/47/General_20Nightly_20Build_20Report/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/47/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (x) {color:red}-1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/47/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (x) {color:red}-1 client integration test{color} --Failed when running client tests on top of Hadoop 2. [see log for details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/47//artifact/output-integration/hadoop-2.log]. (note that this means we didn't run on Hadoop 3) > Create simple pattern matching query for retrieving metrics matching the > pattern > > > Key: HBASE-25002 > URL: https://issues.apache.org/jira/browse/HBASE-25002 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.2.5 >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > Currently we allow querying a metric with a specific metric name. But > generally say under the MBean sub=Tables under a server we might have 'n' > number of tables and we might be interested in a specific metric across all > tables. > So in such cases giving a simple pattern based query will help so that we can > retrieve all metrics that follow that pattern. > The other side effect is that we can also reduce the size of the json we pull > from the server to the querying client. Which are generally smaller scripts > which might not be able to process the big sized response JSON. > Thanks [~anoopsamjohn] for the suggestion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25002) Create simple pattern matching query for retrieving metrics matching the pattern
[ https://issues.apache.org/jira/browse/HBASE-25002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195484#comment-17195484 ] ramkrishna.s.vasudevan commented on HBASE-25002: Pushed to master and branch-2. Since it is an improvment not pushing to branch-2.2 and branch-2.3. > Create simple pattern matching query for retrieving metrics matching the > pattern > > > Key: HBASE-25002 > URL: https://issues.apache.org/jira/browse/HBASE-25002 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.2.5 >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > Currently we allow querying a metric with a specific metric name. But > generally say under the MBean sub=Tables under a server we might have 'n' > number of tables and we might be interested in a specific metric across all > tables. > So in such cases giving a simple pattern based query will help so that we can > retrieve all metrics that follow that pattern. > The other side effect is that we can also reduce the size of the json we pull > from the server to the querying client. Which are generally smaller scripts > which might not be able to process the big sized response JSON. > Thanks [~anoopsamjohn] for the suggestion. -- This message was sent by Atlassian Jira (v8.3.4#803005)