Skip to content

Fix bq load for clashing copy job names#39107

Open
stankiewicz wants to merge 3 commits into
apache:masterfrom
stankiewicz:bq_copy_job_fix
Open

Fix bq load for clashing copy job names#39107
stankiewicz wants to merge 3 commits into
apache:masterfrom
stankiewicz:bq_copy_job_fix

Conversation

@stankiewicz

Copy link
Copy Markdown
Contributor

Fixes: https://github.com/apache/beam/actions/runs/28119469173/job/83267359072


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
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 addresses an issue where BigQuery copy job names could clash during file load operations. By replacing the index-based naming strategy with a deterministic hash derived from the chunk contents, the system ensures that concurrent or repeated copy jobs maintain unique identifiers, thereby improving reliability in distributed execution environments.

Highlights

  • BigQuery Copy Job Naming: Updated the BigQuery copy job naming logic to use a unique hash based on the chunk content instead of a simple index, preventing potential job name collisions.
  • Utility Function: Introduced a new helper function _bq_uuid_list to generate a SHA-256 checksum for lists of strings, ensuring unique identifiers for copy jobs.
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 updates the BigQuery file loads logic in the Python SDK to generate chunk job names using a SHA256 hash of the chunk contents instead of an index-based suffix. The review feedback recommends renaming the 'list' parameter in the new '_bq_uuid_list' helper function to avoid shadowing the built-in type, and replacing '%' string formatting with f-strings for better consistency and modern Python standards.

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.

Comment on lines +173 to +179
def _bq_uuid_list(list):
checksum = hashlib.sha256()
for item in list:
checksum.update(item.encode('utf-8'))
# separator
checksum.update(b'\x00')
return checksum.hexdigest()

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

Avoid using the built-in name list as a parameter name, as it shadows the built-in list type. It is better to use a name like items or lst to prevent potential bugs and maintain readability.

Suggested change
def _bq_uuid_list(list):
checksum = hashlib.sha256()
for item in list:
checksum.update(item.encode('utf-8'))
# separator
checksum.update(b'\x00')
return checksum.hexdigest()
def _bq_uuid_list(items):
checksum = hashlib.sha256()
for item in items:
checksum.update(item.encode('utf-8'))
# separator
checksum.update(b'\x00')
return checksum.hexdigest()
References
  1. Avoid shadowing built-in names like 'list' to prevent naming conflicts and maintain code clarity. (link)

chunk_job_name = copy_job_name_base
if len(chunks) > 1:
chunk_job_name = f"{copy_job_name_base}_{i}"
chunk_job_name = '%s_%s' % (copy_job_name_base, _bq_uuid_list(chunk))

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

Use f-strings instead of % formatting for consistency with the rest of the codebase and modern Python standards (PEP 498).

Suggested change
chunk_job_name = '%s_%s' % (copy_job_name_base, _bq_uuid_list(chunk))
chunk_job_name = f"{copy_job_name_base}_{_bq_uuid_list(chunk)}"
References
  1. Use f-strings (PEP 498) for string formatting to maintain consistency and readability. (link)

chunk_job_name = copy_job_name_base
if len(chunks) > 1:
chunk_job_name = f"{copy_job_name_base}_{i}"
chunk_job_name = '%s_%s' % (copy_job_name_base, _bq_uuid_list(chunk))

@Abacn Abacn Jun 25, 2026

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.

We have to be careful here. I remember bq load job name being deterministic is intended to avoid duplicate data on retry.

@Abacn Abacn Jun 25, 2026

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.

If there is a commit causing these test failures (#38983 ?), consider revert it for the current release then fix forward, since release already cut yesterday and there is a risk potential problems not revealed if fix-forward with cherry-picks

@github-actions

Copy link
Copy Markdown
Contributor

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

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