[ https://issues.apache.org/jira/browse/CASSANDRA-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624096#comment-14624096 ]
Stefania edited comment on CASSANDRA-9448 at 7/13/15 2:42 AM: -------------------------------------------------------------- Thanks for this, your pull request looks good. I merged it and I also rebased. The dtest [pull request|https://github.com/riptano/cassandra-dtest/pull/336] should be merged as soon as possible after committing this ticket, however the review is still pending. CI results: http://cassci.datastax.com/job/stef1927-9448-testall/lastCompletedBuild/testReport/ http://cassci.datastax.com/job/stef1927-9448-dtest/lastCompletedBuild/testReport/ was (Author: stefania): Thanks for this, your pull request looks good. I merged it and I also rebased. The dtest [pull request|https://github.com/riptano/cassandra-dtest/pull/336] should be merged as soon as possible after committing this ticket, however the review is still pending. > Metrics should use up to date nomenclature > ------------------------------------------ > > Key: CASSANDRA-9448 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9448 > Project: Cassandra > Issue Type: Improvement > Components: Tools > Reporter: Sam Tunnicliffe > Assignee: Stefania > Labels: docs-impacting, jmx > Fix For: 3.0 beta 1 > > > There are a number of exposed metrics that currently are named using the old > nomenclature of columnfamily and rows (meaning partitions). > It would be good to audit all metrics and update any names to match what they > actually represent; we should probably do that in a single sweep to avoid a > confusing mixture of old and new terminology. > As we'd need to do this in a major release, I've initially set the fixver for > 3.0 beta1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)