No apologies needed :) . It's not always easy to figure out all the
communication "standards" in the community :).
J.
On Tue, Feb 1, 2022 at 10:53 PM Giorgio Zoppi
wrote:
> Hello,
> my apologies for the inappropriate questions.
> I'll file an issue when it's needed.
> Best Regards,
> Giorgio.
Hello,
my apologies for the inappropriate questions.
I'll file an issue when it's needed.
Best Regards,
Giorgio.
Il giorno mar 1 feb 2022 alle ore 22:38 Jarek Potiuk ha
scritto:
> I think this is not the best place to ask those kinds of questions. Please
> open a slack question or Github
I think this is not the best place to ask those kinds of questions. Please
open a slack question or Github Discussions if you want to discuss "using"
of airflow. All links here: https://airflow.apache.org/community/
Also - if I may suggest you - you asked a very imprecise question and you
are
Hi devs,
I have tried multiple LocalExecutors in 16GB vm and sometimes
I have experienced workers consuming a lot of memory, Is this normal?
Is there any incoming activity to improve worker performance for python
operators?
Is there any java/go operator available?
Best Regards,
Giorgio
Sure - anyone can join - just sign up in doodle with the available slots
and I will announce the time for the meeting time on Friday.
J.
On Tue, Feb 1, 2022 at 6:47 PM Giorgio Zoppi
wrote:
> Hello,
> can i join the meeting? I am reviewing airflow in depth. I am interested
> in helping.
> Best
Hello,
can i join the meeting? I am reviewing airflow in depth. I am interested
in helping.
Best Regards,
Giorgio.
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART;VALUE=DATE:20220202
DTEND;VALUE=DATE:20220205
DTSTAMP:20220201T174720Z
ORGANIZER;CN=alanx@gmail.com:mailto:alanx@gmail.com
Hello Everyone,
I think it's about the time for the next sig-multitenancy meeting :
I created a doodle poll for next week - please mark your availability till
Friday the 4th.
https://doodle.com/poll/axvu2gz7zhv8ieye?utm_source=poll_medium=link
I think what the rough agenda will be:
* AIP-43
Since we have AIP-43 already approved, I think I would love to have more
questions and discussions about AIP-44 - The "Airflow Internal API"
https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-44+Airflow+Internal+API
(as the new name is).
For those who would like to get more context -
Good point Bas.
While I am all for deprecation, I agree this one is very much "hard-wired"
into many users of Airflow, for many likely this is almost a muscle-memory
or copying from existing DAGs.
It's not enough to mandate it but we also should be empathetic and provide
a viable replacement.
Following the discussions from a week ago.
As of last Friday, we also have USD 10.000 worth credits from the AWS for
our CI.
Thanks John and AWS :)
J.
On Fri, Jan 21, 2022 at 7:24 PM Jarek Potiuk wrote:
> Just a small update. Let's hold-off with the sponsorship change. Who knows
> what will
Hello everyone,
Thanks for the questions, Niko! I will try to address them now...
1. The proposed solution is to have these provider-specific projects for
running DAGs being set up for system tests execution and use GitHub CI just
as a trigger for them. This way we will unload the
Regardless the behaviour of days_ago(), a lot of people use it so we’ll
definitely need to document it well with some good examples of alternatives.
That said, I think the usage of days_ago() is actually a side-effect of users
that don’t really need their DAGs to start at X days ago, but want
13 matches
Mail list logo
