Skip to content

Conversation

@Amar3tto
Copy link
Collaborator

No description provided.

@gemini-code-assist
Copy link

Summary of Changes

Hello @Amar3tto, 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 is a "DO NOT MERGE" validation PR aimed at testing compatibility with the upcoming Apache Beam "2.69.0rc1" release. It involves updating the Beam version in the project's Maven "pom.xml" and all relevant Python dependency files ("default_base_python_requirements.txt", "default_base_yaml_requirements.txt", "base_requirements.txt", and "requirements.txt"). Additionally, the Maven profile activation for "validateCandidate" has been adjusted, and a new Python dependency, "google-cloud-secret-manager", has been introduced. The changes ensure the project can build and run with the new Beam release candidate, facilitating early detection of potential issues.

Highlights

  • Apache Beam Version Update: The core Apache Beam version has been upgraded to "2.69.0rc1" across both Java (Maven) and Python dependencies.
  • Maven Repository Configuration: A specific Maven repository URL ("https://repository.apache.org/content/repositories/orgapachebeam-1413") has been added to fetch the Beam release candidate.
  • Maven Profile Activation Change: The "validateCandidate" Maven profile activation logic in "pom.xml" was modified to activate based on the JDK version ("[1.)") instead of "activeByDefault".
  • Python Dependency Resolution Updates: The "requirements.txt" file has been extensively updated to reflect the new Beam version, including regenerated dependency hashes and corrected relative paths in comments.
  • New Python Dependency: "google-cloud-secret-manager" has been added as a new dependency in the Python "requirements.txt".
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.

@codecov
Copy link

codecov bot commented Oct 17, 2025

Codecov Report

❌ Patch coverage is 14.28571% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.97%. Comparing base (4f263f6) to head (0459b07).
⚠️ Report is 3 commits behind head on main.

Files with missing lines Patch % Lines
...le/cloud/teleport/spanner/spannerio/SpannerIO.java 14.28% 12 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #2892      +/-   ##
============================================
- Coverage     50.06%   49.97%   -0.09%     
- Complexity     4967     5345     +378     
============================================
  Files           967      967              
  Lines         59298    59312      +14     
  Branches       6441     6442       +1     
============================================
- Hits          29688    29642      -46     
- Misses        27505    27567      +62     
+ Partials       2105     2103       -2     
Components Coverage Δ
spanner-templates 70.41% <14.28%> (-0.08%) ⬇️
spanner-import-export 68.86% <14.28%> (-0.20%) ⬇️
spanner-live-forward-migration 79.69% <ø> (ø)
spanner-live-reverse-replication 77.42% <ø> (ø)
spanner-bulk-migration 88.21% <ø> (ø)
Files with missing lines Coverage Δ
.../java/org/apache/beam/it/gcp/TemplateTestBase.java 0.00% <ø> (ø)
...le/cloud/teleport/spanner/spannerio/SpannerIO.java 68.38% <14.28%> (-0.95%) ⬇️

... and 8 files with indirect coverage changes

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

@Amar3tto Amar3tto requested review from a team as code owners October 17, 2025 16:20
@Amar3tto
Copy link
Collaborator Author

Templates Python Wrapper Module .................... FAILURE [37:08 min]

  CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2530488Z [ERROR]   CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2531928Z [ERROR]   CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2533326Z [ERROR]   CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2534876Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2536320Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2538262Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2539710Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2541163Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2542622Z [ERROR]   TextIOToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution

@Amar3tto
Copy link
Collaborator Author

Amar3tto commented Oct 20, 2025

Templates Python Wrapper Module .................... FAILURE [37:08 min]

  CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2530488Z [ERROR]   CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2531928Z [ERROR]   CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2533326Z [ERROR]   CSVToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2534876Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2536320Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2538262Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2539710Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2541163Z [ERROR]   JdbcToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution
2025-10-17T18:53:19.2542622Z [ERROR]   TextIOToBigQueryIT>TemplateTestBase.setUpBase:253->TemplateTestBase.getSpecPath:306 » UncheckedExecution

The reason is customGcsTempLocation parameter, which is bigQueryLoadingTemporaryDirectory in DataflowTemplates. We need to set it during staging

@Abacn
Copy link
Contributor

Abacn commented Oct 20, 2025

The reason is customGcsTempLocation parameter, which is bigQueryLoadingTemporaryDirectory in DataflowTemplates. We need to set it during staging

This sounds a upstream breaking change. Any clue why "bigQueryLoadingTemporaryDirectory" becomes needed in Beam 2.69.0 ?

checked that the check in Beam has always been there though: https://github.com/apache/beam/blob/af748d07a1a7ca244ff057554d68932c014d5eeb/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java#L3100

@Amar3tto
Copy link
Collaborator Author

The reason is customGcsTempLocation parameter, which is bigQueryLoadingTemporaryDirectory in DataflowTemplates. We need to set it during staging

This sounds a upstream breaking change. Any clue why "bigQueryLoadingTemporaryDirectory" becomes needed in Beam 2.69.0 ?

checked that the check in Beam has always been there though: https://github.com/apache/beam/blob/af748d07a1a7ca244ff057554d68932c014d5eeb/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java#L3100

It only relates to staging, I think it is because of apache/beam#36209. (.get())
Value only available at runtime, but accessed from a non-runtime context

@Abacn
Copy link
Contributor

Abacn commented Oct 20, 2025

Thanks @Amar3tto, we should fix #36209 to (customGcsTempLocation.isAccessible() && customGcsTempLocation.get() == null). This essentially breaks BigQueryIO for runtime ValueProvider

@Abacn
Copy link
Contributor

Abacn commented Oct 20, 2025

a good news is Python xlang template tests, used to fail on RC validations, now working after apache/beam#36199

@Amar3tto Amar3tto closed this Oct 21, 2025
@Amar3tto Amar3tto reopened this Oct 21, 2025
@Amar3tto Amar3tto closed this Oct 21, 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