Hi, Ramin.
Thank you for your revisions and for your patient replies. +1 for it.
--
Best！
Xuyang
At 2026-03-18 20:15:20, "Ramin Gharib" <[email protected]> wrote:
>Hi everyone,
>
>Following up on my proposal to split the scope of this feature, I have gone
>ahead and updated the FLIP to reflect the changes.
>
>FLIP-557 is now strictly focused on the START_MODE clause. All references
>to STATE_RETENTION have been removed, and the title has been updated to
>match the new scope: FLIP-557: Granular Control over Data Reprocessing in
>Materialized Table Evolution [1].
>
>As discussed, state management and retention are highly complex and deserve
>their own dedicated conversation, which can be addressed in a separate,
>future FLIP. This allows us to focus our immediate efforts on getting the
>START_MODE functionality across the finish line.
>
>Please take a look at the revised FLIP. Since this is a strict reduction in
>scope, I believe there is no need to close the current vote [2] and start a
>new one. If there are no objections to this scoped-down version, I will go
>ahead and conclude this VOTE thread soon.
>
>[1]
>https://cwiki.apache.org/confluence/display/FLINK/FLIP-557%3A+Granular+Control+over+Data+Reprocessing+in+Materialized+Table+Evolution
>[2] https://lists.apache.org/thread/c0kqqn6pb60ow4l54sb9cx9z360p7dg5
>
>Thanks,
>
>Ramin
>
>On Mon, Dec 1, 2025 at 6:23 PM Ramin Gharib <[email protected]> wrote:
>
>> Hi everyone,
>>
>> I would like to start a discussion on FLIP-557: Granular Control over Data
>> Reprocessing and State Retention in Materialized Table Evolution [1].
>>
>> Currently, ALTER MATERIALIZED TABLE forces a full job restart and
>> discards state, which is inefficient for many evolution scenarios. FLIP-557
>> proposes decoupling data scope from state management by introducing two new
>> optional clauses:
>> 1. START_MODE*:* Controls the data processing window (e.g., FROM_BEGINNING,
>> RESUME_OR_...).
>>
>> 2. STATE_RETENTION*:* Controls how existing state is handled (e.g., NONE,
>> PTF_ONLY).
>>
>> This gives users explicit control over cost and correctness during table
>> evolution.
>>
>> For more details, please refer to the FLIP [1].
>>
>> Looking forward to your feedback and thoughts!
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-557%3A+Granular+Control+over+Data+Reprocessing+and+State+Retention+in+Materialized+Table+Evolution
>>
>> Best regards,
>>
>> Ramin Gharib
>>
