mananmangal opened a new pull request, #38980:
URL: https://github.com/apache/beam/pull/38980
Add a dedicated beam-runners-flink-2.2 module targeting Apache Flink
2.2.1, as tracked in #38978.
What changed:
- New runners/flink/2.2 module with build.gradle, job-server, and
job-server-container subprojects, mirroring the existing 2.0 structure with
flink_version = '2.2.1'
- Source overrides for FlinkExecutionEnvironments and DoFnOperator:
migrates from the deprecated org.apache.flink.streaming.api.CheckpointingMode
(moved in Flink 2.2) to
org.apache.flink.core.execution.CheckpointingMode, which also routes
enableCheckpointing() to the non-deprecated setCheckpointingConsistencyMode()
internal path
- Test override for FlinkPipelineOptionsTest using the non-deprecated
import and a version assertion that guards against classpath mismatches
- PUBLISHED_FLINK_VERSIONS updated in both the Python and TypeScript SDKs
- Flink 2.2 added to CI test matrices (ValidatesRunner, PVR Streaming,
Docker snapshot publishing, RC quickstart validation)
- Website compatibility table updated: beam-runners-flink-2.2 supported
from Beam >= 2.75.0
Flink 2.2 breaking changes addressed (DataStream API layer — affects Beam
runner):
- CheckpointingMode class relocation (above)
Flink 2.2 breaking changes that are SQL/cluster-layer only (no runner code
change required):
- TLS cipher suite default changed (FLINK-39022): clusters with
security.ssl.enabled=true on JDK 11.0.30+ / 17.0.18+ / 21.0.10+ / 24+ must
verify ECDHE cipher suite
support before upgrading
- StreamingMultiJoinOperator state format change (FLINK-38209): savepoints
created in Flink 2.1 with table.optimizer.multi-join.enabled=true are not
compatible with 2.2
- SQL row NOT NULL enforcement (FLINK-38181): use
table.legacy-nested-row-nullability=true to restore prior behaviour if needed
Closes #38978
------------------------
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:
- [ ] Mention the appropriate issue in your description (for example:
`addresses #123`), if applicable. This will automatically add a link to the
pull request in the issue. If you would like the issue to automatically close
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
- [ ] Update `CHANGES.md` with noteworthy changes.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
See the [Contributor Guide](https://beam.apache.org/contribute) for more
tips on [how to make review process
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
To check the build health, please visit
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
GitHub Actions Tests Status (on master branch)
------------------------------------------------------------------------------------------------
[](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more
information about GitHub Actions CI or the [workflows
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md)
to see a list of phrases to trigger workflows.
--
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]
