Hi Ramin,

thanks for improving the usability of Materialized tables further.

I'm especially happy that start offset/timestamp are becoming a first class
citizen and users don't need to specify table hints anymore - imho a
construct that should be reserved for advanced users that want to change
the behavior of the optimizer. Hopefully, we can soon provide a sound and
holistic reprocessing story.

FLIP LGTM.

Best,

Arvid

On Tue, Jan 20, 2026 at 10:40 AM Ramin Gharib <[email protected]> wrote:

> Hi everyone,
>
> I would like to check if there are any further comments or feedback
> regarding FLIP-557 [1].
>
> If there are no further points to discuss, I plan to close the discussion
> and start the vote in the next few days.
>
>
> [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
>
> 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
> >
>

Reply via email to