GitHub user novandwiatmaja edited a comment on the discussion: Airflow 3:
data_interval_end == data_interval_start?
If you set AIRFLOW__SCHEDULER__CREATE_CRON_DATA_INTERVALS=True, I think that’s
not the best decision, as it’s not future-proof.
Instead, I took a different approach using:
```
from airflow.timetables.interval import CronDataIntervalTimetable
schedule = CronDataIntervalTimetable("0 0 * * *", timezone="UTC")
```
For existing tasks, the interval may not change unless you delete the
historical task data from the database. However, future DAG runs will follow
the correct data interval start and end.
GitHub link:
https://github.com/apache/airflow/discussions/51371#discussioncomment-14033499
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
