Hey!
I think the main question here is whether Flink 2.0 is going to be state
backward compatible or not.
If not then we need to make the upgrade right now, freeze or not. We have
to decide this as a community.
If we need to preserve backward compatibility then we need to go with a
much more comp
Congratulations, Xuyang!
Best,
Yash Anand
On Sun, Feb 23, 2025 at 10:37 PM Weiqing Yang
wrote:
> Congratulations, Xuyang!
>
> Best,
> Weiqing
>
> On Thu, Feb 20, 2025 at 2:15 AM Feng Jin wrote:
>
> > Congratulations, Xuyang!
> >
> >
> > Best,
> > Feng Jin
> >
> > On Thu, Feb 20, 2025 at 5:44 P
Congratulations, Xuyang!
Best,
Weiqing
On Thu, Feb 20, 2025 at 2:15 AM Feng Jin wrote:
> Congratulations, Xuyang!
>
>
> Best,
> Feng Jin
>
> On Thu, Feb 20, 2025 at 5:44 PM gongzhongqiang
> wrote:
>
> > Congratulations, Xuyang!
> >
> >
> > Best,
> > Zhongqiang Gong
> >
> > Lincoln Lee 于2025年2
Thanks Gyula for driving this discussion!
+1 for upgrading kyro, I have a question about the timeline.
The flink 2.0.0 has been freezed, do we have enough time to
test if it's done in flink 2.0.0?
Best,
Rui
On Fri, Feb 21, 2025 at 9:55 PM Alexander Fedulov
wrote:
> Hi Gyula,
>
> Thanks for bri
Hi xiangyu,
Sorry for my late reply! I have some questions for the FLIP:
1st, for the sql example in the Motivation part, why is cast nulls included
in
the select clause after union all multiple inputs? Related to the
partial-insert
example later, should the cast nulls be in the select clause ins
+1 (non-binding)
Thanks for driving this. It's a nice useability improvement for performing
partial-updates on datalakes.
Best,
Zhanghao Chen
From: xiangyu feng
Sent: Sunday, February 23, 2025 10:44
To: dev@flink.apache.org
Subject: [VOTE] FLIP-506: Support Re
