Update managed-io.md for release 2.72.0-RC2

[Abacn]

Content generated from release 2.72.0-RC2.

[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 brings the managed-io.md documentation up-to-date with the changes introduced in release 2.72.0-RC2. The updates include a logical reordering of connector configuration summaries, a renaming of the SQLSERVER connector to MYSQL throughout the document, and the addition of a new connection_init_sql parameter for MYSQL connections. These modifications ensure the documentation accurately reflects the current state of the managed I/O connectors.

Highlights

• Connector Table Reordering: Reordered the summary tables for ICEBERG and BIGQUERY connectors to improve logical flow within the documentation.
• Connector Renaming: Renamed all SQLSERVER connector documentation entries to MYSQL to reflect updated naming conventions.
• New Configuration Parameter: Introduced the connection_init_sql parameter to both read and write configurations for the MYSQL connector.

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

Changelog

• website/www/site/content/en/documentation/io/managed-io.md
  • Reordered the ICEBERG and BIGQUERY connector entries in the main configuration summary table.
  • Renamed SQLSERVER connector references to MYSQL in both the summary and detailed configuration sections.
  • Added the connection_init_sql parameter to the MYSQL (formerly SQLSERVER) read and write detailed configuration tables.
  • Adjusted the order and content of several detailed connector configuration sections, including ICEBERG, KAFKA, and BIGQUERY.

Activity

• No human activity has been recorded on this pull request yet.

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

[github-actions]

Assigning reviewers:

R: @shunping 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).