Schedule requirement for subdags #7979
Description
Apache Airflow version: 1.7.1.3
Ticket was created 19/Jan/17 15:25
Kubernetes version (if you are using kubernetes) (use kubectl version):
Environment:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a): - Install tools:
- Others:
What happened:
I suspect this to be a known problem but I failed to find an issue about this. Its confusing enough I thought to raise it just in case.
The docs say:
SubDAGs must have a schedule and be enabled. If the SubDAG’s schedule
is set to None or @once, the SubDAG will succeed without having done
anything
And further googling reveals this is because subdags are implemented as a backfill job.
As a user I find this very confusing. I see subdags as just a convenient logical grouping. Why should they need their own schedule, never mind it not being allowed certain values. Im assuming you can just put whatever value and that it just gets ignored. For it wouldnt make logical sense to have your subdag run at a different schedule then the encompassing dag. But I admit to not having explicitly tested that yet.
What you expected to happen:
How to reproduce it:
Anything else we need to know:
Moved here from https://issues.apache.org/jira/browse/AIRFLOW-769