move existing client back to current namespace #811
Labels
api: bigtable
Issues related to the googleapis/python-bigtable API.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
type: cleanup
An internal cleanup or hygiene concern.
Milestone
At the start of
v3
development, I moved the existing client intogoogle.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 classesAlong with this change, we should make sure required public classes are suffixed with
Async
The text was updated successfully, but these errors were encountered: