Skip to content

Conversation

@justinseinlin
Copy link
Contributor

/cc @dhermes

As discussed in #4333, this change addresses the input retry=None for mutate_rows. @jonparrott I made an internal error _BigtableRetryableError and have it be used to trigger the retry instead of raising a fake SerivceUnavailable. Would like to get your opinion regarding this use.

Also factored out test response creation and replaced the magic numbers with constants for RPC Status Code. And removed the extra the from the error message.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Nov 3, 2017
@justinseinlin
Copy link
Contributor Author

This is also a follow up on #4256

SUCCESS = 0
RETRYABLE_1 = 4
RETRYABLE_2 = 10
NON_RETRYABLE = 1

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@justinseinlin
Copy link
Contributor Author

@dhermes Can you help setting the relevant label(s) to the PR? Should we normally set assignee as well? I could update neither though.

@lukesneeringer lukesneeringer merged commit e658658 into googleapis:master Nov 6, 2017
@tseaver tseaver added api: bigtable Issues related to the Bigtable API. priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Nov 6, 2017
@justinseinlin justinseinlin deleted the pr-4333-followup branch November 6, 2017 15:40
chemelnucfin pushed a commit to chemelnucfin/google-cloud-python that referenced this pull request Nov 6, 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.

6 participants