dabla commented on PR #37246: URL: https://github.com/apache/airflow/pull/37246#issuecomment-1937101205
> Also what you could do with this change is likely to implement this: #34860 which will follow the same patterm but by Snowflake Hook We could think of some kind of strategy that is applied for certain hooks/or sqlalchemy dialects. We could have a default strategy, and if a specific strategy is found (base on dialect name for example), then use that one. This is something I was also thinking about now that you mention the above issue. Maybe something for another pull request, as I would like to finish this one as fast as possible as we are also impacted by it. I would also like to take the oppurtunity to add an common SQL operator which allows you to easily persist (insert/replace/upsert) a list of dicts into the database so that you don't need a python operator/decorated task with a hook, something that is now missing in Airflow I. The operator would also simplify the DAG's even more and is also benificient for the DAG processing. We tend to have as less as possible (custom) python code in our DAGs to improve governance and have fast solutions and easy to maintain DAG's which are less error prone. -- 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]
