[
https://issues.apache.org/jira/browse/CASSANDRA-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620147#comment-14620147
]
Stefania commented on CASSANDRA-9448:
-------------------------------------
[~yukim] I may have found a way around it. We cannot avoid duplicating JMX
beans but these are only thin wrappers of metrics. So I implemented an aliasing
mechanism where the same metric is wrapped in different beans registered with
different names. Because we have changed the type from "ColumnFamily" to
"Table", then each single table metric needs an alias, regardless of whether
its name was changed or not. Have a look at the latest commit when you find
some time and let me know what you think.
> 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)
