[
https://issues.apache.org/jira/browse/CASSANDRA-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611721#comment-14611721
]
Stefania commented on CASSANDRA-9448:
-------------------------------------
CASSANDRA-8099 is finally on trunk and I've rebased. I've also took the chance
to then rename the operations in storage proxy, see second commit. You may want
to review the first commit again in case of rebase errors.
I still don't know how to support the deprecated metric names. My idea is just
duplicating them wouldn't work because of the callers, we'd have to wrap them
in setters.
> 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)
