David Blain

On thing I have to take into account: Airflow 2 So I think we will have basic PythonOperator implementation without async support for Airflow 2 and for Airflow 3.2 for...

@uranusjr @Lee-W I've refactored PythonOperator as suggested, already tested it locally and it works. So no more need for dedicated AsyncPythonOperator, it also made the decorator part easier so there...

An additional PR will be opened in which improvements to SFTPHookAsync have been made, I removed those from this PR to make review easier and not add unnecessary complexity not...

Added example dags with async PythonOperator into the documentation.

> I think this is good. I feel like we should keep a copy of BaseAsyncOperator (temporarily) in the standard provider so the feature can be available in old Airflow...

@potiuk @zeroshade This provider could become useful in combo with [Apache Datafusion](https://datafusion.apache.org/). As Datafusion also uses [Apache Arrow](https://arrow.apache.org/) underneath, a provider could become useful when trying to access different backends...

Can you just specify a retry with following parameters on the PowerBIDatasetRefreshOperator? ``` retry_exponential_backoff=True, # to increase the delay after each failed attempt retry_delay=60, retries=5, ```

Those parameters apply on the whole operator, you could also try to specify the check_interval and timeout parameter, which by default both are 60 seconds, I think timeout should be...

> OK I see, so the retry is not specific to the "get status" request. From what I understand, the issue seems to be that the very first request (to...

I understand the issue, I've checked the code of the PowerBITrigger and the check_interval is set to 60 seconds, but the timeout is also 60 seconds by default, which means...