I would say keep the old ones and add new ones to be compatible in addition.
Now your catch led me to more thinking and I think throwing
ConfigurationException deserves more attention. I noticed in
DatabaseDescriptor there are setters that are leaking it to JMX since
cassandra-3.0. I am not sure wh
recated and ignored and remove it in a future version (and you could
> update Config.java to log a message about having a deprecated config
> option). It's a much better operator experience: log for a major version,
> then remove in the next.
>
> On Fri, Feb 11, 2022 at 2:41
This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to
fix a bug that gives impression those work. Confirmed with Benedict on the
ticket.
I agree I absolutely had to document it better, a ticket for documentation
was opened but it slipped from my mind with this emergency releas
