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

dataroaring 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 bd5abae2f9 [doc](sequence col) update typos and usage of sequence 
column (#1310)
bd5abae2f9 is described below

commit bd5abae2f9c7e6c139abe2f28bee7a6165d46dfd
Author: zhannngchen <[email protected]>
AuthorDate: Thu Nov 7 15:07:42 2024 +0800

    [doc](sequence col) update typos and usage of sequence column (#1310)
    
    # Versions
    
    - [x] dev
    - [x] 3.0
    - [x] 2.1
    - [x] 2.0
    
    # Languages
    
    - [x] Chinese
    - [x] English
    
    ---------
    
    Co-authored-by: Chen Zhang <[email protected]>
---
 docs/data-operate/update/unique-update-transaction.md  | 18 +++++++-----------
 .../data-operate/update/unique-update-transaction.md   | 16 ++++++----------
 .../data-operate/update/unique-update-transaction.md   | 18 +++++++-----------
 .../data-operate/update/unique-update-transaction.md   | 18 +++++++-----------
 .../data-operate/update/unique-update-transaction.md   | 18 +++++++-----------
 .../data-operate/update/unique-update-transaction.md   | 18 +++++++-----------
 .../data-operate/update/unique-update-transaction.md   | 18 +++++++-----------
 .../data-operate/update/unique-update-transaction.md   | 18 +++++++-----------
 8 files changed, 55 insertions(+), 87 deletions(-)

diff --git a/docs/data-operate/update/unique-update-transaction.md 
b/docs/data-operate/update/unique-update-transaction.md
index baf7b3adda..93b58db8fc 100644
--- a/docs/data-operate/update/unique-update-transaction.md
+++ b/docs/data-operate/update/unique-update-transaction.md
@@ -41,24 +41,20 @@ The Unique model primarily caters to scenarios that require 
unique primary keys,
 To address this issue, Doris supports sequence columns. Users can specify a 
sequence column during data load, allowing the replacement order to be 
controlled by the user. The sequence column determines the order of 
replacements for rows with the same key column. A higher sequence value can 
replace a lower one, but not vice versa. This method delegates the 
determination of order to the user, enabling control over the replacement 
sequence.
 
 :::note
-Sequence columns are currently supported only in the Uniq model.
+Sequence columns are currently supported only in the Unique model.
 :::
 
 ### Basic Principles
 
-The basic principle is achieved by adding a hidden column called 
__**DORIS_SEQUENCE_COL__. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
+The basic principle is achieved by adding a hidden column called 
**__DORIS_SEQUENCE_COL__**. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
 
 **Table Creation**
 
-When creating a Uniq table, an automatically added hidden column called 
__**DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
+When creating a Unique table, an automatically added hidden column called 
__DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
 
 **Data load**
 
-During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `DORIS_SEQUENCE_COL`, can be set as a column in the data source or a 
column in the table structure.
-
-**Read**
-
-When requesting the value column, an additional read operation is performed 
for the `DORIS_SEQUENCE_COL` column. This column is used as the basis for the 
REPLACE
+During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `__DORIS_SEQUENCE_COL__`, can be set as a column in the data source or 
a column in the table structure.
 
 ### Syntax Usage
 
@@ -66,7 +62,7 @@ When requesting the value column, an additional read 
operation is performed for
 
 **1. Set `sequence_col` (Recommended)**
 
-When creating a Uniq table, specify the mapping of the sequence column to 
other columns in the table.
+When creating a Unique table, specify the mapping of the sequence column to 
other columns in the table.
 
 ```Plain
 PROPERTIES (
@@ -80,7 +76,7 @@ The load method is the same as when there is no sequence 
column, making it relat
 
 **2. Set `sequence_type`**
 
-When creating a Uniq table, specify the type of the sequence column.
+When creating a Unique table, specify the type of the sequence column.
 
 ```Plain
 PROPERTIES (
@@ -157,7 +153,7 @@ If `function_column.sequence_col` or 
`function_column.sequence_type` is set when
 
 For a table that does not support sequence columns, if you want to use this 
feature, you can use the following statement: `ALTER TABLE example_db.my_table 
ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES ("function_column.sequence_type" 
= "Date")` to enable it.
 
-If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the `DORIS_SEQUENCE_COL` 
column, it means that the table supports sequence columns; otherwise, it does 
not.
+If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the 
`__DORIS_SEQUENCE_COL__` column, it means that the table supports sequence 
columns; otherwise, it does not.
 
 ### Usage Example
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-transaction.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-transaction.md
index 7342ef20c1..9280c1f338 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-transaction.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/update/unique-update-transaction.md
@@ -45,24 +45,20 @@ Unique 模型主要针对需要唯一主键的场景,可以保证主键唯一
 为了解决这个问题,Doris 支持了 sequence 列,通过用户在导入时指定 sequence 列,相同 key 列下,按照 sequence 
列的值进行替换,较大值可以替换较小值,反之则无法替换。该方法将顺序的确定交给了用户,由用户控制替换顺序。
 
 :::note
-sequence 列目前只支持 Uniq 模型。
+sequence 列目前只支持 Unique 模型。
 :::
 
 ### 基本原理
 
-通过增加一个隐藏列__**DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
+通过增加一个隐藏列**__DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
 
 **建表**
 
-创建 Uniq 表时,将按照用户指定类型自动添加一个隐藏列__**DORIS_SEQUENCE_COL__**。
+创建 Unique 表时,用户可以设置表中的某一列作为sequence列。
 
 **导入**
 
-导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`DORIS_SEQUENCE_COL`的值既可以设置为数据源中一列,也可以是表结构中的一列。
-
-**读取**
-
-请求包含 value 列时需要额外读取`DORIS_SEQUENCE_COL`列,该列用于在相同 key 列下,REPLACE 
聚合函数替换顺序的依据,较大值可以替换较小值,反之则不能替换。
+导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`__DORIS_SEQUENCE_COL__`的值既可以设置为数据源中一列,也可以是表结构中的一列。
 
 ### 使用语法
 
@@ -70,7 +66,7 @@ sequence 列目前只支持 Uniq 模型。
 
 **1. 设置****`sequence_col`(推荐)**
 
-创建 Uniq 表时,指定 sequence 列到表中其他 column 的映射
+创建 Unique 表时,指定 sequence 列到表中其他 column 的映射
 
 ```Plain
 PROPERTIES (
@@ -161,7 +157,7 @@ CREATE ROUTINE LOAD example_db.test1 ON example_tbl
 
 对于一个不支持 sequence column 的表,如果想要使用该功能,可以使用如下语句: `ALTER TABLE 
example_db.my_table ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES 
("function_column.sequence_type" = "Date")` 来启用。 
 
-如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`DORIS_SEQUENCE_COL` 
列则支持,如果没有则不支持。
+如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`__DORIS_SEQUENCE_COL__` 
列则支持,如果没有则不支持。
 
 ### 使用示例
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/update/unique-update-transaction.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/update/unique-update-transaction.md
index 7342ef20c1..00564a2694 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/update/unique-update-transaction.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/update/unique-update-transaction.md
@@ -45,24 +45,20 @@ Unique 模型主要针对需要唯一主键的场景,可以保证主键唯一
 为了解决这个问题,Doris 支持了 sequence 列,通过用户在导入时指定 sequence 列,相同 key 列下,按照 sequence 
列的值进行替换,较大值可以替换较小值,反之则无法替换。该方法将顺序的确定交给了用户,由用户控制替换顺序。
 
 :::note
-sequence 列目前只支持 Uniq 模型。
+sequence 列目前只支持 Unique 模型。
 :::
 
 ### 基本原理
 
-通过增加一个隐藏列__**DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
+通过增加一个隐藏列**__DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
 
 **建表**
 
-创建 Uniq 表时,将按照用户指定类型自动添加一个隐藏列__**DORIS_SEQUENCE_COL__**。
+创建 Unique 表时,将按照用户指定类型自动添加一个隐藏列__DORIS_SEQUENCE_COL__。
 
 **导入**
 
-导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`DORIS_SEQUENCE_COL`的值既可以设置为数据源中一列,也可以是表结构中的一列。
-
-**读取**
-
-请求包含 value 列时需要额外读取`DORIS_SEQUENCE_COL`列,该列用于在相同 key 列下,REPLACE 
聚合函数替换顺序的依据,较大值可以替换较小值,反之则不能替换。
+导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`__DORIS_SEQUENCE_COL__`的值既可以设置为数据源中一列,也可以是表结构中的一列。
 
 ### 使用语法
 
@@ -70,7 +66,7 @@ sequence 列目前只支持 Uniq 模型。
 
 **1. 设置****`sequence_col`(推荐)**
 
-创建 Uniq 表时,指定 sequence 列到表中其他 column 的映射
+创建 Unique 表时,指定 sequence 列到表中其他 column 的映射
 
 ```Plain
 PROPERTIES (
@@ -84,7 +80,7 @@ sequence_col 用来指定 sequence 列到表中某一列的映射,该列可以
 
 **2. 设置****`sequence_type`**
 
-创建 Uniq 表时,指定 sequence 列类型
+创建 Unique 表时,指定 sequence 列类型
 
 ```Plain
 PROPERTIES (
@@ -161,7 +157,7 @@ CREATE ROUTINE LOAD example_db.test1 ON example_tbl
 
 对于一个不支持 sequence column 的表,如果想要使用该功能,可以使用如下语句: `ALTER TABLE 
example_db.my_table ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES 
("function_column.sequence_type" = "Date")` 来启用。 
 
-如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`DORIS_SEQUENCE_COL` 
列则支持,如果没有则不支持。
+如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`__DORIS_SEQUENCE_COL__` 
列则支持,如果没有则不支持。
 
 ### 使用示例
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-transaction.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-transaction.md
index 7342ef20c1..00564a2694 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-transaction.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/update/unique-update-transaction.md
@@ -45,24 +45,20 @@ Unique 模型主要针对需要唯一主键的场景,可以保证主键唯一
 为了解决这个问题,Doris 支持了 sequence 列,通过用户在导入时指定 sequence 列,相同 key 列下,按照 sequence 
列的值进行替换,较大值可以替换较小值,反之则无法替换。该方法将顺序的确定交给了用户,由用户控制替换顺序。
 
 :::note
-sequence 列目前只支持 Uniq 模型。
+sequence 列目前只支持 Unique 模型。
 :::
 
 ### 基本原理
 
-通过增加一个隐藏列__**DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
+通过增加一个隐藏列**__DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
 
 **建表**
 
-创建 Uniq 表时,将按照用户指定类型自动添加一个隐藏列__**DORIS_SEQUENCE_COL__**。
+创建 Unique 表时,将按照用户指定类型自动添加一个隐藏列__DORIS_SEQUENCE_COL__。
 
 **导入**
 
-导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`DORIS_SEQUENCE_COL`的值既可以设置为数据源中一列,也可以是表结构中的一列。
-
-**读取**
-
-请求包含 value 列时需要额外读取`DORIS_SEQUENCE_COL`列,该列用于在相同 key 列下,REPLACE 
聚合函数替换顺序的依据,较大值可以替换较小值,反之则不能替换。
+导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`__DORIS_SEQUENCE_COL__`的值既可以设置为数据源中一列,也可以是表结构中的一列。
 
 ### 使用语法
 
@@ -70,7 +66,7 @@ sequence 列目前只支持 Uniq 模型。
 
 **1. 设置****`sequence_col`(推荐)**
 
-创建 Uniq 表时,指定 sequence 列到表中其他 column 的映射
+创建 Unique 表时,指定 sequence 列到表中其他 column 的映射
 
 ```Plain
 PROPERTIES (
@@ -84,7 +80,7 @@ sequence_col 用来指定 sequence 列到表中某一列的映射,该列可以
 
 **2. 设置****`sequence_type`**
 
-创建 Uniq 表时,指定 sequence 列类型
+创建 Unique 表时,指定 sequence 列类型
 
 ```Plain
 PROPERTIES (
@@ -161,7 +157,7 @@ CREATE ROUTINE LOAD example_db.test1 ON example_tbl
 
 对于一个不支持 sequence column 的表,如果想要使用该功能,可以使用如下语句: `ALTER TABLE 
example_db.my_table ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES 
("function_column.sequence_type" = "Date")` 来启用。 
 
-如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`DORIS_SEQUENCE_COL` 
列则支持,如果没有则不支持。
+如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`__DORIS_SEQUENCE_COL__` 
列则支持,如果没有则不支持。
 
 ### 使用示例
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-transaction.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-transaction.md
index 7342ef20c1..00564a2694 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-transaction.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/update/unique-update-transaction.md
@@ -45,24 +45,20 @@ Unique 模型主要针对需要唯一主键的场景,可以保证主键唯一
 为了解决这个问题,Doris 支持了 sequence 列,通过用户在导入时指定 sequence 列,相同 key 列下,按照 sequence 
列的值进行替换,较大值可以替换较小值,反之则无法替换。该方法将顺序的确定交给了用户,由用户控制替换顺序。
 
 :::note
-sequence 列目前只支持 Uniq 模型。
+sequence 列目前只支持 Unique 模型。
 :::
 
 ### 基本原理
 
-通过增加一个隐藏列__**DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
+通过增加一个隐藏列**__DORIS_SEQUENCE_COL__**实现,该列的类型由用户在建表时指定,在导入时确定该列具体值,并依据该值决定相同 Key 
列下,哪一行生效。
 
 **建表**
 
-创建 Uniq 表时,将按照用户指定类型自动添加一个隐藏列__**DORIS_SEQUENCE_COL__**。
+创建 Unique 表时,将按照用户指定类型自动添加一个隐藏列__DORIS_SEQUENCE_COL__。
 
 **导入**
 
-导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`DORIS_SEQUENCE_COL`的值既可以设置为数据源中一列,也可以是表结构中的一列。
-
-**读取**
-
-请求包含 value 列时需要额外读取`DORIS_SEQUENCE_COL`列,该列用于在相同 key 列下,REPLACE 
聚合函数替换顺序的依据,较大值可以替换较小值,反之则不能替换。
+导入时,fe 在解析的过程中将隐藏列的值设置成 `order by` 表达式的值 (broker load 和 routine 
load),或者`function_column.sequence_col`表达式的值 (stream load),value 
列将按照该值进行替换。隐藏列`__DORIS_SEQUENCE_COL__`的值既可以设置为数据源中一列,也可以是表结构中的一列。
 
 ### 使用语法
 
@@ -70,7 +66,7 @@ sequence 列目前只支持 Uniq 模型。
 
 **1. 设置****`sequence_col`(推荐)**
 
-创建 Uniq 表时,指定 sequence 列到表中其他 column 的映射
+创建 Unique 表时,指定 sequence 列到表中其他 column 的映射
 
 ```Plain
 PROPERTIES (
@@ -84,7 +80,7 @@ sequence_col 用来指定 sequence 列到表中某一列的映射,该列可以
 
 **2. 设置****`sequence_type`**
 
-创建 Uniq 表时,指定 sequence 列类型
+创建 Unique 表时,指定 sequence 列类型
 
 ```Plain
 PROPERTIES (
@@ -161,7 +157,7 @@ CREATE ROUTINE LOAD example_db.test1 ON example_tbl
 
 对于一个不支持 sequence column 的表,如果想要使用该功能,可以使用如下语句: `ALTER TABLE 
example_db.my_table ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES 
("function_column.sequence_type" = "Date")` 来启用。 
 
-如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`DORIS_SEQUENCE_COL` 
列则支持,如果没有则不支持。
+如果不确定一个表是否支持 sequence column,可以通过设置一个 session variable 来显示隐藏列 `SET 
show_hidden_columns=true` ,之后使用`desc tablename`,如果输出中有`__DORIS_SEQUENCE_COL__` 
列则支持,如果没有则不支持。
 
 ### 使用示例
 
diff --git 
a/versioned_docs/version-2.0/data-operate/update/unique-update-transaction.md 
b/versioned_docs/version-2.0/data-operate/update/unique-update-transaction.md
index baf7b3adda..93b58db8fc 100644
--- 
a/versioned_docs/version-2.0/data-operate/update/unique-update-transaction.md
+++ 
b/versioned_docs/version-2.0/data-operate/update/unique-update-transaction.md
@@ -41,24 +41,20 @@ The Unique model primarily caters to scenarios that require 
unique primary keys,
 To address this issue, Doris supports sequence columns. Users can specify a 
sequence column during data load, allowing the replacement order to be 
controlled by the user. The sequence column determines the order of 
replacements for rows with the same key column. A higher sequence value can 
replace a lower one, but not vice versa. This method delegates the 
determination of order to the user, enabling control over the replacement 
sequence.
 
 :::note
-Sequence columns are currently supported only in the Uniq model.
+Sequence columns are currently supported only in the Unique model.
 :::
 
 ### Basic Principles
 
-The basic principle is achieved by adding a hidden column called 
__**DORIS_SEQUENCE_COL__. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
+The basic principle is achieved by adding a hidden column called 
**__DORIS_SEQUENCE_COL__**. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
 
 **Table Creation**
 
-When creating a Uniq table, an automatically added hidden column called 
__**DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
+When creating a Unique table, an automatically added hidden column called 
__DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
 
 **Data load**
 
-During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `DORIS_SEQUENCE_COL`, can be set as a column in the data source or a 
column in the table structure.
-
-**Read**
-
-When requesting the value column, an additional read operation is performed 
for the `DORIS_SEQUENCE_COL` column. This column is used as the basis for the 
REPLACE
+During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `__DORIS_SEQUENCE_COL__`, can be set as a column in the data source or 
a column in the table structure.
 
 ### Syntax Usage
 
@@ -66,7 +62,7 @@ When requesting the value column, an additional read 
operation is performed for
 
 **1. Set `sequence_col` (Recommended)**
 
-When creating a Uniq table, specify the mapping of the sequence column to 
other columns in the table.
+When creating a Unique table, specify the mapping of the sequence column to 
other columns in the table.
 
 ```Plain
 PROPERTIES (
@@ -80,7 +76,7 @@ The load method is the same as when there is no sequence 
column, making it relat
 
 **2. Set `sequence_type`**
 
-When creating a Uniq table, specify the type of the sequence column.
+When creating a Unique table, specify the type of the sequence column.
 
 ```Plain
 PROPERTIES (
@@ -157,7 +153,7 @@ If `function_column.sequence_col` or 
`function_column.sequence_type` is set when
 
 For a table that does not support sequence columns, if you want to use this 
feature, you can use the following statement: `ALTER TABLE example_db.my_table 
ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES ("function_column.sequence_type" 
= "Date")` to enable it.
 
-If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the `DORIS_SEQUENCE_COL` 
column, it means that the table supports sequence columns; otherwise, it does 
not.
+If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the 
`__DORIS_SEQUENCE_COL__` column, it means that the table supports sequence 
columns; otherwise, it does not.
 
 ### Usage Example
 
diff --git 
a/versioned_docs/version-2.1/data-operate/update/unique-update-transaction.md 
b/versioned_docs/version-2.1/data-operate/update/unique-update-transaction.md
index baf7b3adda..93b58db8fc 100644
--- 
a/versioned_docs/version-2.1/data-operate/update/unique-update-transaction.md
+++ 
b/versioned_docs/version-2.1/data-operate/update/unique-update-transaction.md
@@ -41,24 +41,20 @@ The Unique model primarily caters to scenarios that require 
unique primary keys,
 To address this issue, Doris supports sequence columns. Users can specify a 
sequence column during data load, allowing the replacement order to be 
controlled by the user. The sequence column determines the order of 
replacements for rows with the same key column. A higher sequence value can 
replace a lower one, but not vice versa. This method delegates the 
determination of order to the user, enabling control over the replacement 
sequence.
 
 :::note
-Sequence columns are currently supported only in the Uniq model.
+Sequence columns are currently supported only in the Unique model.
 :::
 
 ### Basic Principles
 
-The basic principle is achieved by adding a hidden column called 
__**DORIS_SEQUENCE_COL__. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
+The basic principle is achieved by adding a hidden column called 
**__DORIS_SEQUENCE_COL__**. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
 
 **Table Creation**
 
-When creating a Uniq table, an automatically added hidden column called 
__**DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
+When creating a Unique table, an automatically added hidden column called 
__DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
 
 **Data load**
 
-During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `DORIS_SEQUENCE_COL`, can be set as a column in the data source or a 
column in the table structure.
-
-**Read**
-
-When requesting the value column, an additional read operation is performed 
for the `DORIS_SEQUENCE_COL` column. This column is used as the basis for the 
REPLACE
+During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `__DORIS_SEQUENCE_COL__`, can be set as a column in the data source or 
a column in the table structure.
 
 ### Syntax Usage
 
@@ -66,7 +62,7 @@ When requesting the value column, an additional read 
operation is performed for
 
 **1. Set `sequence_col` (Recommended)**
 
-When creating a Uniq table, specify the mapping of the sequence column to 
other columns in the table.
+When creating a Unique table, specify the mapping of the sequence column to 
other columns in the table.
 
 ```Plain
 PROPERTIES (
@@ -80,7 +76,7 @@ The load method is the same as when there is no sequence 
column, making it relat
 
 **2. Set `sequence_type`**
 
-When creating a Uniq table, specify the type of the sequence column.
+When creating a Unique table, specify the type of the sequence column.
 
 ```Plain
 PROPERTIES (
@@ -157,7 +153,7 @@ If `function_column.sequence_col` or 
`function_column.sequence_type` is set when
 
 For a table that does not support sequence columns, if you want to use this 
feature, you can use the following statement: `ALTER TABLE example_db.my_table 
ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES ("function_column.sequence_type" 
= "Date")` to enable it.
 
-If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the `DORIS_SEQUENCE_COL` 
column, it means that the table supports sequence columns; otherwise, it does 
not.
+If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the 
`__DORIS_SEQUENCE_COL__` column, it means that the table supports sequence 
columns; otherwise, it does not.
 
 ### Usage Example
 
diff --git 
a/versioned_docs/version-3.0/data-operate/update/unique-update-transaction.md 
b/versioned_docs/version-3.0/data-operate/update/unique-update-transaction.md
index baf7b3adda..93b58db8fc 100644
--- 
a/versioned_docs/version-3.0/data-operate/update/unique-update-transaction.md
+++ 
b/versioned_docs/version-3.0/data-operate/update/unique-update-transaction.md
@@ -41,24 +41,20 @@ The Unique model primarily caters to scenarios that require 
unique primary keys,
 To address this issue, Doris supports sequence columns. Users can specify a 
sequence column during data load, allowing the replacement order to be 
controlled by the user. The sequence column determines the order of 
replacements for rows with the same key column. A higher sequence value can 
replace a lower one, but not vice versa. This method delegates the 
determination of order to the user, enabling control over the replacement 
sequence.
 
 :::note
-Sequence columns are currently supported only in the Uniq model.
+Sequence columns are currently supported only in the Unique model.
 :::
 
 ### Basic Principles
 
-The basic principle is achieved by adding a hidden column called 
__**DORIS_SEQUENCE_COL__. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
+The basic principle is achieved by adding a hidden column called 
**__DORIS_SEQUENCE_COL__**. The type of this column is specified by the user 
during table creation and its specific value is determined during data load. 
Based on this value, the row that takes effect is determined for rows with the 
same key column.
 
 **Table Creation**
 
-When creating a Uniq table, an automatically added hidden column called 
__**DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
+When creating a Unique table, an automatically added hidden column called 
__DORIS_SEQUENCE_COL__ is created, based on the user-specified type.
 
 **Data load**
 
-During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `DORIS_SEQUENCE_COL`, can be set as a column in the data source or a 
column in the table structure.
-
-**Read**
-
-When requesting the value column, an additional read operation is performed 
for the `DORIS_SEQUENCE_COL` column. This column is used as the basis for the 
REPLACE
+During data load, the FE (Frontend) sets the value of the hidden column as the 
value of the `ORDER BY` expression (for broker load and routine load) or the 
value of the `function_column.sequence_col` expression (for stream load). The 
value column is replaced based on this sequence value. The value of the hidden 
column, `__DORIS_SEQUENCE_COL__`, can be set as a column in the data source or 
a column in the table structure.
 
 ### Syntax Usage
 
@@ -66,7 +62,7 @@ When requesting the value column, an additional read 
operation is performed for
 
 **1. Set `sequence_col` (Recommended)**
 
-When creating a Uniq table, specify the mapping of the sequence column to 
other columns in the table.
+When creating a Unique table, specify the mapping of the sequence column to 
other columns in the table.
 
 ```Plain
 PROPERTIES (
@@ -80,7 +76,7 @@ The load method is the same as when there is no sequence 
column, making it relat
 
 **2. Set `sequence_type`**
 
-When creating a Uniq table, specify the type of the sequence column.
+When creating a Unique table, specify the type of the sequence column.
 
 ```Plain
 PROPERTIES (
@@ -157,7 +153,7 @@ If `function_column.sequence_col` or 
`function_column.sequence_type` is set when
 
 For a table that does not support sequence columns, if you want to use this 
feature, you can use the following statement: `ALTER TABLE example_db.my_table 
ENABLE FEATURE "SEQUENCE_LOAD" WITH PROPERTIES ("function_column.sequence_type" 
= "Date")` to enable it.
 
-If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the `DORIS_SEQUENCE_COL` 
column, it means that the table supports sequence columns; otherwise, it does 
not.
+If you are unsure whether a table supports sequence columns, you can set a 
session variable to display hidden columns with `SET show_hidden_columns=true`, 
and then use `desc tablename`. If the output includes the 
`__DORIS_SEQUENCE_COL__` column, it means that the table supports sequence 
columns; otherwise, it does not.
 
 ### Usage Example
 


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


Reply via email to