yanghuai created FLINK-37827:
Summary: Failed to use `SHOW CREATE TABLE` for MATERIALIZED_TABLE
Key: FLINK-37827
URL: https://issues.apache.org/jira/browse/FLINK-37827
Project: Flink
Issue Type:
Zakelly Lan created FLINK-37826:
---
Summary: Some serde-related perfs regression since May 19th
Key: FLINK-37826
URL: https://issues.apache.org/jira/browse/FLINK-37826
Project: Flink
Issue Type:
Thanks everyone for the positive feedback.
As I said, this FLIP is intended for discussing high-level plans for the
new project. The project itself is still at an early stage, and some of the
technical designs and solutions are not completely ready yet. So atm I can
only share some personal though
Thanks Xintong, Sean, and Chris for initiating Flink Agents sub-project.
Big +1 for this proposal in the AI Agent era.
Best,
Ron
Dian Fu 于2025年5月22日周四 09:31写道：
> Thanks for the proposal. It's a promising direction to bring Flink's
> event driven processing capacity into AI agent. Looking forwa
Thanks for the proposal. It's a promising direction to bring Flink's
event driven processing capacity into AI agent. Looking forward!
Regards,
Dian
On Thu, May 22, 2025 at 3:26 AM Yash Anand wrote:
>
> Thank you for the proposal—this initiative will make it much easier to
> build event-driven AI
Thank you for the proposal—this initiative will make it much easier to
build event-driven AI agents seamlessly.
+1 for the proposed Flink Agents sub-project!
On Wed, May 21, 2025 at 9:43 AM Mayank Juneja
wrote:
> +1 on the FLIP. This is a solid step toward building an agentic offering
> that re
+1 on the FLIP. This is a solid step toward building an agentic offering
that really leans into Flink’s strengths, and builds on the momentum from
recent API improvements like FLIP-437 and the proposed FLIP-529.
Also wanted to echo the point around agent memory. More advanced agentic
systems reall
+1 for the proposed flink agents sub-project!
This aligns perfectly with flink's core strengths in real-time event
processing and stateful computations.
Thanks for driving this initiative and looking forward to the
detailed technical designs.
Best,
Lincoln Lee
Hao Li 于2025年5月21日周三 23:28写道：
Hi Xintong, Sean and Chris,
Thanks for driving the initiative. Very exciting to bring AI Agent to Flink
to empower the streaming use cases.
+1 to the FLIP.
Thanks,
Hao
On Wed, May 21, 2025 at 7:35 AM Nishita Pattanayak <
nishita.pattana...@gmail.com> wrote:
> Hi Sean, Chris and Xintong. This s
Hi Sean, Chris and Xintong. This seems to be a very exciting sub-project.
+1 for "flink-agents" sub-project.
I was going through the FLIP , and had some questions regarding the same:
1. How would the external model calls (e.g., OpenAI or internal LLMs)
integrated into Flink tasks without introduci
melin created FLINK-37825:
-
Summary: Standard YAML convert and dump failed
Key: FLINK-37825
URL: https://issues.apache.org/jira/browse/FLINK-37825
Project: Flink
Issue Type: Improvement
Com
+1 (binding)
Best,
Jark
On Wed, 21 May 2025 at 19:36, Gustavo de Morais
wrote:
> +1(non-binding).
>
> Thanks Xuyang,
> Gustavo
>
> On Tue 20. May 2025 at 09:44, Lincoln Lee wrote:
>
> > +1 (binding)
> >
> >
> > Best,
> > Lincoln Lee
> >
> >
> > 曹振 <15533273...@163.com> 于2025年5月20日周二 14:55写道：
>
Thanks to Xintong, Sean, and Chris for initiating this proposal.
I believe this is one of the most exciting FLIPs in the Flink community —
especially in the era of GenAI. It opens up great opportunities for Flink
to
evolve into a more intelligent and autonomous data processing system.
+1 for the
Great to see this discussion getting started — thanks Xintong, Sean, and
Chris!
+1 to initial Flink Agents sub project.
Best,
Guowei
On Wed, May 21, 2025 at 5:52 PM Jing Ge wrote:
> Thanks Xintong, Sean, and Chris for starting this discussion!
>
> +1 for the initiative!
>
> After reading the F
+1(non-binding).
Thanks Xuyang,
Gustavo
On Tue 20. May 2025 at 09:44, Lincoln Lee wrote:
> +1 (binding)
>
>
> Best,
> Lincoln Lee
>
>
> 曹振 <15533273...@163.com> 于2025年5月20日周二 14:55写道：
>
> > +1(non-binding)
> >
> >
> >
> >
> >
> >
> > Best,
> > CaoZhen
> > Replied Message
> > | From |
Hi Ryan,
Thanks for the feedback.
Just a quick clarification—DESCRIBE TABLE in Flink does *not* show table
properties; I believe you might be thinking of SHOW CREATE TABLE, which
does include properties as part of the DDL output. The goal of SHOW CREATE
TABLE is to provide a fully reproducible st
linqigeng created FLINK-37824:
-
Summary: Paimon connector lost column comment in CreateTableEvent
Key: FLINK-37824
URL: https://issues.apache.org/jira/browse/FLINK-37824
Project: Flink
Issue Type
Mika Naylor created FLINK-37823:
---
Summary: Add Python 3.12 support
Key: FLINK-37823
URL: https://issues.apache.org/jira/browse/FLINK-37823
Project: Flink
Issue Type: Improvement
Compo
Thanks Xintong, Sean, and Chris for starting this discussion!
+1 for the initiative!
After reading the FLIP, I have some questions and would love to understand
your thoughts, thanks!
1. Glad to see that Flink Agent will support MCP natively. In this case,
the Flink Agent should be acting as a MC
Thanks for the initiative. +1 and looking forward to its first release!
Thanks and Regards
Pradeepta
> On 21 May 2025, at 8:51 AM, Xintong Song wrote:
>
>
Hi,
+1 (non-binding).
Thanks,
Gustavo
On Wed, 21 May 2025 at 08:32, Kartikey Pant
wrote:
> Hi,
>
> +1 (non-binding)
>
> Thanks, Kartikey.
>
> On Wed, May 21, 2025 at 12:59 AM Roman Khachatryan
> wrote:
>
> > Hi everyone,
> >
> > I'd like to start a vote on FLIP-530: Dynamic job configuration
Hi,
+1 (non-binding)
Thanks, Kartikey.
On Wed, May 21, 2025 at 12:59 AM Roman Khachatryan wrote:
> Hi everyone,
>
> I'd like to start a vote on FLIP-530: Dynamic job configuration
> [1] which has been discussed in this thread [2].
>
> The vote will be open for at least 72 hours unless there is
22 matches
Mail list logo
