gemini-code-assist[bot] commented on PR #37175: URL: https://github.com/apache/beam/pull/37175#issuecomment-3687978744
## Summary of Changes Hello @Abacn, I'm Gemini Code Assist[^1]! 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 initial support for Apache Flink 2.0 within the Apache Beam Flink Runner. It establishes a new Flink 2.0-specific module, adapting the build system and core runner components to align with Flink's updated API, notably the deprecation of the DataSet API. This ensures forward compatibility and leverages the latest Flink features for Beam pipelines. ### Highlights * **Flink 2.0 Module Introduction**: A new dedicated module (`runners/flink/2.0`) has been introduced to house Flink 2.0 specific runner implementations, separating it from previous Flink versions. * **Build System Adaptation**: The `gradle.properties` file now includes Flink 2.0 in the list of supported versions. The `flink_runner.gradle` build script has been updated to manage version-specific source and resource overrides, and to enforce Java 11 for Flink 2.x builds. It also conditionally includes the `flink-java` dependency only for Flink 1.x versions, reflecting the removal of the DataSet API in Flink 2.0. * **Core Runner Component Updates**: New Java files have been added under the `runners/flink/2.0/src/main/java` directory. These files implement Flink 2.0-compatible execution environments, pipeline options, translators, and DoFn operators, adapting to the latest Flink API changes. * **Job Server Configuration**: Dedicated build files for the Flink 2.0 job server and job server containers have been added, including updated Docker image naming logic to correctly identify Flink 2.0 job servers. * **Pipeline Options Documentation Updates**: The documentation for Flink pipeline options (both Java and Python) has been updated. This includes the removal of deprecated options like `failOnCheckpointingErrors` and `reIterableGroupByKeyResult`, the update of `stateBackend` descriptions, and the addition of the `tolerableCheckpointFailureNumber` option. 🧠**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](https://codeassist.google/code-review/login) to enable Memory in your admin console.** <details> <summary><b>Using Gemini Code Assist</b></summary> <br> The full guide for Gemini Code Assist can be found on our [documentation page](https://developers.google.com/gemini-code-assist/docs/review-github-code), here are some quick tips. <b>Invoking Gemini</b> 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. <b>Customization</b> 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](https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github). <b>Limitations & Feedback</b> Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: 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](https://google.qualtrics.com/jfe/form/SV_2cyuGuTWsEw84yG). <b>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](https://cloud.google.com/products/gemini/code-assist).</b> </details> [^1]: Review the [Privacy Notices](https://policies.google.com/privacy), [Generative AI Prohibited Use Policy](https://policies.google.com/terms/generative-ai/use-policy), [Terms of Service](https://policies.google.com/terms), and learn how to configure Gemini Code Assist in GitHub [here](https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github). Gemini can make mistakes, so double check it and [use code with caution](https://support.google.com/legal/answer/13505487). -- 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]
