date:20231016

Re: The "no_status" state

2023-10-16 Thread Oliveira, Niko

I really like this idea as well! One of the _the most common_ questions I get 
from people managing an Airflow env is "Why is my task stuck in state X". 
Anything we can do to make that more discoverable and user friendly, especially 
in the UI instead of (or in addition to) logs would be fantastic!

Thanks to Jens for having a think and pointing out a lot of the implications, I 
agree a quick AIP might be nice for this one.

Cheers,
Niko


From: Scheffler Jens (XC-DX/ETV5) 
Sent: Thursday, September 28, 2023 10:36:00 PM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] The "no_status" state

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.



AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne 
cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas 
confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le 
contenu ne présente aucun risque.



Hi Ryan,

I really like the idea of exposing some more scheduler details. More 
transparency in scheduling also in the UI would help the user in (1) seeing and 
understanding what is going on and (2) reduces the need to crawl for logs and 
raise support tickets if status is “strange”. I often also see this as a 
problem. This is also sometimes generating a bit of “mis trust” in the 
scheduler stability.

From point of scheduler “overhead” I assume as long as we are not making a 
“full scan” just to ensure that each and every task is always up-to-date 
(Scheduler stops processing today after enough tasks have been processes in a 
loop or if scheduling limits are reached) this is OK for me and on the code 
side does not seem to be much overhead.
I have a bit of fear on the other hand that very many frequent updates need to 
happen on the DB as another state would need to be written. So more DB round 
trips are needed. This might hit performance for large DAGs or cases where DAGs 
are scheduled. So at least it would need to filter to update the state to DB 
only if changed to keep performance impact minimal.

From point of naming I still think “no status” is good to indicate that 
scheduler did not digest anything, maybe task was never looked at because 
scheduler actually is really stuck or too busy getting there. I would propose 
if scheduler passes along a task and decides that it is not ready to schedule 
to have an additional state calling e.g. “not_ready” in the state model between 
“none” and “scheduled”.

Finally on the other hand, adding another state in the model, I am not sure 
whether this 100% will help in the use case described by you. Still you might 
need to scratch your head a while if taking a look on UI that a DAG is “stuck” 
until you realize all the options you have configured. Exposing a “why is 
stuck” in a user friendly manner might be another level of complexity in this 
case.

As the state model might touch a lot of code and there might be a longer 
discussion needed, would it be a need to raise an AIP for this? There might be 
a lot more (external, provider??) dependencies adjusting the state model?

Mit freundlichen Grüßen / Best regards

Jens Scheffler

Deterministik open Loop (XC-DX/ETV5)
Robert Bosch GmbH | Hessbruehlstraße 21 | 70565 Stuttgart-Vaihingen | GERMANY | 
www.bosch.com
Tel. +49 711 811-91508 | Mobil +49 160 90417410 | 
jens.scheff...@de.bosch.com

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; Geschäftsführung: 
Dr. Stefan Hartung,
Dr. Christian Fischer, Dr. Markus Forschner, Stefan Grosch, Dr. Markus Heyn, 
Dr. Tanja Rückert

From: Ryan Hatter 
Sent: Donnerstag, 28. September 2023 23:59
To: dev@airflow.apache.org
Subject: The "no_status" state

Over the last couple weeks I've come across a rather tricky problem a few 
times. One DAG run gets "stuck" in the queued state, while subsequent DAG runs 
will be stuck running (screenshot below). One of these issues was caused by 
`max_active_runs` being met when a task instance from a previously run DAG was 
cleared, and one of the tasks had `depends_on_past=True`. This caused the DAG 
run to be stuck in queued in perpetuity until it was realized that the task 
that wasn't getting scheduled needed the failed task in the preceding DAG run 
to be re-run, which in turn causes the stuck running DAG runs to be stuck in 
running. which caused quite a bit of confusion and stress.

Given that Airflow is pretty burnt out on task instance states and colors, I 
propose replacing "no_status" with "dependencies_not_met" and surfacing 
dependencies in the grid view instead of forcing users to already know where to 
look (i.e. "more details" task instance details). Now that I typed it out, I'm 
not sure there should be a

Re: [VOTE] Airflow Providers prepared on October 13, 2023

2023-10-16 Thread Kaxil Naik

+1 binding

On Mon, 16 Oct 2023 at 17:19, Jed Cunningham 
wrote:

> 1 (binding)
>
> Checked signatures, checksums, licences
>

Re: [VOTE] Airflow Providers prepared on October 13, 2023

