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
