potiuk commented on issue #28371:
URL: https://github.com/apache/airflow/issues/28371#issuecomment-1367928949
This is not how Airflow works in a distributed way. The architecture of
Airflow is very explicit and specific about that. Airlow does not take care
about DAG distribution on its own - it is delegated to the appropriate
deployment mechanisms. We simply do not want to implement somethign that other,
existing mechanisms are dedicated to (and they are much better than Airflow in
doing so).
This is a fundamental change in the architecture and if you would like to
pursue that idea (though I can tell you, it's very unlikely to happen), Feature
request is not nearly enough. You would have to start a devlist discussion,
prepare a complete Airflow Improvoment Proposal and convince others that it
makes sense (that should include a detailed proposal on how you want to solve
all the cases of distributed environment challenges). See
https://airflow.apache.org/community/ tor the relevant links for the devlist
and
https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals
for the proposals.
Closing this as "no implement" - but if you are not discouraged - follow the
path I explained.
--
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]
