[
https://issues.apache.org/jira/browse/CASSANDRA-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605014#comment-14605014
]
Stefania commented on CASSANDRA-9448:
-------------------------------------
bq. First of all, isn't it better to keep old names as deprecated until we stop
supporting 2.2?
Agreed but how? I could not find a way to add a deprecated tag or alias name to
metrics or JMX beans. Do you know a way to do this or did you simply mean to
keep duplicated metrics and just deprecate in the documentation?
bq. In StorageService, there are some operations referring ColumnFamily. We
should rename these also.
Could you be more specific and list the methods that feed the metrics? I merely
renamed the methods feeding the metrics or their parents for consistency as
otherwise it would be very confusing. I did not mean to change every single
instance of 'ColumnFamily' in the code. That would be best done in a dedicated
ticket after CASSANDRA-8099 has been merged.
> 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)
