Merge pull request #4151 from Blargian/lightweight_slug_update

Update lightweight-update slug

Author: Blargian

.github/workflows/check-build.yml

@@ -27,7 +27,8 @@ jobs:
         if: matrix.check_type == 'kbcheck'
         run: |
           curl -Ls https://astral.sh/uv/install.sh | sh
-          uv python install 3.12
+          uv clean
+          uv python install 3.12 --verbose
       - name: Setup md-lint environment
         if: matrix.check_type == 'md-lint'
         uses: actions/setup-node@v3

docs/guides/developer/mutations.md

@@ -15,7 +15,7 @@ delete existing data. These operations are labeled "mutations" and are executed
 
 :::tip
 If you need to perform frequent updates, consider using [deduplication](../developer/deduplication.md) in ClickHouse, which allows you to update 
-and/or delete rows without generating a mutation event. Alternatively, use [lightweight updates](/guides/developer/lightweight-update)
+and/or delete rows without generating a mutation event. Alternatively, use [lightweight updates](/docs/sql-reference/statements/update)
 or [lightweight deletes](/guides/developer/lightweight-delete)
 :::
 

docs/guides/developer/lightweight-update.md renamed to docs/guides/developer/on-fly-mutations.md

@@ -1,12 +1,12 @@
 ---
-slug: /guides/developer/lightweight-update
+slug: /guides/developer/on-the-fly-mutations
 sidebar_label: 'On-the-fly mutation'
 title: 'On-the-fly Mutations'
 keywords: ['On-the-fly mutation']
 description: 'Provides a description of on-the-fly mutations'
 ---
 
-## On-the-fly mutations {#lightweight-update}
+## On-the-fly mutations {#on-the-fly-mutations}
 
 When on-the-fly mutations are enabled, updated rows are marked as updated immediately and subsequent `SELECT` queries will automatically return with the changed values. When on-the-fly mutations are not enabled, you may have to wait for your mutations to be applied via a background process to see the changed values.
 

docs/integrations/data-ingestion/etl-tools/dbt/index.md

@@ -815,7 +815,7 @@ In this run, only the new rows are added straight to `imdb_dbt.actor_summary` ta
 
 Historically ClickHouse has had only limited support for updates and deletes, in the form of asynchronous [Mutations](/sql-reference/statements/alter/index.md). These can be extremely IO-intensive and should generally be avoided.
 
-ClickHouse 22.8 introduced [lightweight deletes](/sql-reference/statements/delete.md) and ClickHouse 25.7 introduced [lightweight updates](/guides/developer/lightweight-update). With the introduction of these features, modifications from single update queries, even when being materialized asynchronously, will occur instantly from the user's perspective.
+ClickHouse 22.8 introduced [lightweight deletes](/sql-reference/statements/delete.md) and ClickHouse 25.7 introduced [lightweight updates](/sql-reference/statements/update). With the introduction of these features, modifications from single update queries, even when being materialized asynchronously, will occur instantly from the user's perspective.
 
 This mode can be configured for a model via the `incremental_strategy` parameter i.e.
 

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

@@ -11,5 +11,5 @@ In this section of the documentation, you will learn how you can update your dat
 |-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | [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. |
 | [Update mutations](/managing-data/update_mutations)         | Learn how to update using Update Mutations.                                                                                                                      |
-| [Lightweight updates](/guides/developer/lightweight-update) | Learn how to update using Lightweight Updates.                                                                                                                   |
+| [Lightweight updates](/docs/sql-reference/statements/update) | Learn how to update using Lightweight Updates.                                                                                                                   |
 | [ReplacingMergeTree](/guides/replacing-merge-tree)          | Learn how to update using the ReplacingMergeTree.                                                                                                                |

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

@@ -22,7 +22,7 @@ In summary, update operations should be issued carefully, and the mutations queu
 |---------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | [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.                                                                                                                        |
 | [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.      |
-| [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. |
+| [On-the-fly updates](/guides/developer/on-the-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. |
 | [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.                                                                                                                                |
 | [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.                                       |
 Here is a summary of the different ways to update data in ClickHouse:
@@ -84,9 +84,9 @@ WHERE Id = 404346
 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.)
 ```
 
-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)).
+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-the-fly-mutations#support-for-subqueries-and-non-deterministic-functions)).
 
-Read more about [on-the-fly updates](/guides/developer/lightweight-update).
+Read more about [on-the-fly updates](/guides/developer/on-the-fly-mutations).
 
 ## `CollapsingMergeTree` {#collapsing-merge-tree}
 

sidebars.js

@@ -1123,7 +1123,7 @@ const sidebars = {
         {
           type: "doc",
           label: "Lightweight Updates",
-          id: "guides/developer/lightweight-update"
+          id: "guides/developer/on-fly-mutations"
         },
         {
           type: "doc",

vercel.json

@@ -3365,6 +3365,11 @@
       "source": "/docs/integrations/migration/upload-a-csv-file",
       "destination": "/docs/cloud/migrate/upload-a-csv-file",
       "permanent": true
+    },
+    {
+      "source": "/guides/developer/lightweight-update",
+      "destination": "/guides/developer/on-the-fly-mutations",
+      "permanent": true
     }
   ]
 }