Airflow 2.3.3 None schedule validation
See original GitHub issueUpdating a scheduled DAG to none schedule gives us a broken dag on 2.3.3:
Broken DAG: [/ingestion/examples/airflow/dags/mysql_metadata.py] Invalid timetable expression: Exactly 5 or 6 columns has to be specified for iterator expression.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
airflow.timetables.interval — Airflow Documentation
The default implementation returns an empty dict. Validate the timetable is correctly specified.
Read more >Release Notes — Airflow Documentation
It controls the 'time to sleep' at the end of the Scheduler loop if nothing was scheduled inside SchedulerJob . Before: [scheduler] processor_poll_interval...
Read more >Configuration Reference — Airflow Documentation
If not specified, then the value is considered as None, meaning that the operators are never timed out by default. Type. integer. Default....
Read more >Best Practices - Apache Airflow
Airflow scheduler tries to continuously make sure that what you have in DAGs is correctly reflected in scheduled tasks. Specifically you should not...
Read more >airflow.timetables.base — Airflow Documentation
last_automated_data_interval (DataInterval | None) – The data interval of the associated DAG's last scheduled or backfilled run (manual runs not considered).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@nahuelverdugo Oh, I see. Thanks for explanation 😃
Hi @stepanof after closing this issue we are able to configure
Noneasschedule_interval.