Bolke de Bruin created AIRFLOW-792:
--------------------------------------
Summary: Allow fixing of schedule when wrong start_date / interval
was specified
Key: AIRFLOW-792
URL: https://issues.apache.org/jira/browse/AIRFLOW-792
Project: Apache Airflow
Issue Type: Improvement
Reporter: Bolke de Bruin
When one uses a dynamic start_date (bad practice, but still often used) that
does not match with the interval (e.g.. start_date != date time.now() -
interval) a DAG might never get scheduled in 1.8, but it sometimes would in 1.7.
For people upgrading from 1.7 certain DAGs suddenly might not be scheduled
anymore.
To fix this one needs to change the start_date and rename the DAG. It is more
user friendly to
1) provide a warning when using datetime.now in start_date (monkey patching
date time.now() when loading a DAG)
2) have an airflow command that allows fixing the schedule in the database so
the same dag name can be retained.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
