potiuk commented on pull request #17576: URL: https://github.com/apache/airflow/pull/17576#issuecomment-920781011
I think that might be indeed why @ashb insisted on making that feature experimental - because I see that each one of us has different "use case" in mind when looking at the pre/post hooks. Now when I think of it, it's really closing the gap between more `functional` and more `object oriented` approach of writing DAGs and I think we need to probably figure out a better way of doing that without this hybrid approach where we have Operator classes and functional extensions of them, that does sound like a bit of a "monster hybrid". The thing is - there is nothing "more" that feature adds - you can do everything you do with the pre-/post- hooks currently (also what you do @JavierLopezT ) but in a slightly less verbose way (with less classes and more functions). I do not yet how, but I have a feeling that maybe indeed we should try to find a bit nicer way to incorporate this in the current direction we are taking with more "decorator" / "task" oriented way of writing dags and make sure that the current operator classes ( we have sooo many useful ones) can be much easier integrated with the "functional" way of writing dags and incorporating that pre/post behaviour there. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
