| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…n families As a sideeffect this also fixes a bug where the default deadlines were not applied.
🤖 I have created a release *beep* *boop* --- ## [2.13.2](https://togithub.com/googleapis/python-bigtable/compare/v2.13.1...v2.13.2) (2022-10-20) ### Bug Fixes * Respect deadlines for column family operations ([#687](https://togithub.com/googleapis/python-bigtable/issues/687)) ([df2e64a](https://togithub.com/googleapis/python-bigtable/commit/df2e64a79bbd8b28d0991706607af99d539320d1)) --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
| Back | FazBrowse Home | New Git URL |
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.