[ 
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597336#comment-17597336
 ] 

David Capwell commented on CASSANDRA-17668:
-------------------------------------------

bq. 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

Older branches are for critical bug fixes, so I feel that we should leave them 
be for now (and not mark @Deprecated there), I can be more neutral to adding to 
trunk but not sure I even agree with 4.1....  

If we limit the patch to only trunk, I am +0 to the idea...  not a fan but get 
the point about breaking anyone who used the undocumented behavior...

> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to