[
https://issues.apache.org/jira/browse/AIRFLOW-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Brard updated AIRFLOW-4551:
------------------------------------
Description:
As of today, when the scheduler cannot import a DAG, an entry is
[added|https://github.com/apache/airflow/blob/97ad71c99373759cc022733b2732c3bd43af983d/airflow/models/dagbag.py#L201]
to `import_error` table with the exception message as `stacktrace` (later
displayed on the web-ui).
This is most of the time not enough to debug complex situation.
I would suggest to add the "real" stack trace in addition to the exception.
Using the traceback module should allow for it in a very similar way.
was:
As of today, when the scheduler cannot import a DAG, an entry is added to
`import_error` table with the exception message as `stacktrace` (later
displayed on the web-ui).
This is most of the time not enough to debug complex situation.
I would suggest to add the "real" stack trace in addition to the exception.
Using the traceback module should allow for it in a very similar way.
> Scheduler captures exception and stracktrace
> --------------------------------------------
>
> Key: AIRFLOW-4551
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4551
> Project: Apache Airflow
> Issue Type: New Feature
> Components: scheduler
> Reporter: Emmanuel Brard
> Priority: Minor
>
> As of today, when the scheduler cannot import a DAG, an entry is
> [added|https://github.com/apache/airflow/blob/97ad71c99373759cc022733b2732c3bd43af983d/airflow/models/dagbag.py#L201]
> to `import_error` table with the exception message as `stacktrace` (later
> displayed on the web-ui).
> This is most of the time not enough to debug complex situation.
> I would suggest to add the "real" stack trace in addition to the exception.
> Using the traceback module should allow for it in a very similar way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
