[
https://issues.apache.org/jira/browse/CASSANDRA-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593213#comment-14593213
]
Stefania commented on CASSANDRA-9448:
-------------------------------------
So far here is what I found:
- Groups:
-- "ColumnFamily" -> "Table"
- Types
-- "ColumnFamily" -> "Table"
-- "IndexColumnFamily" -> "IndexTable"
- Metrics:
-- "EstimatedRowSizeHistogram" -> "EstimatedPartitionSizeHistogram"
-- "EstimatedRowCount" -> "EstimatedPartitionCount"
-- "MinRowSize" -> "MinPartitionSize"
-- "MaxRowSize" -> "MaxPartitionSize"
-- "MeanRowSize" -> "MeanPartitionSize"
-- "RowCacheHit" -> "PartitionCacheHit"
-- "RowCacheHitOutOfRange" -> "PartitionCacheHitOutOfRange"
-- "RowCacheMiss" -> "PartitionCacheMiss"
I also renamed the related classes and methods.
> 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
> 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)
