Sbaia opened a new issue, #677: URL: https://github.com/apache/doris-flink-connector/issues/677
### Search before asking - [x] I searched existing issues and pull requests and found no request specifically tracking JDK 21 support. ### Description Flink Doris Connector 26.1.1 supports Flink 2.0 through 2.2, but its compatibility matrix currently lists Java 17 for Flink 2.x. Flink 2.x can run on Java 21, and we operate Flink 2.1 workloads on JDK 21. We would like to contribute explicit JDK 21 build and test coverage so users do not have to rely only on Java bytecode backward compatibility. Current state: - `flink-doris-connector-flink2` compiles with Java 17 source/target. - Build, checkstyle, integration-test, and end-to-end workflows for Flink 2.x run only on JDK 17. - `flink-doris-connector/build.sh` rejects JDK versions other than 17 for Flink 2.x. - The published Flink 2.1 connector uses Java 17 bytecode, so keeping Java 17 as the bytecode target remains desirable for compatibility. ### Proposed scope 1. Keep Java 17 as the compilation/bytecode target for Flink 2.x artifacts. 2. Add JDK 21 build and test coverage for the supported Flink 2.x line. 3. Add JDK 21 coverage to relevant integration and end-to-end workflows. 4. Allow JDK 17 or JDK 21 in `build.sh` for Flink 2.x. 5. Exercise the paths most sensitive to JDK modularization: Arrow, batch Stream Load, Group Commit, and checkpoint/flush behavior. 6. Update the documented Java compatibility matrix only after the test matrix is green. ### Questions - Would maintainers prefer JDK 21 coverage for Flink 2.0, 2.1, and 2.2, or initially only the actively used 2.1/2.2 lines? - Should JDK 21 be documented as supported or experimental, matching Flink's current wording? ### Are you willing to submit PR? - [x] Yes, I am willing to submit a PR. ### Code of Conduct - [x] I agree to follow the Apache Software Foundation Code of 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
