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
[BEAM-9487] Disable allowing unsafe triggers by default #15340
Conversation
All test failures are from a known problem related to Panda and are unrelated to this change. Here's the test for reference, and it has a skip message calling this out:
|
Should |
R: @aaltay |
@@ -2332,22 +2332,19 @@ def expand(self, pcoll): | |||
|
|||
unsafe_reason = trigger.may_lose_data(windowing) | |||
if unsafe_reason != DataLossReason.NO_POTENTIAL_LOSS: | |||
reason_msg = str(unsafe_reason).replace('DataLossReason.', '') | |||
if pcoll.pipeline.allow_unsafe_triggers: |
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.
Just double checking. Is this (pcoll.pipeline.allow_unsafe_triggers
) correct? Would not it be something like pcoll.pipeline.options.allow_unsafe_triggers
?
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.
options
is marked as deprecated with the message, "References to <pipeline>.options will not be supported."
For that reason, I added a property to access the option:
beam/sdks/python/apache_beam/pipeline.py
Line 243 in b0e9f26
def allow_unsafe_triggers(self): |
Yes, please also update the changes.md file for 2.33.0 (or whichever the release this will be part of). |
Updated CHANGES.md to both call out the deprecation in 2.32 and note the breaking change for 2.33. |
Codecov Report
@@ Coverage Diff @@
## master #15340 +/- ##
==========================================
- Coverage 83.81% 83.68% -0.13%
==========================================
Files 440 440
Lines 59795 60292 +497
==========================================
+ Hits 50116 50458 +342
- Misses 9679 9834 +155
Continue to review full report at Codecov.
|
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.
I agree. But let's try one more time. Feel free to merge after the next run. |
Run Python PreCommit |
In the release notes for Beam 2.31, there were two deprecations mentioned that affect GroupByKey in the Python SDK:
This PR making that change in anticipation of the upcoming Beam 2.33 release.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner
compliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.