Add parameter `deferrable` to `AzureBatchOperator`

(6 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Python (16.781 Forks)batch import

area:async-operatorsgood first issuekind:feature

Repository-Metriken

Stars: (44.809 Sterne)
PR-Merge-Metriken: (Durchschn. Merge 7T 18h) (834 gemergte PRs in 30 T)

Beschreibung

Description

The AzureBatchOperator currently has no option to set it to deferrable, which would allow the task to be run by an async low-resource worker ("triggerer"). Therefore Azure Batch tasks block a regular worker, even though they only ping the Azure platform from time to time.

I propose to add this parameter and changing the operator to use asynchronous calls.

As a reference, the AWS Batch operator has a parameter deferrable.

Use case/motivation

Adding this parameter and changing the operator to use asynchronous calls would reduce resource consumption when using Azure Batch.

Related issues

No response

Are you willing to submit a PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct

Contributor Guide

Research-Richtung: Review the current implementation of `AzureBatchOperator` in the Airflow source code, likely located in the `airflow/providers/azure/transfers/` directory. Study the AWS Batch operator's implementation of the `deferrable` parameter and its use of async calls. Examine the triggerer architecture in Airflow documentation. Ensure that adding deferrable support does not break existing synchronous usage.
Tech Stack: python
Domain: backendcloud
Issue Type: Funktion
Schwierigkeit: 3
Geschätzte Zeit: 1-2 Tage
Aktivitätsstatus: Aktiv
Klarheit: Klar
Voraussetzungen: Python programmingAirflow basics
Einsteigerfreundlichkeit: 65