Start date also makes sense for a cron-based dag with catch-up too though...
On 18 May 2022 16:58:54 BST, Malthe <mbo...@gmail.com> wrote: >On Sat, 14 May 2022 at 11:21, Bas Harenslak <b...@astronomer.io.invalid> wrote: >> I think we have the following options when no start_date is given: >> >> 1. schedule_interval is alias e.g. “@daily” —> is a cron expression >> internally (0 0 * * *), so run at 00:00 >> 2. schedule_interval is cron e.g. “0 0 * * *” —> cron expression >> determines when to run, 00:00:00 here >> 3. schedule_interval is timedelta e.g. “timedelta(days=1)” —> only here we >> have no clear start_date and need something as a cutoff time, would use >> first added date as start_date, e.g. 12:34:56 >> >> So that would still result in deterministic DAG runs. > >I think timedelta (i.e. `DeltaDataIntervalTimetable`) and `start_date` >go hand in hand, perhaps to the point of them fusing into one. > >Cheers
