You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Rajat Srivastava (Jira)" <ji...@apache.org> on 2019/10/15 05:45:00 UTC

[jira] [Closed] (AIRFLOW-5653) Log caught AirflowSkipException in task instance log

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

Rajat Srivastava closed AIRFLOW-5653.
-------------------------------------

> 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
>             Fix For: 1.10.6
>
>
> 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)