airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bolke de Bruin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRFLOW-1323) Operators related to Dataproc should keep some parameters consistent
Date Tue, 03 Oct 2017 09:17:00 GMT

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

Bolke de Bruin resolved AIRFLOW-1323.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Issue resolved by pull request #2636
[https://github.com/apache/incubator-airflow/pull/2636]

> Operators related to Dataproc should keep some parameters consistent
> --------------------------------------------------------------------
>
>                 Key: AIRFLOW-1323
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1323
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: operators
>            Reporter: Yu Ishikawa
>            Assignee: Crystal Qian
>            Priority: Minor
>             Fix For: 1.9.0
>
>
> The parameters of {{DataprocClusterDeleteOperator}} and {{DataprocClusterCreateOperator}}
for GCP connection ID are {{google_cloud_conn_id}}.  On the other hand, for example,
>  {{DataProcPigOperator}}'s paramter is {{gcp_conn_id}}. I think this inconsistency may
make users confused. We should keep the parameter's name consistent.
> For another example, parameters for a cluster name don't have consistency like {{cluster_name}}
and {{dataproc_cluster}}.
> - https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/operators/dataproc_operator.py#L58
> - https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/operators/dataproc_operator.py#L626



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message