Re: Please unsubscribe me

Hi, You can do it by yourself, following the step shared at https://airflow.apache.org/community/ (send an email to mailto:dev-unsubscr...@airflow.apache.org to unsubscribe) Regards, XD On Mon, May 9, 2022 at 15:37 Neeku Endhuku Nenu cheppanu < idk.050...@gmail.com> wrote: > I am hereby writ

Re: Add Downloads page at Airflow Apache website?

nged our amazon keys) >> https://www.computerweekly.com/news/252499587/Codecov-supply-chain-attack-has-echoes-of-SolarWinds >> - having signatures and checksums is the only way some of the corporate >> players might be sure of the origin of the software. >> >> J. >&g

Re: Add Downloads page at Airflow Apache website?

Thanks Jarek for proposing this. One minor question I have on this is how we put this side-by-side with the " *Install*" tab/button on our site. Due to how Python packages work, for most users, there is no process of " *Download*". Instead, it is always an "*Install*" process. So for a new user v

Re: Releasing Apache Airflow's Python Client

wing > the semantic versioning more judiciously, so with that can we assume that > users would be cognizant of the related Airflow version implicitly, or do > you think we should mention something like *2.0.X* in the changelog > explicitly? > > On Wed, Mar 31, 2021 at 1:38 PM Deng

Re: Releasing Apache Airflow's Python Client

Thanks, Sumit, for bringing this up. - Regarding *versioning for Python client*: I favour the 1st way as well. The only minor comment I have is: instead of "*mention the release version of the main software*", possibly what users would expect is a "*range of compatible versions of main software*".

Re: Renaming master branches to main

You can refer to the info in this page for unsubscribing: https://airflow.apache.org/community/ This is the “Dev list” mentioned in the page above. Regards, XD On Tue, Mar 16, 2021 at 04:03 yongjie zhao wrote: > Hi, guys. who knows how can unsubscribe from this mail list and what is > the cur

Re: [DISCUSS] Major Version should contain new features or just removal of deprecation?

To me it should be *(b)*, especially given we intend to follow SemVar. People would have specific expectations on MAJOR/MINOR/PATCH if we claim SemVar is followed. *(a)* would cause confusion in such context. XD On Tue, Mar 9, 2021 at 12:43 AM Kaxil Naik wrote: >

Re: [VOTE] Airflow Backport Providers 2021.3.3rc1

+1 (binding) from me. Thanks everyone. XD On Sun, Mar 7, 2021 at 11:09 PM Jarek Potiuk wrote: > Same here, I'd really appreciate one more +1 here from a PMC member - we > know the backport providers are installing well and importing on the > 1.10.14 release (tested in CI). So I'd also love to

Re: [VOTE] Airflow Providers - release candidates from 2021-02-27

Thanks everyone for the efforts to make this release happen! +1 (binding) from me. XD On Sun, Mar 7, 2021 at 11:05 PM Jarek Potiuk wrote: > I'd really appreciate one more +1 here from a PMC. No matter what the > future holds for the provider's release. The vast majority of the providers > hav

Re: [Newsletter] Follow-up after 3 newsletters

+1. Absolutely a good idea. Thanks again for the efforts you put, Karolina👍 On Tue, Feb 23, 2021 at 23:00 Kaxil Naik wrote: > I like the idea to, +1 > > On Tue, Feb 23, 2021, 21:38 Jarek Potiuk wrote: > >> YES >> >> On Tue, Feb 23, 2021 at 7:09 PM Karolina >> wrote: >> >>> Wow, I really like

Re: Create official Apache Airflow publication on Medium.com

It's a good idea to me! Maybe worthwhile discussing how the Publication will be managed to ensure high quality, like: criteria of stories/articles to include, review/approval process, etc. Regards, XD On Sat, Feb 20, 2021 at 9:29 AM Jarek Potiuk wrote: > I think this is a great idea. I did no

Re: Scoping out a new feature for 2.1: improving schedule_interval

A quick thought (*maybe not making sense*): if *schedule_interval* accepts a list of values, we may support much higher complexity. For example, I may want to schedule my jobs at every days' 04:05 AND 02:31 , which cannot be expressed by single Cron pattern. Then I may want to have *schedule_inter

Re: Measuring community state

Hi Tomek, I get the message "*Hi! This form is no longer open. If there's anything you would like to share please use our slack or devlist*" when I try to open the link you shared below. Just check if it's intentionally closed or if anything is wrong? Thanks. XD On Thu, Jan 14, 2021 at 4:16 P

Re: New Airflow Committer: Vikram Koka

Congrats Vikram! XD On Tue, Jan 5, 2021 at 18:25 Felix Uellendall wrote: > Congrats Vikram! Well deserved! > > Felix > > > > Sent from ProtonMail Mobile > > > On Tue, Jan 5, 2021 at 17:56, Tobiasz Kędzierski < > tobiasz.kedzier...@polidea.com> wrote: > > Congrats Vikram! > > On Tue, Jan 5, 202

Re: New PMC Member: Xiaodong Deng

Thanks, Tobiasz and Vikram! A big thanks to the community as well! XD On Mon, Jan 4, 2021 at 12:32 PM Tobiasz Kędzierski < tobiasz.kedzier...@polidea.com> wrote: > Congratulations XD! :) > > On Wed, Dec 30, 2020 at 1:50 AM Vikram Koka wrote: > >> Congratulations XD! >> Excellent work and well

Re: New PMC Member: Xiaodong Deng

Thanks, QP and Kamil! On Tue, Jan 5, 2021 at 05:24 Kamil Breguła wrote: > Congratulations! Well deserved! 🐅 > > On Wed, Dec 30, 2020, 01:23 Kaxil Naik wrote: > >> Hello Airflow Community, >> >> The Project Management Committee (PMC) for Apache Airflow >> has invited *Xiaodong Deng* to become a

Re: Edit access to propose new Airflow feature

Hi Zacharya, I have had a look at the issue. I think what Jarek & Tomek suggested was to share your detailed ideas/proposals in this devlist first (as an email), so that more community members can join the discussion and share their inputs. CWiki edit access is needed in order to draft an AIP (Ai

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

My only question is whether some other channels should be treated the same way as well? For example, channel “#newbie-question” XD On Wed, Dec 23, 2020 at 08:28 Sumit Maheshwari wrote: > Big +1 > > Another reason is that in Slack the history is very limited due to the > free plan. > > > On Wed

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

+1 (non-binding). The issues that can be confirmed in rc1/2 have been well fixed. Cannot wait to see the bunch of new nice features in 2.0 to be rolled out. XD On Thu, Dec 17, 2020 at 02:00 Maxime Beauchemin wrote: > +1 binding > > !!! > > On Wed, Dec 16, 2020 at 2:42

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

The issue you reported should not be considered as a bug of Airflow. simplejson implements JSONEncoder in an incompatible way from the JSONEncoder of Python built-in standard library json (which is used by Airflow). Meanwhile, simplejson is NOT Airflow's dependency. This should not be considered

Re: [VOTE] Release Apache Airflow 1.10.14 based on 1.10.14rc1

+1 (non-binding). In addition to the tests I did on 1.10.13rc1 (Py3.6, LocalExecutor, Postgres), I also validated the fix for the main issue found in 1.10.13 and confirmed the fix in 1.10.14rc1 works well. Thanks! XD On Fri, Dec 4, 2020 at 1:28 AM Kaxil Naik wrote: > Hello Apache Airflow Comm

Re: [VOTE] Approach for supported python versions

J. > > > On Thu, Dec 3, 2020 at 7:51 PM Deng Xiaodong wrote: > >> Thanks Jarek. >> >> To clarify on the 3rd point: I assume you meant "*We support a new >> version of Python after it is officially released, as soon as we manage to >> make it work

Re: [VOTE] Approach for supported python versions

Thanks Jarek. To clarify on the 3rd point: I assume you meant "*We support a new version of Python after it is officially released, as soon as we manage to make it work in our CI pipeline and release a new version of Airflow (non-Patch version) based on this CI setting-up (which might not be immed

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

I would agree with Tomek's suggestion in the beginning, i.e. to "*create better documentation around this feature (with examples and suggestions) instead of accepting XComs to code base.*". That may be a better balance to me personally. XD On Wed, Dec 2, 2020 at 5:21 PM Tomasz Urbaszek wrote:

Re: [VOTE] Release Apache Airflow 1.10.13 based on 1.10.13rc1

+1 (non-binding) Tested (LocalExecutor, Postgres): - scheduler-triggered DagRun - manually-triggered DagRun - As Admin, create Viewer user and delete that user - confirm that, As Viewer, cannot trigger DagRun + cannot access Security or Admin tabs + rejected when access /connection/list/ - As Admi

Re: Rewriting Breeze in Python ?

I agree with Kaxil’s point (or even a bit later, say when 2.0 gets relatively more “stable”). My aspect is more about to concentrate development/community focus. XD On Thu, Nov 12, 2020 at 00:05 Kaxil Naik wrote: > I think we should wait until 2.0 is out before discussing or even > gathering

Re: Proposal: Change default to LocalExecutor and (eventually) remove SequentialExecutor

Sounds good to me to enforce LocalExecutor (and ok to fail hard to me), when (and ONLY when) it’s confirmed user is using MySQL/Postgres. XD On Wed, Nov 11, 2020 at 19:19 Jarek Potiuk wrote: > How about this? Are we doing it for 2.0 :)? Changing default /failing hard > when Postgres/MySQL is u

Re: New Airflow Committer: Ryan Hamilton

Congrats Ryan! The UI improvements you kindly made are definitely a big progress of Airflow 👍 XD On Wed, Oct 28, 2020 at 6:53 PM QP Hou wrote: > Congrats Ryan and wellcome! Great to see dedicated UI engineers to > help modernize Airflow UI :D > > On Wed, Oct 28, 2020 at 10:01 AM Kaxil Naik wr

Re: Airflow Feature Design Feedback

I have the same concern as Yu Qian does, and a bit more elaborations follow below: - "log" table has fields: *id*, *dttm*, *dag_id*, *task_id*, *event*, *execution_date*, *owner*, *extra*. Seems to me only "*event*" or "*extra*"

Re: [VOTE] Enable Github Discussions on Apache Airflow Github Repo

+1. I did share some concerns with folks, but I think mostly already clarified well in the earlier discussion. XD > On 22 Sep 2020, at 9:00 PM, Daniel Imberman wrote: > > +1 > > via Newton Mail > > On Tu

Re: Discuss: should we allow HTML emails on dev@ list

+1 from me definitely. It makes sharing pictures etc much easier. XD On Mon, Sep 14, 2020 at 13:42 Ash Berlin-Taylor wrote: > Hi all, > > > > As I'm sure you are aware, right now the dev@ list does not allow HTML > > emails. I'm finding this more annoying as time goes on. > > > > It turns out

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

Personally I think it does not fit the scope of README very well, and does make the file unnecessarily long. So I would suggest to move it somewhere else too. XD On Tue, Aug 25, 2020 at 10:43 Tomasz Urbaszek wrote: > I agree with Sumit. Regarding opening a PR - Airflow website is also an > >

Re: [DISCUSS] Enable Github Discussions on Apache Airflow Github Repo

The only concern I can think of is it seems serving identical purpose of what Slack is serving at this moment (correct me if I’m wrong please). Then attentions (especially from folks who nicely volunteer to answer questions in community) would be distributed unnecessarily. XD > On 24 Aug 2020

Re: Simplifying the KubernetesExecutor

Hi Ping, Inserting images in the email body doesn’t work for this mail list. So we cannot actually see the pictures you shared. If you find them important, you may share the pictures somewhere then provide the links in the mail body. Thanks. XD On Mon, Aug 24, 2020 at 08:56 Ping Zhang wrote:

Re: [VOTE] Release Apache Airflow 1.10.12 based on 1.10.12rc3

+1 (non-binding). Have re-done the tests I did for for rc1. The minor issue I shared for rc1 has been fixed has well. # Environment - Run with Docker-compose - Python 3.6.10 - Postgres 12.2 - LocalExecutor Thanks Kaxil and everyone. XD > On 22 Aug 2020, at 4:38 PM, Jarek Potiuk wrote: > >

Re: [VOTE] Release Apache Airflow 1.10.12 based on 1.10.12rc1

Thanks a lot, Kaxil, for taking care of the release. And thanks to all contributors. +1 from me. # Environment - Run with Docker-compose - Python 3.6.10 - Postgres 12.2 - LocalExecutor # What's Tested - Run DAGs with CRON schedule and “None” schedule - Create users with Viewer or Op roles, and

Re: Separate Repo vs MonoRepo for Dockerfile & Helm Chart

Thanks Kaxil. Both ideas (having separate repos and having separate voting) sounds sensible to me. Cannot really think of significant drawbacks. XD > On 1 Jul 2020, at 9:35 PM, Kaxil Naik wrote: > > Forgot to mention, having them in separate repo also helps in better > managing each individ

Re: Language matters - don't use the term "whitelist" in Apache Airflow

Appreciate your effort, Ash. And a +1 for this. XD On Sun, Jun 7, 2020 at 23:31 Ash Berlin-Taylor wrote: > Hi everyone, > > I have just opened a PR to rename the few of the remaining instances of > whitelist or blacklist in our code base. (There weren't many.) There are > some we can't remove

Re: [VOTE] Release Apache Airflow 1.10.10 based on 1.10.10rc4

; http://airflow.apache.org/docs/stable/timezone.html#time-zone-aware-dags > <http://airflow.apache.org/docs/stable/timezone.html#time-zone-aware-dags> > > On Apr 7 2020, at 5:30 pm, Deng Xiaodong <mailto:xd.den...@gmail.com>> wrote: > > > Tha

Re: [VOTE] Release Apache Airflow 1.10.10 based on 1.10.10rc4

Thanks, Kaxil, for running the release! I tested with Python 3.6 + LocalExecutor + Postgres+RBAC in Docker environment ( https://github.com/XD-DENG/containerized-airflow/tree/airflow-1-10-10/localexecutor_postgres), including - Run example DAGs & self-defined DAG - Create users via both CLI and U

Re: New committer: Jiajie Zhong

Congratulations Jiajie! XD On Tue, Mar 31, 2020 at 19:29 Jarek Potiuk wrote: > The Project Management Committee (PMC) for Apache Airflow > has invited Jiajie Zhong to become a committer and we are pleased > to announce that he has accepted. > > For quite some time Jiajie makes contributions th

Re: [VOTE] AIP-15: Support Multiple-Schedulers for HA & Better Scheduling Performance

+1 (binding). Thanks for proceeding this AIP, Ash. XD On Tue, Mar 17, 2020 at 22:40 Ash Berlin-Taylor wrote: > Hi all, > > This email calls for a vote on the design proposed in AIP-15, found here > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103092651 > > A few notes

Re: [PROPOSAL][AIP-15 Support Multiple-Schedulers for HA & Better Scheduling Performance]

Would be happy to give +1 for this AIP later! XD On Mon, Mar 16, 2020 at 11:08 PM Ash Berlin-Taylor wrote: > Does anyone have any other opinions about this? If not I'd like to call a > vote (and start working on the code!) > > -ash > On Mar 3 2020, at 12:34 pm, Kaxil Naik wrote: > > The goal

Re: Stateless Webserver with DAG Serialization

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! Completely upleveling the experience using and > maintaining the webserver. Thank you so much everyone who contributed to >

Re: How delete mailinglist subscription

Hi Claudio, You can try to send a mail to dev-unsubscr...@airflow.apache.org Hope you can still keep in touch with the community in other ways :) XD On Tue, Feb 11, 2020 at 07:55 Claudio wrote: > Hello guys,How can I delete my subscription to Airflow dev mailing > list?Sorry but I can't mana

Re: Shorter release vote or 1.10.9 to pin Werkzeug dep

I agree with what Ash is proposing, and would like to give my +1. Thanks. XD > On 7 Feb 2020, at 2:05 PM, Ash Berlin-Taylor wrote: > > Hello all, > > So Werkzeug 1.0 was released this morning, and it finally broke a number of > direct or indirect dependencies of ours (Werkzeug is a WSGI help

Re: [AirFlow]: Pandas DataFrame Between Tasks

taFrame.to_feather.html > > > > R > > > > On Tue, 24 Dec 2019 at 07:52, Deng Xiaodong wrote: > > > > > > Hi David. > > > > > > The only “out of box” way to share data/information between tasks is > > XCom ( > > > > > &g

Re: [AirFlow]: Pandas DataFrame Between Tasks

Hi David. The only “out of box” way to share data/information between tasks is XCom ( https://airflow.apache.org/docs/stable/concepts.html?highlight=xcom#xcoms). For you case, the quick suggestion I can share is - either merging your tasks - or persisting your Pandas Dataframes somewhere then lo

Re: New Committer: Tomasz Urbaszek

Congrats Tomasz! Well deserved! XD On Fri, Dec 20, 2019 at 22:47 Driesprong, Fokko wrote: > Folks, > > The Project Management Committee (PMC) for Apache Airflow > has invited Tomasz Urbaszek to become a committer and we are > pleased to announce that he has accepted. > > He's super active in th

Re: [Discuss] AIP-23 Proposal "Migration out of Travis CI"

+1 for GitHub Actions. I have been using it for months for my side projects, and it’s working very well. I believe most of us are quite tired of the waiting time using Travis CI. The only point I would like to remind is whether we need to communicate with Infra/Legal team for this. XD On Tue, D

Re: [VOTE] Allow using asserts in Airflow code

-1 (binding). As shared earlier, the benefit it brings may not be enough to break even for me. And it’s not irreplaceable. XD > On 5 Dec 2019, at 11:10 PM, Kaxil Naik wrote: > > -1 (binding) it definitely seems to be a source of confusion and comparing > it to the advantages it provides, I w

Re: [DISCUSS] Using asserts in airflow code

-1 from me for using asserts in Airflow code. Firstly, as some folks pointed out, asserts are there mainly for debugging purposes. Second, even though using asserts may bring some benefits in specific context, it’s not enough to “break even” comparing with the potential confusions (e.g. blur boun

Re: New PMC members: Aizhamal and Kevin

Congratulations Kevin and Aizhamal! We do feel the positive differences you brought to the community! XD > On 23 Nov 2019, at 9:30 AM, Kevin Yang wrote: > > Thank you everyone! 🎉 Very excited to continue contributing and to help > guide the project as a member of the PMC. > > Cheers, > Kevin

Re: [VOTE] Accept new Airflow website contribution

+1 (binding) for the new website. It will be very value-adding. Thanks! XD On Fri, Nov 22, 2019 at 06:06 Kevin Yang wrote: > +1(binding) very excited about the new site. Thanks all. > > On Thu, Nov 21, 2019 at 12:19 PM Driesprong, Fokko > wrote: > > > Big +1 (binding) from my side. The new sit

Re: [Final review] Airflow website + need your input to the web copy

Very nice work! - Personally I quite like the moving background elements, and I do not find it distracting. I believe this is very subjective, and we can discuss on each other’s preference forever. So... But anyway, if there will be any vote, mine is +1 for the current one. - At Documentation

Re: Error Starting Scheduler

Thanks CLN. But I think it’s already marked in both README and setup.py that currently Airflow supports up to Python 3.7. So I think it’s already fine. Thanks! XD On Thu, Oct 31, 2019 at 08:15 clhub...@gmail.com wrote: > Resolved: > Apache Airflow not supported on Python 3.8 > > I got it to w

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

Looks good! Thanks for the nice work. I do see a few typos, but I believe this discussion is mainly for UX design so I will revisit typos only in next stage. Regarding UX: currently “Quick Start” is put separately from “Documentation” in your design, while I think “Quick Start” should be part o

Re: [VOTE] Change the Airflow logo

I vote for Option 2, out of these 3 nice designs. XD On Wed, Aug 21, 2019 at 21:02 Bas Harenslak wrote: > Option 1 > > > On 21 Aug 2019, at 15:08, raman gupta ramandu...@gmail.com>> wrote: > > Option 2. > > Thanks, > Raman Gupta > > On Wed, Aug 21, 2019 at 6:26 PM Vardan Gupta

Fwd: Jira Upgrade August 19th 0500 UTC

For contributors' notice: there will be a JIRA upgrade at the time shared below, and downtime is expected. > Begin forwarded message: > > Please be aware that Jira (https://issues.apache.org/jira) will be > unavailable for approximately 4 hours beginning August 19, 2019 0500 > UTC for migration

Re: Data Profiling / Graphs in RBAC UI?

Hi Damian, These feature are deprecated purposely in RBAC UI for security reasons. To my understanding there is no plan to develop replacements for them, since it’s a deprecation rather than a “missing feature”. XD On Fri, Aug 9, 2019 at 21:54 Shaw, Damian P. < damian.sha...@credit-suisse.com>

Re: Airflow DAG Serialisation

Yes, it’s something really worth exploring. Recently I just finished a POC on DAG serialisation as well, while the main objective was to allow “rewriting” some components, like worker (for specific operators/sensors), in languages other than Python. We’re also choosing JSON, so that most langua

Re: [VOTE] Release Apache Airflow 1.10.4rc1 as 1.10.4

+1 (non-binding). There is a minor issue: after clicking the new “Toggle Wrap” button in DAG Code View page, the line numbers on the left side may become unaligned with the code lines. However it’s not a blocker at all to me. Thanks Ash for running the release again, and thanks to all the contr

Re: [VOTE] Labelling scheme for the upcoming official docker images of Airflow

+1 (binding) Thanks for initiating the discussion and the voting. XD On Thu, Jun 27, 2019 at 12:57 Jarek Potiuk wrote: > Hello Airflow community, > > This email call for a vote on "Labelling scheme" for the docker images we > are going to publish at > https://cloud.docker.com/u/apache/reposito

Re: Field "owner" in DAG Model

owner? > I'm running 1.10.3 and in the Search bar it searches only DAG it doesn't > search by owner. > > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > On Wednesday, June 26, 2019 12:27 PM, Deng Xiaodong > wrote: > > > Hi fo

Field "owner" in DAG Model

Hi folks, In DAG Model, we have "owner" field. In earlier Flask-Admin based UI (which is already removed in master branch), it was used by "filter_by_user" config item in [webserver] section to help control access. But now seems it's not used anywhere already (correct me if I'm wrong). I would li

Re: I have joined Astronomer full-time !!

Congrats Kaxil. Have a nice marriage vacation! XD > On 23 Jun 2019, at 5:41 AM, Bas Harenslak > wrote: > > Congrats Kaxil on both events! > > Bas > > On 22 Jun 2019, at 11:53, Felix Uellendall > mailto:felix.uellend...@protonmail.com.INVALID>> > wrote: > > Congrats Kaxil :) > > Am 22/06/

Re: [DISCUSS] Change all example_dags's start_date to specific datetime

Please note that catchup_by_default is True by default. Imagine what will happen if you set these start_date to fixed dates ;-) XD On Fri, May 10, 2019 at 3:34 PM Jiajie Zhong wrote: > Hi Airflowers: > I start this thread proposal to change all example_dags's start_date > to specific datet

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

Congrats Kevin! XD On Wed, May 1, 2019 at 1:09 AM Daniel Imberman < dimberman.opensou...@gmail.com> wrote: > Congrats Kevin! > > On Tue, Apr 30, 2019 at 9:09 AM Aizhamal Nurmamat kyzy > wrote: > > > Congratulations Kevin! > > > > On Tue, Apr 30, 2019 at 02:06 Jiajie Zhong > > wrote: > > > > >

Re: [ANNOUNCE] Please welcome new Airflow committer Joshua Carp

Congrats Joshua! XD On Tue, Apr 30, 2019 at 05:56 Ash Berlin-Taylor wrote: > Nice to have you on the team > > And Bas, Jarek and anyone else I've missed recently! So many new > committers. Welcome all! > > -ash > > On 29 Apr 2019, at 22:52, Tao Feng wrote: > > > > Congrats Joshua! > > > > On M

Re: [ANNOUNCE] Please welcome new Airflow committer Bas Harenslak

Congrats Bas! XD > On 23 Apr 2019, at 6:26 PM, Kaxil Naik wrote: > > Congrats Bas :) > > On Tue, Apr 23, 2019 at 10:25 AM Jarek Potiuk > wrote: > >> Congrats Bas! >> >> J. >> >> On Tue, Apr 23, 2019 at 11:03 AM Driesprong, Fokko >> wrote: >> >>> All, >>> >>> I'm pleased to announce that

Re: Use -x when cherry-picking to v1-10 branches

Agree. XD On Tue, Apr 23, 2019 at 05:15 Kaxil Naik wrote: > Definitely, agreed. > > On Mon, Apr 22, 2019 at 9:28 PM Jarek Potiuk > wrote: > > > Hello Everyone (committers especially). > > > > I have a proposal to improve slightly the cherry-picking process between > > master and v1-10-branches

Re: Proposal: Directly tie Jira into Github for airflow

+1 > On 18 Apr 2019, at 5:28 AM, Kaxil Naik wrote: > > +1 > > On Wed, Apr 17, 2019, 22:25 Tao Feng wrote: > >> +1 >> >> On Wed, Apr 17, 2019 at 2:19 PM Ash Berlin-Taylor wrote: >> >>> +1 >>> >>> I've ask in #asfinfra (on the-asfk.slack.com) to see if we can actually >>> use that on the Ap

Re: [ANNOUNCE] Please welcome new Airflow committer Jarek Potiuk

Congrats Jarek! XD On Thu, Apr 18, 2019 at 05:08 Jarek Potiuk wrote: > Thanks a lot! It's an honor to be part of such great community and I am > happy to take more responsibility as commiter. Looking forward to what we > can do together! > > J.. > > Principal Software Engineer > Phone: +4866079

Re: Longer term Airflow planning

Some personal thoughts about the PR processing speed specifically. I'm trying to benchmark Airflow with other Apache projects (like Spark, Kafka), in terms of PR reviewing/merging speed: as at this moment, there are 400+ open PRs in Spark and 500+ open PRs in Kafka. On the other hand, there are 26

Re: Airflow 1.10.3 has been released!

Thanks Ash! XD On Thu, Apr 11, 2019 at 02:48 Tao Feng wrote: > Thanks Ash for the work! > > > On Wed, Apr 10, 2019 at 11:29 AM Aizhamal Nurmamat kyzy > wrote: > > > Thank you, Ash for all the work! > > > > On Wed, Apr 10, 2019 at 11:26 AM Driesprong, Fokko > > > wrote: > > > > > Thanks a lot

Re: [VOTE] Airflow 1.10.3rc2

+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 for 72 hours. Consider this my (binding) +1. > > Airflow 1.10.3 RC2 is available at: > https

Re: [VOTE] Accept AIP-3: Drop support for Python 2

+1 (non-bonding) On Sun, Mar 24, 2019 at 11:49 Tao Feng wrote: > +1 (binding) > > On Sat, Mar 23, 2019 at 4:19 PM Driesprong, Fokko > wrote: > > > Dear Airflow community, > > > > This email calls for a vote to accept Airflow Improvement Proposal 3: > Drop > > support for Python 2 > > > > The vo

Re: Welcome Daniel Imberman as a new committer!

Congrats Daniel! XD On Tue, Mar 19, 2019 at 06:56 Kevin Yang wrote: > Well deserved, congrats! > > Jarek Potiuk 于2019年3月18日 周一下午3:46写道： > > > Welcome Daniel! > > > > On Mon, Mar 18, 2019 at 11:43 PM Tao Feng wrote: > > > > > Hellow Airflowers, > > > > > > Please join the Apache Airflow PMC in

Re: Calling sudo to remove temp cfg file failed

Tried to have a quick check. Seems sudo will only be required when you use the “run_as_user” option in your task. May you confirm if it’s the case? If yes, possibly try not to use “run_as_user” if you don’t have root permission. XD On Thu, Mar 14, 2019 at 07:55 Junda Yang wrote: > Hi all, >

Re: [DISCUSS] AIP-12 Persist DAG into DB

Hi Kevin, The image you attached is not displayed properly. May you consider uploading it somewhere then provide a link instead? Thanks! XD On Fri, Mar 8, 2019 at 19:38 Kevin Yang wrote: > Hi all, > When I was preparing some work related to this AIP I found something very > concerning. I noti

Re: Welcoming Xiaodong Deng as a new commiter!

Thanks Everyone! XD On Thu, Mar 7, 2019 at 21:25 Ash Berlin-Taylor wrote: > Hello Airflowers, > > Please join the Apache Airflow PMC in welcoming our newest committer: > Xiaodong Deng (a.k.a. XD-DENG ). > > XD has been an active member of the community helping other

Re: Snowflake hook with key pair auth

Agree with Jiajie. You can consider writing the sample private key into a temp file at the beginning of your test, and clean it once it is done. XD On Thu, Mar 7, 2019 at 14:57 jiajie zhong wrote: > Due to this file just use it unittest, I think the best way is to generate > it in test file, ma

Re: Multiple Schedulers - "scheduler_lock"

A solution. No leader / master / slave or election process, > just equal workers that work together. > > Max > > On Sat, Mar 2, 2019 at 7:04 AM Deng Xiaodong wrote: > >> Get your point and agree. And the suggestion you gave lastly to random >> sort DAGs is a great idea

Re: Multiple Schedulers - "scheduler_lock"

ously compete for the same DAGs almost all the time. > > It can be mitigated super-easily by random sorting of the DAGs folder list > after it is prepared (it's file-system dependent now so we do not rely on > particular order) . Then the probability numbers will hold perfectly I >

Re: Multiple Schedulers - "scheduler_lock"

ent double-triggerring, we should make sure that 2 >>>> schedulers aren't processing the same DAG or DagRun at the same time. >>> That >>>> would mean for the scheduler to not start the process of locked DAGs, >> and >>>> by providing

Re: Multiple Schedulers - "scheduler_lock"

t; sequential then I will run again in some occasions. Everyone is having >> idempotent tasks right so no harm done? ;-) >> >> Have you encountered issues? Maybe work those out? >> >> Cheers >> Bolke. >> >> Ve

Re: Multiple Schedulers - "scheduler_lock"

in in some occasions. Everyone is having idempotent tasks > right so no harm done? ;-) > > Have you encountered issues? Maybe work those out? > > Cheers > Bolke. > > Verstuurd vanaf mijn iPad > >> Op 1 mrt. 2019 om 16:25 heeft Deng Xiaodong het &g

Multiple Schedulers - "scheduler_lock"

Hi Max, Following https://lists.apache.org/thread.html/0e21230e08f07ef6f8e3c59887e9005447d6932639d3ce16a103078f@%3Cdev.airflow.apache.org%3E , I’m trying to prepare an AI

Re: Change Airflow Dag Execution time timezone on Airflow UI

Hi Manu, Yes you are right. At this moment changing timezone in UI is not supported, if I’m not wrong. Feature to change timezone in UI may not be an easy/quick task: Changing the timezone in the navbar may be easy, but timezones in Tree view/Graph view, log files, etc., may take effort and time.

Re: Voting on AIPs - what's our process?

Great discussions! Two minor points from me: - For the workflow Ash summarised: may I remind that we may want to decide how long the vote on an AIP should be open as well (3, 5,or 7 days?). This can be decided later when the workflow is formalised. - For the process description Fokko proposed:

Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

My two cents: 1. Can we discuss on the timeline for 2.0? Another big change is FAB-UI ONLY, which is already in master branch. Personally I think it’s already worth considering 2.0, unless there is other existing expectation for 2.0. 2. Before we completely drop Python2 support, we can start add

Re: Usage of airflow/contrib/auth/backends/password_auth.py

schreef Shah Altaf >> My mistake, yes it's just for UI. Not for API. I'll be quiet now :-) >> >> >> >> On Thu, Jan 31, 2019 at 1:42 PM Deng Xiaodong wrote: >> >>> Hi Shah, >>> >>> Thanks for your reply. >>>

Re: Usage of airflow/contrib/auth/backends/password_auth.py

No, please do voice out if you have any concern or suggestion ;-) XD > On 31 Jan 2019, at 9:45 PM, Shah Altaf wrote: > > My mistake, yes it's just for UI. Not for API. I'll be quiet now :-) > > > > On Thu, Jan 31, 2019 at 1:42 PM Deng Xiaodong wrote: >

Re: Usage of airflow/contrib/auth/backends/password_auth.py

gt; > On Thu, Jan 31, 2019 at 1:08 PM Deng Xiaodong wrote: > >> Hi folks, >> >> As you may have noticed, the Flask-Admin based UI (non-RBAC) was already >> deprecated in the master branch. Some works are going on to further clean >> the codebase. >> &

Usage of airflow/contrib/auth/backends/password_auth.py

Hi folks, As you may have noticed, the Flask-Admin based UI (non-RBAC) was already deprecated in the master branch. Some works are going on to further clean the codebase. In the process, we found that there are some “legacy" modules in “airflow/contrib/auth/backends/

Re: [VOTE] Airflow 1.10.2rc3

Hi XD, > > I will test this and let you know. > > One more bug cropped up > https://issues.apache.org/jira/browse/AIRFLOW-3737 . @fokko or someone > with more K8s experience can have a look at it, please? > > Regards, > Kaxil > > On 21/01/2019, 09:05, &q

Re: Selecting S3 endpoint in S3 Connection

Hi Ivan, You can try to add your endpoint in extra confit of your connection, in JSON format, like “{‘host’: ‘’}”. XD On Mon, Jan 21, 2019 at 19:48 Iván Robla Albarrán wrote: > Hi, > > We have our S3 installion (NO AWS) > > Could you help me, how i have to configure the conection? Where and h

Re: Selecting S3 endpoint in S3 Connection

* “Extra Configuration”. You can find it in your connection edit page, the “Extra” section. XD On Mon, Jan 21, 2019 at 20:00 Deng Xiaodong wrote: > Hi Ivan, > > You can try to add your endpoint in extra confit of your connection, in > JSON format, like “{‘host’: ‘’}”. > > &g

Re: [VOTE] Airflow 1.10.2rc3

sue now. I agree that this should be a >> bug which should be fixed. Please remove my +1 vote for release if >> possible. >> >> On Sun, Jan 20, 2019 at 11:12 PM Deng Xiaodong >> wrote: >> >> > Hi Feng Tao, >> > >> > I tried again by de

Re: [VOTE] Airflow 1.10.2rc3

, Jan 21, 2019 at 12:03 Tao Feng wrote: > Hi Xiaodong, > > I just tried with a viewer role which can't reproduce your issue. I could > see all the roles without any issues. Have you reset your db with this rc? > > On Sun, Jan 20, 2019 at 9:50 PM Deng Xiaodong wrote: &g

  1   2   >