2023-10-16 Thread Jed Cunningham

1 (binding)

Checked signatures, checksums, licences

Re: [VOTE] Airflow Providers prepared on October 13, 2023

2023-10-16 Thread Vincent Beck

+1 non binding. I successfully ran testing DAGs against Amazon provider 
package. I also ran all system tests within the Amazon provider package against 
this RC. They all succeeded. You can see the results here: 
https://aws-mwaa.github.io/open-source/system-tests/version/84d99404bb478cd66e359acb5cf1f00d3b2ce2e1_8.8.0rc1.html

On 2023/10/16 16:07:41 Phani Kumar wrote:
> +1 non binding
> 
> On Mon, Oct 16, 2023 at 9:27 PM Hussein Awala  wrote:
> 
> > +1 (binding) I checked my changes, and all looks good.
> >
> > On Mon, Oct 16, 2023 at 9:52 AM utkarsh sharma 
> > wrote:
> >
> > > +1 Non binding
> > >
> > > Thanks,
> > > Utkarsh Sharma
> > >
> > > On Mon, Oct 16, 2023 at 1:06 PM Rahul Vats 
> > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Regards,
> > > > Rahul Vats
> > > > 9953794332
> > > >
> > > >
> > > > On Mon, 16 Oct 2023 at 10:27, Akash Sharma <2akash111...@gmail.com>
> > > wrote:
> > > >
> > > > > +1 (non binding)
> > > > > Tested with few dags. Everything seems fine.
> > > > >
> > > > > Best regards,
> > > > > Akash
> > > > >
> > > > >
> > > > > On Sat, 14 Oct 2023, 01:28 Elad Kalif,  wrote:
> > > > >
> > > > > > Hey all,
> > > > > >
> > > > > > I have just cut the new wave Airflow Providers packages. This email
> > > is
> > > > > > calling a vote on the release,
> > > > > > which will last for 72 hours - which means that it will end on
> > > October
> > > > > 16,
> > > > > > 2023 19:55 PM UTC and until 3 binding +1 votes have been received.
> > > > > >
> > > > > > Consider this my (binding) +1.
> > > > > >
> > > > > > Airflow Providers are available at:
> > > > > > https://dist.apache.org/repos/dist/dev/airflow/providers/
> > > > > >
> > > > > > *apache-airflow-providers--*.tar.gz* are the binary
> > > > > >  Python "sdist" release - they are also official "sources" for the
> > > > > provider
> > > > > > packages.
> > > > > >
> > > > > > *apache_airflow_providers_-*.whl are the binary
> > > > > >  Python "wheel" release.
> > > > > >
> > > > > > The test procedure for PMC members is described in
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members
> > > > > >
> > > > > > The test procedure for and Contributors who would like to test this
> > > RC
> > > > is
> > > > > > described in:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors
> > > > > >
> > > > > >
> > > > > > Public keys are available at:
> > > > > > https://dist.apache.org/repos/dist/release/airflow/KEYS
> > > > > >
> > > > > > Please vote accordingly:
> > > > > >
> > > > > > [ ] +1 approve
> > > > > > [ ] +0 no opinion
> > > > > > [ ] -1 disapprove with the reason
> > > > > >
> > > > > >
> > > > > > Only votes from PMC members are binding, but members of the
> > community
> > > > are
> > > > > > encouraged to test the release and vote with "(non-binding)".
> > > > > >
> > > > > > Please note that the version number excludes the 'rcX' string.
> > > > > > This will allow us to rename the artifact without modifying
> > > > > > the artifact checksums when we actually release.
> > > > > >
> > > > > > The status of testing the providers by the community is kept here:
> > > > > > https://github.com/apache/airflow/issues/34930
> > > > > >
> > > > > > You can find packages as well as detailed changelog following the
> > > below
> > > > > > links:
> > > > > >
> > > > > >
> > https://pypi.org/project/apache-airflow-providers-airbyte/3.4.0rc1/
> > > > > >
> > https://pypi.org/project/apache-airflow-providers-alibaba/2.6.0rc1/
> > > > > > https://pypi.org/project/apache-airflow-providers-amazon/8.8.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-beam/5.3.0rc1/
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.3.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-drill/2.5.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-druid/3.6.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-flink/1.2.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.2.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-hive/6.2.0rc1/
> > > > > >
> > > > >
> > > >
> > >
> > https://pypi.org/project/apache-airflow-providers-apache-impala/1.2.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-kafka/1.2.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-kylin/3.3.0rc1/
> > > > > >
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-livy/3.6.0rc1/
> > > > > >
> > > https://pypi.org/project/apache-airflow-providers-apache-pig/4.2.0rc1/
> > >

