GreatEugenius opened a new pull request, #856:
URL: https://github.com/apache/flink-agents/pull/856
<!--
* Thank you very much for contributing to Flink Agents.
* Please add the relevant components in the PR title. E.g., [api],
[runtime], [java], [python], [hotfix], etc.
-->
<!-- Please link the PR to the relevant issue(s). Hotfix doesn't need this.
-->
Linked issue: #833
Purpose of change
Add Flink 2.3 as a supported distribution while keeping the build baseline
at Flink 2.2.1 / Java 11.
Flink 2.3 jars are Java 17 bytecode, so 2.3 stays a provided runtime target
only — core modules still compile once against the 2.2.1 baseline on JDK 11,
mirroring how the MCP module isolates its 17-only dependency. This avoids
forcing JDK 17 on every build and preserves backward-binary-compat across all
supported Flink versions.
- dist: new flink-2.3 module with provided deps + thin-jar packaging
- e2e: flink-2.3 profile so IT runs the 2.2.1-built jar on a 2.3 runtime
- ci: add {flink 2.3, java 17} to the it-java and it-python matrices
- python: bundle the 2.3 thin jar into the wheel manifest, cover it in the
build-backend test
- misc: refresh ut.sh help text and the cross-language async version notes
Tests
- Full multi-module build on JDK 11 (all 5 dist versions:
1.20/2.0/2.1/2.2/2.3)
- Java IT against Flink 2.3 runtime — 27 pas
- Python IT against Flink 2.3 runtime — 4 passed
- CI matrices extended with {flink 2.3, javapython
API
No public API changes. 2.3 is a packaging/ru
### Documentation
<!-- Do not remove this section. Check the proper box only. -->
- [ ] `doc-needed` <!-- Your PR changes impact docs -->
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [x] `doc-included` <!-- Your PR already contains the necessary
documentation updates -->
--
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]
