-
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
Refactor BaseSensorOperator
introduce skip_policy
parameter
#40924
Conversation
d460b23
to
7308b52
Compare
7308b52
to
4b738a2
Compare
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 good overall - had some comments, most of them are regarding documenation and terminology.
@Lee-W - I'd be happy if you could also review it.
216b94d
to
dbb0210
Compare
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.
Nice!
BaseSensorOperator
introduce skip_policy
parameter
@eladkal gentle ping ( I would like to finish this work for airflow 2.10 , so we can trust sensors again in airflow , cause right now we can't have at least once pattern with the soft_fail option ) |
Hey @raphaelauv -> This one broke our canary builds https://github.com/apache/airflow/actions/runs/10107479883/job/27951619130 -> can you also apply the new policy to all the operators that are raising warnings now ? |
Warnings detected in test case(s):
|
BTW, This should be made compatible with Airflow 2.7 + (maybe we could use common.compat provider. In tne meantime, I will revert this one and maybe it will be better if you combine the two together this time ? |
…er (apache#40924)" This reverts commit ba78d54. This is needed because provider tests started to fail and this one should be combined and tested wiht apache#40923 including compatibility.
fix: #40915
never_fail
parameterskip_policy
parametersoft_fail
andsilent_fail
parameters