-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
[AIRFLOW-4232] Add none_skipped
trigger rule
#5032
Conversation
7389070
to
a308e4d
Compare
Codecov Report
@@ Coverage Diff @@
## master #5032 +/- ##
==========================================
- Coverage 76.23% 76.23% -0.01%
==========================================
Files 466 466
Lines 30098 30105 +7
==========================================
+ Hits 22946 22951 +5
- Misses 7152 7154 +2
Continue to review full report at Codecov.
|
there is already a trigger_rule= |
a308e4d
to
ad60239
Compare
Hi @kaxil thanks for looking into my PR. Currently, So unfortunately |
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.
Looks mostly good, I'd just like a bit more tests please
ad60239
to
b28ace2
Compare
Looks like you have a test failure:
|
0f9b28f
to
dfad1d7
Compare
upstream_failed=0, | ||
done=2, | ||
flag_upstream_failed=False, | ||
session=session)) |
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 assume there was the AttributeError: 'str' object has no attribute 'merge'
because we were just passing a str instead of an actual session.
Downstream tasks should run as long as their parents are in `success`, `failed`, or `upstream_failed` states.
dfad1d7
to
d8b696d
Compare
|
I've made an update to this branch to try and fix those tests @cmdoptesc - I didn't realise that none of the other paths hit the upstream_failed path :/ |
Thanks a million @ashb 💯 Yeah, all the other tests were just using strings, which would probably error out if the |
Downstream tasks should run as long as their parents are in `success`, `failed`, or `upstream_failed` states.
Downstream tasks should run as long as their parents are in `success`, `failed`, or `upstream_failed` states.
Downstream tasks should run as long as their parents are in `success`, `failed`, or `upstream_failed` states.
Downstream tasks should run as long as their parents are in `success`, `failed`, or `upstream_failed` states.
Downstream tasks should run as long as their parents are in `success`, `failed`, or `upstream_failed` states.
Make sure you have checked all steps below.
Jira
Description
Add a "none_skipped" trigger rule so that downstream tasks will only run if all their upstream tasks have succeeded or failed.
Example:
Task 1 >> Task 2
If Task 1 succeeds or fails, Task 2 should drop the temp table as cleanup. However if the task never runs, we should just skip it.
Or perhaps Task 2 is a logging task that only logs successes and failures, but doesn't log skips to cut down on noise.
Tests
Commits
Documentation
Code Quality
flake8