@Rocky does version 4.1 support IMV over iceberg? If so then up to what Iceberg table version?

Yes, StarRocks version 4.1 supports Incremental Materialized Views (IMV) over Iceberg tables. This feature allows the materialized view to refresh only the data that has changed (at the record level) rather than recomputing entire partitions. Key Details for Version 4.1: * Support Status: Supported. Version 4.1 introduces the

refresh_mode

property, which can be set to

INCREMENTAL

during MV creation to enable this behavior. * Supported Iceberg Versions: Version 4.1 adds support for Iceberg V3, in addition to existing support for V1 and V2. * Operational Constraint: While it supports these versions, the Incremental refresh mode in v4.1 is currently limited to append-only tables. If the base Iceberg table undergoes

UPDATE

,

DELETE

(Position/Equality Deletes), or

OVERWRITE

operations, the incremental refresh may fail or be unsupported for those specific changes. Usage Example: To use this feature, you specify the

refresh_mode

in the properties:

sql
CREATE MATERIALIZED VIEW iceberg_mv
REFRESH ASYNC
PROPERTIES (
    "refresh_mode" = "INCREMENTAL"
)
AS 
SELECT col1, sum(col2) 
FROM iceberg_catalog.db.table
GROUP BY col1;

Note: If your Iceberg tables frequently use deletes or updates, StarRocks still supports partition-level incremental refresh (available since v3.1 for V1 tables and enhanced in subsequent versions), which refreshes only the modified partitions rather than the whole table. References • release_notes/release-3.3.md • sql-reference/sql-statements/materialized_view/CREATE_MATERIALIZED_VIEW.md • using_starrocks/async_mv/use_cases/data_lake_query_acceleration_with_materialized_views.md