Re: [VOTE] Airflow Providers prepared on July 12, 2023

+1 (binding) - checked signatures, licence, checksum, source code matches that one from the tag. Checked that my changes are included. On Fri, Jul 14, 2023 at 7:30 PM rahul Vats wrote: > +1 (non-binding) > Tested #32568 > > Regards, > Rahul Vats >

Re: [VOTE] Airflow Providers prepared on July 12, 2023

+1 (non-binding) Tested #32568 Regards, Rahul Vats 9953794332 On Thu, 13 Jul 2023 at 23:03, Utkarsh Sharma wrote: > +1 non-binding > > On Thu, Jul 13, 2023 at 10:48 PM Frank Cash wrote: > > > > +1 (non-binding) > > Tested the SFTP Provider upda

Re: Support for Datasets with execution-time values for use cases requiring more fine-grained dataset specs

Hi Vikram, Thanks for the additional context. That sounds great. What's the best way for us to connect? Jeff Payne From: Vikram Koka Sent: Friday, July 14, 2023 8:00 AM To: jul...@astronomer.io.invalid Cc: dev@airflow.apache.org Subject: Re: Support for Data

Re: Support for Datasets with execution-time values for use cases requiring more fine-grained dataset specs

Hi Jeff, Thank you for bringing this up. This is definitely on my radar and part of a larger AIP which I have been in the process of writing up. We have thought of this use case and deliberately deferred it in the earlier AIP. Doing is definitely quite complex and I think it needs a couple of int

Re: [DISCUSS] Moving Dask Executor to a separate (optional?) dask provider

We all agree on moving the 5 remote executors to their respective providers. The main question now is whether we should pre-install all the providers or not. IMHO we should pre-install Celery, Kubernetes, and Dask providers until Airflow 3.0. Not doing so would be a breaking change for some users,

Re: [DISCUSS] Moving Dask Executor to a separate (optional?) dask provider

I'm too in favor of moving Dask Executor into its own provider, which will make the airflow's codebase more pluggable and orthogonal. Big +1 :) Thanks, Utkarsh Sharma On Fri, Jul 14, 2023 at 2:03 AM Ferruzzi, Dennis wrote: > I'm not sure how much of a train wreck it would turn into, but moving