[
https://issues.apache.org/jira/browse/CASSANDRA-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528475#comment-17528475
]
Ekaterina Dimitrova commented on CASSANDRA-17571:
-------------------------------------------------
On the bright side, this is not a regression as we handle the old config input
types in Converters(former ints cannot be set long value) so in my humble
opinion even if we fix the new config upper bound after the freeze on the 1st,
this is not a regression we have here and no API change will be involved. I
don't plan too prolong it but if we want more time to shape the solution a bit
or for final review - I think we have it. CC [~mck] in case he disagrees with
this statement
> 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]
