Hi everyone,
Thanks to everyone who has participated in the discussion for FLIP-546. The
feedback has been very positive and has helped improve the proposal.
It seems we have reached a good consensus on the direction of the FLIP.
If there are no further objections or major concerns, I would like
Hi Ramin,
thanks for the FLIP. Given that both CREATE and ALTER functionality are
already present in the code base, providing CREATE OR ALTER for all our
DDL in the near future makes a lot of sense to improve the declarative
nature of Flink SQL.
+1 for starting with MATERIALIZED TABLE. And l
Sergei Morozov created FLINK-38334:
--
Summary: MySQL CDC source may get stuck in the INITIAL_ASSIGNING
state
Key: FLINK-38334
URL: https://issues.apache.org/jira/browse/FLINK-38334
Project: Flink
RocMarshal created FLINK-38333:
--
Summary: UMBRELLA: FLIP-495: Support AdaptiveScheduler record and
query the rescale history
Key: FLINK-38333
URL: https://issues.apache.org/jira/browse/FLINK-38333
Projec
Hi Ramin,
Thanks for the feedback - that makes sense,
Kind regards, David.
From: Ramin Gharib
Date: Tuesday, 9 September 2025 at 08:18
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] FLIP-546: Introduce CREATE OR ALTER for
Materialized Tables
Hi Ron,
Thanks again for your det
Hi Ron,
Thanks again for your detailed feedback and for raising the points about CREATE
OR REPLACE and the existing FLIP-492.
Based on your comments and our discussion, I've updated the FLIP document
to include a more detailed rationale in the "Rejected Alternatives"
section. This now covers the
