[
https://issues.apache.org/jira/browse/CASSANDRA-17949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17949:
--------------------------------------------
Change Category: Quality Assurance
Complexity: Normal
Component/s: CI
Status: Open (was: Triage Needed)
> Update CCM post CASSANDRA-17379
> -------------------------------
>
> Key: CASSANDRA-17949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17949
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Priority: Normal
>
> We updated in CASSANDRA-15234 CCM to enable it to handle overloading of
> parameters the way that SnakeYAML works. As we have matching and backward
> compatibility between old and new keys in 4.1 (look into this write up for
> more information
> [https://cassandra.apache.org/doc/4.1/cassandra/configuration/configuration.html).]
> This also allows us not to update for 4.1 the Python DTests but exercise the
> backward compatibility we have in C* in our tests.
> Now CASSANDRA-17379 added a few flags to opt in or out for overloading of
> parameters.
> The default points to -Dcassandra.allow_new_old_config_keys=false but this
> does not affect our tests as CCM handles the overloading in the yaml.
> But this is confusing for users and might lead to issues.
> We need to bring on par one way or another ccm with the new flags introduced
> in CASSANDRA-17379
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
