MartijnVisser opened a new pull request, #272: URL: https://github.com/apache/flink-connector-jdbc/pull/272
## What is the purpose of the change The backwards compatibility workflow can no longer resolve 2.0-SNAPSHOT and 2.1-SNAPSHOT. Since 4.0 the module only tests the current API, so this removes it instead of changing the matrix. ## Brief change log - Remove `.github/workflows/backwards_compatibility.yml` and `flink-connector-jdbc-backward-compatibility` - Move `DataStreamSinkTest` to `flink-connector-jdbc-postgres` as `PostgresJdbcSinkITCase`, the only exactly-once `JdbcSink` test on PostgreSQL - Drop the other tests, which `PostgresDynamicTableSourceITCase`, `PostgresDynamicTableSinkITCase` and `JdbcSourceITCase` (on Derby) already cover ## Verifying this change This change is already covered by existing tests, such as `PostgresJdbcSinkITCase`. I ran it on Flink 2.1.3, 2.2.1, 2.3.0 and 2.4-SNAPSHOT, and `testExactlyOnce` finds an empty table when `JdbcCommitter` skips the commit. This conflicts with #254, which edits `DataStreamSourceTest`, and makes #201 obsolete. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable --- ##### 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]
