Good idea. Personally I think changing the import might be easier to read, but having a DAG policy is better if the goal is to rewrite DAG files as little as possible.
Not sure if that’s a goal I’d agree with, but that’s not my decision to make 😛 I’ll find a way to add it to the document. > On Jul 16, 2024, at 15:07, Abhishek Bhakat > <abhishek.bha...@astronomer.io.INVALID> wrote: > > Seems nice. For the 2nd proposed change, I'm thinking another method for > compat may be a dag_policy that drop-in replaces the params of any Operator. > > Avi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
