Replies: 1 comment
-
It's best to discuss in in devlist. Discussion here is for small things - the change you propose is proposed to change a fundamental assumption on the DAG. And for that, I think you need also to propose HOW to decouple it. High level design proposal of what it would mean to decouple the schedule. What database changes it would require, how it would impact parsing , scheduling and execution, what to do with custom scheduling and asset scheduling etc. etc. At this stage, it's mostly a vague idea, but in order to seriously discuss it, you have to have at least a rough idea what complexities it involves, which part of the system it touches and what are the consequences |
Beta Was this translation helpful? Give feedback.
-
I’d like to initiate a discussion about decoupling the schedule_interval from the DAG definition in Airflow 3 to allow dynamic scheduling through the API. This feature has been requested by users (example), and I believe it could bring significant flexibility and value to the platform.
Current Behavior
As of now, the
schedule_interval
is tightly coupled to the DAG definition, and attempts to modify it using the REST API result in the following error:This constraint limits the ability to manage DAG schedules dynamically, especially for use cases where the schedule needs to be adjusted programmatically or integrated with external systems. and to be honest i don't see why it was designed like that on the first place ?.
Use Cases
Thank you for considering this proposal. would be happy to collaborate.
Beta Was this translation helpful? Give feedback.
All reactions