Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Apr 1, 2026. It is now read-only.
This repository was archived by the owner on Apr 1, 2026. It is now read-only.

move existing client back to current namespace #811

Copy link
Copy link

Description

@daniel-sanche
Issue body actions

At the start of v3 development, I moved the existing client into google.cloud.bigtable.deprecated. For the alpha, we'll need it to be back in it's original namespace.

The new client should be moved to google.cloud.bigtable.data to avoid name collisions with duplicated model classes

Along with this change, we should make sure required public classes are suffixed with Async

Reactions are currently unavailable

Metadata

Metadata

Assignees

Labels

api: bigtableIssues related to the googleapis/python-bigtable API.Issues related to the googleapis/python-bigtable API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: cleanupAn internal cleanup or hygiene concern.An internal cleanup or hygiene concern.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.