MartijnVisser opened a new pull request, #224: URL: https://github.com/apache/flink-connector-jdbc/pull/224
## What is the purpose of the change `JdbcDynamicTableSinkITCase` does not compile against Flink 2.2, which dropped the `isCheckpointingEnabled` parameter from `MockStreamingRuntimeContext`: ``` JdbcDynamicTableSinkITCase.java:[386,72] incompatible types: boolean cannot be converted to int ``` The weekly has failed on this on every run that got that far since 2026-07-26, six of the nine. `v4.1` already carries the fix as 3b7d5fe; it was never forward-ported. This is that commit, cherry-picked unchanged, with Yuepeng Pan's authorship intact. ## Brief change log - Cherry-pick 3b7d5fe: `JdbcDynamicTableSinkITCase` uses a local `TestingStreamingRuntimeContext` in place of `MockStreamingRuntimeContext`. ## Verifying this change This change is already covered by existing tests, such as `DerbyDynamicTableSinkITCase`. `mvn -pl flink-connector-jdbc-core test-compile -Dflink.version=2.2.0` is red on `main` at 0383d2c with the same error and green with this commit; 2.0.0, 2.0.1, 2.1.1 and 2.2.1 stay green. `DerbyDynamicTableSinkITCase` passes on 2.2.0 and 2.0.0 (`Tests run: 6, Failures: 0, Errors: 0`), and `spotless:check` and `checkstyle:check` pass. `JdbcTablePlanTest` fails next, on `JdbcTablePlanTest.xml` not being in execution order, so this alone does not make the weekly green. ## 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: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: Claude Code (Claude Opus 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]
