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

ASF subversion and git services commented on AIRFLOW-2313:
----------------------------------------------------------

Commit b02820a7afcb5205df39c4a639f1ceeb2c9c75ee in incubator-airflow's branch 
refs/heads/master from ebartkus
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=b02820a ]

[AIRFLOW-2313] Add TTL parameters for Dataproc

Three additional optional parameters to
DataprocClusterCreateOperator
which configure Cloud Dataproc Cluster Scheduled
Deletion features.

Closes #3217 from ebartkus/dataproc-ttl


> Add ClusterLifecycleConfig to DataprocClusterCreateOperator
> -----------------------------------------------------------
>
>                 Key: AIRFLOW-2313
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2313
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: contrib, gcp, operators
>    Affects Versions: Airflow 2.0, 1.9.0
>            Reporter: Egidijus Bartkus
>            Assignee: Egidijus Bartkus
>            Priority: Minor
>
> Google introduced [Cloud Dataproc Cluster Scheduled 
> Deletion|https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/scheduled-deletion]
>  feature which isn't yet supported by the DataprocClusterCreateOperator.
>  
> Having this option enabled could be useful to make sure Dataproc cluster 
> doesn't stay active for extended time periods (In case delete 
> DataprocClusterDeleteOperator isn't suitable or fails to run for any reason).
>  
> Implementation requires adding config object 
> [LifecycleConfig|https://cloud.google.com/dataproc/docs/reference/rest/v1beta2/ClusterConfig#LifecycleConfig]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to