You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/05/18 19:27:00 UTC
[jira] [Comment Edited] (CASSANDRA-17638) Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-17638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539024#comment-17539024 ]
Ekaterina Dimitrova edited comment on CASSANDRA-17638 at 5/18/22 7:26 PM:
--------------------------------------------------------------------------
I plan to fix here all new for this release I know about exceptions:
* Methods I noticed in the DatabaseDescriptor which are still not in any release
* The exceptions in the constructors for the new config
I suggest we fix old already released in a separate ticket which will cover all branches and get this out before the release
CC [~dcapwell]
I will post a patch in a bit
was (Author: e.dimitrova):
I plan to fix here all new for this release I know about exceptions:
* Methods I noticed in the DatabaseDescriptor which are still not in any release
* The exceptions in the constructors for the new config
I suggest we fix old already released in a separate ticket which will cover all branches and get this out before the release
> Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions
> ---------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17638
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17638
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> This is follow up ticket on CASSANDRA-17527 and CASSANDRA-17580.
> CASSANDRA-17580 was decided to be a backup non-default option for users who want to be 100% sure there are no leaked Cassandra exceptions. In that sense I will fix here all known ConfigurationExceptions that need to be thrown as IllegalArgumentException for the default behavior as we were always supposed to do that.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org