Skip to content

Switch Lakehouse from v1beta to v1 - #4118

Open
feefs wants to merge 1 commit into
GoogleCloudPlatform:mainfrom
feefs:main
Open

Switch Lakehouse from v1beta to v1#4118
feefs wants to merge 1 commit into
GoogleCloudPlatform:mainfrom
feefs:main

Conversation

@feefs

@feefs feefs commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Lakehouse's Iceberg REST Catalog went GA last November (https://cloud.google.com/blog/products/data-analytics/biglake-metastore-now-supports-iceberg-rest-catalog), so we should be using the v1 api instead of v1beta.

@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 updates the integration tests to use the stable v1 API for the Iceberg REST Catalog. This change ensures that the test suite reflects the current production-ready state of the BigLake Metastore, replacing the deprecated v1beta endpoint.

Highlights

  • API Version Update: Updated the Iceberg REST Catalog URI from v1beta to v1 across all integration tests to align with the GA release of the BigLake Metastore.
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.

@google-cla

google-cla Bot commented Aug 6, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@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 BigLake Iceberg REST catalog URI from the v1beta endpoint to the stable v1 endpoint across multiple integration test files. There are no review comments, so I have no feedback to provide.

@derrickaw derrickaw added the improvement Making existing code better label Aug 7, 2026
@codecov

codecov Bot commented Aug 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.08%. Comparing base (3a2bdfd) to head (5c17fc2).
⚠️ Report is 4 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (3a2bdfd) and HEAD (5c17fc2). Click for more details.

HEAD has 3 uploads less than BASE
Flag BASE (3a2bdfd) HEAD (5c17fc2)
4 1
Additional details and impacted files
@@              Coverage Diff              @@
##               main    #4118       +/-   ##
=============================================
- Coverage     56.16%   38.08%   -18.08%     
+ Complexity     7336      511     -6825     
=============================================
  Files          1126      195      -931     
  Lines         68708    11764    -56944     
  Branches       7777     1179     -6598     
=============================================
- Hits          38587     4480    -34107     
+ Misses        27626     6919    -20707     
+ Partials       2495      365     -2130     
Components Coverage Δ
spanner-templates ∅ <ø> (∅)
spanner-import-export ∅ <ø> (∅)
spanner-live-forward-migration ∅ <ø> (∅)
spanner-live-reverse-replication ∅ <ø> (∅)
spanner-bulk-migration ∅ <ø> (∅)
gcs-spanner-dv ∅ <ø> (∅)
see 956 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Making existing code better size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants