[
https://issues.apache.org/jira/browse/AIRFLOW-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aizhamal Nurmamat kyzy updated AIRFLOW-769:
-------------------------------------------
Labels: subdag (was: )
Component/s: operators
Adding 'operators' component and 'subdag' label for component refactor.
> Schedule requirement for subdags
> --------------------------------
>
> Key: AIRFLOW-769
> URL: https://issues.apache.org/jira/browse/AIRFLOW-769
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators, subdag
> Affects Versions: 1.7.1.3
> Reporter: Dirk Gorissen
> Priority: Major
> Labels: subdag
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
