Hi David,
Thanks for the feedback and the good questions about the evolution scenario.
To clarify the scope of this FLIP, it's focused on introducing the CREATE
OR ALTER syntax itself, and not on expanding Flink's underlying schema
evolution capabilities. Every (un)supported scenario described in
david radley created FLINK-38328:
Summary: Community review acting strangely messages in PRs should
adding and removing labels
Key: FLINK-38328
URL: https://issues.apache.org/jira/browse/FLINK-38328
Hi Ramin,
I like this proposal.
I wondered what you thought of supporting evolutions like :
1.
Changing a column or child object to be nullable?
2.
Allowing column type changes if they were castable? This could require a
rewriting of the column data - so may not be feasible.
3.
WDYT?
Hi,
We had a good meeting today. It looks like the new community labels are working
well. Around two thirds of the PRs are community-reviewed and there are 2 Lets
Go To Merge PRs for committed to merge:
https://github.com/apache/flink/pull/26957
https://github.com/apache/flink/pull/26196
Ful