-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Retry for 'mutate_rows' that return retryable errors. #4256
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
Retry for 'mutate_rows' that return retryable errors. #4256
Conversation
…ponses can get overridden by non-retryableresponse.
…or 1) no retry 2) one retry 3) timeout.
…of creating a custom exception. Also update documentation.
…f rows requested.
|
@lukesneeringer Would it be possible to get this reviewed (and possibly merged) before the upcoming repo split? |
|
@lukesneeringer do you have any comments that I should address? |
|
Nope, this seems fine to me. :-) Confirm that you want it merged? |
|
I'm good with merge. |
| from google.api_core.exceptions import Aborted | ||
| from google.api_core.exceptions import DeadlineExceeded | ||
| from google.api_core.exceptions import ServiceUnavailable | ||
| from google.api_core.exceptions import from_grpc_status |
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.
* Marking Bigtable as "dev" after release. * Updating changelog based on #4256.
* Marking Bigtable as "dev" after release. * Updating changelog based on #4256.
Trying a new PR in place of (#4116).
Reason: A mistake was made in
git rebasecommits that are already pushed to remote, where agit mergeshould have been done.