Hi, devs
Today we had our first meeting for Flink 2.1 release cycle. I'd like to
share the info
synced in the meeting.
1. Feature freezing and release:
- Feature Freeze: June 21, 2025, 00:00 CEST(UTC+2)
- Release: End of July 2025
2. Update 2.1 Release page:
Flink 2.1 release has been ki
Jiaan Geng created FLINK-37716:
--
Summary: Simplify YarnClusterDescriptor by removing parameter
JobGraph
Key: FLINK-37716
URL: https://issues.apache.org/jira/browse/FLINK-37716
Project: Flink
Is
Simply setting config pipeline.object-reuse=true should work for that.
Best,
Zhanghao Chen
From: Winterchill <809025...@qq.com.INVALID>
Sent: Wednesday, April 23, 2025 20:12
To: dev
Subject: [DISCUSS] FlinkSQL support enableObjectReuse to optimize
CopyingChaining
Hi all,
I was reviewing and realised from pull request 26444 [1] which is to do with
removing data associated with eversion state for unit tests. I can look into
creating a migration tool and have copied in some of the people who have been
involved with this for feedback / thoughts on the appro
Hi Nicolas, thanks for the FLIP.
I am fully supportive of the motivation and we should be supporting this
feature. Here are couple of comments from my side:
D1)
Since you shared the implementation details on the FLIP as well, I would
like to discuss whether using Java's WatchService is the best c
Nick M created FLINK-37715:
--
Summary: Flink try use winutils.exe even without hadoop
Key: FLINK-37715
URL: https://issues.apache.org/jira/browse/FLINK-37715
Project: Flink
Issue Type: Bug
Affect
Hi, Timo
I believe I may have misapplied the query hints and table hints. The
current proposal only applies to query hints. For table hints, I think we
would need to create a view, apply the table hints to the view, and use it
as the SEARCH_KEY function's input.
Best,
Shengkai
Shengkai Fang 于2
Hi Timo,
thanks for addressing my points. I'm not set on using STRUCT et al. but
wanted to point out the alternatives.
Regarding the attached class name, I have similar confusion to Hao. I
wonder if Structures types shouldn't be anonymous by default in the sense
that initially we don't attach a c
I think Arvid has a good point. Why not define Object type without class
and when you get it in table api, try to cast it to some class? I found
https://docs.oracle.com/javase/1.5.0/docs/guide/jdbc/getstart/mapping.html.
Under `JAVA_OBJECT` type section. They have:
```
ResultSet rs = stmt.execute
