Update managed-io.md for release 2.72.0-RC3

[damccorm]

Content generated from release 2.72.0-RC3.

[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 updates the documentation for managed I/O connectors, reflecting changes introduced in release 2.72.0-RC3. The primary goal is to ensure the documentation accurately represents the available configuration options and their descriptions for various data sources and sinks, including Iceberg, BigQuery, Kafka, Postgres, MySQL, and SQLServer, by adding new parameters, removing outdated ones, and reordering sections for better readability.

Highlights

• ICEBERG_CDC Connector Documentation: Updated the ICEBERG_CDC connector documentation, including new read parameters such as from_snapshot, from_timestamp, poll_interval_seconds, starting_strategy, streaming, to_snapshot, and to_timestamp, and reordered its placement.
• ICEBERG Read/Write Configuration Refinement: Revised the ICEBERG Read and Write configuration sections, reordering parameters like drop, filter, keep, only, partition_fields, table_properties, direct_write_byte_limit, and triggering_frequency_seconds to their appropriate read/write contexts and updating their descriptions.
• JDBC Connector Parameter Adjustments: Adjusted parameters for various JDBC connectors: POSTGRES Read had disable_auto_commit removed and new parameters (output_parallelization, partition_column, read_query, username) added; SQLSERVER Read and Write had connection_init_sql removed; and MYSQL Read and Write had connection_init_sql added.
• BigQuery Connector Documentation Updates: Updated and reordered the BIGQUERY Read and Write connector documentation to clarify configurations.
• Documentation Structure Reorganization: Reorganized the overall structure of the 'Configuration Details' section for various I/O connectors to improve clarity and logical grouping.

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

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.

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