-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Clarify coders for side inputs on err output. #27568
Clarify coders for side inputs on err output. #27568
Conversation
Codecov Report
@@ Coverage Diff @@
## master #27568 +/- ##
=======================================
Coverage 71.14% 71.15%
=======================================
Files 861 861
Lines 104560 104570 +10
=======================================
+ Hits 74389 74402 +13
+ Misses 28621 28619 -2
+ Partials 1550 1549 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 4 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Assigning reviewers. If you would like to opt out of this review, comment R: @jrmccluskey for label go. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Clarify coders for side inputs on err output. * error tracking in harness. --------- Co-authored-by: lostluck <13907733+lostluck@users.noreply.github.com>
* Clarify coders for side inputs on err output. * error tracking in harness. --------- Co-authored-by: lostluck <13907733+lostluck@users.noreply.github.com>
Tiny change that was necessary to understand how prism was mis-matching coders. Clarify bundle construction failures as part of ProcessBundle, and fail the instruction. Ensure data errors are treated as errors.
See #27550 and #24789.
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.md
with 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.