MartijnVisser opened a new pull request, #29237:
URL: https://github.com/apache/flink/pull/29237
## What is the purpose of the change
The FLINK-39572 backport kept master's Beam imports. release-2.3 builds Beam
2.54.0, where
`Environments`, `ModelCoders` and `ExecutableStage` are in
`org.apache.beam.runners.core.construction` and the vendored gRPC package is
`v1p60p1`, so
`flink-python` no longer compiles. There is no master commit to backport;
master builds Beam 2.75.0.
## Brief change log
- Point the four Beam imports in `DefaultJobBundleFactoryTest` at the
packages Beam 2.54.0 uses
## Verifying this change
This change is already covered by existing tests. `./mvnw -pl flink-python
-DskipTests test-compile`
fails on cf7fbd3317d with the five errors CI reports and passes here on JDK
17, with
`DefaultJobBundleFactoryTest` green. Putting the `Closing environment {}`
log line back into
`DefaultJobBundleFactory` makes it fail again, so it still guards
FLINK-39572. Last nightly:
[azure
79227](https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=79227)
(`compile_ci`).
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Code (Claude Opus 5)
--
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]
