Hi Starrocks Team, Have a small question about the upcoming Incremental Materialized View and how that differs from the Materialized View behavior that Starrocks exhibits today. As I currently understand it, when underlying data in a table changes (inserts/updates) in a source table partition, the corresponding MV partition must be refreshed by reselecting all the data in the relevant source table partition, regardless of the size of the data change, as well as the materialized view type (sync/async) Is my understanding correct? Secondly, I'm led to believe that the upcoming roadmap's Incremental Materialized View behaves somewhat similarly to ClickHouse's Incremental Materialized View behavior, where new data is taken into consideration and only partially updates as opposed to an full refresh of the corresponding partition. Is that understanding correct as well?

<https://docs.starrocks.io/docs/using_starrocks/async_mv/use_cases/create_partitioned_materialized_view/#overview>

Yes and yes! When data changes in a source table partition, StarRocks currently refreshes the corresponding MV partition by recomputing all data in that partition, regardless of the change size. This applies to both sync and async materialized views - the refresh granularity is at the partition level, meaning the entire partition is reselected and rewritten. The incremental mode will only refresh the incremental changed rows since the last refresh, rather than recomputing the entire partition.