Repository navigation
[Claude] Capture behavior of the BigQueryWrapper during requests - #40357
jrmccluskey wants to merge 2 commits into
Conversation
|
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
7092df9 to
a34dfc4
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #40357 +/- ##
=============================================
+ Coverage 56.16% 79.92% +23.75%
=============================================
Files 1124 488 -636
Lines 178336 82713 -95623
Branches 1489 0 -1489
=============================================
- Hits 100170 66109 -34061
+ Misses 75645 16604 -59041
+ Partials 2521 0 -2521
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
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). |
Implements a framework for capturing the existing behavior of requests sent over the wire via the BigQueryWrapper through the generated apitools client + captures the current behavior of those requests in the success, error, and retry paths. Does not change any prod behavior beyond packaging the golden jsons in Beam for testing purposes. These files are largely meant to be temporary to ensure migration to the modern BQ client does not cause any regressions.
Part of #37261
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.