Hi everyone, Thank you to everyone who has participated in the discussion for FLIP-551 and provided valuable feedback. The proposal has been significantly improved as a result, and it seems we have reached a strong consensus.
If there are no further major objections or concerns, I would like to start the formal *[VOTE]* thread for this proposal today. Please voice any final thoughts before then. Best regards, Ramin On Mon, Oct 6, 2025 at 2:18 PM Ramin Gharib <ramingha...@gmail.com> wrote: > Hi everyone, > > I would like to start a discussion on FLIP-551 [1], which proposes making > the FRESHNESS clause optional for Materialized Tables. > > The goal is to simplify the user experience for common streaming cases and > to enable more powerful, platform-level default logic. > > The proposal achieves this by: > > 1. > > Making the FRESHNESS DDL clause optional, falling back to a sensible > default of 1 minute. > 2. > > Introducing a new, MaterializedTableEnricher interface for custom > logic to resolve the final Freshness and RefreshMode into the > ResolvedCatalogMaterializedTable when they are omitted. > > This change reduces boilerplate for users while providing a clean > extension point for advanced use cases. The complete architectural details > and API are in the FLIP. > > I'm looking forward to hearing your feedback. > > [1] > https://cwiki.apache.org/confluence/display/FLINK/FLIP-551%3A+Make+FRESHNESS+Optional+for+Materialized+Tables > > Thanks, > > Ramin >
