[
https://issues.apache.org/jira/browse/AIRFLOW-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Kodama updated AIRFLOW-4726:
-------------------------------
Description:
When there are duplicate operator task ids, it raises `_Broken DAG: Cycle
detected in DAG. Faulty task: foo to foo_`.
This error message is ambiguous, so I suggest that `_Broken DAG: duplicate task
ids. ~~~_` is better.
I examined this case on my local environment (Airflow version: 1.10.3).
DAG script and error messages are on Attachment.
(I changed [https://airflow.apache.org/tutorial.html] a little to make this DAG
script.)
was:
When there are duplicate operator task ids, it raises `Broken DAG: Cycle
detected in DAG. Faulty task: foo to foo`.
This error message is ambiguous, so I suggest that `Broken DAG: duplicate task
ids. ~~~` is better.
I examined this case on my local environment (Airflow version: 1.10.3).
DAG script and error messages are on Attachment.
(I changed [https://airflow.apache.org/tutorial.html] a little to make this DAG
script.)
> Duplicate operator task ids raise inappropriate error message
> -------------------------------------------------------------
>
> Key: AIRFLOW-4726
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4726
> Project: Apache Airflow
> Issue Type: Improvement
> Components: DAG
> Affects Versions: 1.10.3
> Reporter: Yu Kodama
> Assignee: Yu Kodama
> Priority: Minor
> Attachments: airflow_admin.png, duplicate_operators.py
>
>
> When there are duplicate operator task ids, it raises `_Broken DAG: Cycle
> detected in DAG. Faulty task: foo to foo_`.
> This error message is ambiguous, so I suggest that `_Broken DAG: duplicate
> task ids. ~~~_` is better.
>
> I examined this case on my local environment (Airflow version: 1.10.3).
> DAG script and error messages are on Attachment.
> (I changed [https://airflow.apache.org/tutorial.html] a little to make this
> DAG script.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
