j1wonpark opened a new issue, #4318:
URL: https://github.com/apache/amoro/issues/4318

   ### Search before asking
   
   - [x] I have searched in the 
[issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no 
similar issues.
   
   ### What would you like to be improved?
   
   Amoro mixed-format Flink currently maintains version-specific modules for 
Flink 1.18 and 1.19, but does not yet provide a Flink 1.20 variant.
   
   Flink 1.20 is the last minor release of the 1.x line (LTS), and Iceberg's 
multi-engine support matrix maintains it: `iceberg-flink-1.20` is published for 
the Iceberg 1.7 line we currently depend on, and continues to be published 
through the latest Iceberg releases. Adding a Flink 1.20 variant keeps Amoro's 
mixed-format Flink support aligned with the engine versions Iceberg maintains, 
and reduces friction for future Iceberg upgrades.
   
   With this addition the mixed-format Flink support matrix becomes 1.18 / 1.19 
/ 1.20, which matches the usual three-version policy, so no version needs to be 
dropped.
   
   ### How should we improve?
   
   We should add mixed Flink 1.20 support to Amoro. This likely includes:
   
   - adding `v1.20/amoro-mixed-flink-1.20`
   - adding `v1.20/amoro-mixed-flink-runtime-1.20`
   - updating parent module definitions
   - validating catalog, source/sink, and runtime compatibility under Flink 1.20
   - updating documentation for the supported Flink version matrix
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Subtasks
   
   - [ ] Add mixed Flink 1.20 modules
   - [ ] Verify compile/tests for Flink 1.20
   - [ ] Update related documentation
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to