airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kaxil Naik (Jira)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-4226) DataProcPySparkOperator gets project ID from gcp_conn_id rather than project_id
Date Wed, 25 Sep 2019 18:26:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937970#comment-16937970
] 

Kaxil Naik commented on AIRFLOW-4226:
-------------------------------------

Thanks [~kamil.bregula]

> DataProcPySparkOperator gets project ID from gcp_conn_id rather than project_id
> -------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4226
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4226
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: gcp
>    Affects Versions: 1.10.3, 1.10.4, 1.10.5
>            Reporter: Aaron Liblong
>            Assignee: Kaxil Naik
>            Priority: Minor
>             Fix For: 1.10.6
>
>
> DataProcPySparkOperator gets [the project ID for the cluster it creates|https://github.com/apache/airflow/blob/master/airflow/contrib/operators/dataproc_operator.py#L1334]
from [the hook instantiated from gcp_conn_id|https://github.com/apache/airflow/blob/master/airflow/contrib/operators/dataproc_operator.py#L1324]
rather than from its own project_id property. This is contrary to how every other operator
in this module works. Not sure if it's a bug or intended.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message