Exercise Flink 2.0 test

[Abacn]

Please add a meaningful description for your change here

---

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 @Abacn, 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 focuses on preparing the build environment and continuous integration (CI) for Apache Flink 2.0. It refines the Gradle build configuration to dynamically manage Flink versions, specifically enabling the system to recognize Flink 2.0 as the latest version. Additionally, various CI trigger files have been updated, including the introduction of new Flink-related test triggers, to ensure comprehensive testing with the anticipated Flink 2.0 integration.

Highlights

• Flink Versioning Logic Update: The build system's logic for determining the latestFlinkVersion has been updated. It now dynamically selects the last version from the allFlinkVersions list, removing a previous hardcoded value of '1.20' and a TODO comment related to Flink 2.0 support, indicating readiness for Flink 2.0.
• CI Trigger File Modifications: Numerous .github/trigger_files have been modified. These changes include incrementing modification/revision counters and removing outdated pull request references, primarily to re-trigger or update existing Flink-related continuous integration tests.
• New Flink Test Suite Activations: New empty trigger files have been added for beam_PostCommit_Java_Tpcds_Flink.json, beam_PostCommit_PortableJar_Flink.json, and beam_PostCommit_Python_Examples_Flink.json. This suggests the activation or preparation of new Flink-specific test suites within the CI pipeline.

🧠 New Feature in Public Preview: You can now enable Memory 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/** (7)
  • .github/workflows/beam_PostCommit_Java_Nexmark_Flink.yml
  • .github/workflows/beam_PostCommit_Java_PVR_Flink_Streaming.yml
  • .github/workflows/beam_PostCommit_Java_Tpcds_Flink.yml
  • .github/workflows/beam_PostCommit_Java_ValidatesRunner_Flink.yml
  • .github/workflows/beam_PostCommit_XVR_Flink.yml
  • .github/workflows/beam_PreCommit_Java_PVR_Flink_Batch.yml
  • .github/workflows/beam_PreCommit_Java_PVR_Flink_Docker.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 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 counter productive. 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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