Re: [VOTE] Airflow Providers prepared on October 13, 2023

2023-10-16 Thread Phani Kumar

+1 non binding

On Mon, Oct 16, 2023 at 9:27 PM Hussein Awala  wrote:

> +1 (binding) I checked my changes, and all looks good.
>
> On Mon, Oct 16, 2023 at 9:52 AM utkarsh sharma 
> wrote:
>
> > +1 Non binding
> >
> > Thanks,
> > Utkarsh Sharma
> >
> > On Mon, Oct 16, 2023 at 1:06 PM Rahul Vats 
> wrote:
> >
> > > +1 (non-binding)
> > >
> > > Regards,
> > > Rahul Vats
> > > 9953794332
> > >
> > >
> > > On Mon, 16 Oct 2023 at 10:27, Akash Sharma <2akash111...@gmail.com>
> > wrote:
> > >
> > > > +1 (non binding)
> > > > Tested with few dags. Everything seems fine.
> > > >
> > > > Best regards,
> > > > Akash
> > > >
> > > >
> > > > On Sat, 14 Oct 2023, 01:28 Elad Kalif,  wrote:
> > > >
> > > > > Hey all,
> > > > >
> > > > > I have just cut the new wave Airflow Providers packages. This email
> > is
> > > > > calling a vote on the release,
> > > > > which will last for 72 hours - which means that it will end on
> > October
> > > > 16,
> > > > > 2023 19:55 PM UTC and until 3 binding +1 votes have been received.
> > > > >
> > > > > Consider this my (binding) +1.
> > > > >
> > > > > Airflow Providers are available at:
> > > > > https://dist.apache.org/repos/dist/dev/airflow/providers/
> > > > >
> > > > > *apache-airflow-providers--*.tar.gz* are the binary
> > > > >  Python "sdist" release - they are also official "sources" for the
> > > > provider
> > > > > packages.
> > > > >
> > > > > *apache_airflow_providers_-*.whl are the binary
> > > > >  Python "wheel" release.
> > > > >
> > > > > The test procedure for PMC members is described in
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members
> > > > >
> > > > > The test procedure for and Contributors who would like to test this
> > RC
> > > is
> > > > > described in:
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors
> > > > >
> > > > >
> > > > > Public keys are available at:
> > > > > https://dist.apache.org/repos/dist/release/airflow/KEYS
> > > > >
> > > > > Please vote accordingly:
> > > > >
> > > > > [ ] +1 approve
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 disapprove with the reason
> > > > >
> > > > >
> > > > > Only votes from PMC members are binding, but members of the
> community
> > > are
> > > > > encouraged to test the release and vote with "(non-binding)".
> > > > >
> > > > > Please note that the version number excludes the 'rcX' string.
> > > > > This will allow us to rename the artifact without modifying
> > > > > the artifact checksums when we actually release.
> > > > >
> > > > > The status of testing the providers by the community is kept here:
> > > > > https://github.com/apache/airflow/issues/34930
> > > > >
> > > > > You can find packages as well as detailed changelog following the
> > below
> > > > > links:
> > > > >
> > > > >
> https://pypi.org/project/apache-airflow-providers-airbyte/3.4.0rc1/
> > > > >
> https://pypi.org/project/apache-airflow-providers-alibaba/2.6.0rc1/
> > > > > https://pypi.org/project/apache-airflow-providers-amazon/8.8.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-beam/5.3.0rc1/
> > > > >
> > > > >
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.3.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-drill/2.5.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-druid/3.6.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-flink/1.2.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.2.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-hive/6.2.0rc1/
> > > > >
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-apache-impala/1.2.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-kafka/1.2.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-kylin/3.3.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-livy/3.6.0rc1/
> > > > >
> > https://pypi.org/project/apache-airflow-providers-apache-pig/4.2.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-pinot/4.2.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-spark/4.2.0rc1/
> > > > >
> > >
> https://pypi.org/project/apache-airflow-providers-apache-sqoop/4.1.0rc1/
> > > > >
> https://pypi.org/project/apache-airflow-providers-apprise/1.1.0rc1/
> > > > >
> https://pypi.org/project/apache-airflow-providers-arangodb/2.3.0rc1/
> > > > > https://pypi.org/project/apache-airflow-providers-asana/2.3.0rc1/
> > > > >
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/2.2.0rc1/
> > > > >

