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

Posted to commits@airflow.apache.org by "Jordan Zucker (JIRA)" <ji...@apache.org> on 2019/06/20 19:53:00 UTC

[jira] [Updated] (AIRFLOW-4829) EMR job flow and step sensor should provide a reason why the job failed

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

Jordan Zucker updated AIRFLOW-4829:
-----------------------------------
    Description: 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.  (was: Currently, when using the EmrJobFlowSensor 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.)

> 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)