Thanks for Jane and Sergey's proposal!
+1 to correct the Table API behavior.
I have one question: Is the influence only limited to the RowType? Does the
Map or Array type have the same problems?
Best,
Shengkai
[DISCUSS][FLINK-31830] Align the Nullability Handling of ROW between SQL
and TableA
J
Guojun Li created FLINK-33932:
-
Summary: Support retry mechanism for rocksdb uploader
Key: FLINK-33932
URL: https://issues.apache.org/jira/browse/FLINK-33932
Project: Flink
Issue Type: Improvemen
KarlManong created FLINK-33933:
--
Summary: SerializedThrowable will be java.lang.StackOverflowError
when AsyncLookupFunction throw an exception
Key: FLINK-33933
URL: https://issues.apache.org/jira/browse/FLINK-33933
Hi, Jane, thanks for driving this.
IMO, it is important to keep same consistent semantics between table api and
sql, not only for maintenance, but also for user experience. But for users, the
impact of this modification is a bit large. Is it possible to consider
introducing a deprecated optio
Cai Liuyang created FLINK-33934:
---
Summary: Flink SQL Source use raw format maybe lead to data lost
Key: FLINK-33934
URL: https://issues.apache.org/jira/browse/FLINK-33934
Project: Flink
Issue T
Rui Fan created FLINK-33935:
---
Summary: Improve the default value doc and logic for some state
backend and checkpoint related options
Key: FLINK-33935
URL: https://issues.apache.org/jira/browse/FLINK-33935
P
Hi devs,
Thanks for all the feedback. If there are no more comments, I would like to
start a vote for this FLIP, thanks again!
Best,
Fang Yong
On Wed, Dec 20, 2023 at 9:12 PM Yong Fang wrote:
> Hi Ken,
>
> Thanks for your feedback. The purpose of this FLIP is to improve the use
> of serializat
