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

Posted to commits@airflow.apache.org by "Jonas Laake (JIRA)" <ji...@apache.org> on 2019/01/11 15:06:00 UTC

[jira] [Created] (AIRFLOW-3682) Default aws_conn_id is wrong for emr_base_sensor and emr_create_job_flow_operator

Jonas Laake created AIRFLOW-3682:
------------------------------------

             Summary: Default aws_conn_id is wrong for emr_base_sensor and emr_create_job_flow_operator
                 Key: AIRFLOW-3682
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3682
             Project: Apache Airflow
          Issue Type: Bug
          Components: aws, boto3
    Affects Versions: 1.10.1
            Reporter: Jonas Laake
            Assignee: Jonas Laake
             Fix For: 1.10.2


Changing default aws_conn_id and emr_create_job_flow_operator for consistency with emr_base_sensor

 

In the emr_base_sensor, the default aws_conn_id is set to 'aws_default'. It should be the same for the emr_add_steps_operator and the  emr_create_job_flow_operator, so they land inside the same boto3 session?
For the current implementation it leads to errors where the EMR cluster is not found by the emr_step_sensor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)