[
https://issues.apache.org/jira/browse/AIRFLOW-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953658#comment-16953658
]
ASF subversion and git services commented on AIRFLOW-5653:
----------------------------------------------------------
Commit a04cafdc248ba27c8d0384ab6b8d8d707d69e9bc in airflow's branch
refs/heads/v1-10-stable from Rajat Srivastava
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=a04cafd ]
[AIRFLOW-5653] Log caught AirflowSkipException in task instance log (#6330)
[AIRFLOW-5653] Log caught AirflowSkipException in task instance log
Logging any caught AirflowSkipException with message in models/taskinstance.py
to remove confusion due to no task skipping information in the logs
(cherry picked from commit 1a4c16432b8718189269e63c3afcd2709eed7379)
> 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)
