Skip to content

Fix comma-separated selected_fields in BigQuery to SQL transfers - #71775

Closed
FrankYang0529 wants to merge 1 commit into
apache:mainfrom
FrankYang0529:bigquery-to-sql-normalize-selected-fields
Closed

FrankYang0529 wants to merge 1 commit into
apache:mainfrom
FrankYang0529:bigquery-to-sql-normalize-selected-fields

Conversation

@FrankYang0529

@FrankYang0529 FrankYang0529 commented Aug 18, 2026 •

Copy link
Copy Markdown
Member

Why

  • The docstring says selected_fields is a "List of fields to return (comma-separated)". The operator passes that value to two places: BigQueryHook.list_rows() splits it on commas, but insert_rows(target_fields=...) does not.

  • common.sql builds the column list with ", ".join(map(escape_word, target_fields)), so a string is iterated character by character. With selected_fields="emp_name,salary":

    -- before
    INSERT INTO employees (e, m, p, _, n, a, m, e, ",", s, a, l, a, r, y) VALUES (%s, %s)
    -- after
    INSERT INTO employees (emp_name, salary) VALUES (%s, %s)

How

  • BigQueryToSqlBaseOperator.__init__ normalises a comma-separated string into list[str], so BigQueryToPostgres / BigQueryToMySql / BigQueryToMsSql all get a real column list on both the BigQuery read and the SQL write side.

Verification

  • uv run --project providers/google pytest providers/google/tests/unit/google/cloud/transfers/test_bigquery_to_postgres.py providers/google/tests/unit/google/cloud/transfers/test_bigquery_to_mysql.py -v

Was generative AI tooling used to co-author this PR?
  • Yes - Claude Code

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

@boring-cyborg boring-cyborg Bot added area:providers provider:google Google (including GCP) related issues labels Aug 18, 2026
@FrankYang0529
FrankYang0529 marked this pull request as ready for review August 19, 2026 07:16
@FrankYang0529
FrankYang0529 requested a review from shahar1 as a code owner August 19, 2026 07:16
) -> None:
super().__init__(**kwargs)
if isinstance(selected_fields, str):
selected_fields = [field.strip() for field in selected_fields.split(",") if field.strip()]

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.

Was treating an empty normalized string as “all fields” intentional? Would it be safer to raise ValueError when a provided string contains no valid fields and add a test for that case? Did you test this case as well?

@potiuk potiuk added the closed because of open PR limit Closed as a one-time step of introducing the open pull request limit label Sep 25, 2026
@potiuk

potiuk commented Sep 25, 2026

Copy link
Copy Markdown
Member

Hello @FrankYang0529 - thank you for your contributions to Apache Airflow!

The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 30 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:

These pull requests stay open because maintainers are already engaged in them - they count towards your limit:

This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are.

What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or gh pr reopen <PR_NUMBER> --repo apache/airflow. Reopen the ones you are ready to follow through - keep them rebased, respond to review comments and fix failing checks.

While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack.

Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst.


Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting

@potiuk potiuk closed this Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers closed because of open PR limit Closed as a one-time step of introducing the open pull request limit provider:google Google (including GCP) related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants