-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding basic Bigtable client. #1148
Conversation
""" | ||
|
||
# Prevent creation of Client.connection. | ||
_connection_class = None |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@tseaver PTAL. I plan on squashing into a single commit before merging, but just added a new commit for now so you could see the diff. Two concerns:
|
Also, I'll be teaching until 2pm Pacific tomorrow, then commuting home, but then free for the rest of the week. I'd really like to increase the velocity of these reviews so we can get the Bigtable stuff in by EOQ (it may end up being impossible, but I'd like to at least give it a chance). I've been the bottleneck on the velocity so far (ADDED: and hopefully won't be starting tomorrow afternoon). |
passed falls back to the default inferred from the | ||
environment. | ||
If ``_connection_class`` is :data:`None`, stores the ``credentials`` | ||
on the client instead of the newly created ``connection``. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
LGTM, modulo the note about the out-of-date docstring for |
To do this, had to de-couple some of the existing client behavior from convenience methods since we don't need to use the _connection_class in Bigtable. In particular, we want both the service account factories for the client and the implicit project behavior.
355fa75
to
484113d
Compare
@tseaver I ripped out the comment and squashed the commits into a single one. Merging now. LMK if there are issues and we can roll back. |
FYI @tseaver I am essentially done with the package in https://github.com/dhermes/gcloud-python-bigtable so will now be porting over the code in (hopefully) easy to review chunks.
I'd really like to get this all in by the end of September (end of the quarter).
/cc @jgeewax
NOTE: I am holding off on bringing in documentation until there is working code in here.