clacke commented on issue #5498: [AIRFLOW-4509] SubDagOperator using scheduler
instead of backfill
URL: https://github.com/apache/airflow/pull/5498#issuecomment-538615069
We have solved the problem, and uncovered another problem. Working on
navigating my company's open source contribution
clacke commented on issue #5498: [AIRFLOW-4509] SubDagOperator using scheduler
instead of backfill
URL: https://github.com/apache/airflow/pull/5498#issuecomment-533051838
I can't believe I actually found it.
clacke commented on issue #5498: [AIRFLOW-4509] SubDagOperator using scheduler
instead of backfill
URL: https://github.com/apache/airflow/pull/5498#issuecomment-533049167
Correction: We have actually moved to using `POST
/api/experimental/dags/:dag_id/dag_runs` for triggering the DAG, not
clacke commented on issue #5498: [AIRFLOW-4509] SubDagOperator using scheduler
instead of backfill
URL: https://github.com/apache/airflow/pull/5498#issuecomment-531573202
All DAGs are Schedule: None and the parent is triggered externally with
parameters using [the REST
clacke commented on issue #5498: [AIRFLOW-4509] SubDagOperator using scheduler
instead of backfill
URL: https://github.com/apache/airflow/pull/5498#issuecomment-531572470
I'll construct a minimal example and try things out. The operator creating
the dagrun does sound like what should
clacke commented on issue #5498: [AIRFLOW-4509] SubDagOperator using scheduler
instead of backfill
URL: https://github.com/apache/airflow/pull/5498#issuecomment-531052581
The head of the sub-DAG itself has no dependencies, the only constraint is
that it should only be run when the
clacke commented on issue #5498: [AIRFLOW-4509] SubDagOperator using scheduler
instead of backfill
URL: https://github.com/apache/airflow/pull/5498#issuecomment-530738432
How is this feature intended to work?
I'm finding that if I leave our sub-DAGs paused (as they were with the old
