[
https://issues.apache.org/jira/browse/AIRFLOW-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869796#comment-16869796
]
ASF subversion and git services commented on AIRFLOW-4829:
----------------------------------------------------------
Commit 06dba668b99d38f60854bb3ca1dc6dd1cd17991e in airflow's branch
refs/heads/master from Jordan Zucker
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=06dba66 ]
[AIRFLOW-4829] More descriptive exceptions for EMR sensors (#5452)
EMR sensors, including the EmrStepSensor and the EmrJobFlowSensor
don't include failure reasons in exceptions though they already
have that info in the boto3 response from the EMR api. This adds
that info to exceptions.
Example exception:
> AirflowException: EMR job failed for code: BOOTSTRAP_FAILURE with message
> Master instance (i-02c25cade3cbfc453) failed attempting to download bootstrap
> action 1 file from S3
> EMR job flow and step sensor should provide a reason why the job failed
> -----------------------------------------------------------------------
>
> Key: AIRFLOW-4829
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4829
> Project: Apache Airflow
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 1.10.3
> Reporter: Jordan Zucker
> Assignee: Jordan Zucker
> Priority: Minor
>
> Currently, when using the EmrJobFlowSensor and the EmrStepSensor there is an
> exception raised when a cluster fails. But no information is provided on what
> the failure was. The sensor that raises the exception already has the info in
> the boto3 response from the EMR api and this could be easily provided by
> extending the exception message with more details. This could be made a
> boolean or just always provided.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
