[jira] [Updated] (CASSANDRA-17574) Throw exception on wrong config boundaries
[ https://issues.apache.org/jira/browse/CASSANDRA-17574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17574: Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Component/s: Local/Config Discovered By: User Report Severity: Normal Status: Open (was: Triage Needed) > Throw exception on wrong config boundaries > -- > > Key: CASSANDRA-17574 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17574 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > > 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.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17574) Throw exception on wrong config boundaries
[ https://issues.apache.org/jira/browse/CASSANDRA-17574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17574: Fix Version/s: 4.x > Throw exception on wrong config boundaries > -- > > Key: CASSANDRA-17574 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17574 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.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.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