Re: [VOTE] Airflow Providers prepared on October 13, 2023

2023-10-16 Thread Hussein Awala

+1 (binding) I checked my changes, and all looks good.

On Mon, Oct 16, 2023 at 9:52 AM utkarsh sharma 
wrote:

> +1 Non binding
>
> Thanks,
> Utkarsh Sharma
>
> On Mon, Oct 16, 2023 at 1:06 PM Rahul Vats  wrote:
>
> > +1 (non-binding)
> >
> > Regards,
> > Rahul Vats
> > 9953794332
> >
> >
> > On Mon, 16 Oct 2023 at 10:27, Akash Sharma <2akash111...@gmail.com>
> wrote:
> >
> > > +1 (non binding)
> > > Tested with few dags. Everything seems fine.
> > >
> > > Best regards,
> > > Akash
> > >
> > >
> > > On Sat, 14 Oct 2023, 01:28 Elad Kalif,  wrote:
> > >
> > > > Hey all,
> > > >
> > > > I have just cut the new wave Airflow Providers packages. This email
> is
> > > > calling a vote on the release,
> > > > which will last for 72 hours - which means that it will end on
> October
> > > 16,
> > > > 2023 19:55 PM UTC and until 3 binding +1 votes have been received.
> > > >
> > > > Consider this my (binding) +1.
> > > >
> > > > Airflow Providers are available at:
> > > > https://dist.apache.org/repos/dist/dev/airflow/providers/
> > > >
> > > > *apache-airflow-providers--*.tar.gz* are the binary
> > > >  Python "sdist" release - they are also official "sources" for the
> > > provider
> > > > packages.
> > > >
> > > > *apache_airflow_providers_-*.whl are the binary
> > > >  Python "wheel" release.
> > > >
> > > > The test procedure for PMC members is described in
> > > >
> > > >
> > >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members
> > > >
> > > > The test procedure for and Contributors who would like to test this
> RC
> > is
> > > > described in:
> > > >
> > > >
> > >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors
> > > >
> > > >
> > > > Public keys are available at:
> > > > https://dist.apache.org/repos/dist/release/airflow/KEYS
> > > >
> > > > Please vote accordingly:
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > >
> > > > Only votes from PMC members are binding, but members of the community
> > are
> > > > encouraged to test the release and vote with "(non-binding)".
> > > >
> > > > Please note that the version number excludes the 'rcX' string.
> > > > This will allow us to rename the artifact without modifying
> > > > the artifact checksums when we actually release.
> > > >
> > > > The status of testing the providers by the community is kept here:
> > > > https://github.com/apache/airflow/issues/34930
> > > >
> > > > You can find packages as well as detailed changelog following the
> below
> > > > links:
> > > >
> > > > https://pypi.org/project/apache-airflow-providers-airbyte/3.4.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-alibaba/2.6.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-amazon/8.8.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-beam/5.3.0rc1/
> > > >
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.3.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-drill/2.5.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-druid/3.6.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-flink/1.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-hive/6.2.0rc1/
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-apache-impala/1.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-kafka/1.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-kylin/3.3.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-livy/3.6.0rc1/
> > > >
> https://pypi.org/project/apache-airflow-providers-apache-pig/4.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-pinot/4.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-spark/4.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-apache-sqoop/4.1.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-apprise/1.1.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-arangodb/2.3.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-asana/2.3.0rc1/
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/2.2.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-celery/3.4.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-cloudant/3.3.0rc1/
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/7.7.0rc1/
> > > >
> https://pypi.org/project/apache-airflow-providers-common-sql/1.8.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-daskexecutor/1.1.0rc1/
> > > >
>

[ANNOUNCE] Apache Airflow Python Client 2.7.2 Released

2023-10-16 Thread Ephraim Anierobi

Dear Airflow community,

I'm happy to announce that Airflow Python Client 2.7.2 was just released.

We also made this version available on PyPI for convenience:
`pip install apache-airflow-client`
https://pypi.org/project/apache-airflow-client/2.7.2/

The documentation is available at:
https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html

Find the changelog here for more details:
https://github.com/apache/airflow-client-python/blob/main/CHANGELOG.md#v272


Cheers,
Ephraim

[RESULT][VOTE] Release Airflow Python Client 2.7.2 from 2.7.2rc1

2023-10-16 Thread Ephraim Anierobi

Hello,

