Details
Description
Remove Constants.KEY_DTEST_API_CONFIG_CHECK which currently is set to false for in-jvm upgrade tests which means we don't do the regular checks for invalid yaml that Cassandra does on startup for those tests.
We need to be able to acknowledge new config parameters added to newer versions. Those should be ignored in the old Cassandra versions during upgrade tests instead of ignoring the checks for the whole configuration file on all Cassandra versions.
Attachments
Issue Links
- is related to
-
CASSANDRA-17532 Set Constants.KEY_DTEST_API_CONFIG_CHECK=true by default for in-jvm upgrade tests
- Review In Progress