[
https://issues.apache.org/jira/browse/AIRFLOW-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829725#comment-16829725
]
ASF subversion and git services commented on AIRFLOW-3143:
----------------------------------------------------------
Commit 1c8e5f3aa9393530bd6d8c241d7df12ad7897633 in airflow's branch
refs/heads/v1-10-stable from Joel Croteau
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=1c8e5f3 ]
[AIRFLOW-3143] Support Auto-Zone in DataprocClusterCreateOperator (#5169)
Allows you to let GCP decide what zone to put your cluster on by setting zone
to None or a blank string, making the parameter optional. Per the API spec at
https://cloud.google.com/dataproc/docs/reference/rest/v1beta2/ClusterConfig#InstanceGroupConfig,
this means that all machineTypeUris have to be in short form.
(cherry picked from commit afb44542662a2b5478cc3834b9fd8470b411b84f)
> Support auto-zone in DataprocClusterCreateOperator
> --------------------------------------------------
>
> Key: AIRFLOW-3143
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3143
> Project: Apache Airflow
> Issue Type: Improvement
> Components: contrib, operators
> Reporter: Wilson Lian
> Assignee: Joel Croteau
> Priority: Minor
> Fix For: 1.10.4, 2.0.0
>
>
> [Dataproc
> Auto-zone|https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone]
> allows users to omit the zone when creating a cluster, and the service will
> pick a zone in the chosen region.
> Providing an empty string or None for `zone` would match up with how users
> would request auto-zone via direct API access, but as-is the
> DataprocClusterCreateOperator makes a bad API request when such values are
> passed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
