docs: add samples from bigtable #38
Conversation
…rm/python-docs-samples#371) * Add Bigtable hello world sample. * Update secrets for Bigtable tests.
Also, change the sample to use sequential keys (with a disclaimer) to match the Java sample. I had forgotten to add a sample usage to get a specific row, so add that, too.
…table Add region tags to bigtable/hello sample.
I noticed that the `bigtable/hello` sample was not quitting when I sent a `Ctrl-C` this should fix that problem.
…table Close HappyBase connection in bigtable/hello sample.
This sample uses the "raw" [gcloud-python Cloud Bigtable package](https://googlecloudplatform.github.io/gcloud-python/stable/bigtable-usage.html).
This sample uses the "raw" [gcloud-python Cloud Bigtable package](https://googlecloudplatform.github.io/gcloud-python/stable/bigtable-usage.html).
…table bigtable: add raw gcloud-python hello sample.
…table bigtable: add raw gcloud-python hello sample.
Table of Contents generated with:
doctoc --title '**Table of Contents**' bigtable
Needs to wait for next gcloud-python launch. Tested locally with a
previous version of grpcio.
Table of Contents generated with:
doctoc --title '**Table of Contents**' bigtable
Needs to wait for next gcloud-python launch. Tested locally with a
previous version of grpcio.
…table-v2 Update Bigtable samples to v2.
…table-v2 Update Bigtable samples to v2.
Change-Id: I6bf9a8acb9ba7d067b3095b5857094cbc322ff58
Change-Id: I6bf9a8acb9ba7d067b3095b5857094cbc322ff58
googlebot
added
the
cla: no
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
googlebot
added
cla: yes
busunkim96
changed the title
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
googlebot
added
cla: no
busunkim96
added
cla: yes
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
busunkim96
added
the
kokoro:force-run
yoshi-kokoro
removed
the
kokoro:force-run
kolea2
added
the
kokoro:force-run
yoshi-kokoro
removed
the
kokoro:force-run
busunkim96
added
the
automerge
|
@kolea2 Any idea what's up with the system tests? It seems to consistently be the same failure |
|
Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR |
1 similar comment
|
Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR |
|
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
kolea2
added
the
kokoro:force-run
yoshi-kokoro
removed
the
kokoro:force-run
Samples from https://github.com/GoogleCloudPlatform/python-docs-samples/tree/master/bigtable
Samples are unaltered.