Skip to content

Conversation

@stankiewicz
Copy link
Contributor

parse message once during transform construction.


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)

Build python source distribution and wheels
Python tests
Java tests
Go tests

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
Copy link
Contributor

Summary of Changes

Hello @stankiewicz, 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 introduces an optimization to the ConvertToBeamRows transform within the BigQuery I/O connector. The change ensures that the BigQuery schema is processed and converted into the appropriate object type only once during the transform's construction. This avoids repetitive schema parsing operations for each data element, leading to improved performance and reduced overhead in data conversion pipelines.

Highlights

  • Schema Parsing Optimization: The ConvertToBeamRows transform now ensures that the BigQuery schema is parsed only once during its initialization. This prevents redundant schema parsing for every element processed, improving efficiency.
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.

@stankiewicz
Copy link
Contributor Author

R: @ahmedabu98

@github-actions
Copy link
Contributor

github-actions bot commented Oct 4, 2025

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

@stankiewicz
Copy link
Contributor Author

python 3.13 unrelated test failure - apache_beam.examples.wordcount_it_test.WordCountIT

@stankiewicz
Copy link
Contributor Author

stankiewicz commented Oct 6, 2025

python 3.9 = unrelated - AttributeError: 'TestCloudSQLPostgresEnrichment' object has no attribute '_cache_client_retries'

fix here: #36406

@stankiewicz
Copy link
Contributor Author

stankiewicz commented Oct 6, 2025

[gw4] [ 27%] FAILED apache_beam/io/gcp/bigquery_file_loads_test.py::TestBigQueryFileLoads::test_multiple_identical_destinations_on_write_truncate
fix here: #36402

@stankiewicz
Copy link
Contributor Author

Run Python PreCommit 3.13

@stankiewicz
Copy link
Contributor Author

Run Python_ML PreCommit 3.9

@stankiewicz
Copy link
Contributor Author

Run Python_Integration PreCommit 3.13

@stankiewicz
Copy link
Contributor Author

Run Python_Coverage PreCommit 3.9

@stankiewicz
Copy link
Contributor Author

Run Python_ML PreCommit 3.12

@stankiewicz
Copy link
Contributor Author

Run Python_PVR_Flink PreCommit

@codecov
Copy link

codecov bot commented Oct 6, 2025

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.87%. Comparing base (9cd994e) to head (f858528).
⚠️ Report is 68 commits behind head on master.

Files with missing lines Patch % Lines
sdks/python/apache_beam/io/gcp/bigquery.py 0.00% 2 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##             master   #36393      +/-   ##
============================================
+ Coverage     56.84%   56.87%   +0.03%     
  Complexity     3386     3386              
============================================
  Files          1220     1220              
  Lines        185898   186139     +241     
  Branches       3523     3523              
============================================
+ Hits         105672   105875     +203     
- Misses        76885    76923      +38     
  Partials       3341     3341              
Flag Coverage Δ
python 80.94% <0.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@stankiewicz
Copy link
Contributor Author

Unrelated errors.

R: @liferoad

@liferoad
Copy link
Contributor

liferoad commented Oct 6, 2025

/gemini review

def __init__(self, schema, dynamic_destinations):
if not isinstance(schema,
(bigquery.TableSchema, bigquery.TableFieldSchema)):
schema = bigquery_tools.get_bq_tableschema(schema)
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need remove the lines in beam_row_from_dict?

Copy link
Contributor

Choose a reason for hiding this comment

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

or beam_row_from_dict is used elsewhere, so we should keep it. Just a thought.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I could remove it but
beam_row_from_dict is publicly used method so removing this if would be potentially breaking change.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

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 introduces a valuable optimization to ConvertToBeamRows by parsing the schema once during the transform's construction rather than for each element. This change should improve performance, especially for large PCollections. The implementation is correct and addresses the goal of the PR. I've added one comment regarding a now-redundant check that could be removed to improve maintainability.

Comment on lines +2767 to +2769
if not isinstance(schema,
(bigquery.TableSchema, bigquery.TableFieldSchema)):
schema = bigquery_tools.get_bq_tableschema(schema)
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This is a good optimization to parse the schema once at transform construction. This change makes the schema parsing logic inside bigquery_tools.beam_row_from_dict redundant. To improve maintainability and prevent confusion, consider removing the redundant check from beam_row_from_dict as part of this PR or in a follow-up change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good bot

@liferoad liferoad merged commit 1a6ec3a into apache:master Oct 6, 2025
146 of 166 checks passed
Abacn added a commit that referenced this pull request Oct 14, 2025
Abacn added a commit that referenced this pull request Oct 14, 2025
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.

2 participants