potiuk edited a comment on issue #20073: URL: https://github.com/apache/airflow/issues/20073#issuecomment-986928222
The "triggering" time is a bad idea for specifying custom schedules, because the DAGs are already created and scheduled. The DAG Run that you mention is only single DAG execution, and since you are triggering it - by definition it has no schedule, because this is jus single "execution" of the DAG Run - it has "no schedule" at the point you trigger it (because this is a DAG Run , not DAG). There is no way we can change "schedule" by submitting a DAG Run at this point - it's just logically impossible :). And It simply not the right "place" - the UI / API are not supposed to change anything in DAG definition (at least not yet). For now the only way how you can modify the DAG is via parsing DAG file coming from the DAG_FOLDER directory. There is no other way (for now) However as of Airflow 2.2 you hav custom timetables that might help you a bit to manage complex schedules There is no way we can change "schedule" by submitting a DAG at this point. It simply not the right way - also the UI / API are not supposed to change anythin in DAG definition.(stll with using DAG Factories ) but I am not sure if it addresses your problem. https://airflow.apache.org/docs/apache-airflow/2.2.0/howto/timetable.html Also there are some AIPs - Airflow Improvement Proposals (which we are not actively working on right now) - for example https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-5+Remote+DAG+Fetcher - that might better fit your rrequirements. But this will take quite a while likely as it is not at all priority for anyone that I know would work on -- 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]
