Hi Ping,
I had this idea about auto-fixing deprecation warnings too when I started the
airflint project.
I totally agree with what you said that often people ignore these warnings and
therefore a cli tool would come in very handy. It could look similar to the
airflint project and also be based
Hi Jarek,
Thanks for pushing forward with this AIP.
I am very interesting in this part:
All tests for DagProcessor, Workers (including Operators) and triggers are
executed in both modes "DBDirect'' and "DBIsolation ''. The code for
Airflow Database API, the DbApiClient and DBSession are
Hi Daniel,
+1 for ‘schedule' and thanks for bringing this up.
I agree with Vikram, we should be very careful about deprecating existing
params even if we have warnings around it. Not sure if this is a general
case, but I notice that people ignore warnings all the time until it starts
to break.
In case you forgot about us @Vikram, gentle nudge
On Mon, Aug 1, 2022 at 8:40 AM Daniel Standish <
daniel.stand...@astronomer.io> wrote:
> Well, this is a discussion thread, so let's discuss!
>
> Vikram, what kind of implications are you thinking of? Maybe you could
> provide a little more
Dear Airflow community,
I'm happy to announce that Apache Airflow Client 2.3.0 was just released.
The source release, as well as the binary "sdist" release, are available
here:
https://dist.apache.org/repos/dist/release/airflow/clients/python/2.3.0
We also made this version available on PyPi
Hello Dev Community,
The release of Apache Airflow Client 2.3.0 (based on RC1) has been accepted.
5 “+1” votes received:
- Ash Berlin-Taylor (binding)
- Jarek Potiuk (binding)
- Pankaj Koti
- Phani Kumar
- Sumit Maheshwari (binding)
No "-1" votes received
Vote thread:
