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 33f62d128ba [doc](typo) fix some typo in `update` section (#1280)
33f62d128ba is described below
commit 33f62d128baabd1c79537f3ee716e1ebbbedee87
Author: yagagagaga <[email protected]>
AuthorDate: Tue Nov 5 17:43:36 2024 +0800
[doc](typo) fix some typo in `update` section (#1280)
# Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [x] 2.0
# Languages
- [x] Chinese
- [x] English
---
docs/data-operate/delete/batch-delete-manual.md | 2 +-
docs/data-operate/update/unique-update-transaction.md | 8 ++++----
.../current/data-operate/delete/batch-delete-manual.md | 2 +-
.../current/data-operate/update/unique-update-transaction.md | 8 ++++----
.../version-2.0/data-operate/delete/batch-delete-manual.md | 2 +-
.../version-2.0/data-operate/update/unique-update-transaction.md | 8 ++++----
.../version-2.1/data-operate/delete/batch-delete-manual.md | 2 +-
.../version-2.1/data-operate/update/unique-update-transaction.md | 8 ++++----
.../version-3.0/data-operate/delete/batch-delete-manual.md | 2 +-
.../version-3.0/data-operate/update/unique-update-transaction.md | 8 ++++----
.../version-2.0/data-operate/delete/batch-delete-manual.md | 2 +-
.../version-2.0/data-operate/update/unique-update-transaction.md | 8 ++++----
.../version-2.1/data-operate/delete/batch-delete-manual.md | 2 +-
.../version-2.1/data-operate/update/unique-update-transaction.md | 8 ++++----
.../version-3.0/data-operate/delete/batch-delete-manual.md | 2 +-
.../version-3.0/data-operate/update/unique-update-transaction.md | 8 ++++----
16 files changed, 40 insertions(+), 40 deletions(-)
diff --git a/docs/data-operate/delete/batch-delete-manual.md
b/docs/data-operate/delete/batch-delete-manual.md
index 9b870e596e6..dc2f274830d 100644
--- a/docs/data-operate/delete/batch-delete-manual.md
+++ b/docs/data-operate/delete/batch-delete-manual.md
@@ -340,4 +340,4 @@ mysql DESC test;
:::tip Tip
When data is written and deleted at the same time in the imported data (e.g.,
in the Flink CDC scenario), using the sequence column can effectively ensure
consistency when the data arrives out of order, avoiding the deletion operation
of an old version that arrives later, and accidentally deleting the new version
of the data that arrives first.
-:::
\ No newline at end of file
+:::
diff --git a/docs/data-operate/update/unique-update-transaction.md
b/docs/data-operate/update/unique-update-transaction.md
index a6422a7994c..82587357a25 100644
--- a/docs/data-operate/update/unique-update-transaction.md
+++ b/docs/data-operate/update/unique-update-transaction.md
@@ -201,7 +201,7 @@ PROPERTIES(
Table structure:
```sql
-MySQL > desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -235,7 +235,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
The result is:
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -257,7 +257,7 @@ After completing the above steps, load the following data:
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -277,7 +277,7 @@ In the loaded data, the sequence column (modify_date) of
all previously loaded d
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/batch-delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/batch-delete-manual.md
index 063f9018530..64975c25356 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/batch-delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/delete/batch-delete-manual.md
@@ -335,4 +335,4 @@ li,male,10
并没有被删除，这是因为在底层的依赖关系上，会先判断 key 相同的情况，对外展示 sequence
列的值大的行数据，然后在看该行的`DORIS_DELETE_SIGN`值是否为 1，如果为 1 则不会对外展示，如果为 0，则仍会读出来。
-当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
\ No newline at end of file
+当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
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 ec4669817db..508af6cfb3a 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
@@ -200,7 +200,7 @@ PROPERTIES(
表结构如下：
```sql
-MySQL desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -234,7 +234,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
结果为
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -256,7 +256,7 @@ MySQL > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -276,7 +276,7 @@ MySQL [test] > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/delete/batch-delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/delete/batch-delete-manual.md
index 1e2820c8b5d..55a763a63ed 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/delete/batch-delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/delete/batch-delete-manual.md
@@ -345,4 +345,4 @@ li,male,10
并没有被删除，这是因为在底层的依赖关系上，会先判断 key 相同的情况，对外展示 sequence
列的值大的行数据，然后在看该行的`DORIS_DELETE_SIGN`值是否为 1，如果为 1 则不会对外展示，如果为 0，则仍会读出来。
-当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
\ No newline at end of file
+当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
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 ec4669817db..508af6cfb3a 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
@@ -200,7 +200,7 @@ PROPERTIES(
表结构如下：
```sql
-MySQL desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -234,7 +234,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
结果为
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -256,7 +256,7 @@ MySQL > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -276,7 +276,7 @@ MySQL [test] > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/batch-delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/batch-delete-manual.md
index 063f9018530..64975c25356 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/batch-delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/delete/batch-delete-manual.md
@@ -335,4 +335,4 @@ li,male,10
并没有被删除，这是因为在底层的依赖关系上，会先判断 key 相同的情况，对外展示 sequence
列的值大的行数据，然后在看该行的`DORIS_DELETE_SIGN`值是否为 1，如果为 1 则不会对外展示，如果为 0，则仍会读出来。
-当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
\ No newline at end of file
+当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
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 ec4669817db..508af6cfb3a 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
@@ -200,7 +200,7 @@ PROPERTIES(
表结构如下：
```sql
-MySQL desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -234,7 +234,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
结果为
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -256,7 +256,7 @@ MySQL > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -276,7 +276,7 @@ MySQL [test] > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/batch-delete-manual.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/batch-delete-manual.md
index 063f9018530..64975c25356 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/batch-delete-manual.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/delete/batch-delete-manual.md
@@ -335,4 +335,4 @@ li,male,10
并没有被删除，这是因为在底层的依赖关系上，会先判断 key 相同的情况，对外展示 sequence
列的值大的行数据，然后在看该行的`DORIS_DELETE_SIGN`值是否为 1，如果为 1 则不会对外展示，如果为 0，则仍会读出来。
-当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
\ No newline at end of file
+当导入数据中同时存在数据写入和删除时（例如 CDC 场景中），使用 Sequence
列可以有效的保证当数据乱序到达时的一致性，避免后到达的一个旧版本的删除操作，误删掉了先到达的新版本的数据。
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 ec4669817db..508af6cfb3a 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
@@ -200,7 +200,7 @@ PROPERTIES(
表结构如下：
```sql
-MySQL desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -234,7 +234,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
结果为
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -256,7 +256,7 @@ MySQL > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -276,7 +276,7 @@ MySQL [test] > select * from test_table;
查询数据
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
diff --git
a/versioned_docs/version-2.0/data-operate/delete/batch-delete-manual.md
b/versioned_docs/version-2.0/data-operate/delete/batch-delete-manual.md
index 8b2231ff26d..ffea9b609d2 100644
--- a/versioned_docs/version-2.0/data-operate/delete/batch-delete-manual.md
+++ b/versioned_docs/version-2.0/data-operate/delete/batch-delete-manual.md
@@ -350,4 +350,4 @@ mysql DESC test;
:::tip Tip
When data is written and deleted at the same time in the imported data (e.g.,
in the Flink CDC scenario), using the sequence column can effectively ensure
consistency when the data arrives out of order, avoiding the deletion operation
of an old version that arrives later, and accidentally deleting the new version
of the data that arrives first.
-:::
\ No newline at end of file
+:::
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 a6422a7994c..82587357a25 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
@@ -201,7 +201,7 @@ PROPERTIES(
Table structure:
```sql
-MySQL > desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -235,7 +235,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
The result is:
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -257,7 +257,7 @@ After completing the above steps, load the following data:
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -277,7 +277,7 @@ In the loaded data, the sequence column (modify_date) of
all previously loaded d
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
diff --git
a/versioned_docs/version-2.1/data-operate/delete/batch-delete-manual.md
b/versioned_docs/version-2.1/data-operate/delete/batch-delete-manual.md
index 9b870e596e6..dc2f274830d 100644
--- a/versioned_docs/version-2.1/data-operate/delete/batch-delete-manual.md
+++ b/versioned_docs/version-2.1/data-operate/delete/batch-delete-manual.md
@@ -340,4 +340,4 @@ mysql DESC test;
:::tip Tip
When data is written and deleted at the same time in the imported data (e.g.,
in the Flink CDC scenario), using the sequence column can effectively ensure
consistency when the data arrives out of order, avoiding the deletion operation
of an old version that arrives later, and accidentally deleting the new version
of the data that arrives first.
-:::
\ No newline at end of file
+:::
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 a6422a7994c..82587357a25 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
@@ -201,7 +201,7 @@ PROPERTIES(
Table structure:
```sql
-MySQL > desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -235,7 +235,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
The result is:
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -257,7 +257,7 @@ After completing the above steps, load the following data:
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -277,7 +277,7 @@ In the loaded data, the sequence column (modify_date) of
all previously loaded d
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
diff --git
a/versioned_docs/version-3.0/data-operate/delete/batch-delete-manual.md
b/versioned_docs/version-3.0/data-operate/delete/batch-delete-manual.md
index 9b870e596e6..dc2f274830d 100644
--- a/versioned_docs/version-3.0/data-operate/delete/batch-delete-manual.md
+++ b/versioned_docs/version-3.0/data-operate/delete/batch-delete-manual.md
@@ -340,4 +340,4 @@ mysql DESC test;
:::tip Tip
When data is written and deleted at the same time in the imported data (e.g.,
in the Flink CDC scenario), using the sequence column can effectively ensure
consistency when the data arrives out of order, avoiding the deletion operation
of an old version that arrives later, and accidentally deleting the new version
of the data that arrives first.
-:::
\ No newline at end of file
+:::
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 a6422a7994c..82587357a25 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
@@ -201,7 +201,7 @@ PROPERTIES(
Table structure:
```sql
-MySQL > desc test_table;
+MySQL> desc test_table;
+-------------+--------------+------+-------+---------+---------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-------+---------+---------+
@@ -235,7 +235,7 @@ curl --location-trusted -u root: -T testData
http://host:port/api/test/test_tabl
The result is:
```sql
-MySQL > select * from test_table;
+MySQL> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -257,7 +257,7 @@ After completing the above steps, load the following data:
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
@@ -277,7 +277,7 @@ In the loaded data, the sequence column (modify_date) of
all previously loaded d
Query the data:
```sql
-MySQL [test] > select * from test_table;
+MySQL [test]> select * from test_table;
+---------+------------+----------+-------------+---------+
| user_id | date | group_id | modify_date | keyword |
+---------+------------+----------+-------------+---------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
