[
https://issues.apache.org/jira/browse/AIRFLOW-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924416#comment-16924416
]
jack commented on AIRFLOW-4873:
-------------------------------
[~ash] still I don't understand. If you have a Broken DAG than it's associate
to some place in the code. Some specific row which is associated to a specific
DAG.
I'll explain better the issue. In my company there is a tool which allows to
generate DAGs.
There is no correlation between the .py file name to the dag_id and no one can
access the .py file saved in the dag folder.
The dag_id is a logic name but the .py file is random sequence of numbers.
So in order to fix the issue one must know the dag_id to find it in the Airflow
UI.
> Improve BROKEN DAG error message by specifying dag_id
> ------------------------------------------------------
>
> Key: AIRFLOW-4873
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4873
> Project: Apache Airflow
> Issue Type: Improvement
> Components: ui
> Affects Versions: 1.10.3
> Reporter: jack
> Assignee: Omkar
> Priority: Major
> Labels: easy-fix
>
> In some cases there is a broken DAG message appear in the UI:
>
> {code:java}
> Broken DAG: [/home/airflow/dags/my_dag.py] No module named 'HelperClass'
> {code}
>
> The problem here is that the error indicates only the file name but it
> doesn't specify the dag_id.
> The error could be improved to (or similar):
>
> {code:java}
> Broken DAG: DAG_ID : [/home/airflow/dags/my_dag.py] No module named
> 'HelperClass' {code}
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
