dabla commented on PR #37937: URL: https://github.com/apache/airflow/pull/37937#issuecomment-1994873785
> > > (as long as tests are fixed that is :) ) > > > > > > I'm working on that I hope I will have them fix today. > > But now my question remains, do we really throw an Exception when bad mixing is being detected, or do we log a warning message? As this will have a huge impact on those doing bad things in DAG's :) At the moment the code is throwing an AirflowException. We could opt for a transition period and first log a warning message like stating: "Hey, you are doing bad operator mixing, this won't be allowed anymore in for example Airflow 2.9+!". > > I think we could turn error on in 2.9.0 but allow for an escape hatch (ugly) if somoene wants to continue using it for "now". The hack will have to be ugly - say `allow_wrong_operator_usage` in the operator's constructor -- it should also be poorly documented and explained as a a hack - with explanation how one can use taskflow + hooks for example to achieve similar effect. Good idea. Another idea I suddenly thought of is that we could add an Airflow config parameter which determines that, like we have the config parameter for the unit_test_mode, than having some good named parameter which enables/disables this option. Just thinking out loud. -- 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]