Apache Airflow Python Client 2.7.2 (based on RC1) has been accepted.

3 "+1" binding votes received:
- Ephraim Anierobi
- Pierre Jeambrun
- Hussein Awala

4 "+1" non-binding votes received:
- Utkarsh Sharma
- Phani Kumar
- Aritra Basu
- Pankaj Singh

Vote thread:
https://lists.apache.org/thread/bgtw9cds5n8gggkw6whxvvc769p0xvbh

I'll continue with the release process, and the release announcement will
follow shortly.

Cheers,
Ephraim

Re: [VOTE] Airflow Providers prepared on October 13, 2023

2023-10-16 Thread utkarsh sharma

+1 Non binding

Thanks,
Utkarsh Sharma

On Mon, Oct 16, 2023 at 1:06 PM Rahul Vats  wrote:

> +1 (non-binding)
>
> Regards,
> Rahul Vats
> 9953794332
>
>
> On Mon, 16 Oct 2023 at 10:27, Akash Sharma <2akash111...@gmail.com> wrote:
>
> > +1 (non binding)
> > Tested with few dags. Everything seems fine.
> >
> > Best regards,
> > Akash
> >
> >
> > On Sat, 14 Oct 2023, 01:28 Elad Kalif,  wrote:
> >
> > > Hey all,
> > >
> > > I have just cut the new wave Airflow Providers packages. This email is
> > > calling a vote on the release,
> > > which will last for 72 hours - which means that it will end on October
> > 16,
> > > 2023 19:55 PM UTC and until 3 binding +1 votes have been received.
> > >
> > > Consider this my (binding) +1.
> > >
> > > Airflow Providers are available at:
> > > https://dist.apache.org/repos/dist/dev/airflow/providers/
> > >
> > > *apache-airflow-providers--*.tar.gz* are the binary
> > >  Python "sdist" release - they are also official "sources" for the
> > provider
> > > packages.
> > >
> > > *apache_airflow_providers_-*.whl are the binary
> > >  Python "wheel" release.
> > >
> > > The test procedure for PMC members is described in
> > >
> > >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members
> > >
> > > The test procedure for and Contributors who would like to test this RC
> is
> > > described in:
> > >
> > >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors
> > >
> > >
> > > Public keys are available at:
> > > https://dist.apache.org/repos/dist/release/airflow/KEYS
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > >
> > > Only votes from PMC members are binding, but members of the community
> are
> > > encouraged to test the release and vote with "(non-binding)".
> > >
> > > Please note that the version number excludes the 'rcX' string.
> > > This will allow us to rename the artifact without modifying
> > > the artifact checksums when we actually release.
> > >
> > > The status of testing the providers by the community is kept here:
> > > https://github.com/apache/airflow/issues/34930
> > >
> > > You can find packages as well as detailed changelog following the below
> > > links:
> > >
> > > https://pypi.org/project/apache-airflow-providers-airbyte/3.4.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-alibaba/2.6.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-amazon/8.8.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-beam/5.3.0rc1/
> > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.3.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-drill/2.5.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-druid/3.6.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-flink/1.2.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.2.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-hive/6.2.0rc1/
> > >
> >
> https://pypi.org/project/apache-airflow-providers-apache-impala/1.2.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-kafka/1.2.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-kylin/3.3.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-livy/3.6.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-apache-pig/4.2.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-pinot/4.2.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-spark/4.2.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-apache-sqoop/4.1.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-apprise/1.1.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-arangodb/2.3.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-asana/2.3.0rc1/
> > >
> >
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/2.2.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-celery/3.4.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-cloudant/3.3.0rc1/
> > >
> >
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/7.7.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-common-sql/1.8.0rc1/
> > >
> https://pypi.org/project/apache-airflow-providers-daskexecutor/1.1.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-databricks/4.6.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-datadog/3.4.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-dbt-cloud/3.4.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-dingding/3.3.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-discord/3.4.0rc1/
> > > https://pypi.org/project/apache-airflow-providers-docker/3.8.0rc1/
>

Re: [VOTE] Airflow Providers prepared on October 13, 2023

2023-10-16 Thread Rahul Vats

+1 (non-binding)

Regards,
Rahul Vats
9953794332


On Mon, 16 Oct 2023 at 10:27, Akash Sharma <2akash111...@gmail.com> wrote:

