[ https://issues.apache.org/jira/browse/HBASE-17716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900266#comment-15900266 ]
Hudson commented on HBASE-17716: -------------------------------- SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #131 (See [https://builds.apache.org/job/HBase-1.3-JDK8/131/]) HBASE-17716 Formalize Scan Metric names (stack: rev d6ca93ce123ac03848d06733201c7d62c24604b2) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/metrics/ScanMetrics.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/metrics/ServerSideScanMetrics.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/TestServerSideScanMetricsFromClientSide.java > Formalize Scan Metric names > --------------------------- > > Key: HBASE-17716 > URL: https://issues.apache.org/jira/browse/HBASE-17716 > Project: HBase > Issue Type: Bug > Components: metrics > Reporter: Karan Mehta > Assignee: Karan Mehta > Priority: Minor > Fix For: 2.0.0, 1.3.1, 1.2.5 > > Attachments: HBASE-17716.patch, HBASE-17716_v2.patch, > HBASE-17716_v2.patch > > > HBase provides various metrics through the API's exposed by ScanMetrics > class. > The JIRA PHOENIX-3248 requires them to be surfaced through the Phoenix > Metrics API. Currently these metrics are referred via hard-coded strings, > which are not formal and can break the Phoenix API. Hence we need to refactor > the code to assign enums for these metrics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)