Replies: 3 comments
-
Thanks for opening your first issue here! Be sure to follow the issue template! |
Beta Was this translation helpful? Give feedback.
-
Am I right in thinking that it would schedule those dags, bug not actually run any of the tasks in those dag runs currently? |
Beta Was this translation helpful? Give feedback.
-
yeah, but it doesn't make much sense to create these dag runs with no tasks runnable. We have many users defined the start_date in the default_args and they have some requirements to change the start_date. Sometimes, it's a larger time interval between these two dates, thus it would waste time to waiting for these empty dag runs created and it's also not friendly to show dag runs in web ui as they would see a larger number of empty dags runs. |
Beta Was this translation helpful? Give feedback.
-
Apache Airflow version: v1.10.14
Environment:
uname -a
): Linux aor-k8s-ci-test-01 4.4.0-1111-aws How do you use hooks? #123-Ubuntu SMP Sat Jul 4 02:03:15 UTC 2020 x86_64 x86_64 x86_64 GNU/LinuxWhat happened:
it won't take effect when updating the start_date in the default_args.
e.g. a daily job like this
default_args = { 'owner': 'airflow', 'depends_on_past': False, 'start_date': timezone.datetime(2020, 5, 1) } dag = DAG(dag_id, schedule_interval=timedelta(days=1), max_active_runs=5, catchup=True, default_args=default_args)
It would schedule the first dag run of "2020/05/01" and if we updated start_date above to "2020/10/01", the next dag it would schedule is "2020/05/02" instead of "2020/10/01", which means it would not take effect.
What you expected to happen:
when start_date has changed, the execution_time of the next dag run should not be early than it.
How to reproduce it:
Anything else we need to know:
Beta Was this translation helpful? Give feedback.
All reactions