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/05/11 18:44:00 UTC

[jira] [Commented] (CASSANDRA-17571) Config upper bound should be handled earlier

    [ https://issues.apache.org/jira/browse/CASSANDRA-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17535063#comment-17535063 ] 

Ekaterina Dimitrova commented on CASSANDRA-17571:
-------------------------------------------------

For the record, [~adelapena] suggested nested classes as we might need also other types in the future and that refactoring will help us to maintain the types easily. Also, the code shrinks nicely and all upper bound validations will be in the constructors.

I will post the final version for review later today.

> 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.x, 4.1-beta
>
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org