Skip to content

Update to Beam 2.71.0#3222

Merged
damccorm merged 12 commits intomainfrom
users/damccorm/2.71.0-validation-2
Jan 23, 2026
Merged

Update to Beam 2.71.0#3222
damccorm merged 12 commits intomainfrom
users/damccorm/2.71.0-validation-2

Conversation

@damccorm
Copy link
Copy Markdown
Contributor

@damccorm damccorm commented Jan 15, 2026

No description provided.

@damccorm damccorm mentioned this pull request Jan 15, 2026
Draft
@gemini-code-assist
Copy link
Copy Markdown

gemini-code-assist bot commented Jan 15, 2026

Summary of Changes

Hello @damccorm, 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 focuses on updating the project's dependencies to a newer release candidate of Apache Beam. It involves modifying the Maven build configuration to point to the new Beam version and repository, as well as updating numerous Python dependency files to reflect the new Beam version and introduce several new related Python packages. The changes ensure compatibility and leverage the latest features or fixes from the updated Beam version and its ecosystem.

Highlights

  • Apache Beam Version Update: The core Apache Beam version has been updated from 2.70.0 to 2.71.0 in the pom.xml file, and Python dependencies for Apache Beam have been updated to 2.71.0rc2 across various requirements.txt files.
  • Maven Repository Configuration: A new Apache Beam Maven repository URL (https://repository.apache.org/content/repositories/orgapachebeam-1421) has been added to pom.xml to fetch the updated Beam artifacts.
  • Build Profile Activation Logic: The activation logic for the validateCandidate Maven profile in pom.xml has been changed from activeByDefault to a JDK version range [1.).
  • Python Dependency Updates: Several Python dependencies, including beartype (from 0.21.0 to 0.22.9) and numpy (from 2.2.6 to 2.4.0), have been updated, along with their corresponding SHA256 hashes for integrity verification.
  • New Python Dependencies Introduced: New Python packages such as betterproto, envoy-data-plane, grpclib, h2, hpack, and hyperframe have been added to the requirements.txt files, indicating new functionalities or updated dependency trees.
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
Copy Markdown

codecov bot commented Jan 15, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.92%. Comparing base (200724c) to head (531ee88).
⚠️ Report is 27 commits behind head on main.

Additional details and impacted files 
@@             Coverage Diff              @@
##               main    #3222      +/-   ##
============================================
+ Coverage     50.84%   50.92%   +0.08%     
- Complexity     5135     5537     +402     
============================================
  Files           976      977       +1     
  Lines         60106    60351     +245     
  Branches       6575     6596      +21     
============================================
+ Hits          30562    30735     +173     
- Misses        27391    27463      +72     
  Partials       2153     2153
Components Coverage Δ
spanner-templates 71.02% <ø> (+0.04%) ⬆️
spanner-import-export 69.06% <ø> (+0.18%) ⬆️
spanner-live-forward-migration 80.12% <ø> (+0.01%) ⬆️
spanner-live-reverse-replication 77.68% <ø> (-0.08%) ⬇️
spanner-bulk-migration 88.45% <ø> (+0.01%) ⬆️
see 21 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.

@damccorm
Copy link
Copy Markdown
Contributor Author

damccorm commented Jan 15, 2026

This is running into the same problems as the last rc :( I'm not sure why yet. I did confirm that https://repository.apache.org/content/repositories/orgapachebeam-1421/org/apache/beam/beam-sdks-java-io-google-cloud-platform/2.71.0/ should contain the correct Spanner version...

@damccorm damccorm mentioned this pull request Jan 15, 2026
Closed
3 tasks
@damccorm
Try snapshot after publishing apache/beam#37323
d85fc02 
Updated Beam version to SNAPSHOT and changed Maven repository URL.
@damccorm damccorm mentioned this pull request Jan 16, 2026
Merged
3 tasks
@damccorm
Copy link
Copy Markdown
Contributor Author

damccorm commented Jan 16, 2026

mvn help:effective-pom -Dartifact=org.apache.beam:beam-sdks-java-google-cloud-platform-bom:2.71.0 still shows

      <dependency>
        <groupId>com.google.cloud</groupId>
        <artifactId>google-cloud-spanner</artifactId>
        <version>6.105.0</version>
      </dependency>

which is probably the issue. I'll dig in more here.

@damccorm damccorm mentioned this pull request Jan 16, 2026
Open
17 tasks
@damccorm damccorm changed the title [DO NOT MERGE] Validate Beam 2.71.0rc2 [DO NOT MERGE] Validate Beam 2.71.0rc3 Jan 16, 2026
damccorm
damccorm commented Jan 17, 2026
View reviewed changes
@damccorm damccorm changed the title [DO NOT MERGE] Validate Beam 2.71.0rc3 Update to Beam 2.71.0 Jan 22, 2026
@damccorm damccorm marked this pull request as ready for review January 23, 2026 13:08
@damccorm damccorm requested a review from Abacn January 23, 2026 13:08
Abacn
Abacn reviewed Jan 23, 2026
View reviewed changes
Abacn
Abacn previously approved these changes Jan 23, 2026
View reviewed changes
@damccorm damccorm merged commit 2c55616 into main Jan 23, 2026
66 of 68 checks passed
@damccorm damccorm deleted the users/damccorm/2.71.0-validation-2 branch January 23, 2026 19:24
MnkyGns pushed a commit to MnkyGns/DataflowTemplates that referenced this pull request Feb 12, 2026
@damccorm @MnkyGns
Update to Beam 2.71.0 (GoogleCloudPlatform#3222)
3a71e17 
* [DO NOT MERGE] Validate Beam 2.71.0rc1

* Update to RC 2

* regen

* Try snapshot after publishing apache/beam#37323

Updated Beam version to SNAPSHOT and changed Maven repository URL.

* Update to rc3

* not snapshot

* temporarily clear java cache

* temporarily clear java cache

* Use non-rc 2.71

* Add back missing line
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Abacn Abacn Abacn approved these changes

Assignees

No one assigned

Labels

package-upgrade size/XXL

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@damccorm @Abacn