novandwiatmaja commented on issue #52145:
URL: https://github.com/apache/airflow/issues/52145#issuecomment-3163544296
If you set AIRFLOW__SCHEDULER__CREATE_CRON_DATA_INTERVALS=True, I feel like
that’s not the best choice—it’s not really future-proof.
I went with a different approach using:
```
from airflow.timetables.interval import CronDataIntervalTimetable
schedule = CronDataIntervalTimetable("0 0 * * *", timezone="UTC")
```
For tasks that have already run, the interval probably won’t change—unless
you delete the historical task data from the database. But for the next DAG
runs, it should use the correct start and end of the data interval.
--
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]