[
https://issues.apache.org/jira/browse/AIRFLOW-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951236#comment-16951236
]
ASF GitHub Bot commented on AIRFLOW-5653:
-----------------------------------------
aoen commented on pull request #6330: [AIRFLOW-5653] Log caught
AirflowSkipException in task instance log
URL: https://github.com/apache/airflow/pull/6330
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
