j1wonpark opened a new pull request, #4141: URL: https://github.com/apache/amoro/pull/4141
## Why are the changes needed? Close #4127. Amoro's mixed-format Flink integration currently supports Flink 1.17 and 1.18. Iceberg's multi-engine support matrix includes Flink 1.19, and aligning Amoro's supported versions with Iceberg reduces friction for future Iceberg upgrades. ## Brief change log - Add `v1.19/amoro-mixed-flink-1.19` module with `pom.xml` depending on `iceberg-flink-1.19` and `paimon-flink-1.19` - Add `v1.19/amoro-mixed-flink-runtime-1.19` module - Register both modules in `amoro-format-mixed/amoro-mixed-flink/pom.xml` - Update `README.md` and `docs/_index.md` to include Flink 1.19.x in the supported version matrix - Update `docs/engines/flink/flink-get-started.md` and `using-logstore.md` to cover Flink 1.19 - Add `dev/e2e/kind-config.yaml` for local E2E cluster setup **Note on `amoro-mixed-flink-common`:** The common module compiles against Flink 1.18 APIs (`provided` scope). All APIs used in common are confirmed compatible with Flink 1.19 — deprecated items (`RichParallelSourceFunction`, `open(Configuration)`, `getExecutionConfig()`) are scheduled for removal in Flink 2.0 and continue to work in 1.19 with fallback support. No breaking API changes were identified between Flink 1.18 and 1.19 for the APIs used in this module. **Note on CI:** The existing CI workflows build all Flink version modules in a single pass (no per-version matrix); registering the new modules in `pom.xml` is sufficient for CI coverage. ## How was this patch tested? - [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible - [ ] Add screenshots for manual tests if appropriate - [x] Run test locally before making a pull request ## Documentation - Does this pull request introduce a new feature? yes - If yes, how is the feature documented? docs -- 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]
