You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "miklosovic (Jira)" <ji...@apache.org> on 2023/06/07 18:35:00 UTC
[jira] [Updated] (CASSANDRA-14667) Upgrade Dropwizard Metrics to 4.x
[ https://issues.apache.org/jira/browse/CASSANDRA-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
miklosovic updated CASSANDRA-14667:
-----------------------------------
Attachment: signature.asc
Option 4) would work too imho.
So this would make metrics functional in tests? If it is just about copying a class and moving it to appropriate package, that seems to me like the least invasive change plus metrics would work too. That is better than metrics not working and putting withoutMetrics everywhere.
What is the cost of that custom class (classes) in the repo from the maintenance perspective? Just copy&forget?
Sent from ProtonMail mobile
\
> Upgrade Dropwizard Metrics to 4.x
> ---------------------------------
>
> Key: CASSANDRA-14667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14667
> Project: Cassandra
> Issue Type: Task
> Components: Observability/Metrics
> Reporter: Stig Rohde Døssing
> Assignee: Maxim Muzafarov
> Priority: Normal
> Fix For: 5.x
>
> Attachments: signature.asc
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Cassandra currently uses Metrics 3.1.5. Version 4.0.0 added some fixes for Java 9 compatibility. It would be good to upgrade the Metrics library as part of the version of Cassandra that adds Java 9 compatibility (https://issues.apache.org/jira/browse/CASSANDRA-9608).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org