alessio-giuliano-pix4d commented on issue #52145: URL: https://github.com/apache/airflow/issues/52145#issuecomment-4395958278
I just spent a good amount of time trying to debug an issue with data interval start being equal to the end. It seems that the documentation does not reflect the actual behavior. From: https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/timetable.html#differences-between-trigger-and-data-interval-timetables > A trigger timetable (CronTriggerTimetable or DeltaTriggerTimetable) does not address the concept of data interval, while a “data interval” one (CronDataIntervalTimetable or DeltaDataIntervalTimetable) does. From: https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/timetable.html#whether-taking-care-of-data-interval > For a data interval timetable, the value of data_interval_start and data_interval_end are different. data_interval_end is the time when a Dag run is triggered, while data_interval_start is the start of the interval. From: https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/timetable.html#crondataintervaltimetable > CronDataIntervalTimetable > A timetable that accepts a cron expression, creates data intervals according to the interval between each cron trigger points, and triggers a Dag run at the end of each data interval. (...) Select this timetable by providing a valid cron expression as a string to the schedule parameter of a Dag, as described in the Dags documentation. With the default config, providing a cron expression as the schedule parameter gives the same value for `data_interval_start` and `data_interval_end`, which contradicts the documentation. -- 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]
