[
https://issues.apache.org/jira/browse/CASSANDRA-17431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525058#comment-17525058
]
Ekaterina Dimitrova commented on CASSANDRA-17431:
-------------------------------------------------
CCM patch
[committed|https://github.com/riptano/ccm/commit/4609ac46beccd3ab86463a345ed59e998d664d04]
and CCM [retagged|https://github.com/riptano/ccm/tags]
trunk patch
[committed|https://github.com/apache/cassandra/commit/dac738d2eba8629d4f482d7cbfd855d2c5b9df47]
second so that the CI acknowledges the CCM changes:
To https://github.com/apache/cassandra.git
03ef67c9d5..dac738d2eb trunk -> trunk
*I had a mistake in the 3 setters({_}setPermissionsUpdateInterval{_},
_setCredentialsUpdateInterval_ and _setRolesUpdateInterval_), was ignoring to
throw the exception on negative values (which we do currently on trunk). I
didn't rerun the CI as this just mimics the current trunk. Please let me know
if you have any concerns.*
> Move the rest of the Config parameters to the new Config framework
> ------------------------------------------------------------------
>
> Key: CASSANDRA-17431
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17431
> Project: Cassandra
> Issue Type: Task
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.x
>
>
> Migrate also all Config parameters that are in Config, but not presented in
> cassandra.yaml to the new config framework. Not presented in the yaml as they
> are considered advanced only for advanced users.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
