Sql calcite connection properties docs

[Arunodoy18]

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[bot]]

Summary of Changes

Hello @Arunodoy18, 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 significantly enhances Apache Beam by expanding the capabilities and documentation for SQL transforms in YAML pipelines, improving BigQuery I/O functionality, and adding useful file system utilities. The core focus is on providing clearer guidance and more robust support for SQL dialect configurations through calcite_connection_properties, alongside critical updates to BigQuery's streaming write methods and a new Python example for dynamic side inputs. These changes collectively aim to make Beam more flexible and user-friendly for diverse data processing scenarios.

Highlights

• SQL Calcite Properties Documentation & Examples: New comprehensive documentation and a suite of examples have been added for configuring calcite_connection_properties in Beam YAML pipelines. This allows users to easily adapt SQL transforms to various database dialects, including PostgreSQL, BigQuery, MySQL, and Oracle, by specifying function libraries, lexical rules, and other parsing behaviors.
• BigQuery I/O Enhancements: The BigQuery I/O connector has been improved to correctly handle the STORAGE_API_AT_LEAST_ONCE write method, particularly concerning triggering frequency for unbounded PCollections. Additionally, an issue related to Change Data Capture (CDC) when using STORAGE_WRITE_API has been addressed, ensuring smoother operation for CDC workflows.
• File System Glob Wildcard Escaping: New utility methods, escapeGlobWildcards and unescapeGlobWildcards, have been introduced to the FileSystems class. These methods provide a robust way to handle special glob wildcard characters (*, ?, {, }) in file paths, treating them as literals rather than pattern matching symbols.
• New Python Side Input Snippet: A new Python snippet, side_input_slow_update_global_window, has been added to demonstrate a common pattern for creating periodically updating side inputs. This example utilizes PeriodicSequence and Latest.Globally() within a global window, providing a practical guide for users.

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

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.

[^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[bot]]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[Arunodoy18]

assign set of reviewers

[github-actions[bot]]

Assigning reviewers:

R: @shunping for label python. R: @kennknowles for label java. 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).

[github-actions[bot]]

Reminder, please take a look at this pr: @shunping @kennknowles @shunping

[github-actions[bot]]

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @claudevdm for label python. R: @Abacn for label java. R: @damccorm for label website.

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)

[damccorm]

waiting on author