[
https://issues.apache.org/jira/browse/AIRFLOW-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147776#comment-17147776
]
ASF subversion and git services commented on AIRFLOW-5500:
----------------------------------------------------------
Commit e1b4fcfa7eba4fa3fd0af00242e1809f7ae75a04 in airflow's branch
refs/heads/v1-10-test from Charles Bournhonesque
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=e1b4fcf ]
[AIRFLOW-5500] Fix the trigger_dag api in the case of nested subdags
Co-authored-by: Charles Bournhonesque <charles.bournhones...@benevolent.ai>
(cherry picked from commit 16e06f802b30ce7c3972b1a8165e3d6327dee761)
> Bug in trigger api endpoint
> ----------------------------
>
> Key: AIRFLOW-5500
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5500
> Project: Apache Airflow
> Issue Type: Bug
> Components: api
> Affects Versions: 1.10.1
> Reporter: Deavarajegowda M T
> Priority: Critical
> Attachments: 3level.py
>
>
> Unable to trigger workflow with nested sub dags, getting following error:
> sqlalchemy.exc.IntegrityError: (psycopg2.IntegrityError) duplicate key value
> (dag_id,execution_date)=('dummy.task1.task_level1.task_level2','2019-09-10
> 13:00:27+00:00') violates unique constraint
> "dag_run_dag_id_execution_date_key"
> trigger_dag for nested sub_dags is called twice.
>
> fix:
> in airflow/api/common/experimental/trigger_dag.py -
> while populating subdags for a dag, each subdag's subdags is also populated
> to main dag.
> So no need to repopulate subdags for each subdag separately.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
