Skip to content
This repository was archived by the owner on Apr 1, 2026. It is now read-only.

[DRAFT] chore: reorganize client structure#1200

Closed
daniel-sanche wants to merge 5 commits intov3_stagingfrom
admin_alias
Closed

[DRAFT] chore: reorganize client structure#1200
daniel-sanche wants to merge 5 commits intov3_stagingfrom
admin_alias

Conversation

@daniel-sanche
Copy link
Copy Markdown
Contributor

This branch is a proof-of-concept, re-organizing the client structure to be more clear, and adding aliases to protect existing functionality:

  • the legacy/classic client was moved into google.cloud.bigtable.classic
    • imports referencing google.cloud.bigtable remain working as an alias
  • the admin client was moved into google.cloud.bigtable.admin
    • google.cloud.bigtable_admin_v2 remains as an alias
  • internal references were updated to point to new canonical locations

If we go through with this change:

  • add tests to import packages from both locations in different ways, and make sure all imports continue working (ex: import google.cloud.bigtable.Client, from google.cloud.bigtable import Client, etc)
  • update owlbot.py to move gapic generated admin files to new location

@product-auto-label product-auto-label bot added size: xl Pull request size is extra large. api: bigtable Issues related to the googleapis/python-bigtable API. labels Aug 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

api: bigtable Issues related to the googleapis/python-bigtable API. size: xl Pull request size is extra large.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant