Re: [DISCUSS] Donating Airflow k8s Operator

Strong +1 On Thu, Sep 12, 2019 at 7:29 AM Aizhamal Nurmamat kyzy wrote: > Hello Airflow community, > > Over the last year, an engineer at Google developed, and open sourced a > Kubernetes operator to run Airflow[1]. Anyone can use it to deploy Airflow > on their k8s cluster freely. > > There hav

Re: [PLEASE PARTICIPATE][AIP-11] UI phase of Airflow website

Liked it very much. Great work. Should we add a link to the demo installation of Airflow? something like this https://demo.gethue.com. On Thu, Oct 3, 2019 at 11:12 PM Ry Walker wrote: > I love it - great work :) > > Sent via Superhuman ( https://sprh.mn/?vip=r...@rywalker.com ) > > On Thu, Oc

Re: [VOTE] AIP-24: Persisting serialized DAG in DB for webserver scalability

On this, I'm more aligned with the +1 community here. While I agree that this is not the complete solution and work doesn't stop here, but I see it as a stepping stone in the right direction. It's a very big challenge to develop and deliver a change of this magnitude, so I believe that should be do

Re: [VOTE] Accept donation of Airflow k8s Operator to Apache Airflow

+1 (binding) On Fri, Nov 22, 2019 at 12:47 PM Tao Feng wrote: > +1 (binding) > > On Thu, Nov 21, 2019 at 3:38 PM Tomasz Urbaszek < > tomasz.urbas...@polidea.com> > wrote: > > > +1 (non-binding) > > > > Tomek > > > > On Thu, 21 Nov 2019 at 19:52, Kamil Breguła > > wrote: > > > > > +1 (non bindin

Re: Big performance optimization of Scheduler - 10x faster , 2000+ fewer queries count

Awesome work guys!! Kudos to all of you 👏 On Wed, Feb 26, 2020 at 6:59 AM Jiajie Zhong wrote: > Good work! Thanks Kamil > > Best Wish > — Jiajie

Re: Stateless Webserver with DAG Serialization

Great stuff!! Thanks to everyone who contributed 👏 On Sat, Mar 14, 2020 at 2:26 PM Deng Xiaodong wrote: > It is really great news and would be a big plus. > > Thanks Kaxil, Ash, Anita, and Zhou Fang! > > > XD > > > On 14 Mar 2020, at 2:31 AM, Kevin Yang wrote: > > > > This is thrilling news! Co

Re: [DISCUSS] Stop using Jira (since we aren't using it properly)

I'm totally in favor of not using Jira, as they are serving hardly any purpose other than just a useless step before creating a PR. However, I don't think to make a GitHub issue mandatory is also a good step, as eventually, it'll meet the same fate of being opened just before opening a PR. So IMO

Re: [VOTE] Switch from using Jira to Github Issues

+1 binding On Mon, Mar 16, 2020 at 11:44 PM Kevin Yang wrote: > +1 binding > > On Mon, Mar 16, 2020 at 9:34 AM Tao Feng wrote: > > > +1 > > > > On Mon, Mar 16, 2020 at 7:36 AM Ash Berlin-Taylor > wrote: > > > > > The original discuss thread is here. > > > > > > https://lists.apache.org/thread.

Re: [VOTE] AIP-31: Airflow functional DAG definition

+1 binding On Thu, Mar 26, 2020 at 9:50 AM Chao-Han Tsai wrote: > +1 binding > > On Wed, Mar 25, 2020 at 1:56 PM Kaxil Naik wrote: > > > +1 binding > > > > On Wed, Mar 25, 2020 at 8:55 PM Dan Davydov > > > wrote: > > > > > Sorry +1 (binding) :). > > > > > > On Wed, Mar 25, 2020 at 4:53 PM Dan

Re: Move "Who uses Airflow?" (to Ecosystem? or new "users" page)?

Not sure, if I've seen such a list with any other open-source project. So I feel it's a bit awkward to list 100s of different companies and people names on the main page of an Apache project. Hence, +1 from my side to move the list somewhere else. On Tue, Aug 25, 2020 at 1:35 PM Jarek Potiuk wr

Re: [ANNOUNCEMENT] Breeze rewrite to Python finally completed !!! Congrats to Bowrna, Edith (and Elad as mentor)!

Awesome work Bowrna, Edith, and Jarek. 👏 On Tue, Oct 4, 2022 at 10:30 AM Felix Uellendall wrote: > Congrats & Well done! I love the new breeze! 🤩 It is so much more > user-friendly now. > > Best, > Felix > > > > Sent from Proton Mail for iOS > > > On Tue, Oct 4, 2022 at 06:45, Bowrna Prabhakaran

Re: [DISCUSSION] Release of API clients

There had been a discussion around this earlier, though I couldn't find the thread. So if we want to release clients with each Airflow release, then we've to move away from current semantic versioning, something which we had decided in that thread. Also, so far I've not seen any API changes in a p

Re: [DISCUSSION] Release of API clients

@Jarek Potiuk we are talking about the same thing & on the same page with versioning, though releasing clients with each Airflow release confuses me. On Tue, Nov 15, 2022 at 4:04 PM Jarek Potiuk wrote: > > > > There had been a discussion around this earlier, though I couldn't find > the thread.

Re: [DISCUSSION] Release of API clients

s simple: > > > > * release Airflow > > * do we need to release Python API Client -> if yes, release > > * do we need to release Go API Client -> if yes, release > > * release Docker Image > > > > I hope this "algorithm" is pretty straigh

Re: [DISCUSSION] Release of API clients

this or should I follow > up with a vote ? I think this one qualifies for a lazy consensus but I > would be glad to call for a 'normal' vote, just let me know :) > > > > Best regards, > > Pierre > > > > Le mer. 16 nov. 2022 à 06:17, Sumit Mah

Re: [LAZY CONSENSUS] Unsubscribe links in users@ mailing list footers

+1 On Fri, Mar 3, 2023 at 8:37 PM Beck, Vincent wrote: > +1 > > > > *From: *Elad Kalif > *Reply-To: *"dev@airflow.apache.org" > *Date: *Friday, March 3, 2023 at 9:50 AM > *To: *"dev@airflow.apache.org" > *Subject: *RE: [EXTERNAL][LAZY CONSENSUS] Unsubscribe links in users@ > mailing list foot

Re: [VOTE] Release Airflow Python Client 2.6.0 from 2.6.0rc3

+1 (binding). @Ephraim Anierobi the links are not correct in the email though, due to the VERSION keyword instead of the actual version. Please keep a note of that next time. On Tue, May 9, 2023 at 1:12 PM Jarek Potiuk wrote: > +1 (binding) - all looks good and docs are updated, checked sign

Re: [DISCUSS] API Clients Major version

The ask by Pierre is very valid and makes a lot of sense. When we defined this versioning system, we took a lot of inspiration from Python clients of other famous OSS software like Kubernetes & probably did not think of the versioning changes in the generator itself. I looked at the k8s python-cli

Re: [VOTE] AIP 61 - Hybrid Executors

+1 (binding) On Fri, Feb 2, 2024 at 8:18 PM Bishundeo, Rajeshwar wrote: > +1 (non-binding) > This will be an awesome feature!! > > -- Rajesh > > > > > > > On 2024-02-02, 12:44 AM, "Mehta, Shubham" LID> wrote: > > > CAUTION: This email originated from outside of t

Re: Call with Nielsen team demoing their DAG debugging feature

Same, add me as well. Thanks!! On Sat, Jun 8, 2024 at 2:27 PM Kaxil Naik wrote: > Same, would love to join > > On Sat, 8 Jun 2024 at 09:19, Aritra Basu wrote: > > > Hi Jarek, > > > > I'd be interested to join. > > > > -- > > Regards, > > Aritra Basu > > > > On Sat, Jun 8, 2024, 12:24 PM Jarek P

Re: [Meeting Notes] Airflow 3.0 Dev call - 13 June 2024

Thanks Kaxil for MoM. I missed the last session but will try to join the next one. On Mon, Jun 17, 2024 at 11:52 AM Amogh Desai wrote: > You have covered the minutes of the meeting thoroughly, Kaxil. > > Finally got the calls added to my calendar too :) > > Thanks & Regards, > Amogh Desai > > >

Re: Airflow Feature Design Feedback

+1 for the feature. Looking at the schema of the log table, I think it's perfect to store such kind of information. On Fri, Oct 16, 2020 at 9:55 PM Daniel Imberman wrote: > This could be pretty valuable for future audits. I’d personally rather > avoid adding fields to the DB in general. Could we

Re: A Visual Editor for Airflow pipelines

Is there any open PR in Elyra, where any of the mentioned approach (api, s3, git-sync etc) has been tried out? I think it's important for Airflow devs to know the underlying architecture of Elyra to suggest something. By a quick look at the .pipeline JSON file, it seems like you would need to do a

Re: [DISCUSS] Custom XCom backends in core or not

My 2 cents on this: What is wrong with having some code which can be used by multiple users. What is the point in 10s of 100s of companies maintaining their own implementation of things. Isn't that we've separated providers from the core so that the priority of maintaining them wouldn't be the sam

Re: [VOTE] Release Apache Airflow 2.0.0 form 2.0.0rc3

Great work indeed & looking forward to it. My big +1 for the release, though I've not tested it myself, so ideally the vote doesn't count. On Thu, Dec 17, 2020 at 12:44 PM Tao Feng wrote: > +1 (binding) great work! > > On Wed, Dec 16, 2020 at 23:02 Deng Xiaodong wrote: > >> +1 (non-binding). >>

Re: [DISCUSS] Switch off / Prefer GitHub discussions over slack #troubleshooting channel?

Big +1 Another reason is that in Slack the history is very limited due to the free plan. On Wed, Dec 23, 2020 at 11:35 AM Jarek Potiuk wrote: > Hello everyone, > > I had a thought - should we start redirecting people and maybe even > disable the #troubleshooting channel in our Slack? (includin

Re: Builds Meeting this Thursday

Thanks for the heads-up Jarek, Will it be recorded? On Wed, Jan 13, 2021 at 3:15 AM Jarek Potiuk wrote: > For those who are interested in performance/security of Github Actions, > there is a meeting of "builds" for ASF this Thursday - where Brian Douglas > Github's Staff Developers Advocate wi

Re: [DISCUSS][AIP-38 Modern Web Application]

Wow, the new demo UI is super slick and awesome. Great work Ryan and Brent. 👏 On Thu, Feb 25, 2021 at 2:59 PM Jarek Potiuk wrote: > For whatever reason there was an ".invalid" added to your address in > reply, so let me just resend it :) > > On Thu, Feb 25, 2021 at 10:28 AM Jarek Potiuk wrote:

Re: New Committers: James Timmins, Elad Kalif & Daniel Standish

Congratulations to all!! On Mon, Mar 1, 2021 at 9:26 PM Felix Uellendall wrote: > Congrats! Well deserved! :) > > > > Sent from ProtonMail Mobile > > > On Mon, Mar 1, 2021 at 16:42, Vikram Koka > wrote: > > Congratulations James, Elad, and Daniel, great work! > > > On Mon, Mar 1, 2021 at 6:57 A

Re: [VOTE] AIP-38: Modern Web Application

+1 (binding) On Wed, Mar 3, 2021 at 9:48 PM Vikram Koka wrote: > Ryan and Brent, > > Great job on the AIP and looking forward to seeing this happen. > > +1 (binding) > > > > On Wed, Mar 3, 2021 at 8:16 AM Redwan Rahman > wrote: > >> +1 (non-binding) >> >> On Wed, Mar 3, 2021 at 10:31 AM Ryan Ha

Releasing Apache Airflow's Python Client

che/airflow-client-go> clients, so should we try to release them together or they should follow their own paths? In general, I'm against batching them together, cause the person who is releasing them may not be able to test all the different clients in the future. Let me know your thoughts on these 2 points. Thanks, Sumit Maheshwari PMC Apache Airflow

Re: Releasing Apache Airflow's Python Client

mp the python client version just for a bug fix in > the go client. > > Thanks, > QP > > On Tue, Mar 30, 2021 at 1:56 AM Sumit Maheshwari > wrote: > > > > Hello Airflow dev community > > > > I'm writing this mail in regards to seek feedback on the f

Re: Releasing Apache Airflow's Python Client

the release of different client libraries*: I agree with > you. They should be versioned & released separately. > > > Regards, > XD > > On Wed, Mar 31, 2021 at 9:21 AM Sumit Maheshwari > wrote: > >> Thanks QP for your feedback. I think the latest release of K8s cl

Re: Releasing Apache Airflow's Python Client

not do this and this (and of course it will >>> not have neither client nor airflow version specified and we will have to >>> ask for clarification). >>> >> >>> >> So as I see it - maybe release-wise it's a little redundant and you'd >>> have t

Re: Releasing Apache Airflow's Python Client

nicest approach for both users and maintainers. > In this case we do not even have to maintain the 'compatibility' matrix i > mentioned before. And we keep 100% Semver semantics. And we can add > automated tests for all the 'last X.Y client + airflow' combination as >

Re: Releasing Apache Airflow's Python Client

