NestDream opened a new issue, #20775: URL: https://github.com/apache/hudi/issues/20775
### Feature Description **What the feature achieves:** Add Flink 2.3 to the Flink versions Hudi builds and tests against: a `hudi-flink2.3.x` adapter module, a `flink2.3` Maven profile and a `hudi-flink2.3-bundle`, the same way Flink 2.2 was added in #19655 and Flink 2.1 in #17574. **Why this feature is needed:** Flink 2.3.0 is the newest Flink release and has been on Maven Central since June 2026. Hudi master has profiles and bundles for Flink 1.18 to 2.2 only. Users on Flink 2.3 have no bundle that is compiled and tested against their Flink version, and the Hudi CI does not run on Flink 2.3. ### User Experience **How users will use this feature:** - Configuration changes needed: users pick the `hudi-flink2.3-bundle` jar for a Flink 2.3.0 cluster. On Flink 2.3 a streaming `INSERT INTO` a table with a primary key fails at planning time when the upsert key of the query differs from the primary key, for example with an append-only source, unless the statement has an `ON CONFLICT` clause or `table.exec.sink.require-on-conflict` is `false`. This comes from Flink 2.3 (FLIP-558, FLINK-38926). - API changes: none. - Usage examples: `mvn clean package -DskipTests -Dflink2.3 -pl packaging/hudi-flink-bundle -am` builds `packaging/hudi-flink-bundle/target/hudi-flink2.3-bundle-<version>.jar`. ### Hudi RFC Requirements **RFC PR link:** (if applicable) Not applicable. **Why RFC is/isn't needed:** - Does this change public interfaces/APIs? (Yes/No) No - Does this change storage format? (Yes/No) No - Justification: The change adds a Flink version specific adapter module and a build profile, as was done for Flink 2.1 and 2.2 without an RFC. I have a branch for this, built and tested against Flink 2.3.0, and will open a pull request. -- 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]
