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

Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/07/01 14:51:00 UTC

[jira] [Commented] (AIRFLOW-4226) DataProcPySparkOperator gets project ID from gcp_conn_id rather than project_id

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

jack commented on AIRFLOW-4226:
-------------------------------

[~kamil.bregula] [~kaxilnaik] do you know if this is intentional?

also need to add gcp component to the ticket

> 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: Bug
>            Reporter: Aaron Liblong
>            Priority: Minor
>
> 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
(v7.6.3#76005)