[
https://issues.apache.org/jira/browse/CASSANDRA-20932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-20932:
------------------------------------------
Fix Version/s: 5.1
(was: 5.x)
Source Control Link:
https://github.com/apache/cassandra/commit/76d0c25139fb1acfae616e3c750887238378d467
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Do not emit warning on duplicate keys in snakeyaml to preserve behavior
> pre-CASSANDRA-20928
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-20932
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20932
> Project: Apache Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> upgrade of snakeyaml 2.1 to 2.4 under CASSANDRA-20928 started to emit
> warnings into the logs when it detects that respective YAML file contains
> duplicate keys. This is happening while we run tests, as we are concatenating
> various yaml fragments into one yaml we use for tests (cassandra.yaml,
> cdc.yaml and similar). This will emit warnings to logs and tests will fail
> because they expect empty error output.
> The solution is to not emit warnings on duplicate keys.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
