Add Flink 2.2.1 runner support

[mananmangal]

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.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces support for Apache Flink 2.2.1 within the Apache Beam ecosystem. It includes the creation of a new runner module, necessary source code migrations to address breaking API changes in Flink 2.2, and comprehensive updates to build configurations, SDK metadata, and documentation to ensure seamless integration and validation of the new Flink version.

Highlights

• New Flink Runner Module: Added a dedicated beam-runners-flink-2.2 module to support Apache Flink 2.2.1.
• API Migration: Migrated deprecated Flink APIs, such as CheckpointingMode, to their new locations in Flink 2.2.
• Dependency Resolution: Implemented a global Gradle resolution strategy for lz4-java to resolve capability conflicts between Flink 2.2 and other libraries.
• Ecosystem Updates: Updated CI test matrices, Python and TypeScript SDK version lists, and documentation to include Flink 2.2 support.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (4)
  • .github/workflows/beam_PostCommit_Java_PVR_Flink_Streaming.yml
  • .github/workflows/beam_PostCommit_Java_ValidatesRunner_Flink.yml
  • .github/workflows/beam_Publish_Docker_Snapshots.yml
  • .github/workflows/run_rc_validation_java_quickstart.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces support for Flink 2.2 across the Beam codebase, including updating supported version lists in properties, Python, and TypeScript options, adding a global Gradle capability resolution for the org.lz4:lz4-java conflict, and creating the new runners/flink/2.2 module with overridden classes such as FlinkExecutionEnvironments and DoFnOperator. The review feedback identifies two key improvement opportunities: first, in DoFnOperator.java, the lambda within numProcessingTimeTimers() should use the local manager parameter instead of directly referencing the class field timeServiceManager; second, in FlinkExecutionEnvironments.java, a null check should be added for optionsNode in configureWebUIOptions to prevent a potential NullPointerException when parsing options.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[mananmangal]

assign set of reviewers

[github-actions]

Assigning reviewers:

R: @shunping for label python.
R: @liferoad for label build.
R: @Abacn for label website.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[Abacn]

Thanks for the contribution. Yeah Beam is a bit behind (two minor versions) in terms of Flink support. After 2.1 in 1.17-2.0 would already have 6 versions. We'd need to clean up EOL versions (1.17, 1.18) before merging this one.

[mananmangal]

Thanks for the contribution. Yeah Beam is a bit behind (two minor versions) in terms of Flink support. After 2.1 in 1.17-2.0 would already have 6 versions. We'd need to clean up EOL versions (1.17, 1.18) before merging this one.

Thanks for the context!
The primary motivation here is that AWS Managed Service for Apache Flink decided to move directly to Flink 2.2, completely skipping 2.0 and 2.1 (AWS Release Version Docs). Because of this jump, users on that platform currently have no compatible Beam runner for Flink 2.x.

Makes total sense on cleaning up the EOL versions first. If there an existing issue or effort for the 1.17, 1.18 cleanup, I can follow that along.

[Abacn]

Thanks for the context. Same for GCP Dataproc: https://docs.cloud.google.com/managed-spark/docs/concepts/versioning/image-release-3.0 (2.3 supports 1.17, now 3.0-RC directly jumped to 2.2 though earlier RC was on 2.0).

There is no known blocker for dropping 1.17, 1.18 after #38279 gets merged.