This is an automated email from the ASF dual-hosted git repository.

csun5285 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 7f9d954e520 [fix](docs) Remove sequence_mapping documentation from 4.x 
and 4.1.0 release notes (#4678)
7f9d954e520 is described below

commit 7f9d954e520d723ce9dcb6095d7b09ae02890d79
Author: Chenyang Sun <[email protected]>
AuthorDate: Fri Nov 20 17:35:34 2026 +0800

    [fix](docs) Remove sequence_mapping documentation from 4.x and 4.1.0 
release notes (#4678)
    
    `sequence_mapping` (apache/doris#54936) was merged only into `master`
    and is not included in `branch-4.1` or `branch-4.2`. Remove the `4.x`
    `multi-stream-update-for-unique-model` pages, sidebar entry, inbound
    links in `update-overview`, and the `4.1.0` release note entry across
    locales while keeping the `dev` documentation intact.
    
    ## Versions
    
    - [ ] dev
    - [x] 4.x
    - [ ] 3.x
    - [ ] 2.1 or older (not covered by version/language sync gate)
    
    ## Languages
    
    - [x] Chinese
    - [x] English
    
    ## Docs Checklist
    
    - [x] Checked by AI
    - [ ] Test Cases Built (documentation removal; no new SQL examples)
    - [x] Updated required version and language counterparts, or explained
    why not
    - [x] If only one language changed, confirmed whether source/translation
    counterparts need sync
    
    ## Versions
    
    - [ ] dev
    - [ ] 4.x
    - [ ] 3.x
    - [ ] 2.1 or older (not covered by version/language sync gate)
    
    ## Languages
    
    - [ ] Chinese
    - [ ] English
    
    ## Docs Checklist
    
    - [ ] Checked by AI
    - [ ] Test Cases Built
    - [ ] Updated required version and language counterparts, or explained
    why not
    - [ ] If only one language changed, confirmed whether source/translation
    counterparts need sync
---
 .../update/multi-stream-update-for-unique-model.md | 312 ---------------------
 .../data-operate/update/update-overview.md         |   3 +-
 .../update/multi-stream-update-for-unique-model.md | 312 ---------------------
 .../data-operate/update/update-overview.md         |   3 +-
 .../update/multi-stream-update-for-unique-model.md | 312 ---------------------
 .../data-operate/update/update-overview.md         |   3 +-
 .../current/v4.1/release-4.1.0.md                  |   4 -
 .../update/multi-stream-update-for-unique-model.md | 312 ---------------------
 .../data-operate/update/update-overview.md         |   3 +-
 releasenotes/v4.1/release-4.1.0.md                 |   2 -
 scripts/last-update/data.json                      |   2 -
 scripts/migrate-4.x/new-slugs-en.txt               |   1 -
 scripts/migrate-4.x/new-slugs-zh.txt               |   1 -
 .../multi-stream-update-for-unique-model.json      |  20 --
 .../multi-stream-update-for-unique-model.json      |  37 ---
 .../multi-stream-update-for-unique-model.json      |  37 ---
 .../update/multi-stream-update-for-unique-model.md | 312 ---------------------
 .../data-operate/update/update-overview.md         |   3 +-
 versioned_sidebars/version-4.x-sidebars.json       |   3 +-
 19 files changed, 6 insertions(+), 1676 deletions(-)

diff --git 
a/i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
 
b/i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
deleted file mode 100644
index 6bfd638aeb3..00000000000
--- 
a/i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
+++ /dev/null
@@ -1,312 +0,0 @@
----
-{
-    "title": "Unique モデルにおける複数ストリームからの更新",
-    "language": "ja",
-    "description": "Doris の Unique モデルの Sequence Mapping 
機能を使用し、複数のデータストリームが同じワイドテーブルの異なる列を同時に更新する際のバージョン管理の問題を解決します。"
-}
----
-
-<!-- Knowledge type: Feature + Procedure -->
-<!-- Applicable scenarios: Concurrent writes from multiple data streams to a 
wide table / Real-time updates for some columns combined with on-demand updates 
for others -->
-
-## ビジネスシナリオと課題
-
-データウェアハウスのワイドテーブルでは、同じテーブルの列でも**異なるデータソース**や**異なる処理パイプライン**に由来することがよくあります。一般的な例は次のとおりです。
-
-- **リアルタイムストリーム**: テーブルの一部のフィールド(ユーザーの行動に関する列など)を継続的に更新します。
-- **オフラインストリーム(またはオンデマンドストリーム)**: 
テーブルの他のフィールド(ユーザープロファイルやタグに関する列など)を特定のタイミングで更新します。
-
-このシナリオでは、複数のデータストリームが同じ主キーテーブルに同時に書き込むため、主に次の二つの問題が生じます。
-
-| 課題 | 説明 |
-| --- | --- |
-| **同時書き込みによる上書き** | データストリームごとに到着時刻が異なります。単純な REPLACE 
集約では、各ストリームのデータがバージョン順に更新されることを保証できません。 |
-| **データ結合のコストが高い** | 
すべての列のデータがそろうまで書き込みを待つことは、ほぼ不可能です。待ち時間が非常に長くなる可能性があり、業務上許容できません。 |
-
-Doris の Unique モデルは Sequence 列に基づくバージョン管理を標準でサポートしていますが、**グローバル Sequence 
列は一つだけしか定義できません**。そのため、異なるデータストリームが更新する列ごとにバージョンを独立して管理することはできません。この問題に対応するため、Doris
 は **Sequence Mapping** 機能を提供しています。
-
-## 解決方法: Sequence Mapping
-
-<!-- Knowledge type: One-line definition -->
-
-**Sequence Mapping** は、Doris の Unique 
モデルがサポートする、複数ストリームからの同時更新の仕組みです。データ列ごとに異なる Sequence 
列を指定することで、各データストリームのバージョンを互いに干渉せずに管理できます。
-
-### 動作の仕組み
-
-Unique テーブルに次の列があるとします。
-
-| 列 | A | B | C | D | E | s1 | s2 |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| 役割 | キー | キー | 値 | 値 | 値 | Sequence | Sequence |
-
-- データストリーム 1 は列 `A, B, C, D` に書き込み、`s1` をバージョン管理列として使用します。
-- データストリーム 2 は列 `A, B, E` に書き込み、`s2` をバージョン管理列として使用します。
-
-このマッピングでは、次のように動作します。
-
-- `s1` は列 `C, D` のバージョンを管理します。新しいデータの `s1` が既存データの `s1` より大きい場合にのみ、`C, D, s1` 
が更新されます。
-- `s2` は列 `E` のバージョンを管理します。新しいデータの `s2` が既存データの `s2` より大きい場合にのみ、`E, s2` 
が更新されます。
-- 二つのストリームは**互いに干渉せず**、クエリではすべての列の最新データを読み取れます。
-
-## 使用例
-
-### 1. Sequence Mapping に対応するテーブルを作成する
-
-`sequence_mapping.<sequence_col>` プロパティを `PROPERTIES` で使用して、Sequence 
列と、その列が管理する Value 列のマッピングを宣言します。
-
-次の例では、列 `c, d` のバージョンを `s1` で管理し、列 `e` のバージョンを `s2` で管理する Unique テーブルを作成します。
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `e`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT "",
-    `s2` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d",
-    "sequence_mapping.s2" = "e"
-);
-```
-
-> Sequence 列でサポートされる型は整数型、`DATE`、`DATETIME` です。**列を作成した後に型を変更することはできません。**
-
-作成後のテーブルスキーマは次のとおりです。
-
-```sql
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| s2    | int    | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-```
-
-### 2. データを書き込んでクエリする
-
-次の五つの INSERT 操作は、Sequence 値の違いが各列の更新にどう影響するかを示しています。
-
-**INSERT 1**: `c, d, s1` のみに書き込み、`e, s2` には書き込みません。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,2,2,2);
-Query OK, 1 row affected (0.080 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**INSERT 2**: `s1=1` は既存の `s1=2` より小さいため、`c, d, s1` は更新されません。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,1,1,1);
-Query OK, 1 row affected (0.048 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**INSERT 3**: `e, s2` に書き込みます。更新前の `s2` は `NULL`(最小値として扱われます)だったため、`e, s2` 
が更新されます。
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.043 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 |    2 |    2 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**INSERT 4**: `s1=3` は既存の `s1=2` より大きいため、`c, d, s1` が更新されます。`e, s2` には影響しません。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,3,3,3);
-Query OK, 1 row affected (0.049 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    2 |    3 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**INSERT 5**: 両方の列グループに書き込みます。`s1=4` と `s2=4` はどちらも既存の値より大きいため、すべての列が更新されます。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-更新結果のまとめは次のとおりです。
-
-| 操作 | 更新条件 | 更新された列 |
-| --- | --- | --- |
-| INSERT 1 | `c, d, s1` への最初の書き込み | `c, d, s1` |
-| INSERT 2 | 新しい `s1` < 既存の `s1` | なし |
-| INSERT 3 | `e, s2` への最初の書き込み | `e, s2` |
-| INSERT 4 | 新しい `s1` > 既存の `s1` | `c, d, s1` |
-| INSERT 5 | 新しい `s1` と `s2` がどちらも既存の値より大きい | `c, d, s1, e, s2` |
-
-### 3. 列を追加または削除する
-
-Sequence Mapping テーブルでは、`ALTER TABLE` を使用して列やマッピングを動的に追加または削除できます。
-
-**初期テーブルの作成**: `s1 -> c,d` のマッピングのみを設定します。
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d"
-);
-```
-
-**初期データの書き込み**:
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values 
(1,1,1,1,1),(1,1,3,3,3),(1,1,2,2,2);
-Query OK, 3 rows affected (0.101 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |
-+------+------+------+------+------+
-```
-
-**列とマッピングの追加**: `ALTER TABLE` を使用して列 `e, s2` を追加すると同時に、`s2 -> e` のマッピングを宣言します。
-
-```sql
-MySQL > alter table upsert_test add column (e int(11) NULL, s2 bigint) 
PROPERTIES('sequence_mapping.s2' = 'e');
-Query OK, 0 rows affected (0.011 sec)
-
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s2    | bigint | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 | NULL | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**新しいマッピングが有効になった後の書き込み**:
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.052 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |    2 |    2 |
-+------+------+------+------+------+------+------+
-
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    5 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-**列の削除**: Value 列 `e` を削除すると、対応するマッピングが無効になります。その後、Sequence 列 `s2` を削除します。
-
-```sql
-MySQL > alter table upsert_test drop column e;
-Query OK, 0 rows affected (0.006 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | s2   |
-+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+
-
-MySQL > alter table upsert_test drop column s2;
-Query OK, 0 rows affected (0.005 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |
-+------+------+------+------+------+
-```
-
-## 使用上の制約
-
-<!-- Knowledge type: Configuration parameters / Usage limitations -->
-
-Sequence Mapping を使用する際は、次の制約に注意してください。
-
-| 分類 | 制約 |
-| --- | --- |
-| **テーブル作成時の設定** | `light_schema_change` を有効にする必要があります。テーブル作成時に 
`sequence_mapping` プロパティを宣言しなかった場合、後から有効にすることはできません。 |
-| **列の型** | Sequence 
列でサポートされるのは整数型と時間型(`DATE`、`DATETIME`)のみで、作成後に型を変更することはできません。 |
-| **列の役割** | Sequence 列もマッピング対象の列も Key 列にはできません。Key 以外のすべての列を Sequence 
列にマッピングする必要があります。 |
-| **マッピング関係** | 異なる Sequence 列にマッピングする列は**重複できません**(例えば、`d` を `s1` と `s2` 
の両方にマッピングすることはできません)。マッピングを設定した後は**変更できません**(例えば、すでに `s1` にマッピングした列を `s2` 
に再マッピングすることはできません)。 |
-| **DDL の制限** | 列名の変更と Rollup の作成はサポートされません。 |
-| **ストレージモード** | 現在サポートされるのは MOR(Merge-on-Read)テーブルのみです。グローバル Sequence 
列との併用はサポートされません。バッチ削除操作もサポートされません。 |
-| **ロード時の動作** | ロード時に含まれないフィールドには、デフォルト値または `NULL` が自動的に設定されます。Sequence 
列の比較では、`NULL` は**最小値**として扱われます。 |
diff --git 
a/i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
 
b/i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
index 273d3f6272b..eaedfcc2158 100644
--- 
a/i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
+++ 
b/i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
@@ -145,7 +145,6 @@ PROPERTIES (
 詳細は次を参照してください。
 
 - Sequence 列、MVCC によるバージョン管理、`UPDATE` の並行実行パラメータなどについては、[Unique Key 
モデルにおける更新の並行制御](./unique-update-concurrent-control.md)を参照してください。
-- 複数のデータストリームが同じワイドテーブルの異なる列を同時に更新する場合は、Sequence Mapping 
を使用して列ごとのバージョン順序を個別に制御できます。詳細は[Unique Key 
モデルにおける複数ストリームからの更新](./multi-stream-update-for-unique-model.md)を参照してください。
 
 ### 2.3 削除マーカーの処理の流れ
 
@@ -230,7 +229,7 @@ Flink CDC などのツールは、上流データベース(MySQL、PostgreSQL
     - ユーザー行動ストリームは `page_view_count` と `last_login_time` を更新します。
     - 取引ストリームは `total_orders` と `total_amount` を更新します。
 
-各ストリームが変更された列だけを書き込むことで、IO の負荷を軽減し、リアルタイム JOIN 
のリソース消費を避けられます。複数ストリームの並行実行時のバージョン管理については、[Unique Key 
モデルにおける複数ストリームからの更新](./multi-stream-update-for-unique-model.md)を参照してください。
+各ストリームが変更された列だけを書き込むことで、IO の負荷を軽減し、リアルタイム JOIN のリソース消費を避けられます。
 
 ## 4. 利用上の推奨事項 {#4-usage-recommendations}
 
diff --git 
a/i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
 
b/i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
deleted file mode 100644
index 934575e6585..00000000000
--- 
a/i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
+++ /dev/null
@@ -1,312 +0,0 @@
----
-{
-    "title": "Unique 모델의 다중 스트림 업데이트",
-    "language": "ko",
-    "description": "Doris Unique 모델의 Sequence Mapping 기능을 사용하여 여러 데이터 스트림이 동일한 
와이드 테이블의 서로 다른 열을 동시에 업데이트할 때 발생하는 버전 제어 문제를 해결합니다."
-}
----
-
-<!-- Knowledge type: Feature + Procedure -->
-<!-- Applicable scenarios: Concurrent writes from multiple data streams to a 
wide table / Real-time updates for some columns combined with on-demand updates 
for others -->
-
-## 활용 시나리오와 문제점 {#business-scenarios-and-pain-points}
-
-데이터 웨어하우스의 와이드 테이블에서는 동일한 테이블의 서로 다른 열이 **서로 다른 데이터 소스**나 **서로 다른 처리 파이프라인**에서 
오는 경우가 많습니다. 대표적인 사례는 다음과 같습니다.
-
-- **실시간 스트림**: 테이블의 일부 필드(예: 사용자 행동 관련 열)를 지속적으로 업데이트합니다.
-- **오프라인 스트림(또는 온디맨드 스트림)**: 특정 시점에 테이블의 다른 필드(예: 사용자 프로필이나 태그 관련 열)를 업데이트합니다.
-
-이러한 시나리오에서는 여러 데이터 스트림이 동일한 기본 키 테이블에 동시에 데이터를 쓰면서 두 가지 핵심 문제에 직면합니다.
-
-| 문제점 | 설명 |
-| --- | --- |
-| **동시 쓰기에 따른 덮어쓰기 문제** | 데이터 스트림마다 도착 시점이 다릅니다. 단순한 REPLACE 집계만으로는 각 스트림의 
데이터가 버전 순서대로 업데이트된다고 보장할 수 없습니다. |
-| **높은 데이터 결합 비용** | 모든 열의 데이터가 모일 때까지 기다렸다가 쓰는 것은 사실상 불가능합니다. 대기 시간이 매우 길어질 수 
있으며, 업무에서 이를 감당하기 어렵습니다. |
-
-Doris Unique 모델은 Sequence 열을 기반으로 하는 버전 제어를 기본적으로 지원하지만, **전역 Sequence 열 하나만 
정의할 수 있으므로** 서로 다른 데이터 스트림에서 오는 각 열의 업데이트 버전을 독립적으로 제어할 수 없습니다. 이를 해결하기 위해 
Doris는 **Sequence Mapping** 기능을 제공합니다.
-
-## 해결 방법: Sequence Mapping {#solution-sequence-mapping}
-
-<!-- Knowledge type: One-line definition -->
-
-**Sequence Mapping**은 Doris Unique 모델이 지원하는 다중 스트림 동시 업데이트 메커니즘입니다. 데이터 열마다 서로 
다른 Sequence 열을 지정하여 각 데이터 스트림의 버전을 상호 간섭 없이 독립적으로 제어할 수 있습니다.
-
-### 동작 원리 {#how-it-works}
-
-Unique 테이블에 다음과 같은 열이 있다고 가정합니다.
-
-| 열 | A | B | C | D | E | s1 | s2 |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| 역할 | Key | Key | Value | Value | Value | Sequence | Sequence |
-
-- 데이터 스트림 1은 `A, B, C, D` 열에 데이터를 쓰고, `s1`을 버전 제어 열로 사용합니다.
-- 데이터 스트림 2는 `A, B, E` 열에 데이터를 쓰고, `s2`를 버전 제어 열로 사용합니다.
-
-이 매핑을 사용하면 다음과 같이 동작합니다.
-
-- `s1`은 `C, D` 열의 버전을 제어합니다. 새 데이터의 `s1`이 기존 데이터의 `s1`보다 클 때만 `C, D, s1`이 
업데이트됩니다.
-- `s2`는 `E` 열의 버전을 제어합니다. 새 데이터의 `s2`가 기존 데이터의 `s2`보다 클 때만 `E, s2`가 업데이트됩니다.
-- 두 스트림은 **서로 간섭하지 않으며**, 쿼리에서 모든 열의 최신 데이터를 읽을 수 있습니다.
-
-## 사용 예제 {#usage-example}
-
-### 1. Sequence Mapping을 지원하는 테이블 생성 
{#1-create-a-table-that-supports-sequence-mapping}
-
-`sequence_mapping.<sequence_col>` 속성을 `PROPERTIES`에 지정하여 Sequence 열과 해당 열이 
제어하는 Value 열 사이의 매핑을 선언합니다.
-
-다음 예제에서는 `c, d` 열의 버전을 `s1`으로 제어하고, `e` 열의 버전을 `s2`로 제어하는 Unique 테이블을 생성합니다.
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `e`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT "",
-    `s2` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d",
-    "sequence_mapping.s2" = "e"
-);
-```
-
-> Sequence 열에서 지원하는 타입은 정수 타입, `DATE`, `DATETIME`입니다. **열을 생성한 후에는 타입을 변경할 수 
없습니다.**
-
-생성 후 테이블 스키마는 다음과 같습니다.
-
-```sql
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| s2    | int    | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-```
-
-### 2. 데이터 쓰기 및 쿼리 {#2-write-and-query-data}
-
-다음 다섯 번의 삽입 작업은 서로 다른 Sequence 값이 각 열의 업데이트에 어떤 영향을 미치는지 보여 줍니다.
-
-**삽입 1**: `c, d, s1`에만 데이터를 쓰고, `e, s2`에는 쓰지 않습니다.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,2,2,2);
-Query OK, 1 row affected (0.080 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**삽입 2**: `s1=1`이 기존 값인 `s1=2`보다 작으므로 `c, d, s1`은 업데이트되지 않습니다.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,1,1,1);
-Query OK, 1 row affected (0.048 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**삽입 3**: `e, s2`에 데이터를 씁니다. 기존 `s2`가 `NULL`(가장 작은 값으로 처리됨)이었으므로 `e, s2`가 
업데이트됩니다.
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.043 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 |    2 |    2 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**삽입 4**: `s1=3`이 기존 값인 `s1=2`보다 크므로 `c, d, s1`이 업데이트되며, `e, s2`는 영향을 받지 않습니다.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,3,3,3);
-Query OK, 1 row affected (0.049 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    2 |    3 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**삽입 5**: 두 열 그룹 모두에 데이터를 씁니다. `s1=4`와 `s2=4`가 모두 기존 값보다 크므로 모든 열이 업데이트됩니다.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-업데이트 결과를 요약하면 다음과 같습니다.
-
-| 작업 | 실행 조건 | 업데이트된 열 |
-| --- | --- | --- |
-| 삽입 1 | `c, d, s1`에 최초 쓰기 | `c, d, s1` |
-| 삽입 2 | 새 `s1` < 기존 `s1` | 없음 |
-| 삽입 3 | `e, s2`에 최초 쓰기 | `e, s2` |
-| 삽입 4 | 새 `s1` > 기존 `s1` | `c, d, s1` |
-| 삽입 5 | 새 `s1`과 `s2`가 모두 기존 값보다 큼 | `c, d, s1, e, s2` |
-
-### 3. 열 추가 또는 삭제 {#3-add-or-drop-columns}
-
-Sequence Mapping 테이블은 `ALTER TABLE`을 사용하여 열과 매핑을 동적으로 추가하거나 삭제할 수 있습니다.
-
-**초기 테이블 생성**: `s1 -> c,d` 매핑 하나만 포함합니다.
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d"
-);
-```
-
-**초기 데이터 쓰기**:
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values 
(1,1,1,1,1),(1,1,3,3,3),(1,1,2,2,2);
-Query OK, 3 rows affected (0.101 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |
-+------+------+------+------+------+
-```
-
-**열과 매핑 추가**: `ALTER TABLE`을 사용하여 `e, s2` 열을 추가하면서 `s2 -> e` 매핑을 함께 선언합니다.
-
-```sql
-MySQL > alter table upsert_test add column (e int(11) NULL, s2 bigint) 
PROPERTIES('sequence_mapping.s2' = 'e');
-Query OK, 0 rows affected (0.011 sec)
-
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s2    | bigint | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 | NULL | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**새 매핑이 적용된 후 데이터 쓰기**:
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.052 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |    2 |    2 |
-+------+------+------+------+------+------+------+
-
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    5 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-**열 삭제**: Value 열인 `e`를 삭제하면 해당 매핑이 무효화됩니다. 그런 다음 Sequence 열인 `s2`를 삭제합니다.
-
-```sql
-MySQL > alter table upsert_test drop column e;
-Query OK, 0 rows affected (0.006 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | s2   |
-+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+
-
-MySQL > alter table upsert_test drop column s2;
-Query OK, 0 rows affected (0.005 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |
-+------+------+------+------+------+
-```
-
-## 사용 제약 사항 {#usage-constraints}
-
-<!-- Knowledge type: Configuration parameters / Usage limitations -->
-
-Sequence Mapping을 사용할 때는 다음 제약 사항에 유의해야 합니다.
-
-| 범주 | 제약 사항 |
-| --- | --- |
-| **테이블 생성 설정** | `light_schema_change`를 활성화해야 합니다. 테이블 생성 시 
`sequence_mapping` 속성을 선언하지 않으면 나중에 활성화할 수 없습니다. |
-| **열 타입** | Sequence 열은 정수 타입과 시간 타입(`DATE`, `DATETIME`)만 지원하며, 생성 후에는 타입을 
변경할 수 없습니다. |
-| **열 역할** | Sequence 열과 매핑된 열은 모두 Key 열이 될 수 없습니다. 모든 비 Key 열은 Sequence 열에 
매핑되어야 합니다. |
-| **매핑 관계** | 서로 다른 Sequence 열에 매핑된 열은 **겹칠 수 없습니다**(예: `d`를 `s1`과 `s2` 모두에 
매핑할 수 없음). 매핑을 설정한 후에는 **변경할 수 없습니다**(예: 이미 `s1`에 매핑된 열을 `s2`에 다시 매핑할 수 없음). |
-| **DDL 제한 사항** | 열 이름 변경은 지원하지 않습니다. Rollup 생성은 지원하지 않습니다. |
-| **저장 모드** | 현재 MOR (Merge-on-Read) 테이블만 지원합니다. 전역 Sequence 열과 함께 활성화하는 것은 
지원하지 않습니다. 일괄 삭제 작업은 지원하지 않습니다. |
-| **데이터 적재 시 동작** | 데이터 적재 시 포함되지 않은 필드는 기본값 또는 `NULL`로 자동으로 채워집니다. Sequence 
열을 비교할 때 `NULL`은 **가장 작은 값**으로 처리됩니다. |
diff --git 
a/i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
 
b/i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
index 0282235f72e..00872c0897f 100644
--- 
a/i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
+++ 
b/i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
@@ -145,7 +145,6 @@ PROPERTIES (
 자세한 내용은 다음 문서를 참고하세요.
 
 - Sequence 열, MVCC 버전 관리, `UPDATE` 동시성 매개변수 등의 동시성 제어 기능은 [Unique Key 모델의 업데이트 
동시성 제어](./unique-update-concurrent-control.md)를 참고하세요.
-- 여러 데이터 스트림이 동일한 와이드 테이블의 서로 다른 열을 동시에 업데이트하는 경우, Sequence Mapping을 사용하여 각 열의 
버전 순서를 독립적으로 제어할 수 있습니다. 자세한 내용은 [Unique Key 모델의 다중 스트림 
업데이트](./multi-stream-update-for-unique-model.md)를 참고하세요.
 
 ### 2.3 삭제 마커의 처리 과정 {#23-workflow-of-the-delete-marker}
 
@@ -230,7 +229,7 @@ Flink CDC 같은 도구는 업스트림 데이터베이스(MySQL, PostgreSQL, Or
     - 사용자 행동 스트림은 `page_view_count`와 `last_login_time`을 업데이트합니다.
     - 트랜잭션 스트림은 `total_orders`와 `total_amount`를 업데이트합니다.
 
-각 스트림은 변경된 열만 쓰므로 IO 오버헤드를 줄이고 실시간 조인의 리소스 사용을 피할 수 있습니다. 여러 스트림이 동시에 업데이트하는 
시나리오의 버전 제어는 [Unique Key 모델의 다중 스트림 
업데이트](./multi-stream-update-for-unique-model.md)를 참고하세요.
+각 스트림은 변경된 열만 쓰므로 IO 오버헤드를 줄이고 실시간 조인의 리소스 사용을 피할 수 있습니다.
 
 ## 4. 사용 권장 사항 {#4-usage-recommendations}
 
diff --git 
a/i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
 
b/i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
deleted file mode 100644
index aa23c37a136..00000000000
--- 
a/i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
+++ /dev/null
@@ -1,312 +0,0 @@
----
-{
-    "title": "Обновления из нескольких потоков для модели Unique",
-    "language": "ru",
-    "description": "Используйте функцию Sequence Mapping модели Unique в Doris 
для решения проблем контроля версий при одновременном обновлении разных 
столбцов одной широкой таблицы несколькими потоками данных."
-}
----
-
-<!-- Knowledge type: Feature + Procedure -->
-<!-- Applicable scenarios: Concurrent writes from multiple data streams to a 
wide table / Real-time updates for some columns combined with on-demand updates 
for others -->
-
-## Сценарии использования и основные проблемы 
{#business-scenarios-and-pain-points}
-
-В хранилищах данных с широкими таблицами разные столбцы одной таблицы часто 
поступают из **разных источников данных** или **разных конвейеров обработки**. 
Типичные примеры:
-
-- **Поток реального времени**: непрерывно обновляет часть полей таблицы 
(например, столбцы, связанные с поведением пользователей).
-- **Офлайн-поток (или поток по требованию)**: обновляет другие поля таблицы в 
определённые моменты времени (например, столбцы, связанные с профилями 
пользователей или тегами).
-
-В таком сценарии несколько потоков данных одновременно записывают данные в 
одну таблицу с первичным ключом, что приводит к двум основным проблемам:
-
-| Проблема | Описание |
-| --- | --- |
-| **Перезапись при одновременном обновлении** | Разные потоки данных поступают 
в разное время. Простая агрегация REPLACE не гарантирует, что данные каждого 
потока будут обновляться в порядке версий. |
-| **Высокие затраты на объединение данных** | Практически невозможно 
дождаться, пока данные всех столбцов будут собраны перед записью. Ожидание 
может оказаться слишком долгим и неприемлемым для бизнеса. |
-
-Модель Unique в Doris изначально поддерживает контроль версий на основе 
столбца Sequence, но **позволяет определить только один глобальный столбец 
Sequence**. Это не даёт возможности независимо управлять версиями обновлений 
разных столбцов из разных потоков данных. Для решения этой задачи в Doris 
предусмотрена функция **Sequence Mapping**.
-
-## Решение: Sequence Mapping {#solution-sequence-mapping}
-
-<!-- Knowledge type: One-line definition -->
-
-**Sequence Mapping** — это механизм одновременного обновления из нескольких 
потоков, поддерживаемый моделью Unique в Doris. Он позволяет назначить разные 
столбцы Sequence разным столбцам данных и тем самым обеспечить независимый 
контроль версий для каждого потока данных без взаимного влияния.
-
-### Принцип работы {#how-it-works}
-
-Предположим, таблица модели Unique содержит следующие столбцы:
-
-| Столбец | A | B | C | D | E | s1 | s2 |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| Роль | Key | Key | Value | Value | Value | Sequence | Sequence |
-
-- Поток данных 1 записывает данные в столбцы `A, B, C, D` и использует `s1` в 
качестве столбца контроля версий.
-- Поток данных 2 записывает данные в столбцы `A, B, E` и использует `s2` в 
качестве столбца контроля версий.
-
-При таком сопоставлении:
-
-- `s1` управляет версией столбцов `C, D`: только если `s1` новых данных 
больше, чем `s1` существующих данных, обновляются `C, D, s1`.
-- `s2` управляет версией столбца `E`: только если `s2` новых данных больше, 
чем `s2` существующих данных, обновляются `E, s2`.
-- Эти два потока **не влияют друг на друга**, а запросы могут читать 
актуальные данные всех столбцов.
-
-## Пример использования {#usage-example}
-
-### 1. Создание таблицы с поддержкой Sequence Mapping 
{#1-create-a-table-that-supports-sequence-mapping}
-
-Используйте свойство `sequence_mapping.<sequence_col>` в разделе `PROPERTIES`, 
чтобы задать сопоставление между столбцом Sequence и столбцами Value, которыми 
он управляет.
-
-В следующем примере создаётся таблица модели Unique, в которой версиями 
столбцов `c, d` управляет `s1`, а версиями столбца `e` управляет `s2`:
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `e`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT "",
-    `s2` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d",
-    "sequence_mapping.s2" = "e"
-);
-```
-
-> Поддерживаемые типы столбцов Sequence: целочисленные типы, `DATE` и 
`DATETIME`. **После создания столбца его тип изменить нельзя.**
-
-После создания схема таблицы выглядит следующим образом:
-
-```sql
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| s2    | int    | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-```
-
-### 2. Запись данных и выполнение запросов {#2-write-and-query-data}
-
-Следующие пять операций вставки показывают, как разные значения Sequence 
влияют на обновление каждого столбца.
-
-**Вставка 1**: записываются только `c, d, s1`, а `e, s2` не записываются.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,2,2,2);
-Query OK, 1 row affected (0.080 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**Вставка 2**: `s1=1` меньше существующего значения `s1=2`, поэтому `c, d, s1` 
не обновляются.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,1,1,1);
-Query OK, 1 row affected (0.048 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**Вставка 3**: записываются `e, s2`. Поскольку предыдущее значение `s2` было 
`NULL` (считается наименьшим значением), `e, s2` обновляются.
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.043 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 |    2 |    2 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**Вставка 4**: `s1=3` больше существующего значения `s1=2`, поэтому `c, d, s1` 
обновляются, а `e, s2` остаются без изменений.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,3,3,3);
-Query OK, 1 row affected (0.049 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    2 |    3 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**Вставка 5**: записываются обе группы столбцов. И `s1=4`, и `s2=4` больше 
существующих значений, поэтому обновляются все столбцы.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-Сводка результатов обновления:
-
-| Операция | Условие срабатывания | Обновлённые столбцы |
-| --- | --- | --- |
-| Вставка 1 | Первая запись `c, d, s1` | `c, d, s1` |
-| Вставка 2 | Новое значение `s1` < существующее значение `s1` | Нет |
-| Вставка 3 | Первая запись `e, s2` | `e, s2` |
-| Вставка 4 | Новое значение `s1` > существующее значение `s1` | `c, d, s1` |
-| Вставка 5 | Оба новых значения `s1` и `s2` больше существующих значений | 
`c, d, s1, e, s2` |
-
-### 3. Добавление и удаление столбцов {#3-add-or-drop-columns}
-
-Таблица с Sequence Mapping поддерживает динамическое добавление и удаление 
столбцов и сопоставлений с помощью `ALTER TABLE`.
-
-**Создание исходной таблицы**: таблица содержит только одно сопоставление `s1 
-> c,d`.
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d"
-);
-```
-
-**Запись исходных данных**:
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values 
(1,1,1,1,1),(1,1,3,3,3),(1,1,2,2,2);
-Query OK, 3 rows affected (0.101 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |
-+------+------+------+------+------+
-```
-
-**Добавление столбцов и сопоставления**: используйте `ALTER TABLE`, чтобы 
добавить столбцы `e, s2` и одновременно задать сопоставление `s2 -> e`.
-
-```sql
-MySQL > alter table upsert_test add column (e int(11) NULL, s2 bigint) 
PROPERTIES('sequence_mapping.s2' = 'e');
-Query OK, 0 rows affected (0.011 sec)
-
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s2    | bigint | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 | NULL | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**Запись после вступления нового сопоставления в силу**:
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.052 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |    2 |    2 |
-+------+------+------+------+------+------+------+
-
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    5 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-**Удаление столбцов**: удалите столбец Value `e`, после чего соответствующее 
сопоставление перестанет действовать. Затем удалите столбец Sequence `s2`.
-
-```sql
-MySQL > alter table upsert_test drop column e;
-Query OK, 0 rows affected (0.006 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | s2   |
-+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+
-
-MySQL > alter table upsert_test drop column s2;
-Query OK, 0 rows affected (0.005 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |
-+------+------+------+------+------+
-```
-
-## Ограничения использования {#usage-constraints}
-
-<!-- Knowledge type: Configuration parameters / Usage limitations -->
-
-При использовании Sequence Mapping учитывайте следующие ограничения:
-
-| Категория | Ограничение |
-| --- | --- |
-| **Настройки при создании таблицы** | Параметр `light_schema_change` должен 
быть включён. Если свойство `sequence_mapping` не задано при создании таблицы, 
включить его позднее нельзя. |
-| **Типы столбцов** | Столбцы Sequence поддерживают только целочисленные типы 
и типы даты и времени (`DATE`, `DATETIME`); после создания столбца его тип 
изменить нельзя. |
-| **Роли столбцов** | Ни столбцы Sequence, ни сопоставленные им столбцы не 
могут быть столбцами Key. Все столбцы, кроме Key, должны быть сопоставлены со 
столбцом Sequence. |
-| **Связи сопоставления** | Наборы столбцов, сопоставленных разным столбцам 
Sequence, **не могут пересекаться** (например, `d` нельзя сопоставить 
одновременно с `s1` и `s2`). После создания сопоставления **его нельзя 
изменить** (например, столбец, уже сопоставленный с `s1`, нельзя переназначить 
столбцу `s2`). |
-| **Ограничения DDL** | Переименование столбцов не поддерживается. Создание 
Rollup не поддерживается. |
-| **Режим хранения** | В настоящее время поддерживаются только таблицы MOR 
(Merge-on-Read). Одновременное использование с глобальным столбцом Sequence не 
поддерживается. Пакетные операции удаления не поддерживаются. |
-| **Семантика загрузки** | Поля, не указанные при загрузке, автоматически 
заполняются значениями по умолчанию или `NULL`. При сравнении столбцов Sequence 
значение `NULL` считается **наименьшим значением**. |
diff --git 
a/i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
 
b/i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
index 7ace53a2ddd..abfc42c37d1 100644
--- 
a/i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
+++ 
b/i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
@@ -145,7 +145,6 @@ PROPERTIES (
 Дополнительная информация:
 
 - О возможностях управления параллельным доступом, таких как столбец Sequence, 
управление версиями MVCC и параметры параллельного выполнения `UPDATE`, см. 
[Управление параллельными обновлениями в модели Unique 
Key](./unique-update-concurrent-control.md).
-- Если несколько потоков данных одновременно обновляют разные столбцы одной 
широкой таблицы, можно использовать Sequence Mapping для независимого 
управления порядком версий каждого столбца. Подробнее см. [Многопоточные 
обновления в модели Unique Key](./multi-stream-update-for-unique-model.md).
 
 ### 2.3 Механизм работы метки удаления {#23-workflow-of-the-delete-marker}
 
@@ -230,7 +229,7 @@ PROPERTIES (
     - Поток пользовательского поведения обновляет `page_view_count` и 
`last_login_time`.
     - Поток транзакций обновляет `total_orders` и `total_amount`.
 
-Каждый поток записывает только изменённые столбцы, что снижает накладные 
расходы на IO и позволяет избежать затрат ресурсов на соединения в реальном 
времени. Об управлении версиями при одновременной работе нескольких потоков см. 
[Многопоточные обновления в модели Unique 
Key](./multi-stream-update-for-unique-model.md).
+Каждый поток записывает только изменённые столбцы, что снижает накладные 
расходы на IO и позволяет избежать затрат ресурсов на соединения в реальном 
времени.
 
 ## 4. Рекомендации по использованию {#4-usage-recommendations}
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs-releases/current/v4.1/release-4.1.0.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs-releases/current/v4.1/release-4.1.0.md
index 5f95fc1f1e7..8d39c2f8117 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs-releases/current/v4.1/release-4.1.0.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs-releases/current/v4.1/release-4.1.0.md
@@ -655,10 +655,6 @@ AND t1.ts >= t2.ts;
 
   支持自适应调整 MemTable Flush 线程池大小,可以根据集群实时负载自动匹配更合适的写入并发,在高写入场景下更好地平衡吞吐、资源占用与稳定性。
 
-- **主键模型多流更新**
-
-  主键模型支持通过 sequence_mapping 进行多流合并更新,不同数据流可以分别更新同一张表的不同列,并按各自 sequence 
字段完成合并,适合实时流更新与离线数据补写并行写入的场景。
-
 - **Routine Load 灵活列更新**
 
   Routine Load 
支持灵活的部分列更新,允许对非主键列进行灵活更新,同一批次内不同行可以更新不同列。适用于状态变更、特征回填、标签更新等场景,进一步简化数据维护流程。
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
deleted file mode 100644
index b13e68f5a21..00000000000
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
+++ /dev/null
@@ -1,312 +0,0 @@
----
-{
-    "title": "主键模型的多流更新",
-    "language": "zh-CN",
-    "description": "使用 Doris Unique 模型的 Sequence Mapping 
功能,解决多条数据流并发更新同一张宽表中不同列的版本控制问题。"
-}
----
-
-<!-- 知识类型: 功能特性 + 操作步骤 -->
-<!-- 适用场景: 多数据流并发写入宽表 / 部分列实时更新 + 部分列按需更新 -->
-
-## 业务场景与痛点
-
-在数据仓库的宽表场景中,同一张表的不同列往往来自**不同的数据源**或**不同的处理链路**,常见情况如下:
-
-- **实时流**:持续更新表中的部分字段(例如:用户行为相关列)。
-- **离线流(或按需流)**:在特定时机更新表中的另外一些字段(例如:用户画像、标签相关列)。
-
-这种场景下,多条数据流会并发写入同一张主键表,并面临两个核心问题:
-
-| 痛点 | 说明 |
-| --- | --- |
-| **并发覆盖问题** | 不同数据流到达时间不同步,简单的 REPLACE 聚合无法保证每一流各自数据按版本顺序更新。 |
-| **数据拼接代价高** | 在写入前等待所有列拼接完成几乎不可行,间隔时间可能很长,业务难以承受。 |
-
-Doris Unique 模型原生支持基于 Sequence 列的版本控制,但**只能定义单个全局 Sequence 
列**,无法独立控制不同数据流对各自列的更新版本。为此,Doris 提供了 **Sequence Mapping** 功能。
-
-## 解决方案:Sequence Mapping
-
-<!-- 知识类型: 一句话定义 -->
-
-**Sequence Mapping** 是 Doris Unique 模型支持的一种多流并发更新机制:通过为不同的数据列指定不同的 Sequence 
列,实现多条数据流各自独立的版本控制,互不干扰。
-
-### 工作原理
-
-假设一张 Unique 表包含如下列:
-
-| 列名 | A | B | C | D | E | s1 | s2 |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| 角色 | Key | Key | Value | Value | Value | Sequence | Sequence |
-
-- 数据流 1 写入 `A、B、C、D` 列,使用 `s1` 作为版本控制列。
-- 数据流 2 写入 `A、B、E` 列,使用 `s2` 作为版本控制列。
-
-通过这种映射关系:
-
-- `s1` 控制 `C、D` 列的版本:仅当新到数据的 `s1` 大于已存数据的 `s1` 时,`C、D、s1` 才会被更新。
-- `s2` 控制 `E` 列的版本:仅当新到数据的 `s2` 大于已存数据的 `s2` 时,`E、s2` 才会被更新。
-- 两流之间**互不干扰**,查询时可读取所有列的最新数据。
-
-## 使用示例
-
-### 1. 创建支持 Sequence Mapping 的表
-
-通过 `PROPERTIES` 中的 `sequence_mapping.<sequence_col>` 属性,声明 Sequence 列与受其控制的 
Value 列之间的映射关系。
-
-下面示例创建一张 Unique 表,指定 `c、d` 列依赖 `s1` 控制版本,`e` 列依赖 `s2` 控制版本:
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `e`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT "",
-    `s2` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d",
-    "sequence_mapping.s2" = "e"
-);
-```
-
-> Sequence 列支持的类型:整型、`DATE`、`DATETIME`。**列创建后不能更改类型**。
-
-创建完成后,表结构如下:
-
-```sql
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| s2    | int    | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-```
-
-### 2. 写入与查询数据
-
-下面通过五次插入操作,演示不同 Sequence 值对各列的更新效果。
-
-**第 1 次插入**:仅写入 `c、d、s1`,未写入 `e、s2`。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,2,2,2);
-Query OK, 1 row affected (0.080 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**第 2 次插入**:`s1=1`,小于已存的 `s1=2`,因此 `c、d、s1` 不会被更新。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,1,1,1);
-Query OK, 1 row affected (0.048 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**第 3 次插入**:写入 `e、s2`,由于此前 `s2` 为 `NULL`(视为最小值),`e、s2` 被更新。
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.043 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 |    2 |    2 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**第 4 次插入**:`s1=3`,大于已存的 `s1=2`,因此 `c、d、s1` 被更新;`e、s2` 不受影响。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,3,3,3);
-Query OK, 1 row affected (0.049 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    2 |    3 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**第 5 次插入**:同时写入两组列,`s1=4`、`s2=4` 均大于已存值,所有列被更新。
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-更新效果汇总如下:
-
-| 操作 | 触发条件 | 更新的列 |
-| --- | --- | --- |
-| 第 1 次插入 | 首次写入 `c、d、s1` | `c、d、s1` |
-| 第 2 次插入 | 新 `s1` < 已存 `s1` | 无更新 |
-| 第 3 次插入 | 首次写入 `e、s2` | `e、s2` |
-| 第 4 次插入 | 新 `s1` > 已存 `s1` | `c、d、s1` |
-| 第 5 次插入 | 新 `s1`、`s2` 均大于已存值 | `c、d、s1、e、s2` |
-
-### 3. 添加或删除列
-
-Sequence Mapping 表支持通过 `ALTER TABLE` 动态添加或删除列与映射关系。
-
-**初始建表**:仅含一组映射 `s1 -> c,d`。
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d"
-);
-```
-
-**写入初始数据**:
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values 
(1,1,1,1,1),(1,1,3,3,3),(1,1,2,2,2);
-Query OK, 3 rows affected (0.101 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |
-+------+------+------+------+------+
-```
-
-**新增列与映射**:通过 `ALTER TABLE` 同时添加 `e、s2` 列,并声明 `s2 -> e` 映射。
-
-```sql
-MySQL > alter table upsert_test add column (e int(11) NULL, s2 bigint) 
PROPERTIES('sequence_mapping.s2' = 'e');
-Query OK, 0 rows affected (0.011 sec)
-
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s2    | bigint | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 | NULL | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**新映射生效后写入**:
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.052 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |    2 |    2 |
-+------+------+------+------+------+------+------+
-
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    5 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-**删除列**:删除 Value 列 `e`,对应的映射也会随之失效;再删除 Sequence 列 `s2`。
-
-```sql
-MySQL > alter table upsert_test drop column e;
-Query OK, 0 rows affected (0.006 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | s2   |
-+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+
-
-MySQL > alter table upsert_test drop column s2;
-Query OK, 0 rows affected (0.005 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |
-+------+------+------+------+------+
-```
-
-## 使用约束
-
-<!-- 知识类型: 配置参数 / 使用限制 -->
-
-使用 Sequence Mapping 时,需要注意以下约束:
-
-| 类别 | 约束 |
-| --- | --- |
-| **建表配置** | 必须开启 `light_schema_change`;如果建表时未声明 `sequence_mapping` 
属性,后续无法再开启。 |
-| **列类型** | Sequence 列仅支持整型与时间类型(`DATE`、`DATETIME`),创建后不能更改类型。 |
-| **列角色** | Sequence 列与映射列均不能作为 Key 列;所有非 Key 列必须映射到某个 Sequence 列。 |
-| **映射关系** | 不同 Sequence 列的映射列**不能重叠**(例如 `d` 不能同时映射到 `s1` 与 
`s2`);映射关系建立后**不支持修改**(例如已映射到 `s1` 的列无法再改为映射到 `s2`)。 |
-| **DDL 限制** | 暂不支持列重命名;暂不支持创建 Rollup。 |
-| **存储模式** | 暂仅支持 MOR(Merge-on-Read)表;不支持与全局 Sequence 列同时启用;不支持批量删除操作。 |
-| **导入语义** | 导入时未包含的字段会自动用默认值或 `NULL` 填充;Sequence 列在比较时,`NULL` 视为**最小值**。 |
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
index 15c7970a2c7..838f115b2c5 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/update-overview.md
@@ -145,7 +145,6 @@ PROPERTIES (
 更多内容:
 
 - Sequence 列、MVCC 版本管理、`UPDATE` 
并发参数等并发控制能力详见:[主键模型的更新并发控制](./unique-update-concurrent-control.md)。
-- 多条数据流同时更新一张宽表的不同列时,可使用 Sequence Mapping 
控制每列各自的版本顺序,详见:[主键模型的多流更新](./multi-stream-update-for-unique-model.md)。
 
 ### 2.3 删除标记的工作流程
 
@@ -230,7 +229,7 @@ PROPERTIES (
     - 用户行为流更新 `page_view_count`、`last_login_time`;
     - 交易流更新 `total_orders`、`total_amount`。
 
-每个流仅写入变化列,可降低 IO 开销并避免实时 Join 
的资源消耗。多流并发场景下的版本控制见:[主键模型的多流更新](./multi-stream-update-for-unique-model.md)。
+每个流仅写入变化列,可降低 IO 开销并避免实时 Join 的资源消耗。
 
 ## 4. 使用建议
 
diff --git a/releasenotes/v4.1/release-4.1.0.md 
b/releasenotes/v4.1/release-4.1.0.md
index 5d4bf79a632..95589176f43 100644
--- a/releasenotes/v4.1/release-4.1.0.md
+++ b/releasenotes/v4.1/release-4.1.0.md
@@ -588,8 +588,6 @@ AND t1.ts >= t2.ts;
 - **[Continuous Load 
PostgreSQL](https://doris.apache.org/zh-CN/docs/4.x/data-operate/import/streaming-job/continuous-load-postgresql-single)**
 - **Self-Adaptation Write Scheduling**
   Supports Self-Adaptation adjustment of the MemTable Flush thread pool size, 
which can automatically match a more appropriate write concurrency level based 
on the real-time load of the cluster, better balancing throughput, resource 
utilization, and stability in high-write scenarios.
-- **Multi-stream Update of Primary Key Model**
-  The primary key model supports multi-stream merge updates through 
sequence_mapping. Different data streams can update different columns of the 
same table separately and complete the merge according to their respective 
sequence fields, which is suitable for scenarios where real-time stream updates 
and offline data supplementation are written in parallel.
 - **Routine Load Flexible Column Update**
   Routine Load supports flexible partial update, allowing for flexible updates 
to non-primary key columns, and different rows within the same batch can update 
different columns. It is suitable for scenarios such as status changes, feature 
backfilling, and label updates, further simplifying the data maintenance 
process.
 - **Dynamic Parameter Tuning for Routine Load**
diff --git a/scripts/last-update/data.json b/scripts/last-update/data.json
index ac719334ee1..44b67abebb2 100644
--- a/scripts/last-update/data.json
+++ b/scripts/last-update/data.json
@@ -6067,7 +6067,6 @@
   
"i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/overview.mdx":
 "2026-05-17T13:13:02-07:00",
   
"i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/transaction.md":
 "2026-05-28T12:31:47+08:00",
   
"i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update-and-delete.mdx":
 "2026-05-17T13:13:02-07:00",
-  
"i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md":
 "2026-05-17T13:13:02-07:00",
   
"i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/partial-column-update.md":
 "2026-05-28T12:31:47+08:00",
   
"i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/unique-update-concurrent-control.md":
 "2026-05-17T13:13:02-07:00",
   
"i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/update/unique-update-sql.md":
 "2026-05-17T13:13:02-07:00",
@@ -10125,7 +10124,6 @@
   "versioned_docs/version-4.x/data-operate/overview.mdx": 
"2026-05-17T13:13:02-07:00",
   "versioned_docs/version-4.x/data-operate/transaction.md": 
"2026-06-13T22:33:14-07:00",
   "versioned_docs/version-4.x/data-operate/update-and-delete.mdx": 
"2026-05-17T13:13:02-07:00",
-  
"versioned_docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md":
 "2026-05-17T13:13:02-07:00",
   "versioned_docs/version-4.x/data-operate/update/partial-column-update.md": 
"2026-05-28T12:31:47+08:00",
   
"versioned_docs/version-4.x/data-operate/update/unique-update-concurrent-control.md":
 "2026-05-17T13:13:02-07:00",
   "versioned_docs/version-4.x/data-operate/update/unique-update-sql.md": 
"2026-05-17T13:13:02-07:00",
diff --git a/scripts/migrate-4.x/new-slugs-en.txt 
b/scripts/migrate-4.x/new-slugs-en.txt
index 3a5923b80ab..ca19aa5d62a 100644
--- a/scripts/migrate-4.x/new-slugs-en.txt
+++ b/scripts/migrate-4.x/new-slugs-en.txt
@@ -302,7 +302,6 @@ data-operate/import/load-manual
 data-operate/overview
 data-operate/transaction
 data-operate/update-and-delete
-data-operate/update/multi-stream-update-for-unique-model
 data-operate/update/partial-column-update
 data-operate/update/unique-update
 data-operate/update/unique-update-concurrent-control
diff --git a/scripts/migrate-4.x/new-slugs-zh.txt 
b/scripts/migrate-4.x/new-slugs-zh.txt
index 80200c89757..ebcad0b7767 100644
--- a/scripts/migrate-4.x/new-slugs-zh.txt
+++ b/scripts/migrate-4.x/new-slugs-zh.txt
@@ -302,7 +302,6 @@ data-operate/import/load-manual
 data-operate/overview
 data-operate/transaction
 data-operate/update-and-delete
-data-operate/update/multi-stream-update-for-unique-model
 data-operate/update/partial-column-update
 data-operate/update/unique-update
 data-operate/update/unique-update-concurrent-control
diff --git 
a/translations/state/ja/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
 
b/translations/state/ja/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
deleted file mode 100644
index 327381c81f1..00000000000
--- 
a/translations/state/ja/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
+++ /dev/null
@@ -1,20 +0,0 @@
-{
-  "schemaVersion": 1,
-  "page": {
-    "pluginId": "default",
-    "version": "4.x",
-    "docId": "data-operate/update/multi-stream-update-for-unique-model",
-    "locale": "ja",
-    "sourceLocale": "en",
-    "sourcePath": 
"versioned_docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md",
-    "targetPath": 
"i18n/ja/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md",
-    "sourceCommit": "618b88463542c388ef5d477f53e4f17162fd5eb7",
-    "sourceHash": 
"416b7fa15cd57123c911c42bb04495daadd5ca57268da5104d99ea0a52ce2497",
-    "sourceTechnicalHash": 
"17b983d3283143f3c39558b0dbcae7b1afbc8541f5eab048d76afa406cdacff5",
-    "targetHash": 
"452faaa3be3b220d99d60e5237956d4116e4bb2bdeb0e18bcb35e7fd0b84b46e",
-    "reviewStatus": "machine",
-    "ownership": "machine",
-    "translatedAt": "2026-10-15T02:27:01.606Z",
-    "glossaryVersion": "0"
-  }
-}
diff --git 
a/translations/state/ko/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
 
b/translations/state/ko/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
deleted file mode 100644
index 718980505b4..00000000000
--- 
a/translations/state/ko/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
+++ /dev/null
@@ -1,37 +0,0 @@
-{
-  "schemaVersion": 1,
-  "page": {
-    "pluginId": "default",
-    "version": "4.x",
-    "docId": "data-operate/update/multi-stream-update-for-unique-model",
-    "locale": "ko",
-    "sourceLocale": "en",
-    "sourcePath": 
"versioned_docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md",
-    "targetPath": 
"i18n/ko/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md",
-    "sourceCommit": "f1464d3fb0dd6007d36104a970c3bc7db282d822",
-    "sourceHash": 
"416b7fa15cd57123c911c42bb04495daadd5ca57268da5104d99ea0a52ce2497",
-    "sourceTechnicalHash": 
"17b983d3283143f3c39558b0dbcae7b1afbc8541f5eab048d76afa406cdacff5",
-    "targetHash": 
"77abe43a37fd3209e68898bac8de37af57d96c92149eca2db3778b3ecae736dc",
-    "reviewStatus": "machine",
-    "ownership": "machine",
-    "translatedAt": "2026-10-19T09:21:26.296Z",
-    "glossaryVersion": "1",
-    "generation": {
-      "policy": "whole-document-v1",
-      "mode": "full",
-      "reason": "local-t09-batch",
-      "attempts": 1,
-      "modelCalls": 1,
-      "acceptedWithWarnings": false,
-      "sourceHash": 
"416b7fa15cd57123c911c42bb04495daadd5ca57268da5104d99ea0a52ce2497",
-      "targetHash": 
"77abe43a37fd3209e68898bac8de37af57d96c92149eca2db3778b3ecae736dc",
-      "warnings": [],
-      "history": [
-        {
-          "attempt": 1,
-          "issues": []
-        }
-      ]
-    }
-  }
-}
diff --git 
a/translations/state/ru/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
 
b/translations/state/ru/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
deleted file mode 100644
index e1fd617ddd7..00000000000
--- 
a/translations/state/ru/pages/default/4.x/data-operate/update/multi-stream-update-for-unique-model.json
+++ /dev/null
@@ -1,37 +0,0 @@
-{
-  "schemaVersion": 1,
-  "page": {
-    "pluginId": "default",
-    "version": "4.x",
-    "docId": "data-operate/update/multi-stream-update-for-unique-model",
-    "locale": "ru",
-    "sourceLocale": "en",
-    "sourcePath": 
"versioned_docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md",
-    "targetPath": 
"i18n/ru/docusaurus-plugin-content-docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md",
-    "sourceCommit": "87417f1fefb604bf8a98d1fea0ace4beaccc4b2c",
-    "sourceHash": 
"416b7fa15cd57123c911c42bb04495daadd5ca57268da5104d99ea0a52ce2497",
-    "sourceTechnicalHash": 
"17b983d3283143f3c39558b0dbcae7b1afbc8541f5eab048d76afa406cdacff5",
-    "targetHash": 
"5c0c6536483a34cb247aa8915fc4e6bd65967a23bedde6cf092958ac558c5a65",
-    "reviewStatus": "machine",
-    "ownership": "machine",
-    "translatedAt": "2026-10-22T14:34:47.966Z",
-    "glossaryVersion": "1",
-    "generation": {
-      "policy": "whole-document-v1",
-      "mode": "full",
-      "reason": "local-t09-batch",
-      "attempts": 1,
-      "modelCalls": 1,
-      "acceptedWithWarnings": false,
-      "sourceHash": 
"416b7fa15cd57123c911c42bb04495daadd5ca57268da5104d99ea0a52ce2497",
-      "targetHash": 
"5c0c6536483a34cb247aa8915fc4e6bd65967a23bedde6cf092958ac558c5a65",
-      "warnings": [],
-      "history": [
-        {
-          "attempt": 1,
-          "issues": []
-        }
-      ]
-    }
-  }
-}
diff --git 
a/versioned_docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
 
b/versioned_docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
deleted file mode 100644
index a333fea57c9..00000000000
--- 
a/versioned_docs/version-4.x/data-operate/update/multi-stream-update-for-unique-model.md
+++ /dev/null
@@ -1,312 +0,0 @@
----
-{
-    "title": "Multi-Stream Updates for the Unique Model",
-    "language": "en",
-    "description": "Use the Sequence Mapping feature of the Doris Unique model 
to solve version control problems when multiple data streams concurrently 
update different columns of the same wide table."
-}
----
-
-<!-- Knowledge type: Feature + Procedure -->
-<!-- Applicable scenarios: Concurrent writes from multiple data streams to a 
wide table / Real-time updates for some columns combined with on-demand updates 
for others -->
-
-## Business Scenarios and Pain Points
-
-In wide-table scenarios in a data warehouse, different columns of the same 
table often come from **different data sources** or **different processing 
pipelines**. Common cases include:
-
-- **Real-time stream**: Continuously updates some fields of the table (for 
example, columns related to user behavior).
-- **Offline stream (or on-demand stream)**: Updates other fields of the table 
at specific times (for example, columns related to user profiles or tags).
-
-In this scenario, multiple data streams concurrently write to the same 
primary-key table and face two core problems:
-
-| Pain Point | Description |
-| --- | --- |
-| **Concurrent overwrite problem** | Different data streams arrive at 
different times. A simple REPLACE aggregation cannot guarantee that the data 
from each stream is updated in version order. |
-| **High cost of joining data** | It is almost impossible to wait for all 
columns to be assembled before writing. The interval can be very long, and the 
business cannot tolerate it. |
-
-The Doris Unique model natively supports version control based on a Sequence 
column, but **only a single global Sequence column can be defined**, which 
cannot independently control the update version of different columns from 
different data streams. To address this, Doris provides the **Sequence 
Mapping** feature.
-
-## Solution: Sequence Mapping
-
-<!-- Knowledge type: One-line definition -->
-
-**Sequence Mapping** is a multi-stream concurrent update mechanism supported 
by the Doris Unique model. By specifying different Sequence columns for 
different data columns, it enables independent version control for each data 
stream without interference.
-
-### How It Works
-
-Suppose a Unique table contains the following columns:
-
-| Column | A | B | C | D | E | s1 | s2 |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| Role | Key | Key | Value | Value | Value | Sequence | Sequence |
-
-- Data stream 1 writes to columns `A, B, C, D` and uses `s1` as the version 
control column.
-- Data stream 2 writes to columns `A, B, E` and uses `s2` as the version 
control column.
-
-With this mapping:
-
-- `s1` controls the version of columns `C, D`: only when the `s1` of the new 
data is greater than the `s1` of the existing data, `C, D, s1` are updated.
-- `s2` controls the version of column `E`: only when the `s2` of the new data 
is greater than the `s2` of the existing data, `E, s2` are updated.
-- The two streams **do not interfere with each other**, and queries can read 
the latest data of all columns.
-
-## Usage Example
-
-### 1. Create a Table That Supports Sequence Mapping
-
-Use the `sequence_mapping.<sequence_col>` property in `PROPERTIES` to declare 
the mapping between a Sequence column and the Value columns it controls.
-
-The following example creates a Unique table where columns `c, d` are 
version-controlled by `s1`, and column `e` is version-controlled by `s2`:
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `e`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT "",
-    `s2` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d",
-    "sequence_mapping.s2" = "e"
-);
-```
-
-> Supported types for Sequence columns: integer types, `DATE`, and `DATETIME`. 
**The type cannot be changed after the column is created.**
-
-After creation, the table schema is as follows:
-
-```sql
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| s2    | int    | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-```
-
-### 2. Write and Query Data
-
-The following five insert operations demonstrate how different Sequence values 
affect updates of each column.
-
-**Insert 1**: Writes only `c, d, s1` and does not write `e, s2`.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,2,2,2);
-Query OK, 1 row affected (0.080 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**Insert 2**: `s1=1` is less than the existing `s1=2`, so `c, d, s1` are not 
updated.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,1,1,1);
-Query OK, 1 row affected (0.048 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 | NULL |    2 | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**Insert 3**: Writes `e, s2`. Since the previous `s2` was `NULL` (treated as 
the smallest value), `e, s2` are updated.
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.043 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    2 |    2 |    2 |    2 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**Insert 4**: `s1=3` is greater than the existing `s1=2`, so `c, d, s1` are 
updated, while `e, s2` are not affected.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values (1,1,3,3,3);
-Query OK, 1 row affected (0.049 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    2 |    3 |    2 |
-+------+------+------+------+------+------+------+
-```
-
-**Insert 5**: Writes both groups of columns. Both `s1=4` and `s2=4` are 
greater than the existing values, so all columns are updated.
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | e    | s1   | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-A summary of the update results:
-
-| Operation | Trigger Condition | Updated Columns |
-| --- | --- | --- |
-| Insert 1 | First write of `c, d, s1` | `c, d, s1` |
-| Insert 2 | New `s1` < existing `s1` | None |
-| Insert 3 | First write of `e, s2` | `e, s2` |
-| Insert 4 | New `s1` > existing `s1` | `c, d, s1` |
-| Insert 5 | Both new `s1` and `s2` are greater than existing values | `c, d, 
s1, e, s2` |
-
-### 3. Add or Drop Columns
-
-A Sequence Mapping table supports dynamically adding or dropping columns and 
mappings using `ALTER TABLE`.
-
-**Initial table creation**: Contains only one mapping `s1 -> c,d`.
-
-```sql
-CREATE TABLE `upsert_test` (
-    `a`  bigint(20) NULL COMMENT "",
-    `b`  int(11)    NULL COMMENT "",
-    `c`  int(11)    NULL COMMENT "",
-    `d`  int(11)    NULL COMMENT "",
-    `s1` int(11)    NULL COMMENT ""
-) ENGINE=OLAP
-UNIQUE KEY(`a`, `b`)
-COMMENT "OLAP"
-DISTRIBUTED BY HASH(`a`, `b`) BUCKETS 1
-PROPERTIES (
-    "enable_unique_key_merge_on_write" = "false",
-    "light_schema_change" = "true",
-    "replication_num" = "1",
-    "sequence_mapping.s1" = "c,d"
-);
-```
-
-**Write initial data**:
-
-```sql
-MySQL > insert into upsert_test(a, b, c, d, s1) values 
(1,1,1,1,1),(1,1,3,3,3),(1,1,2,2,2);
-Query OK, 3 rows affected (0.101 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |
-+------+------+------+------+------+
-```
-
-**Add columns and mapping**: Use `ALTER TABLE` to add columns `e, s2` and 
declare the `s2 -> e` mapping at the same time.
-
-```sql
-MySQL > alter table upsert_test add column (e int(11) NULL, s2 bigint) 
PROPERTIES('sequence_mapping.s2' = 'e');
-Query OK, 0 rows affected (0.011 sec)
-
-MySQL > desc upsert_test;
-+-------+--------+------+-------+---------+---------+
-| Field | Type   | Null | Key   | Default | Extra   |
-+-------+--------+------+-------+---------+---------+
-| a     | bigint | Yes  | true  | NULL    |         |
-| b     | int    | Yes  | true  | NULL    |         |
-| c     | int    | Yes  | false | NULL    | REPLACE |
-| d     | int    | Yes  | false | NULL    | REPLACE |
-| s1    | int    | Yes  | false | NULL    | REPLACE |
-| e     | int    | Yes  | false | NULL    | REPLACE |
-| s2    | bigint | Yes  | false | NULL    | REPLACE |
-+-------+--------+------+-------+---------+---------+
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 | NULL | NULL |
-+------+------+------+------+------+------+------+
-```
-
-**Write after the new mapping takes effect**:
-
-```sql
-MySQL > insert into upsert_test(a, b, e, s2) values (1,1,2,2);
-Query OK, 1 row affected (0.052 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    3 |    3 |    3 |    2 |    2 |
-+------+------+------+------+------+------+------+
-
-MySQL > insert into upsert_test(a, b, c, d, s1, e, s2) values (1,1,5,5,4,5,4);
-Query OK, 1 row affected (0.050 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | e    | s2   |
-+------+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    5 |    4 |
-+------+------+------+------+------+------+------+
-```
-
-**Drop columns**: Drop the Value column `e`, and the corresponding mapping is 
invalidated. Then drop the Sequence column `s2`.
-
-```sql
-MySQL > alter table upsert_test drop column e;
-Query OK, 0 rows affected (0.006 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+------+
-| a    | b    | c    | d    | s1   | s2   |
-+------+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |    4 |
-+------+------+------+------+------+------+
-
-MySQL > alter table upsert_test drop column s2;
-Query OK, 0 rows affected (0.005 sec)
-
-MySQL > select * from upsert_test;
-+------+------+------+------+------+
-| a    | b    | c    | d    | s1   |
-+------+------+------+------+------+
-|    1 |    1 |    5 |    5 |    4 |
-+------+------+------+------+------+
-```
-
-## Usage Constraints
-
-<!-- Knowledge type: Configuration parameters / Usage limitations -->
-
-When using Sequence Mapping, note the following constraints:
-
-| Category | Constraint |
-| --- | --- |
-| **Table creation configuration** | `light_schema_change` must be enabled. If 
the `sequence_mapping` property is not declared at table creation, it cannot be 
enabled later. |
-| **Column types** | Sequence columns only support integer types and time 
types (`DATE`, `DATETIME`), and the type cannot be changed after creation. |
-| **Column roles** | Neither Sequence columns nor mapped columns can be Key 
columns. All non-Key columns must be mapped to a Sequence column. |
-| **Mapping relationships** | Mapped columns of different Sequence columns 
**cannot overlap** (for example, `d` cannot be mapped to both `s1` and `s2`). 
After a mapping is established, **it cannot be modified** (for example, a 
column already mapped to `s1` cannot be remapped to `s2`). |
-| **DDL limitations** | Column renaming is not supported. Rollup creation is 
not supported. |
-| **Storage mode** | Currently only MOR (Merge-on-Read) tables are supported. 
Enabling alongside a global Sequence column is not supported. Batch delete 
operations are not supported. |
-| **Load semantics** | Fields not included during loading are automatically 
filled with default values or `NULL`. When comparing Sequence columns, `NULL` 
is treated as the **smallest value**. |
diff --git a/versioned_docs/version-4.x/data-operate/update/update-overview.md 
b/versioned_docs/version-4.x/data-operate/update/update-overview.md
index 840010e5970..f01265e7156 100644
--- a/versioned_docs/version-4.x/data-operate/update/update-overview.md
+++ b/versioned_docs/version-4.x/data-operate/update/update-overview.md
@@ -145,7 +145,6 @@ PROPERTIES (
 For more information:
 
 - For concurrency control capabilities such as the Sequence column, MVCC 
version management, and `UPDATE` concurrency parameters, see: [Concurrency 
Control of Updates in the Unique Key 
Model](./unique-update-concurrent-control.md).
-- When multiple data streams update different columns of the same wide table 
simultaneously, you can use Sequence Mapping to control the version order of 
each column independently. For details, see: [Multi-Stream Updates in the 
Unique Key Model](./multi-stream-update-for-unique-model.md).
 
 ### 2.3 Workflow of the Delete Marker
 
@@ -230,7 +229,7 @@ Using partial column updates, you can complete multi-source 
wide table assembly
     - The user behavior stream updates `page_view_count` and `last_login_time`.
     - The transaction stream updates `total_orders` and `total_amount`.
 
-Each stream writes only the changed columns, which reduces IO overhead and 
avoids the resource consumption of real-time joins. For version control in 
multi-stream concurrent scenarios, see: [Multi-Stream Updates in the Unique Key 
Model](./multi-stream-update-for-unique-model.md).
+Each stream writes only the changed columns, which reduces IO overhead and 
avoids the resource consumption of real-time joins.
 
 ## 4. Usage Recommendations
 
diff --git a/versioned_sidebars/version-4.x-sidebars.json 
b/versioned_sidebars/version-4.x-sidebars.json
index 4fe5609ff3e..f2d29857312 100644
--- a/versioned_sidebars/version-4.x-sidebars.json
+++ b/versioned_sidebars/version-4.x-sidebars.json
@@ -556,8 +556,7 @@
                 "data-operate/update/update-of-unique-model",
                 "data-operate/update/update-of-aggregate-model",
                 "data-operate/update/partial-column-update",
-                "data-operate/update/unique-update-concurrent-control",
-                "data-operate/update/multi-stream-update-for-unique-model"
+                "data-operate/update/unique-update-concurrent-control"
               ]
             },
             {


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to