Uh oh!
There was an error while loading. Please reload this page.
bigtable: Require google-cloud-bigtable>=2.42.0 and test Python BigtableIO write error surfacing - #39820
Merged
damccorm merged 1 commit intoAug 20, 2026
Conversation
mutianfforce-pushed
the
bigtable-python-batcher-error-handling
branch
from
August 19, 2026 16:19
18e9dec to
151f342Comparegoogle-cloud-bigtable 2.42.0 improves MutationsBatcher error handling so that errors raised during async flushes are surfaced instead of being swallowed. Bump the minimum version and add BigtableIO write tests that assert batch errors are surfaced (and fail the bundle) from the async flush path, the buffered-row flush at finish_bundle, and close() itself.
mutianfforce-pushed
the
bigtable-python-batcher-error-handling
branch
from
August 19, 2026 16:27
151f342 to
c50d361CompareContributor
Assigning reviewers: R: @shunping for label python. Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
Uh oh!
There was an error while loading. Please reload this page.
damccorm added a commit
that referenced
this pull request
Aug 20, 2026
…39820) (#39831) google-cloud-bigtable 2.42.0 improves MutationsBatcher error handling so that errors raised during async flushes are surfaced instead of being swallowed. Bump the minimum version and add BigtableIO write tests that assert batch errors are surfaced (and fail the bundle) from the async flush path, the buffered-row flush at finish_bundle, and close() itself. Co-authored-by: Mattie Fu <mattiefu@google.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
google-cloud-bigtableto>=2.42.0,<3. 2.42.0 improvesMutationsBatchererror handling so that errors raised during async flushes are surfaced instead of swallowed._BigTableWriteFnwrite tests asserting that batch errors are surfaced (and thus fail the bundle, so the runner retries) from:finish_bundle()/close(),close()itself.Previously a batch-level failure during an asynchronous flush could be dropped without failing the bundle. Requiring 2.42.0 and adding these regression tests guards the error-surfacing behavior end-to-end through Beam.
Fix#39755