[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597333#comment-17597333
]
Ekaterina Dimitrova edited comment on CASSANDRA-17668 at 8/29/22 6:09 PM:
--------------------------------------------------------------------------
I am pretty sure we said we shouldn’t break users in long ago released versions
for those exceptions. Also, whoever doesn’t want to migrate will keep on using
the old ones. But also people will be using tools that were broken before.
There is choice.
Yes, it is not documented in the API but if it breaks someone’s tools in a
patch release and we know it It is not nice to break them if it was there for
years.
Another suggestion is to keep the deprecation in old branches and only fix in
4.1/trunk? WDYT? That I would accept after being well documented
was (Author: e.dimitrova):
I am pretty sure we said we shouldn’t break users in long ago released versions
for those exceptions.
Yes, it is not documented in the API but if it breaks someone’s tools in a
patch release and we know it It is not nice to break them if it was there for
years.
Another suggestion is to keep the deprecation in old branches and only fix in
4.1/trunk? WDYT? That I would accept after being well documented
> Fix leak of non-standard Java types in our Exceptions as clients using JMX
> are unable to handle them
> ----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
> Reporter: Ekaterina Dimitrova
> Assignee: Leonard Ma
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major
> versions, not 4.1 regressions.
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and
> _setRepairSessionSpaceInMegabytes(since 4.0)_
> in the DatabaseDescriptor.
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf
> (both since 4.0)_
> are used in both setters and on startup. They shouldn't throw
> ConfigurationException in the setters.
> There might be more but those are at least a few obvious I found in the
> DatabaseDescriptor.
> CC [~dcapwell]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
