MartijnVisser opened a new pull request, #47: URL: https://github.com/apache/flink-connector-cassandra/pull/47
## Purpose of the change Support Flink 1.20, see [FLINK-41112](https://issues.apache.org/jira/browse/FLINK-41112). This supersedes #29, thanks @HuangZhenQiu for the start. CI only tests 1.20, because 3.3 targets the 1.20 LTS line only and the 1.20 `SourceTestSuiteBase` doesn't compile against 1.19. ## Brief change log - Build against Flink 1.20.0 and test against 1.20.5 in CI; the weekly run only tests 1.20-SNAPSHOT - Use `org.apache.flink.core.execution.CheckpointingMode`, which `SourceTestSuiteBase` takes since 1.20 - Manage log4j at 2.24.3 for dependency convergence, since Flink 1.20.2 moved to that version. This replaces #41 - Drop the `Preconditions` entries from the ArchUnit store: [FLINK-35454](https://issues.apache.org/jira/browse/FLINK-35454) allows connectors to depend on `org.apache.flink.util` in 1.20, so these are no longer violations ## Verifying this change Ran the CI build locally (`mvn clean deploy` with `-Pcheck-convergence`, plus the license check) against Flink 1.20.0 and 1.20.5 on JDK 11 and 17. All four pass with 112 unit tests and 39 ITs, and the ArchUnit store doesn't change on either version. The ITs ran with a local workaround for the macOS issue below. The source ITs fail on macOS with or without this change, because the driver can't reach the second Cassandra container. Linux CI isn't affected, and the fix is separate from this change. ## Impact and documentation Flink 1.20 is now the lowest supported version. The log4j dependencies are test and provided scope only, so nothing changes in the shaded jar. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: Claude Code (Claude Opus 5.5) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