e on the client side. For example, the first release of the Python client would be *2.0.0* which would be based on *Airflow 2.0.1*. On Mon, Apr 5, 2021 at 5:46 PM Sumit Maheshwari wrote: > I think I'm fine with the approach you suggested Jarek. This approach > mitigates the need to

[VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc1

is no changelog. The source code for this release can be found here: https://github.com/apache/airflow-client-python/tree/r2.0 Thanks, Sumit Maheshwari PMC Apache Airflow

Re: [VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc1

c1: > > airflow-client-2.0.0rc1license-templates/ > airflow-client-2.0.0rc1airflow_client/ > airflow-client-2.0.0rc1.github/ > ... > > J. > > > > > On Wed, Apr 7, 2021 at 2:34 PM Sumit Maheshwari wrote: > >> Hello everyone, >> >> I have cut th

Re: [VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc1

I think I've used an extra prefix while preparing the tar, fixed it now. Please check. TIA. On Thu, Apr 8, 2021 at 1:06 PM Sumit Maheshwari wrote: > Seems weird. Thanks for letting me know, checking it now. > > On Thu, Apr 8, 2021 at 2:30 AM Jarek Potiuk wrote: > >> H

Re: [VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc1

e) where we have a description of the release > process. It is necessary to make it repeatable so that anyone can do it. > There we also need to have a description about adding TAG to the release > (and potentially moving the 'stable") tag when the final release is made

Re: [VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc1

Thanks to Jarek, we've fixed almost all the shortcomings with the first release candidate. I'm going ahead and closing this voting thread and would start another for the rc2. - Sumit On Mon, Apr 12, 2021 at 12:33 PM Sumit Maheshwari wrote: > Thanks a lot, Jarek for the detailed

[VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc2

is no changelog. The source code for this release can be found here: https://github.com/apache/airflow-client-python/tree/r2.0 Thanks, Sumit Maheshwari PMC Apache Airflow

Re: [DISCUSS] Dag Calendar View proposal

Nice thoughts, it would be a good addition to Airflow. A couple of suggestions: - A 3yr history is a lot, and most probably everyone out there cleanup data older than 3-6 months. Also, it might involve a heavy query for the datastore to handle. I would prefer a week or month view like we

Re: [VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc2

in PyPI is "airflow-client". But all other >>> packages of ours start with "apache-airflow". >>> >>> I think (Ash , Kaxil?) we are obliged to use 'apache' as the name of the >>> package. >>> >>> I think that calls for

Re: [VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc2

Thanks for the confirmation Jarek. I would create a new Voting thread, hence closing this one. On Wed, Apr 14, 2021 at 1:21 PM Jarek Potiuk wrote: > correct > > On Wed, Apr 14, 2021 at 6:05 AM Sumit Maheshwari > wrote: > >> Thanks, Jarek and Kaxil for catching thi

Re: Searchable Slack archives are now here -- if we want it.

Great work Ash, +1 from my side on keeping this. Also liked the domain "slack-archives.org" :) On Wed, Apr 14, 2021 at 6:10 PM Ash Berlin-Taylor wrote: > Hello everyone, > > Thanks to prompting from Sumit, I have "resurrected" a project I started > back in 2019, and have got searchable slack

Re: Support WebHook Alerting

Yeah, we've been using on_failure_callbacks for a long time and sending alerts to slack and pagerduty. On Thu, Apr 15, 2021 at 4:30 PM Ash Berlin-Taylor wrote: > Yes, this sounds like a good feature, but I would go about it in a > slightly different way that is less "special cased" to just chat

[VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc3

elease and vote with "(non-binding)". As this is the first release, there is no changelog. The source code for this release can be found here: https://github.com/apache/airflow-client-python/tree/r2.0 Thanks, Sumit Maheshwari PMC Apache Airflow

Re: [VOTE] Release Airflow Python Client 2.0.0 based on 2.0.0rc3

irflow_client module. >> >> +1 binding. >> >> >> On Mon, 19 Apr, 2021 at 20:49, Jarek Potiuk wrote: >> >> +1 (binding). Checked the signatures etc. Installed client locally and >> run it with airflow. All looks good ! >> >> On Mon, Apr 19, 202

[RESULT][VOTE] Release Airflow Python Client 2.0.0

/r9f0477a710f1e94818b5b0a313fff963470b6c8da677705912d4f823%40%3Cdev.airflow.apache.org%3E I'll continue with the release process, and the release announcement will follow shortly. Thanks, Sumit Maheshwari PMC Apache Airflow

Re: [RESULT][VOTE] Release Airflow Python Client 2.0.0

Oops, my bad. Thanks, Ash for pointing it out. Will wait for 72hrs & resend the results. On Tue, Apr 20, 2021 at 12:56 PM Ash Berlin-Taylor wrote: > Hi Sumit, > > We need to wait for the 72 hour period first - the vote is not yet over > > -ash > > On 20 April 2021 07:43

Re: [DISCUSS] AIP-1 and Airflow multi-tenancy

I'll join as well (I believe the zoom link will work without an invite) On Wed, Apr 21, 2021 at 10:48 AM Dimitris Stafylarakis wrote: > hi all, > > great to read about this, I'd like to join in! Can I just join using the > zoom link tomorrow or do I need an invitation? (If I do need one, please

[RESULT][VOTE] Release Airflow Python Client 2.0.0

/r9f0477a710f1e94818b5b0a313fff963470b6c8da677705912d4f823%40%3Cdev.airflow.apache.org%3E I'll continue with the release process, and the release announcement will follow shortly. Thanks, Sumit Maheshwari PMC Apache Airflow

Airflow Airflow Client 2.0.0 is released

ailable on PyPi for convenience (`pip install apache-airflow-client`): https://pypi.python.org/pypi/apache-airflow-client The documentation is available on: https://airflow.apache.org/ Find the CHANGELOG here for more details: https://github.com/apache/airflow-client-python/blob/2.0.0/CHANGELOG.md

Re: Airflow Airflow Client 2.0.0 is released

Thanks, Jarek for testing the stuff multiple times, and providing guidance throughout the process :) On Fri, Apr 23, 2021 at 2:45 PM Jarek Potiuk wrote: > Wohoo! Congrats ! Good job Sumit! > > On Fri, Apr 23, 2021 at 10:20 AM Sumit Maheshwari > wrote: > >> Dear Airflow

Re: Airflow Airflow Client 2.0.0 is released

k to the >> client github repo from pypi :) >> >> Thanks, >> QP Hou >> >> On Fri, Apr 23, 2021 at 1:20 AM Sumit Maheshwari >> wrote: >> > >> > Dear Airflow community, >> > >> > I'm happy to announce that Apache Airfl

Re: Airflow Airflow Client 2.0.0 is released

t; > J. > > On Sat, Apr 24, 2021 at 11:14 AM Sumit Maheshwari > wrote: > >> Hi QP, >> >> Yes, I had updated the readme right after the first release. Will update >> the PyPi page as well & link it to the GitHub repo. Thanks. >> >> On Sat, Apr 2

Re: [ANNOUNCE] Apache Airflow Helm Chart version 1.0.0 Released

Awesome work guys 👏 On Thu, May 20, 2021 at 2:19 PM Tomasz Urbaszek wrote: > Big kudos to everyone who enabled that! > > On Thu, 20 May 2021 at 10:37, Jarek Potiuk wrote: > >> Great! This is a major step forward for the community! >> >> On Thu, May 20, 2021 at 4:57 AM Vikram Koka >> wrote: >>

Re: MSSQL compatbility for Airflow, YAY!

Awesome.. Great work Aneesh & Jarek.. 👏👏 On Wed, May 26, 2021 at 3:11 PM Jarek Potiuk wrote: > Hello everyone, > > After a long struggle and ENORMOUS effort from Aneesh Joseph we have > just merged the PR that adds MSSQL for the Dev version of Airflow. > https://github.com/apache/airflow/pul

[VOTE] Release Airflow Python Client 2.1.0 based on 2.1.0rc1

e and vote with "(non-binding)". *Changelog*: *Major changes:*Client code is generated using OpenApi's 5.1.1 generator CLI *Major fixes:*Fixed the iteration issue on array items caused by unsupported class 'object' (issue #15) *New API supported:*Permissions Plugins Pr

Re: [VOTE] Release Airflow Python Client 2.1.0 based on 2.1.0rc1

sue" and we are waiting > for new version of Open API generator ? > > J > > On Thu, May 27, 2021 at 9:25 AM Sumit Maheshwari > wrote: > >> Hello everyone, >> >> I have cut the first release candidate for the Airflow Python Client >> 2.1.0. The client c

[RESULT][VOTE] Release Airflow Python Client 2.1.0

Hello Dev Community, The release of Apache Airflow Client 2.1.0 (based on RC1) has been accepted. 3 “+1” binding votes received: - Jarek Potiuk (binding) - Kaxil Naik (binding) - Sumit Maheshwari (binding) No "-1" votes received Vote thread: https://lists.apache.org/t

[ANNOUNCE] Apache Airflow Python Client version 2.1.0 Released

/master/CHANGELOG.md#v210 Cheers, Sumit Maheshwari PMC Apache Airflow

Re: Renaming master branch to main is now done.

👏👏 On Tue, Jun 1, 2021 at 3:57 PM Dennis Akpenyi wrote: > Great Job! > > On Tue, Jun 1, 2021 at 12:19 PM Jarek Potiuk wrote: > >> Wohoo! >> >> On Tue, Jun 1, 2021 at 12:06 PM Ash Berlin-Taylor wrote: >> >>> Hi everyone, >>> >>> This rename has now happened, and the default brach for apache/air

Re: Advice on running local dev webserver

This is how I run webserver on local: 1. Checkout the code from GitHub 2. Create or activate a python3 virtualenv 3. Within Airflow dir, do a "python setup.py install" or "pip install -e ." 4. Run "./airflow/www/compile_assets.sh" to compile JS assets 5. If this is the first time you are running A

Re: [VOTE] Release Airflow Python Client 2.1.0 based on 2.1.0rc1

Thanks, Justin for letting us know about the missing NOTICE file. We'll add that asap. Regards, Sumit On Thu, Jun 10, 2021 at 6:26 AM Justin Mclean wrote: > Hi, > > I'm not on your PMC but I took a look at this release and noticed it was > missing a NOTICE file you might want to look into th

Re: [DISCUSS] Managing provider Connections via UI in managed Airflow services

A question for AWS & GCP folks, how would a user be able to use some custom dependencies (pip packages) in their setups, especially for the previous Airflow versions, where the Airflow webserver would need all the packages. If there is a way to solve that, then the same can be used for providers as

Re: Roadmap ideas for Airflow 2.2 and beyond

I have some working code saved in my git stash on what Rob suggested. I implemented pre_state_changed_callback and post_state_changed_callback to handle and react to any state change of a dag_run. However, given that dga_run can be updated by the webserver as well, which means executing Python code

Re: [ANNOUNCE] Airflow 2.2.0 is released

Awesome 👏 On Tue, Oct 12, 2021 at 11:13 AM Kaxil Naik wrote: > That's another big milestone for Airflow. > > Thank you to everyone who contributed to this release and Jed for steering > this release. > > Regards, > Kaxil > > On Tue, Oct 12, 2021 at 2:46 AM Javier Lopez > wrote: > >> There are s

[VOTE] Release Airflow Python Client 2.2.0 based on 2.2.0rc1

un_id} | Modify a DAG run DELETE /users/{username} | Delete a user PATCH /users/{username} | Update a user POST /users | Create a user Thanks, Sumit Maheshwari PMC Apache Airflow

Re: [VOTE] Release Airflow Python Client 2.2.0 based on 2.2.0rc1

Gentle reminder On Thu, Nov 18, 2021 at 5:59 PM Sumit Maheshwari wrote: > Hello everyone, > > I have cut the first release candidate for the Airflow Python Client 2.2.0. > The client consists of APIs corresponding to REST APIs available in > *Apache Airflow 2.2.2* release. This e

[RESULT][VOTE] Release Airflow Python Client 2.2.0

Hello Dev Community, The release of Apache Airflow Client 2.2.0 (based on RC1) has been accepted. 5 “+1” binding votes received: - Jarek Potiuk (binding) - Kaxil Naik (binding) - Ephraim Anierobi - Kamil Bregula - Sumit Maheshwari (binding) No "-1" votes received Vote thr

[ANNOUNCE] Apache Airflow Python Client version 2.2.0 Released

/blob/master/CHANGELOG.md Cheers, Sumit Maheshwari PMC Apache Airflow

Re: Please vote on the PR of the Month for this month's Airflow Newsletter!

24284 On Tue, Jun 28, 2022 at 7:52 AM Jarek Potiuk wrote: > * 24284 by far > > On Mon, Jun 27, 2022 at 11:21 PM Jed Cunningham > wrote: > > > > My write in is 24249, which adds viewing task logs in the new Grid UI: > https://github.com/apache/airflow/pull/24249 > > > > If we are doing this rank

[VOTE] Release Airflow Python Client 2.3.0 based on 2.3.0rc1

skInstances/{task_id}/listMapped | List mapped task instances Thanks, Sumit Maheshwari PMC Apache Airflow

Re: [VOTE] Release Airflow Python Client 2.3.0 based on 2.3.0rc1

ouldn't do. (Since it's under airflow_client/ folder we don't > need to fix it now, but we should fix it before the next release please) > > -ash > > On Thu, Jul 28 2022 at 01:19:53 +05:30:00, Sumit Maheshwari < > sumeet.ma...@gmail.com> wrote: > > Hello everyo

Re: [VOTE] Release Airflow Python Client 2.3.0 based on 2.3.0rc1

maybe remove it too and make it part of the documentation > https://airflow.apache.org/docs/ ? Currently it redirects to the repo, > but having the docs on our side would be a nice touch. > > J. > > > > On Thu, Jul 28, 2022 at 2:04 PM Sumit Maheshwari > wrote: > >

Re: [VOTE] Release Airflow Python Client 2.3.0 based on 2.3.0rc1

removing them from the package later I guess. > > J > > On Thu, Jul 28, 2022 at 7:01 PM Sumit Maheshwari > wrote: > >> Thanks Jarek, >> >> Yeah, I don't think that any of the existing issues got fixed in this >> release. To fix these issues we prolly n

[RESULT][VOTE] Release Airflow Python Client 2.3.0

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: https://lists.

[ANNOUNCE] Apache Airflow Python Client version 2.3.0 Released

tails: https://github.com/apache/airflow-client-python/blob/master/CHANGELOG.md Cheers, Sumit Maheshwari PMC Apache Airflow

Why docs are still pointing to old days.

Folks, I see that link to documentation for Airflow's GitHub page takes to some older version of docs at https://airflow.apache.org, while the latest docs are available at https://airflow.readthedocs.io/en/latest/. Does someone know the reason behind this behavior and how we can fix this? Thanks

Re: Why docs are still pointing to old days.

release (as mentioned on > the > girhub readme) and the readthedocs page contains verisoned documentation > (latest, latest stable, 1.10,1.9, etc) > > Regards, > > Kaxil > > On Fri, Jan 11, 2019, 08:11 Sumit Maheshwari wrote: > > > Folks, > > > > I see that li

Re: Why docs are still pointing to old days.

ahh!! my bad. I always scroll to the last :) On Fri, Jan 11, 2019 at 3:07 PM Kaxil Naik wrote: > We do have it. Check the getting started section :) > > On Fri, Jan 11, 2019, 09:18 Sumit Maheshwari wrote: > > > Thanks for the info Kaxil. > > > > In that case s

Re: [VOTE] Airflow 1.10.3rc2

+1 (binding) On Mon, Apr 8, 2019 at 10:04 AM Deng Xiaodong wrote: > +1 (non-binding) > > Thanks a lot Ash. > > > XD > > On Sun, Apr 7, 2019 at 16:03 Ash Berlin-Taylor wrote: > > > Hey all, > > > > I have cut Airflow 1.10.3 RC2. This email is calling a vote on the > > release, which will last fo

Re: Airflow 1.10.3 has been released!

Kudos to Ash!! On Thu, Apr 11, 2019 at 12:34 PM Chao-Han Tsai wrote: > Thanks Ash! > > On Wed, Apr 10, 2019 at 6:07 PM Jiajie Zhong > wrote: > > > Thanks Ash! > > > > Best wish. > > -- Jiajie > > > > From: Deng Xiaodong > > Sent: Thursday, April 11, 2019 7:13 >

Re: [ANNOUNCE] Please welcome new Airflow committer Kevin Yang

Welcome, Kevin!! On Sat, May 4, 2019 at 9:29 PM Bolke de Bruin wrote: > Welcome! > > Sent from my iPhone > > > On 2 May 2019, at 11:59, Szymon Przedwojski < > szymon.przedwoj...@polidea.com> wrote: > > > > Congratulations Kevin! > > > > Szymon Przedwojski > > Polidea | Software Engineer > > > >

Re: Announcement: I'm joining Astronomer!

Congrats Daniel. Really good news for Airflow. On Fri, May 31, 2019 at 5:05 AM Jarek Potiuk wrote: > Congrats! > > On Fri, May 31, 2019 at 12:54 AM Tao Feng wrote: > > > Daniel, > > > > Congrats! Win-win for you, Airflow and Astronomer! > > > > Best, > > -Tao > > > > On Thu, May 30, 2019 at 3:3

Re: [VOTE] AIP-16: CLI: Use nested commands instead of flags

+1 (binding) On Tue, Jun 11, 2019 at 8:19 PM James Meickle wrote: > +1 (non-binding) > > On Tue, Jun 11, 2019 at 7:15 AM Ash Berlin-Taylor wrote: > > > Hi Airflowers, > > > > This email calls for a vote to introduce restructure the CLI to use > nested > > commands instead of flags. The vote wil

Re: I have joined Astronomer full-time !!

Congrats for both the big moves Kaxil :) On Fri, Jun 21, 2019 at 12:42 PM Bolke de Bruin wrote: > Awesome! Congrats twice! > > Looking forward to catch-up in London after the summer. > > Sent from my iPhone > > > On 21 Jun 2019, at 21:11, Ash Berlin-Taylor wrote: > > > > Looking forward to seei

Re: Airflow meetup in India

Last year I did one survey for interested people to join and talk for Airflow meetup, but the response wasn't very overwhelming. Maybe this time things got changed. My employer (Twitter) would be happy to help in anyway possible. On Fri, Aug 16, 2019 at 12:39 PM Maulik Soneji wrote: > +1 for t

Re: [DISCUSS] Tweaks to the Airflow logo

Loved the new pinwheel logo. Thanks, Chris and Daniel. On Fri, Aug 16, 2019 at 10:07 AM Chao-Han Tsai wrote: > Thanks Chris for the new Airflow logo. > > Personally I like the new pinwheel design better. Its fins are more > natural as they seem be made by folding four Isosceles right triangle >

Re: Airflow meetup in India

gt;> > >> > > Interested. We use airflow extensively at Walmart labs. >> > > >> > > On Fri, 16 Aug, 2019, 1:03 PM Sumit Maheshwari, < >> sumeet.ma...@gmail.com> >> > > wrote: >> > > >> > > > Las

Re: Airflow meetup in India

il > > On Mon, Aug 19, 2019 at 5:03 AM ramandu...@gmail.com > > wrote: > > > We are from Noida but would be open to participate in Bangalore's meetup. > > > > Thanks, > > Raman Gupta > > On 2019/08/18 04:40:27, Sumit Maheshwari wrote: > &

Re: Airflow meetup in India

sponsor the > > events. > > > > Hope to coordinate and arrange the 1st meetup soon. > > > > Regards, > > Kaxil > > > > On Mon, Aug 19, 2019 at 1:07 PM raman gupta > wrote: > > > > > +1. > > > Thanks, > > &g

Re: [IE] Re: [VOTE] Change the Airflow logo

Option 1 On Wed, Aug 21, 2019 at 10:54 PM Chen Tong wrote: > Option 1! > > On Wed, Aug 21, 2019 at 1:18 PM Felipe Elias Lolas Isuani < > felipe.elias...@gmail.com> wrote: > > > Option 1 👏 > > > > El 21-08-2019, a la(s) 12:56, Maxime Beauchemin < > > maximebeauche...@gmail.com> escribió: > > > >

Re: New committer: Rahul Vats

Congratulations Rahul 🎉 On Wed, Apr 2, 2025 at 4:59 PM Freddy Demiane wrote: > Congratulations Rahul! > > On Wed, Apr 2, 2025 at 12:27 PM Rahul Vats wrote: > > > Thank you, everyone. It is great to be part of the team. I truly > appreciate > > all the guidance and support from the community. >

Re: [DISCUSS] Apache Airflow official MCP Server

At Uber, we've been using GenAI to debug task failures and suggest further mitigation steps to our users. We would love to collaborate on this project and share our learnings & contribute. On Mon, Jun 2, 2025 at 11:09 AM Amogh Desai wrote: > I agree that a use case driven approach is the way to

[DISCUSS] AIP-92 Isolate DAG parsing logic

Hello everyone, I have created a draft version to separate the running of DAG processor from Airflow's core services and moved it closer to the execution side. Please review the proposal and provide your valuable feedback. PS: We are in the process of adopting Airflow3 from some in-house setup,

Re: [DISCUSS] AIP-92 Isolate DAG parsing logic

> with the goals of making Airflow well-scalable beyond a single-team > deployment (and AIP-85 goals), so you have my full support with this one. > > I've left a couple of clarification requests on the AIP page. > > Thanks, > Igor > > On Fri, Jul 25, 2025 at 11:50 AM

Re: [DISCUSS] AIP-92 Isolate DAG parsing logic

Thanks Jarek and Ash, for the initial review. It's good to know that the DAG processor has some preemptive measures in place to prevent access to the DB. However, the main issue we are trying to solve is not to provide DB creds to the customer teams, who are using Airflow as a multi-tenant orchestr

  1   2   >