[
https://issues.apache.org/jira/browse/CASSANDRA-17574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931911#comment-17931911
]
Nikolay Izhikov commented on CASSANDRA-17574:
---------------------------------------------
Hello [~e.dimitrova], [~brandon.williams]
I want to fix this issue.
As far as I can see `Config` class contains many public fields.
So, there are no way to intercept change of config to check value validity.
Can we move all requried config fields to private scope to control changes?
> Throw exception on wrong config boundaries
> ------------------------------------------
>
> Key: CASSANDRA-17574
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17574
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 5.x
>
>
> While working on CASSANDRA-15234 we noticed usage of negative values where
> they are not supposed to be used. We fixed that for the parameters in scope -
> type duration, data storage and data rate but as [~brandon.williams] pointed
> - there are other examples from the rest of the config that is good to be
> fixed too.
> This ticket should handle:
> - check the rest of the parameters, where negatives shouldn't be allowed they
> shouldn't be allowed
> - ensure that whatever validations we apply to parameters during startup
> (check the DatabaseDescriptor) are applied also in the respective setters for
> those parameters.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
