You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/07/29 00:12:00 UTC
[jira] [Updated] (CASSANDRA-17785) Switch to using @Nullable for all Config class properties which can be nullable
[ https://issues.apache.org/jira/browse/CASSANDRA-17785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ekaterina Dimitrova updated CASSANDRA-17785:
--------------------------------------------
Change Category: Operability
Complexity: Normal
Component/s: Local/Config
Fix Version/s: 4.x
Priority: Low (was: Normal)
Status: Open (was: Triage Needed)
> Switch to using @Nullable for all Config class properties which can be nullable
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-17785
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17785
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Priority: Low
> Fix For: 4.x
>
>
> Currently we allow [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/config/YamlConfigurationLoader.java#L369] null value for those properties that have null default value in Config.
> We added exception for two properties as part of this PR - [https://github.com/apache/cassandra/pull/1758#discussion_r932618899]
> As discuessed in the PR, we would like to explore the opportunity to switch nullable properties to using the @Nullable annotation no matter whether they are or they are not having null value in Config.
> We need to ensure extensive testing for this switch plus documenting it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org