[CASSANDRA-17785] Switch to using @Nullable for all Config class properties which can be nullable

• Type: Improvement
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Local/Config
• Change Category: Operability
• Complexity: Normal
• Platform: All
• Assignee: Unassigned
• Reporter: Ekaterina Dimitrova
• Created: 29/Jul/22 00:11
• Updated: 07/Mar/23 10:53

Description

Currently we allow here 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. 

Issue Links

• is a child of: CASSANDRA-17737 Validate that JMX updates in Config class any properties that were moved to the new config classes and not local copies