The GitHub Actions job "Flink Connector JDBC CI Backwards Compatibility" on flink-connector-jdbc.git/FLINK-40725-changelog-onconflict has failed. Run started by GitHub user spuru9 (triggered by spuru9).
Head commit for run: 719b005ca9bfdface6479695b38757a1ba29e06d / Purushottam Sinha <[email protected]> [FLINK-40725][tests] Fix sink/catalog ITCases for Flink 2.3.0 ON CONFLICT validation Flink 2.3.0 (FLIP-558, FLINK-38926) tightened the planner: a query whose upsert key differs from the sink primary key is now rejected unless the INSERT declares an ON CONFLICT clause. Several ITCases that write a changelog / grouped result into an upsert sink therefore fail on 2.3.0 with a ValidationException while passing on 2.1.x/2.2.x: - JdbcDynamicTableSinkITCase.testReadingFromChangelogSource (shared base, all database modules) - MySqlCatalogTestBase.testGroupByInsert (MySql) - OceanBaseMysqlCatalogITCase.testGroupByInsert (OceanBase) Add ON CONFLICT DO DEDUPLICATE to those INSERTs only when running against Flink >= 2.3.0. DO DEDUPLICATE keeps the latest record per key, matching the prior upsert semantics; the clause does not parse on 2.1.x/2.2.x so it is version-gated. Version detection lives in a shared test helper, FlinkVersionUtils, backed by FlinkVersion.current(): it resolves at runtime to the version on the test classpath, so the source references no version-specific constant (FlinkVersion.v2_3 does not exist in the baseline flink.version the connector compiles against, so it cannot be named directly). Also add Flink 2.3.0 to the push_pr CI matrix so these paths are exercised. Verified locally against Flink 2.1.3, 2.2.1 and 2.3.0 (the three affected tests pass on all three; default baseline still compiles), on JDK 17 and 21. Generated-by: Claude Code (Claude Opus 4.8) Report URL: https://github.com/apache/flink-connector-jdbc/actions/runs/35570453426 With regards, GitHub Actions via GitBox
