[yaml] - add bigquery destination test

[derrickaw]

We currently don't have any active tests dealing with dynamic destinations, so adding one for BQ.

---

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]

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 introduces a crucial integration test for BigQuery dynamic destinations within the YAML test framework. The primary goal is to enhance the robustness of the system by verifying that data can be correctly written to and read from BigQuery tables whose names are dynamically generated based on input data fields. This addition improves the overall reliability of data processing pipelines utilizing this feature.

Highlights

• New BigQuery Dynamic Destination Test: A new YAML-based integration test has been added to validate the functionality of BigQuery dynamic destinations. This test creates data, writes it to BigQuery using dynamic table naming based on a 'country' field, and then asserts the correct data is read from the dynamically created tables.
• Increased Test Coverage: This PR addresses a gap in test coverage by introducing the first active test specifically for dynamic destinations within the YAML test suite, ensuring this feature works as expected.

🧠 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

• .github/trigger_files/beam_PostCommit_Yaml_Xlang_Direct.json
  • Incremented the revision number to trigger the test suite.
• sdks/python/apache_beam/yaml/extended_tests/databases/bigquery_dynamic_destinations.yaml
  • Added a new YAML test configuration for BigQuery dynamic destinations.
  • Defined a pipeline that creates user data with country information.
  • Configured a WriteToBigQuery transform to use dynamic table naming based on the 'country' field.
  • Included subsequent ReadFromBigQuery and AssertEqual transforms to verify data in the dynamically created tables (e.g., _US, _UK, _CN).

Activity

• No human activity has occurred 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. ↩

[derrickaw]

Run Python_ML PreCommit 3.11

[derrickaw]

Run Yaml_Xlang_Direct PostCommit

[derrickaw]

Run Python_Examples PreCommit 3.10

[derrickaw]

Run Python_ML PreCommit 3.11

[derrickaw]

Run Python_ML PreCommit 3.11

[derrickaw]

Run Python_Examples PreCommit 3.10