Materialized views in Hive connector

I’m curious about how Starburst implements the materialized view function of Hive Connector,it looks different from the materialized view of Hive。

I know from the docs that a materialized view consists of a view definition and a storage table. How does Starburst determine if materialized views are out of date? with cron or refresh_interval properties ?

Starburst’s implementation of MVs is independent from the Hive engine’s own materialized views.
The MV’s are considered out of date if the automatic imports configured via cron or refresh_interval haven’t completed successfully in recent past. Depending on whether incremental_column MV property is specified, the refresh could be incremental or full.