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/09/25 10:20: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=16937597#comment-16937597 ]
jack commented on AIRFLOW-4226:
-------------------------------
[~kaxilnaik] ping :)
> 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
> Components: gcp
> 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
(v8.3.4#803005)