potiuk commented on code in PR #25121: URL: https://github.com/apache/airflow/pull/25121#discussion_r923390120
########## docs/apache-airflow/howto/dynamic-dag-generation.rst: ########## @@ -140,3 +140,20 @@ Each of them can run separately with related configuration .. warning:: Using this practice, pay attention to "late binding" behaviour in Python loops. See `that GitHub discussion <https://github.com/apache/airflow/discussions/21278#discussioncomment-2103559>`_ for more details + + +Optimizing DAG parsing in workers/Kubernetes Pods Review Comment: > This trick works regardless of the chosen executor, right? Correct. > Should we mention k8s here? Yeah. We should not. I think it's just mostly "namiing" problem. There is nothing K8S-specific here. We can simply mention "when your task is being executed" rather than mentioning K8S POd or Worker. The thing is that people don't generaly realise that no-matter which executor they use, the task is actually executed with the right "airflow run task" command - for most people this is an implementation detail that they do not know. But in this case we are talking about optimisation which is on such a level, that educating the users about it, mighy make sense. Let me rephrase it. -- 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]
