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

   ### 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 still maintains version-specific modules for Flink 
1.17, including the `v1.17/amoro-mixed-flink-1.17` and 
`v1.17/amoro-mixed-flink-runtime-1.17` modules.
   
   According to Iceberg's current multi-engine support matrix, Flink 1.17 is 
already End of Life, while newer versions such as Flink 1.19 and 1.20 are 
maintained:
   https://iceberg.apache.org/multi-engine-support/
   
   Continuing to keep mixed Flink 1.17 in the version matrix increases 
maintenance cost and makes future Iceberg upgrades harder to carry out.
   
   ### How should we improve?
   
   We should drop mixed Flink 1.17 support from Amoro.
   
   This likely includes:
   - removing `v1.17/amoro-mixed-flink-1.17`
   - removing `v1.17/amoro-mixed-flink-runtime-1.17`
   - updating the mixed Flink parent POM and related build definitions
   - updating CI/build matrix if Flink 1.17 is still covered there
   - updating documentation for the supported Flink version matrix
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Subtasks
   
   - [ ] Remove mixed Flink 1.17 modules from the build
   - [ ] Update related parent POM entries and build definitions
   - [ ] Update CI/build matrix if needed
   - [ ] Update documentation for supported Flink versions
   
   ### 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