| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@tseaver Rebased on top of `master. PTAL. |
Sorry, something went wrong.
|
@tseaver PTAL. (So you can at least get a feel for how stubs are created and how they work.) |
Sorry, something went wrong.
|
What would be smoothest? I dropped off reviewing this one because it seemed like #1159 was the Right Thing(TM) for dealing with the wonky gRPC dependency. I can go ahead an review here, with the notion that we will split out the per-API projects later. |
Sorry, something went wrong.
|
I think #1159 would be smoothest. If we decide NOT to split out into sub-packages then we can revive this. |
Sorry, something went wrong.
Sorry, something went wrong.
For now, just adding custom getters which will tell users whether the Client has been started. Commit to add methods to actually make the stubs and start the Client will be forthcoming.
This creates gRPC stubs for talking to each Bigtable service needed by the client.
In particular, explaining why we __enter__ them but have no corresponding __enter__ for our users.
|
@tseaver PTAL. I added a comment in the 3rd commit. |
Sorry, something went wrong.
|
LGTM. |
Sorry, something went wrong.
Adding gRPC stubs to Bigtable clients
I've confirmed that the unit tests in python-compute are still passing with this change. Fixes #1154
Source-Link: googleapis/synthtool@bd9ede2 Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:04c35dc5f49f0f503a306397d6d043685f8d2bb822ab515818c4208d7fb2db3a Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com> Co-authored-by: Tim Sweña (Swast) <swast@google.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com> Co-authored-by: mukund-ananthu <83691193+mukund-ananthu@users.noreply.github.com> Co-authored-by: Anthonios Partheniou <partheniou@google.com>
| Back | FazBrowse Home | New Git URL |
NOTE: Uses #1153 as diffbase