Skip to content

Update managed-io.md for release 2.75.0-RC1#39178

Open
shunping wants to merge 1 commit into
masterfrom
updates_managed_io_docs_2.75.0_rc1
Open

Update managed-io.md for release 2.75.0-RC1#39178
shunping wants to merge 1 commit into
masterfrom
updates_managed_io_docs_2.75.0_rc1

Conversation

@shunping

Copy link
Copy Markdown
Collaborator

Content generated from release 2.75.0-RC1.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 managed-io.md documentation to align with the 2.75.0-RC1 release. The changes primarily involve restructuring and updating the configuration tables for several IO connectors to better reflect their current capabilities and parameter requirements.

Highlights

  • Documentation Updates: Updated the managed-io.md documentation to reflect the latest changes for release 2.75.0-RC1, including reorganized and updated configuration tables for various IO connectors.
  • Connector Configuration Changes: Refined the configuration parameters for ICEBERG, ICEBERG_CDC, POSTGRES, SQLSERVER, and BIGQUERY connectors to ensure accurate representation of supported options.
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.

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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request reorganizes and updates the Managed IO documentation for several connectors, including Iceberg, Iceberg CDC, Postgres, SQL Server, and BigQuery. The changes restructure the configuration tables and update parameter details. The review feedback highlights minor typos, grammatical errors, and redundancies in the documentation text, providing specific suggestions to improve readability and correctness.

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.

</td>
<td>
Properties used to set up the Iceberg catalog.
The source's starting strategy. Valid options are: "earliest" or "latest". Can be overriden by setting a starting snapshot or timestamp. Defaults to earliest for batch, and latest for streaming.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There is a typo in the description: "overriden" should be spelled "overridden".

Suggested change
The source's starting strategy. Valid options are: "earliest" or "latest". Can be overriden by setting a starting snapshot or timestamp. Defaults to earliest for batch, and latest for streaming.
The source's starting strategy. Valid options are: "earliest" or "latest". Can be overridden by setting a starting snapshot or timestamp. Defaults to earliest for batch, and latest for streaming.

<td>
A list of field names to keep in the input record. All other fields are dropped before writing. Is mutually exclusive with 'drop' and 'only'.
Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".
</td>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase "as standalone parameter" is grammatically incorrect. It should be "as a standalone parameter" or "as standalone parameters".

Suggested change
</td>
Used to set connection properties passed to the JDBC driver not already defined as a standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".

<td>
The name of a single record field that should be written. Is mutually exclusive with 'keep' and 'drop'.
This method is used to override the size of the data that is going to be fetched and loaded in memory per every database call. It should ONLY be used if the default value throws memory errors.
</td>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

"per every database call" is slightly redundant. It should be "per database call" or "for each database call".

Suggested change
</td>
This method is used to override the size of the data that is going to be fetched and loaded in memory per database call. It should ONLY be used if the default value throws memory errors.

</td>
<td>
Whether to reshuffle the resulting PCollection so results are distributed to all workers.
Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase "as standalone parameter" is grammatically incorrect. It should be "as a standalone parameter" or "as standalone parameters".

Suggested change
Used to set connection properties passed to the JDBC driver not already defined as standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".
Used to set connection properties passed to the JDBC driver not already defined as a standalone parameter (e.g. username and password can be set using parameters above accordingly). Format of the string must be "key1=value1;key2=value2;".

@github-actions

Copy link
Copy Markdown
Contributor

Assigning reviewers:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant