From c6dd953f1d0a69891c2562ed722e8b24865252ed Mon Sep 17 00:00:00 2001 From: synack-ppetruneac <85931465+synack-ppetruneac@users.noreply.github.com> Date: Fri, 29 Nov 2024 11:14:38 +0200 Subject: [PATCH 1/3] docs: Update refreshable-materialized-view.md to cross reference DEPENDS ON --- docs/en/materialized-view/refreshable-materialized-view.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/materialized-view/refreshable-materialized-view.md b/docs/en/materialized-view/refreshable-materialized-view.md index 7826d2e59d5..f49dd6d3e3b 100644 --- a/docs/en/materialized-view/refreshable-materialized-view.md +++ b/docs/en/materialized-view/refreshable-materialized-view.md @@ -25,7 +25,7 @@ ClickHouse incremental materialized views are enormously powerful and typically However, there are use cases where this incremental process is not required or is not applicable. Some problems are either incompatible with an incremental approach or don't require real-time updates, with a periodic rebuild being more appropriate. For example, you may want to regularly perform a complete recomputation of a view over the full dataset because it uses a complex join, which is incompatible with an incremental approach. -> Refreshable materialized views can run batch processes performing tasks such as denormalization. Dependencies can be created between refreshable materialized views such that one view depends on the results of another and only executes once it is complete. This can replace scheduled workflows or simple DAGs such as a [dbt](https://www.getdbt.com/) job. +> Refreshable materialized views can run batch processes performing tasks such as denormalization. Dependencies can be created between refreshable materialized views such that one view depends on the results of another and only executes once it is complete. This can replace scheduled workflows or simple DAGs such as a [dbt](https://www.getdbt.com/) job. To find out more about how to set dependancies between refreshable materialized views go to [CREATE VIEW](https://clickhouse.com/docs/en/sql-reference/statements/create/view#refresh-dependencies), `Dependancies` section. ## How do you refresh a refreshable materialized view? From 6bf79a636ea46dfe20ef2fe0cbcaf6658fc5e552 Mon Sep 17 00:00:00 2001 From: Pablo Musa Date: Fri, 29 Nov 2024 10:21:45 +0100 Subject: [PATCH 2/3] Update docs/en/materialized-view/refreshable-materialized-view.md --- docs/en/materialized-view/refreshable-materialized-view.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/materialized-view/refreshable-materialized-view.md b/docs/en/materialized-view/refreshable-materialized-view.md index f49dd6d3e3b..11723288581 100644 --- a/docs/en/materialized-view/refreshable-materialized-view.md +++ b/docs/en/materialized-view/refreshable-materialized-view.md @@ -25,7 +25,7 @@ ClickHouse incremental materialized views are enormously powerful and typically However, there are use cases where this incremental process is not required or is not applicable. Some problems are either incompatible with an incremental approach or don't require real-time updates, with a periodic rebuild being more appropriate. For example, you may want to regularly perform a complete recomputation of a view over the full dataset because it uses a complex join, which is incompatible with an incremental approach. -> Refreshable materialized views can run batch processes performing tasks such as denormalization. Dependencies can be created between refreshable materialized views such that one view depends on the results of another and only executes once it is complete. This can replace scheduled workflows or simple DAGs such as a [dbt](https://www.getdbt.com/) job. To find out more about how to set dependancies between refreshable materialized views go to [CREATE VIEW](https://clickhouse.com/docs/en/sql-reference/statements/create/view#refresh-dependencies), `Dependancies` section. +> Refreshable materialized views can run batch processes performing tasks such as denormalization. Dependencies can be created between refreshable materialized views such that one view depends on the results of another and only executes once it is complete. This can replace scheduled workflows or simple DAGs such as a [dbt](https://www.getdbt.com/) job. To find out more about how to set dependencies between refreshable materialized views go to [CREATE VIEW](https://clickhouse.com/docs/en/sql-reference/statements/create/view#refresh-dependencies), `Dependencies` section. ## How do you refresh a refreshable materialized view? From b6a5adf5f57326ad89bac2977faa562e67ba9d69 Mon Sep 17 00:00:00 2001 From: Dale McDiarmid Date: Fri, 6 Dec 2024 12:06:38 +0000 Subject: [PATCH 3/3] Keep links relative --- docs/en/materialized-view/refreshable-materialized-view.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/materialized-view/refreshable-materialized-view.md b/docs/en/materialized-view/refreshable-materialized-view.md index 11723288581..bc8e4f920e4 100644 --- a/docs/en/materialized-view/refreshable-materialized-view.md +++ b/docs/en/materialized-view/refreshable-materialized-view.md @@ -25,7 +25,7 @@ ClickHouse incremental materialized views are enormously powerful and typically However, there are use cases where this incremental process is not required or is not applicable. Some problems are either incompatible with an incremental approach or don't require real-time updates, with a periodic rebuild being more appropriate. For example, you may want to regularly perform a complete recomputation of a view over the full dataset because it uses a complex join, which is incompatible with an incremental approach. -> Refreshable materialized views can run batch processes performing tasks such as denormalization. Dependencies can be created between refreshable materialized views such that one view depends on the results of another and only executes once it is complete. This can replace scheduled workflows or simple DAGs such as a [dbt](https://www.getdbt.com/) job. To find out more about how to set dependencies between refreshable materialized views go to [CREATE VIEW](https://clickhouse.com/docs/en/sql-reference/statements/create/view#refresh-dependencies), `Dependencies` section. +> Refreshable materialized views can run batch processes performing tasks such as denormalization. Dependencies can be created between refreshable materialized views such that one view depends on the results of another and only executes once it is complete. This can replace scheduled workflows or simple DAGs such as a [dbt](https://www.getdbt.com/) job. To find out more about how to set dependencies between refreshable materialized views go to [CREATE VIEW](/docs/en/sql-reference/statements/create/view#refresh-dependencies), `Dependencies` section. ## How do you refresh a refreshable materialized view?