Airflow scheduler make it run regardless12/24/2023 ![]() ![]() If you look at the next DAG run in the UI, the logical date is 22:42:33, which is shown as the Next Run value in the Airflow UI. The value in the Data interval end field is 5 minutes later. The logical date is also included in the Run ID field and identifies the DAG run in the Airflow metadata database. Looking at the most recent DAG run, the logical date is 22:37:33, which is displayed in the Data interval start field in the following image. To demonstrate how these concepts work together, consider a DAG that is scheduled to run every 5 minutes. In versions of Airflow 2.2 and earlier, specifying schedule_interval is the only way to define a DAG schedule. Additionally, timetables have to be passed using the timetable parameter, which was deprecated in Airflow 2.4 and later. In Airflow 2.3 and earlier, the schedule_interval is used instead of the schedule parameter and it only accepts cron expressions or timedelta objects. end_date: The last date your DAG will be executed.This parameter is required for your DAG to be scheduled by Airflow. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |