Skip to content
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

Update bigtable to use operation.future #3623

Merged
merged 1 commit into from
Jul 20, 2017
Merged

Update bigtable to use operation.future #3623

merged 1 commit into from
Jul 20, 2017

Conversation

theacodes
Copy link
Contributor

@theacodes theacodes commented Jul 18, 2017

Towards #3617

NOTE: This is a breaking change. Bigtable previously returned google.cloud.operation instances from long-running operations, it now returns google.cloud.future.operation instances.

@theacodes theacodes added api: bigtable Issues related to the Bigtable API. DevEx labels Jul 18, 2017
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jul 18, 2017
@theacodes
Copy link
Contributor Author

@dhermes @lukesneeringer this is ready for review.

Copy link
Contributor

@dhermes dhermes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM though I have two concerns:

  • I wish you'd separate the bugfix in _prepare_create_request (where you add location to the request payload) into a new PR
  • It'd be nice to get CircleCI green, especially for these system tests with the changes (have you run them?)

@@ -49,7 +44,8 @@ def _prepare_create_request(cluster):
parent=cluster._instance.name,
cluster_id=cluster.cluster_id,
cluster=data_v2_pb2.Cluster(
serve_nodes=cluster.serve_nodes,
location=cluster.location,
serve_nodes=cluster.serve_nodes

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@@ -65,27 +64,6 @@ class Config(object):
IN_EMULATOR = False


def _wait_until_complete(operation, max_attempts=5):

This comment was marked as spam.

@theacodes
Copy link
Contributor Author

Rebased, will merge when CI is green.

@dhermes
Copy link
Contributor

dhermes commented Jul 20, 2017

😀 Yay!

@theacodes theacodes merged commit 1ed681b into master Jul 20, 2017
@theacodes theacodes deleted the bigtable-future branch July 20, 2017 18:00
landrito pushed a commit to landrito/google-cloud-python that referenced this pull request Aug 21, 2017
landrito pushed a commit to landrito/google-cloud-python that referenced this pull request Aug 22, 2017
landrito pushed a commit to landrito/google-cloud-python that referenced this pull request Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigtable Issues related to the Bigtable API. cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants