StarRocks, a Linux Foundation project, is a next-generation sub-second MPP OLAP database for full analytics scenarios, including multi-dimensional analytics, real-time analytics, and ad-hoc queries. StarRocks received InfoWorld’s 2023 BOSSIE Award for best open source software.

StarRocks

There seems to be a contradiction in the docs about refreshing materialized views built on top of catalogs

<https://docs.starrocks.io/docs/sql-reference/sql-statements/materialized_view/CREATE_MATERIALIZED_VIEW/|CREATE_MATERIALIZED_VIEW Docs>
&gt; Currently, StarRocks cannot perceive if the base table data in the external catalog has changed, so all partitions will be refreshed by default every time the base table is refreshed.
<https://docs.starrocks.io/docs/using_starrocks/async_mv/use_cases/data_lake_query_acceleration_with_materialized_views/|Data lake query acceleration with materialized views docs>
&gt; External table materialized views do not support automatic refresh *triggered by base table data changes*. They only support asynchronous *fixed-interval* refresh and manual refresh.
&gt; 
&gt; For Hive Catalog, Iceberg Catalog (starting from v3.1.4), JDBC catalog (starting from v3.1.4, only for MySQL range-partitioned tables), and Paimon Catalog (starting from v3.2.1), StarRocks supports detecting data changes at the partition level. As a result, StarRocks can:
&gt; • Refresh only the partitions with data changes to avoid full-size refresh, reducing resource consumption caused by refresh.
So how do refreshes work on external catalogs? Can it refresh only partitions where the data has changed or will it refresh everything by default?