> +1 (non binding)
> Tested with few dags. Everything seems fine.
>
> Best regards,
> Akash
>
>
> On Sat, 14 Oct 2023, 01:28 Elad Kalif,  wrote:
>
> > Hey all,
> >
> > I have just cut the new wave Airflow Providers packages. This email is
> > calling a vote on the release,
> > which will last for 72 hours - which means that it will end on October
> 16,
> > 2023 19:55 PM UTC and until 3 binding +1 votes have been received.
> >
> > Consider this my (binding) +1.
> >
> > Airflow Providers are available at:
> > https://dist.apache.org/repos/dist/dev/airflow/providers/
> >
> > *apache-airflow-providers--*.tar.gz* are the binary
> >  Python "sdist" release - they are also official "sources" for the
> provider
> > packages.
> >
> > *apache_airflow_providers_-*.whl are the binary
> >  Python "wheel" release.
> >
> > The test procedure for PMC members is described in
> >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members
> >
> > The test procedure for and Contributors who would like to test this RC is
> > described in:
> >
> >
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors
> >
> >
> > Public keys are available at:
> > https://dist.apache.org/repos/dist/release/airflow/KEYS
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > Only votes from PMC members are binding, but members of the community are
> > encouraged to test the release and vote with "(non-binding)".
> >
> > Please note that the version number excludes the 'rcX' string.
> > This will allow us to rename the artifact without modifying
> > the artifact checksums when we actually release.
> >
> > The status of testing the providers by the community is kept here:
> > https://github.com/apache/airflow/issues/34930
> >
> > You can find packages as well as detailed changelog following the below
> > links:
> >
> > https://pypi.org/project/apache-airflow-providers-airbyte/3.4.0rc1/
> > https://pypi.org/project/apache-airflow-providers-alibaba/2.6.0rc1/
> > https://pypi.org/project/apache-airflow-providers-amazon/8.8.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-beam/5.3.0rc1/
> >
> >
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.3.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-drill/2.5.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-druid/3.6.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-flink/1.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-hive/6.2.0rc1/
> >
> https://pypi.org/project/apache-airflow-providers-apache-impala/1.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-kafka/1.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-kylin/3.3.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-livy/3.6.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-pig/4.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-pinot/4.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-spark/4.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apache-sqoop/4.1.0rc1/
> > https://pypi.org/project/apache-airflow-providers-apprise/1.1.0rc1/
> > https://pypi.org/project/apache-airflow-providers-arangodb/2.3.0rc1/
> > https://pypi.org/project/apache-airflow-providers-asana/2.3.0rc1/
> >
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/2.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-celery/3.4.0rc1/
> > https://pypi.org/project/apache-airflow-providers-cloudant/3.3.0rc1/
> >
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/7.7.0rc1/
> > https://pypi.org/project/apache-airflow-providers-common-sql/1.8.0rc1/
> > https://pypi.org/project/apache-airflow-providers-daskexecutor/1.1.0rc1/
> > https://pypi.org/project/apache-airflow-providers-databricks/4.6.0rc1/
> > https://pypi.org/project/apache-airflow-providers-datadog/3.4.0rc1/
> > https://pypi.org/project/apache-airflow-providers-dbt-cloud/3.4.0rc1/
> > https://pypi.org/project/apache-airflow-providers-dingding/3.3.0rc1/
> > https://pypi.org/project/apache-airflow-providers-discord/3.4.0rc1/
> > https://pypi.org/project/apache-airflow-providers-docker/3.8.0rc1/
> >
> https://pypi.org/project/apache-airflow-providers-elasticsearch/5.1.0rc1/
> > https://pypi.org/project/apache-airflow-providers-exasol/4.3.0rc1/
> > https://pypi.org/project/apache-airflow-providers-facebook/3.3.0rc1/
> > https://pypi.org/project/apache-airflow-providers-ftp/3.6.0rc1/
> >

Re: The "no_status" state

Re: [VOTE] Airflow Providers prepared on October 13, 2023

Re: [VOTE] Airflow Providers prepared on October 13, 2023

Re: [VOTE] Airflow Providers prepared on October 13, 2023

Re: [VOTE] Airflow Providers prepared on October 13, 2023

Re: [VOTE] Airflow Providers prepared on October 13, 2023

[ANNOUNCE] Apache Airflow Python Client 2.7.2 Released

[RESULT][VOTE] Release Airflow Python Client 2.7.2 from 2.7.2rc1

Re: [VOTE] Airflow Providers prepared on October 13, 2023

Re: [VOTE] Airflow Providers prepared on October 13, 2023

10 matches

Site Navigation

Mail list logo

Footer information