airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajat Srivastava (Jira)" <j...@apache.org>
Subject [jira] [Updated] (AIRFLOW-5653) Log caught AirflowSkipException in task instance log
Date Mon, 14 Oct 2019 10:17:00 GMT

     [ https://issues.apache.org/jira/browse/AIRFLOW-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajat Srivastava updated AIRFLOW-5653:
--------------------------------------
    Component/s:     (was: operators)
        Summary: Log caught AirflowSkipException in task instance log  (was: Logging airflow
operator raised exceptions)

> Log caught AirflowSkipException in task instance log
> ----------------------------------------------------
>
>                 Key: AIRFLOW-5653
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5653
>             Project: Apache Airflow
>          Issue Type: Task
>          Components: logging
>    Affects Versions: 1.10.5
>            Reporter: Rajat Srivastava
>            Assignee: Rajat Srivastava
>            Priority: Minor
>
> It seems like when an operator throws AirflowSkipException, airflow captures it and marks
following tasks as skipped too, but it leaves no trace in the task instances log and does
not show exception message. This can confuse the users as they can't figure out in log why
operators were marked as skipped.
> We should explicitly log the exception and its message in task instance logs, and consider
other airflow-caught exceptions too. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message