fix: respect deadlines for column family operations #687
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a very small fix to specifically address a blocker for a customer. This does not try to address the wider issue of timeouts.
The root of the problem is described here:
googleapis/gapic-generator-python#1477
The tldr is that the default timeouts in base.py are applied by default across all of our RPCs. The only exceptions are ReadRows and MutateRows (and after this PR column operations).
Fixing the broader problem will require coordination with:
googleapis/python-api-core#462
We also need to to flesh out a design for overriding deadlines per method and/or rpc.