Hi Dev,
Thanks all for voting. I'm closing the vote and the result will be posted
in a separate email.
Thanks,
Hao
On Fri, May 9, 2025 at 12:43 AM Martijn Visser
wrote:
> +1 (binding)
>
> On Fri, May 9, 2025 at 9:27 AM Yunfeng Zhou
> wrote:
>
> > +1(non-binding)
> >
> > Best,
> > Yunfeng
> >
Hi Dev,
I'm happy to announce that FLIP-525: Model ML_PREDICT, ML_EVALUATE
Implementation Design [1] has been accepted with 6 approving votes (3
binding) [2]
Yash Anand (non-binding)
Mayank Juneja (non-binding)
Shengkai Fang (binding)
Ron Liu (binding)
Yunfeng Zhou (non-binding)
Martijn Visser (b
Hi, xuyang
Thanks for proposing this FLIP — it’s very helpful for scenarios involving
large states.
I have a few questions regarding the node whitelist section:
1. If the TableSource implements FilterPushdownSpec, take LEFT JOIN as an
example — when the right side supports filter pushdown, the s
+1(binding)
Best,
Ron
Lincoln Lee 于2025年5月12日周一 09:55写道：
> +1 (binding)
>
>
> Best,
> Lincoln Lee
>
>
> shuai xu 于2025年5月9日周五 17:46写道：
>
> > Hi devs,
> >
> > Thank you for providing feedback on FLIP-519: Introduce async lookup key
> > ordered mode[1].
> > I'd like to start a vote on this FLIP
+1 (binding)
Best,
Ron
Hao Li 于2025年5月10日周六 02:35写道：
> +1 (non-binding)
>
> Thanks,
> Hao
>
> On Fri, May 9, 2025 at 3:41 AM Arvid Heise wrote:
>
> > +1 (binding)
> >
> > Cheers
> >
> > On Wed, May 7, 2025 at 6:37 PM Gustavo de Morais >
> > wrote:
> >
> > > Hi everyone,
> > >
> > > I'd like t
+1 (binding)
Best,
Zakelly
On Mon, May 12, 2025 at 9:55 AM Lincoln Lee wrote:
> +1 (binding)
>
>
> Best,
> Lincoln Lee
>
>
> shuai xu 于2025年5月9日周五 17:46写道：
>
> > Hi devs,
> >
> > Thank you for providing feedback on FLIP-519: Introduce async lookup key
> > ordered mode[1].
> > I'd like to star
Hi Roman
Thanks for driving this feature. +1 for this proposal.
I also agree with the suggestion made by Feifan.
Currently, not all configuration items are job-level configurations [1].
Even for those that are, not all job-level config options can be updated at
runtime through the Adaptive Sched
Thanks Roman for driving this useful improvement, +1 for this proposal.
Also thanks discussion from Hangxiang and Rui Fan. Regarding question 1, I
have some ideas for discussion:
Based on the consideration of providing stable expectations for users, I
think we should perform configuration checks
Hi everyone,
Thanks all for voting. I'm closing the vote and the result will be posted
in a separate email.
Best,
Xuannan
> On May 8, 2025, at 13:57, Jingsong Li wrote:
>
> +1 binding
>
> On Thu, May 8, 2025 at 11:17 AM Leonard Xu wrote:
>>
>> +1(binding)
>>
>> Best,
>> Leonard
>>
>>> 20
+1 (binding)
Best,
Lincoln Lee
shuai xu 于2025年5月9日周五 17:46写道：
> Hi devs,
>
> Thank you for providing feedback on FLIP-519: Introduce async lookup key
> ordered mode[1].
> I'd like to start a vote on this FLIP. Here is the discussion thread[2].
>
>
> The vote will be open for at least 72 hour
Thanks Roman for driving this valuable proposal, it uses the Adaptive
Scheduler to greatly reduce the downtime of configuration updates,
so +1 for this proposal!
Overall LGTM, thanks to Hangxiang for the questions, and I have the
same questions with Hangxiang. I'd like to share my thoughts:
For
Hi all,
If there are no more discussions. I will start voting tomorrow.
Thanks,
Hao
On Thu, May 8, 2025 at 10:38 AM Hao Li wrote:
> Hi Ron,
>
> > whether the predict or evaluate introduced in this FLIP can be
> serialized to SQL?
>
> Yes. It can be serialized to SQL. We just need to provide se
Hi devs,
I'm happy to announce that FLIP-521: Integrating Variant Type into Flink:
Enabling Efficient Semi-Structured Data Processing[1] has been accepted
with 9 approving votes (8 binding) [2]
Timo Walther (binding)
Gyula Fóra (binding)
Lincoln Lee (binding)
Xintong Song (binding)
weijie guo (bi
13 matches
Mail list logo
