Skip to content

Commit b074723

Browse files
committed
fix broken links
1 parent c531c62 commit b074723

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

docs/guides/developer/mutations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ delete existing data. These operations are labeled "mutations" and are executed
1515

1616
:::tip
1717
If you need to perform frequent updates, consider using [deduplication](../developer/deduplication.md) in ClickHouse, which allows you to update
18-
and/or delete rows without generating a mutation event. Alternatively, use [lightweight updates](/guides/developer/lightweight-update)
18+
and/or delete rows without generating a mutation event. Alternatively, use [lightweight updates](/docs/sql-reference/statements/update)
1919
or [lightweight deletes](/guides/developer/lightweight-delete)
2020
:::
2121

docs/managing-data/updating-data/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,5 +11,5 @@ In this section of the documentation, you will learn how you can update your dat
1111
|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
1212
| [Overview](/updating-data/overview) | Provides an overview of the differences in updating data between ClickHouse and OLTP databases, as well as the various methods available to do so in ClickHouse. |
1313
| [Update mutations](/managing-data/update_mutations) | Learn how to update using Update Mutations. |
14-
| [Lightweight updates](/guides/developer/lightweight-update) | Learn how to update using Lightweight Updates. |
14+
| [Lightweight updates](/docs/sql-reference/statements/update) | Learn how to update using Lightweight Updates. |
1515
| [ReplacingMergeTree](/guides/replacing-merge-tree) | Learn how to update using the ReplacingMergeTree. |

docs/managing-data/updating-data/overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In summary, update operations should be issued carefully, and the mutations queu
2222
|---------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
2323
| [Update mutation](/sql-reference/statements/alter/update) | `ALTER TABLE [table] UPDATE` | Use when data must be updated to disk immediately (e.g. for compliance). Negatively affects `SELECT` performance. |
2424
| [Lightweight updates](/sql-reference/statements/update) | `UPDATE [table] SET ... WHERE` | Use for updating small amounts of data (up to ~10% of table). Creates patch parts for immediate visibility without rewriting entire columns. Adds overhead to `SELECT` queries but has predictable latency. Currently experimental. |
25-
| [On-the-fly updates](/guides/developer/lightweight-update) | `ALTER TABLE [table] UPDATE` | Enable using `SET apply_mutations_on_fly = 1;`. Use when updating small amounts of data. Rows are immediately returned with updated data in all subsequent `SELECT` queries but are initially only internally marked as updated on disk. |
25+
| [On-the-fly updates](/guides/developer/on-fly-mutations) | `ALTER TABLE [table] UPDATE` | Enable using `SET apply_mutations_on_fly = 1;`. Use when updating small amounts of data. Rows are immediately returned with updated data in all subsequent `SELECT` queries but are initially only internally marked as updated on disk. |
2626
| [ReplacingMergeTree](/engines/table-engines/mergetree-family/replacingmergetree) | `ENGINE = ReplacingMergeTree` | Use when updating large amounts of data. This table engine is optimized for data deduplication on merges. |
2727
| [CollapsingMergeTree](/engines/table-engines/mergetree-family/collapsingmergetree) | `ENGINE = CollapsingMergeTree(Sign)` | Use when updating individual rows frequently, or for scenarios where you need to maintain the latest state of objects that change over time. For example, tracking user activity or article stats. |
2828
Here is a summary of the different ways to update data in ClickHouse:
@@ -84,9 +84,9 @@ WHERE Id = 404346
8484
1 row in set. Elapsed: 0.149 sec. Processed 59.55 million rows, 259.91 MB (399.99 million rows/s., 1.75 GB/s.)
8585
```
8686

87-
Note that for on-the-fly updates, a mutation is still used to update the data; it is just not materialized immediately and applied during `SELECT` queries. It will still be applied in the background as an asynchronous process and incurs the same heavy overhead as a mutation and thus is an I/O intense operation that should be used sparingly. The expressions that can be used with this operation are also limited (see here for [details](/guides/developer/lightweight-update#support-for-subqueries-and-non-deterministic-functions)).
87+
Note that for on-the-fly updates, a mutation is still used to update the data; it is just not materialized immediately and applied during `SELECT` queries. It will still be applied in the background as an asynchronous process and incurs the same heavy overhead as a mutation and thus is an I/O intense operation that should be used sparingly. The expressions that can be used with this operation are also limited (see here for [details](/guides/developer/on-fly-mutations#support-for-subqueries-and-non-deterministic-functions)).
8888

89-
Read more about [on-the-fly updates](/guides/developer/lightweight-update).
89+
Read more about [on-the-fly updates](/guides/developer/on-fly-mutations).
9090

9191
## `CollapsingMergeTree` {#collapsing-merge-tree}
9292

0 commit comments

Comments
 (0)