airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-415) Make dag_id not found error due to dag failing to parse clearer
Date Fri, 12 Aug 2016 02:27:20 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418270#comment-15418270
] 

ASF subversion and git services commented on AIRFLOW-415:
---------------------------------------------------------

Commit 785dd1901d3fdae3f2b4c92e06c868415ff275a5 in incubator-airflow's branch refs/heads/master
from [~aoen]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=785dd19 ]

[AIRFLOW-415] Make dag_id not found error clearer

When a dag fails to parse and a user tries to run it e.g. via the command line airflow will
give an error "dag_id not found" which is not clear since it sounds like the dag is completely
missing rather than it just failing to parse. The message should be made clearer to address
this possibility.

The longer term fix is to not display exceptions with tracebacks to users like this but catch
and give an error message.

Please accept this PR that addresses the following issues:
- https://issues.apache.org/jira/browse/AIRFLOW-415

artwr mistercrunch

Closes #1725 from aoen/ddavydov/clearer_dag_could_not_be_found_error


> Make dag_id not found error due to dag failing to parse clearer
> ---------------------------------------------------------------
>
>                 Key: AIRFLOW-415
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-415
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Dan Davydov
>            Assignee: Dan Davydov
>            Priority: Minor
>
> When a dag fails to parse and a user tries to run it e.g. via the command line airflow
will give an error "dag_id not found" which is not clear since it sounds like the dag is completely
missing rather than it just having an error. The message should be made clearer to address
this possibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message