Hi everyone,

I recently started a thread about scoping out this feature, and with the feedback there and a lot of exploring and thinking James Timmins and I have come up with the following AIP

<https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-39+Richer+scheduler_interval>

To quote the AIP: we propose a new name for execution_date, introduce a new concept called "data interval", and present an interface for more powerful pluggable scheduling behaviours.

Once we have this feature in place we have the ability to give users much more control over /when/ their DAGs are scheduled, and hopefully we also remove one of the long standing difficult concepts to learn, that of the "execution_date", by replacing it with a more explicit concept of data_interval.

Feedback appreciated, and I would ask that we don't bike shed /too/ much on the name of things, but alternative suggestions are appreciated, as we want to find something that we don't have to rename again in the future :)

Thanks,
Ash and James

Reply via email to