[
https://issues.apache.org/jira/browse/CASSANDRA-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528472#comment-17528472
]
Ekaterina Dimitrova commented on CASSANDRA-17571:
-------------------------------------------------
I spent my evening again thinking about this as really those extensions become
convoluted but I don't see a better way at this point.
Like I can get back validation utility methods in the DD and leave considering
better general handling with next version but this is error-prone.
Creating a new range max annotation to all new properties in Config is not
really easy option as we would need conversions... The best is to do it in the
constructors at this point.
I will sleep on it and finish tomorrow morning. In case someone has something
better in the meantime - I am open to hear it.
> Config upper bound should be handled earlier
> --------------------------------------------
>
> Key: CASSANDRA-17571
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17571
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.1
>
>
> Config upper bound should be handled on startup/config setup and not during
> conversion
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
