potiuk commented on PR #41463:
URL: https://github.com/apache/airflow/pull/41463#issuecomment-2308893314
Hey @raphaelauv -> maybe that is a misunderstanding. We can't really
"remove" soft fail and replace it in the providers "now' - they will still have
to support 2.8 - 2.10, so we cannot **really* remove soft_fail (and tests with
it). This was not really possible in 2.10 and is not really going to be
possible now.
What I really see as the moment we implement it is when we have the new
"task-sdk" in Airflow 3 - this is where it will be providing "Base Sensor" ,
"Base Operator" - and there we will be able to do similar things as with
"common.compat" - where we will be able to add new functionality ("Fail
Policy") without having to be tied with specific Airflow 3 version.
I think the way implemented now it's not really usable - it won't work for
Airfllow 2, and Airflow 3 will have the "sdk" implemented differently, so I am
not sure it's worth spending time on it now. There is no "easy" way of
implementing it without breaking current "2.8, 2.9, 2.10" behaviour.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
