Skip to content

Conversation

@mpeddada1
Copy link
Collaborator

@mpeddada1 mpeddada1 commented Jan 7, 2026

Fixes #7356.
Removes deprecated admin classes for spanner and a few unused mocks. Also adds a migration guide.

@product-auto-label product-auto-label bot added the api: spanner Issues related to the Spanner API. label Jan 7, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello @mpeddada1, 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 performs a significant cleanup by eliminating previously deprecated admin classes and their related components from the Spanner client library. This action streamlines the codebase, removes obsolete interfaces, and ensures that the library adheres to its deprecation policy, making it easier to maintain and evolve.

Highlights

  • Removal of Deprecated Admin Classes: The pull request completely removes the deprecated DatabaseAdminClient and InstanceAdminClient classes, along with their corresponding Connection interfaces, implementation files, and header definitions.
  • Cleanup of Build System and Tests: All references to the removed deprecated admin classes have been purged from CMakeLists.txt files, Bazel build definitions (.bzl files), and associated unit and integration tests.

🧠 New Feature in Public Preview: You can now enable Memory 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 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

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 correctly removes the deprecated DatabaseAdminClient and InstanceAdminClient classes, along with their associated connection classes, tests, and build file entries. The changes are clean and align with the goal of removing deprecated code.

I have a few suggestions for further cleanup: the mock files for the removed connection and stub classes appear to be unused now and could also be removed, along with their entries in the build files. I've left specific comments on the test files that used them.

@codecov
Copy link

codecov bot commented Jan 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.88%. Comparing base (a83d81f) to head (6d5a7d3).
⚠️ Report is 1 commits behind head on prepare-for-v3.0.0.

Additional details and impacted files
@@                  Coverage Diff                   @@
##           prepare-for-v3.0.0   #15862      +/-   ##
======================================================
+ Coverage               92.84%   92.88%   +0.03%     
======================================================
  Files                    2417     2398      -19     
  Lines                  222256   218492    -3764     
======================================================
- Hits                   206362   202948    -3414     
+ Misses                  15894    15544     -350     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@devbww
Copy link
Contributor

devbww commented Jan 7, 2026

You should check that the edits/deletions in this PR match those made in the copybara rules used when importing google-cloud-cpp into google3. They should have the same effect.

I don't know whether the google3 import now uses the v3 branch or not (if not, I would suggest that you change it to do so ASAP), but don't forget to remove the copybara rules when this PR is merged into the import branch.

Aside: My recollection is that there are additional copybara rules that remove other deprecated code from google3. You should probably check on the status of those too.

@mpeddada1
Copy link
Collaborator Author

You should check that the edits/deletions in this PR match those made in the copybara rules used when importing google-cloud-cpp into google3. They should have the same effect.

I don't know whether the google3 import now uses the v3 branch or not (if not, I would suggest that you change it to do so ASAP), but don't forget to remove the copybara rules when this PR is merged into the import branch.

Aside: My recollection is that there are additional copybara rules that remove other deprecated code from google3. You should probably check on the status of those too.

hm that's a good point about copybara. I've created a ticket to track this change. cc/ @scotthart

@mpeddada1 mpeddada1 marked this pull request as ready for review January 8, 2026 16:15
@mpeddada1 mpeddada1 requested a review from a team as a code owner January 8, 2026 16:15
@mpeddada1 mpeddada1 requested a review from scotthart January 8, 2026 16:37
Copy link
Member

@scotthart scotthart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ABI dump for spanner will need to be updated to reflect these changes.

@mpeddada1 mpeddada1 requested a review from scotthart January 8, 2026 19:19
@mpeddada1 mpeddada1 merged commit 5cd5046 into googleapis:prepare-for-v3.0.0 Jan 8, 2026
51 of 52 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the Spanner API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants