I will certainly be there :).
I give 3 talks and co-lead the data engineering track with Ismael :)
On Thu, Jul 14, 2022 at 2:45 AM Aizhamal Nurmamat kyzy
wrote:
>
> Anyone planning to come to ApacheCon? I will be there, and would love to see
> you all in person :)
>
> On Sat, Jul 2, 2022 at 3:3
Anyone planning to come to ApacheCon? I will be there, and would love to
see you all in person :)
On Sat, Jul 2, 2022 at 3:33 AM Jarek Potiuk wrote:
> Hey Everyone,
>
> The registration for ONSITE ApacheCon in New Orleans, Louisiana,
> October 3-6, is now open.
>
> This is the first time we have
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
Saturday 16th of July 2022, 23:45 CEST.
Consider this my (binding) +1.
This is a bit more than regular release of provider
Thank you all for your responses.
Dennis, With respect to your concern on the "hard data - numbers" to
support the assertion of the audience. I agree that we don't have the hard
numbers at this time to support this assertion and I also understand your
concern that there is additional burden to an
I don't think it makes sense to deprecate it at this time just to re-add
it. It's not necessarily backward incompatibility if you are fixing
something that is not functioning as intended / desired. And I'm not sure
that we'll really have to break backcompat even if you don't want to
interpret it
Hi Vikram,
Great thoughts on this.
I agree with this:
> I am concerned that we are overwhelming our audience segment (1) with the
> work and configurations around running Airflow at scale.
I would like to see a better separation on 1) how to set up an airflow
cluster in production, how to moni
You are absolutely right that it will be very hard to "fix" the SLA as it
stands while keeping backwards compatibility.
My thoughts on the new / updated SLA mechanism will NOT be compatible, but
will address the core need for data timeliness.
Hmm, that's an interesting thought on "marking it as de
Cool to see that people still need SLA in Airflow. I see the points
why and they make perfect sense. Glad we discussed it :)
Still - WDYT do we want to signal current SLA as "deprecated" now
(even if we do not know what will replace it?) - at least as a signal
to stay away from it.
Or do we want t
- resending below to keep the same thread as Ping's response. My
prior response and Ping's were sent at the same time, but I did not two two
email threads --
I understand the frustration with the SLA feature as it stands.
I struggled with trying to understand this early on and finally understood
Hi Jarek,
Yep, it is more useful in the stress test stage before releasing a new
version with some extra set up to ensure no scheduler performance
degradation due to a release. This can also help to find the scaling limit
of the scheduler with a certain SLA, like upper limit of the number of
tasks
I understand the frustration with the SLA feature as it stands.
I struggled with trying to understand this early on and finally understood
how they were broken.
Having said that, I believe that Airflow users strongly care about the
timeliness and consequently SLAs of their data. I also believe tha
Hi Jarek,
Thanks for bringing this up.
I agree the SLA feature needs some work. However, I think we want an
equivalent SLA feature as it is still very useful.
Thanks,
Ping
On Tue, Jul 12, 2022 at 12:42 AM Jarek Potiuk wrote:
> Hey everyone,
>
> I keep on being involved in discussions where
12 matches
Mail list logo
