From b274ce68e04123a7cccf0ec79590778458cb70dc Mon Sep 17 00:00:00 2001 From: Alexey Milovidov Date: Sat, 9 Nov 2024 19:08:44 +0100 Subject: [PATCH] Update refreshable-materialized-view.md --- .../materialized-view/refreshable-materialized-view.md | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/docs/en/materialized-view/refreshable-materialized-view.md b/docs/en/materialized-view/refreshable-materialized-view.md index 6bd63240ba1..0de41ebdb9c 100644 --- a/docs/en/materialized-view/refreshable-materialized-view.md +++ b/docs/en/materialized-view/refreshable-materialized-view.md @@ -1,14 +1,10 @@ --- slug: /en/materialized-view/refreshable-materialized-view -title: Refreshable Materialized View (experimental) +title: Refreshable Materialized View description: How to use materialized views to speed up queries keywords: [refreshable materialized view, refresh, materialized views, speed up queries, query optimization] --- -import ExperimentalBadge from '@theme/badges/ExperimentalBadge'; - - - Refreshable materialized views can be considered conceptually similar to materialized views in traditional OLTP databases, storing the result of a specified query for quick retrieval and reducing the need to repeatedly execute resource-intensive queries. Unlike ClickHouse’s [incremental materialized views](/en/materialized-view), this requires the periodic execution of the query over the full dataset - the results of which are stored in a target table for querying. This result set should in theory be smaller than the original dataset, allowing the subsequent query to execute faster.