Skip to content

Commit 45de723

Browse files
bobhan1bobhan1
committed
remove current/3.0 en/zh docs
1 parent 882b223 commit 45de723

File tree

8 files changed

+8
-286
lines changed

8 files changed

+8
-286
lines changed

‎docs/data-operate/import/handling-messy-data.md

Lines changed: 1 addition & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,7 @@ This makes it easier to handle data loading problems and keeps data management s
3636

3737
## Strict Mode
3838

39-
Strict mode serves two primary purposes:
40-
1. Filtering out data rows where column type conversion fails during load
41-
2. Restricting updates to existing columns only in partial column update scenarios
39+
The main function of strict mode is to filter out data rows where column type conversion fails during load.
4240

4341
### Filtering Strategy for Column Type Conversion Failures
4442

@@ -82,73 +80,6 @@ The system employs different strategies based on the strict mode setting:
8280
3. Although `10` exceeds the range, since its type meets decimal requirements, strict mode does not affect it.
8381
:::
8482

85-
### Restricting Partial Column Updates to Existing Columns Only
86-
87-
In strict mode, each row in a partial column update must have its Key already exist in the table. In non-strict mode, partial column updates can both update existing rows (where Key exists) and insert new rows (where Key doesn't exist).
88-
89-
For example, given a table structure as follows:
90-
```sql
91-
CREATE TABLE user_profile
92-
(
93-
id INT,
94-
name VARCHAR(10),
95-
age INT,
96-
city VARCHAR(10),
97-
balance DECIMAL(9, 0),
98-
last_access_time DATETIME
99-
) ENGINE=OLAP
100-
UNIQUE KEY(id)
101-
DISTRIBUTED BY HASH(id) BUCKETS 1
102-
PROPERTIES (
103-
"enable_unique_key_merge_on_write" = "true"
104-
);
105-
```
106-
107-
The table contains one record as follows:
108-
```sql
109-
mysql> select * from user_profile;
110-
+------+-------+------+----------+---------+---------------------+
111-
| id | name | age | city | balance | last_access_time |
112-
+------+-------+------+----------+---------+---------------------+
113-
| 1 | kevin | 18 | shenzhen | 400 | 2023-07-01 12:00:00|
114-
+------+-------+------+----------+---------+---------------------+
115-
```
116-
117-
When using Insert Into with strict mode to perform partial column updates, the insertion will fail because the second and third rows with keys `(3)` and `(18)` do not exist in the original table:
118-
```sql
119-
SET enable_unique_key_partial_update=true;
120-
SET enable_insert_strict = true;
121-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
122-
(1, 500, '2023-07-03 12:00:01'),
123-
(3, 23, '2023-07-03 12:00:02'),
124-
(18, 9999999, '2023-07-03 12:00:03');
125-
ERROR 1105 (HY000): errCode = 2, detailMessage = Insert has filtered data in strict mode
126-
```
127-
128-
When using Insert Into with non-strict mode to perform partial column updates:
129-
```sql
130-
SET enable_unique_key_partial_update=true;
131-
SET enable_insert_strict = false;
132-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
133-
(1, 500, '2023-07-03 12:00:01'),
134-
(3, 23, '2023-07-03 12:00:02'),
135-
(18, 9999999, '2023-07-03 12:00:03');
136-
```
137-
138-
The existing record will be updated, and two new records will be inserted. For columns not specified in the insert statement, if a default value is defined, it will be used; if the column allows NULL values, NULL will be used; otherwise, the insertion will fail.
139-
140-
The query result is as follows:
141-
```sql
142-
mysql> select * from user_profile;
143-
+------+-------+------+----------+---------+---------------------+
144-
| id | name | age | city | balance | last_access_time |
145-
+------+-------+------+----------+---------+---------------------+
146-
| 1 | kevin | 18 | shenzhen | 500 | 2023-07-03 12:00:01 |
147-
| 3 | NULL | NULL | NULL | 23 | 2023-07-03 12:00:02 |
148-
| 18 | NULL | NULL | NULL | 9999999 | 2023-07-03 12:00:03 |
149-
+------+-------+------+----------+---------+---------------------+
150-
```
151-
15283
### Enable Strict Mode
15384

15485
Strict mode (strict_mode) defaults to False. Here's how to set it for different load methods:

‎docs/data-operate/import/import-way/stream-load-manual.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1032,7 +1032,7 @@ Doris supports a very rich set of column transformations and filtering operation
10321032

10331033
### Enable strict mode import
10341034

1035-
The strict_mode attribute is used to set whether the import task runs in strict mode. This attribute affects the results of column mapping, transformation, and filtering, and it also controls the behavior of partial column updates. For specific instructions on strict mode, please refer to the [Handling Messy Data](../../../data-operate/import/handling-messy-data) documentation.
1035+
The strict_mode attribute is used to set whether the import task runs in strict mode. This attribute affects the results of column mapping, transformation, and filtering. For specific instructions on strict mode, please refer to the [Handling Messy Data](../../../data-operate/import/handling-messy-data) documentation.
10361036

10371037
### Perform partial column updates/flexible partial update during import
10381038

‎i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/handling-messy-data.md

Lines changed: 1 addition & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,7 @@ under the License.
3333

3434
## 严格模式
3535

36-
严格模式具有两个主要功能：
37-
1. 对导入过程中发生列类型转换失败的数据行进行过滤。
38-
2. 在部分列更新场景中，限制只能更新已存在的列。
36+
严格模式的主要功能是对导入过程中发生列类型转换失败的数据行进行过滤。
3937

4038
### 列类型转换失败的过滤策略
4139

@@ -79,74 +77,6 @@ under the License.
7977
3. `10` 虽然是一个超过范围的值，但是因为其类型符合 decimal 的要求，所以严格模式对其不产生影响。
8078
:::
8179

82-
83-
### 限定部分列更新只能更新已有的列
84-
85-
在严格模式下，部分列更新插入的每一行数据必须满足该行数据的 Key 在表中已经存在。而在非严格模式下，进行部分列更新时可以更新 Key 已经存在的行，也可以插入 Key 不存在的新行。
86-
87-
例如有表结构如下：
88-
```sql
89-
CREATE TABLE user_profile
90-
(
91-
id INT,
92-
name VARCHAR(10),
93-
age INT,
94-
city VARCHAR(10),
95-
balance DECIMAL(9, 0),
96-
last_access_time DATETIME
97-
) ENGINE=OLAP
98-
UNIQUE KEY(id)
99-
DISTRIBUTED BY HASH(id) BUCKETS 1
100-
PROPERTIES (
101-
"enable_unique_key_merge_on_write" = "true"
102-
);
103-
```
104-
105-
表中有一条数据如下：
106-
```sql
107-
mysql> select * from user_profile;
108-
+------+-------+------+----------+---------+---------------------+
109-
| id | name | age | city | balance | last_access_time |
110-
+------+-------+------+----------+---------+---------------------+
111-
| 1 | kevin | 18 | shenzhen | 400 | 2023-07-01 12:00:00|
112-
+------+-------+------+----------+---------+---------------------+
113-
```
114-
115-
当用户使用严格模式的 Insert Into 部分列更新向表中插入上述数据时，由于开启了严格模式且第二、三行的数据的 key(`(3)`, `(18)`) 不在原表中，所以本次插入会失败：
116-
```sql
117-
SET enable_unique_key_partial_update=true;
118-
SET enable_insert_strict = true;
119-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
120-
(1, 500, '2023-07-03 12:00:01'),
121-
(3, 23, '2023-07-03 12:00:02'),
122-
(18, 9999999, '2023-07-03 12:00:03');
123-
ERROR 1105 (HY000): errCode = 2, detailMessage = Insert has filtered data in strict mode
124-
```
125-
126-
当用户使用非严格模式的 Insert Into 部分列更新向表中插入如下数据时：
127-
```sql
128-
SET enable_unique_key_partial_update=true;
129-
SET enable_insert_strict = false;
130-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
131-
(1, 500, '2023-07-03 12:00:01'),
132-
(3, 23, '2023-07-03 12:00:02'),
133-
(18, 9999999, '2023-07-03 12:00:03');
134-
```
135-
136-
表中原有的一条数据将会被更新，此外还向表中插入了两条新数据。对于插入的数据中用户没有指定的列，如果该列有默认值，则会以默认值填充；否则，如果该列可以为 NULL，则将以 NULL 值填充；否则本次插入不成功。
137-
138-
查询结果如下：
139-
```sql
140-
mysql> select * from user_profile;
141-
+------+-------+------+----------+---------+---------------------+
142-
| id | name | age | city | balance | last_access_time |
143-
+------+-------+------+----------+---------+---------------------+
144-
| 1 | kevin | 18 | shenzhen | 500 | 2023-07-03 12:00:01 |
145-
| 3 | NULL | NULL | NULL | 23 | 2023-07-03 12:00:02 |
146-
| 18 | NULL | NULL | NULL | 9999999 | 2023-07-03 12:00:03 |
147-
+------+-------+------+----------+---------+---------------------+
148-
```
149-
15080
### 开启严格模式
15181
严格模式（strict_mode）默认为 False，以下是各种导入方式的设置方法：
15282

‎i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/stream-load-manual.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1036,7 +1036,7 @@ Doris 可以在导入语句中支持非常丰富的列转换和过滤操作。
10361036

10371037
### 启用严格模式导入
10381038

1039-
`strict_mode` 属性用于设置导入任务是否运行在严格模式下。该属性会对列映射、转换和过滤的结果产生影响，它同时也将控制部分列更新的行为。关于严格模式的具体说明，可参阅 [严格模式](../handling-messy-data#严格模式) 文档。
1039+
`strict_mode` 属性用于设置导入任务是否运行在严格模式下。该属性会对列映射、转换和过滤的结果产生影响。关于严格模式的具体说明，可参阅 [严格模式](../handling-messy-data#严格模式) 文档。
10401040

10411041
### 导入时进行部分列更新/灵活部分列更新
10421042

‎i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/import/handling-messy-data.md

Lines changed: 1 addition & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,7 @@ under the License.
3333

3434
## 严格模式
3535

36-
严格模式具有两个主要功能：
37-
1. 对导入过程中发生列类型转换失败的数据行进行过滤。
38-
2. 在部分列更新场景中，限制只能更新已存在的列。
36+
严格模式的主要功能是对导入过程中发生列类型转换失败的数据行进行过滤。
3937

4038
### 列类型转换失败的过滤策略
4139

@@ -79,74 +77,6 @@ under the License.
7977
3. `10` 虽然是一个超过范围的值，但是因为其类型符合 decimal 的要求，所以严格模式对其不产生影响。
8078
:::
8179

82-
83-
### 限定部分列更新只能更新已有的列
84-
85-
在严格模式下，部分列更新插入的每一行数据必须满足该行数据的 Key 在表中已经存在。而在非严格模式下，进行部分列更新时可以更新 Key 已经存在的行，也可以插入 Key 不存在的新行。
86-
87-
例如有表结构如下：
88-
```sql
89-
CREATE TABLE user_profile
90-
(
91-
id INT,
92-
name VARCHAR(10),
93-
age INT,
94-
city VARCHAR(10),
95-
balance DECIMAL(9, 0),
96-
last_access_time DATETIME
97-
) ENGINE=OLAP
98-
UNIQUE KEY(id)
99-
DISTRIBUTED BY HASH(id) BUCKETS 1
100-
PROPERTIES (
101-
"enable_unique_key_merge_on_write" = "true"
102-
);
103-
```
104-
105-
表中有一条数据如下：
106-
```sql
107-
mysql> select * from user_profile;
108-
+------+-------+------+----------+---------+---------------------+
109-
| id | name | age | city | balance | last_access_time |
110-
+------+-------+------+----------+---------+---------------------+
111-
| 1 | kevin | 18 | shenzhen | 400 | 2023-07-01 12:00:00|
112-
+------+-------+------+----------+---------+---------------------+
113-
```
114-
115-
当用户使用严格模式的 Insert Into 部分列更新向表中插入上述数据时，由于开启了严格模式且第二、三行的数据的 key(`(3)`, `(18)`) 不在原表中，所以本次插入会失败：
116-
```sql
117-
SET enable_unique_key_partial_update=true;
118-
SET enable_insert_strict = true;
119-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
120-
(1, 500, '2023-07-03 12:00:01'),
121-
(3, 23, '2023-07-03 12:00:02'),
122-
(18, 9999999, '2023-07-03 12:00:03');
123-
ERROR 1105 (HY000): errCode = 2, detailMessage = Insert has filtered data in strict mode
124-
```
125-
126-
当用户使用非严格模式的 Insert Into 部分列更新向表中插入如下数据时：
127-
```sql
128-
SET enable_unique_key_partial_update=true;
129-
SET enable_insert_strict = false;
130-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
131-
(1, 500, '2023-07-03 12:00:01'),
132-
(3, 23, '2023-07-03 12:00:02'),
133-
(18, 9999999, '2023-07-03 12:00:03');
134-
```
135-
136-
表中原有的一条数据将会被更新，此外还向表中插入了两条新数据。对于插入的数据中用户没有指定的列，如果该列有默认值，则会以默认值填充；否则，如果该列可以为 NULL，则将以 NULL 值填充；否则本次插入不成功。
137-
138-
查询结果如下：
139-
```sql
140-
mysql> select * from user_profile;
141-
+------+-------+------+----------+---------+---------------------+
142-
| id | name | age | city | balance | last_access_time |
143-
+------+-------+------+----------+---------+---------------------+
144-
| 1 | kevin | 18 | shenzhen | 500 | 2023-07-03 12:00:01 |
145-
| 3 | NULL | NULL | NULL | 23 | 2023-07-03 12:00:02 |
146-
| 18 | NULL | NULL | NULL | 9999999 | 2023-07-03 12:00:03 |
147-
+------+-------+------+----------+---------+---------------------+
148-
```
149-
15080
### 开启严格模式
15181
严格模式（strict_mode）默认为 False，以下是各种导入方式的设置方法：
15282

‎i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/import/import-way/stream-load-manual.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1014,7 +1014,7 @@ Doris 可以在导入语句中支持非常丰富的列转换和过滤操作。
10141014

10151015
### 启用严格模式导入
10161016

1017-
`strict_mode` 属性用于设置导入任务是否运行在严格模式下。该属性会对列映射、转换和过滤的结果产生影响，它同时也将控制部分列更新的行为。关于严格模式的具体说明，可参阅 [严格模式](../handling-messy-data#严格模式) 文档。
1017+
`strict_mode` 属性用于设置导入任务是否运行在严格模式下。该属性会对列映射、转换和过滤的结果产生影响。关于严格模式的具体说明，可参阅 [严格模式](../handling-messy-data#严格模式) 文档。
10181018

10191019
### 导入时进行部分列更新/灵活部分列更新
10201020

‎versioned_docs/version-3.0/data-operate/import/handling-messy-data.md

Lines changed: 1 addition & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,7 @@ This makes it easier to handle data loading problems and keeps data management s
3636

3737
## Strict Mode
3838

39-
Strict mode serves two primary purposes:
40-
1. Filtering out data rows where column type conversion fails during load
41-
2. Restricting updates to existing columns only in partial column update scenarios
39+
The main function of strict mode is to filter out data rows where column type conversion fails during load.
4240

4341
### Filtering Strategy for Column Type Conversion Failures
4442

@@ -82,73 +80,6 @@ The system employs different strategies based on the strict mode setting:
8280
3. Although `10` exceeds the range, since its type meets decimal requirements, strict mode does not affect it.
8381
:::
8482

85-
### Restricting Partial Column Updates to Existing Columns Only
86-
87-
In strict mode, each row in a partial column update must have its Key already exist in the table. In non-strict mode, partial column updates can both update existing rows (where Key exists) and insert new rows (where Key doesn't exist).
88-
89-
For example, given a table structure as follows:
90-
```sql
91-
CREATE TABLE user_profile
92-
(
93-
id INT,
94-
name VARCHAR(10),
95-
age INT,
96-
city VARCHAR(10),
97-
balance DECIMAL(9, 0),
98-
last_access_time DATETIME
99-
) ENGINE=OLAP
100-
UNIQUE KEY(id)
101-
DISTRIBUTED BY HASH(id) BUCKETS 1
102-
PROPERTIES (
103-
"enable_unique_key_merge_on_write" = "true"
104-
);
105-
```
106-
107-
The table contains one record as follows:
108-
```sql
109-
mysql> select * from user_profile;
110-
+------+-------+------+----------+---------+---------------------+
111-
| id | name | age | city | balance | last_access_time |
112-
+------+-------+------+----------+---------+---------------------+
113-
| 1 | kevin | 18 | shenzhen | 400 | 2023-07-01 12:00:00|
114-
+------+-------+------+----------+---------+---------------------+
115-
```
116-
117-
When using Insert Into with strict mode to perform partial column updates, the insertion will fail because the second and third rows with keys `(3)` and `(18)` do not exist in the original table:
118-
```sql
119-
SET enable_unique_key_partial_update=true;
120-
SET enable_insert_strict = true;
121-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
122-
(1, 500, '2023-07-03 12:00:01'),
123-
(3, 23, '2023-07-03 12:00:02'),
124-
(18, 9999999, '2023-07-03 12:00:03');
125-
ERROR 1105 (HY000): errCode = 2, detailMessage = Insert has filtered data in strict mode
126-
```
127-
128-
When using Insert Into with non-strict mode to perform partial column updates:
129-
```sql
130-
SET enable_unique_key_partial_update=true;
131-
SET enable_insert_strict = false;
132-
INSERT INTO user_profile (id, balance, last_access_time) VALUES
133-
(1, 500, '2023-07-03 12:00:01'),
134-
(3, 23, '2023-07-03 12:00:02'),
135-
(18, 9999999, '2023-07-03 12:00:03');
136-
```
137-
138-
The existing record will be updated, and two new records will be inserted. For columns not specified in the insert statement, if a default value is defined, it will be used; if the column allows NULL values, NULL will be used; otherwise, the insertion will fail.
139-
140-
The query result is as follows:
141-
```sql
142-
mysql> select * from user_profile;
143-
+------+-------+------+----------+---------+---------------------+
144-
| id | name | age | city | balance | last_access_time |
145-
+------+-------+------+----------+---------+---------------------+
146-
| 1 | kevin | 18 | shenzhen | 500 | 2023-07-03 12:00:01 |
147-
| 3 | NULL | NULL | NULL | 23 | 2023-07-03 12:00:02 |
148-
| 18 | NULL | NULL | NULL | 9999999 | 2023-07-03 12:00:03 |
149-
+------+-------+------+----------+---------+---------------------+
150-
```
151-
15283
### Enable Strict Mode
15384

15485
Strict mode (strict_mode) defaults to False. Here's how to set it for different load methods:

‎versioned_docs/version-3.0/data-operate/import/import-way/stream-load-manual.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1008,7 +1008,7 @@ Doris supports a very rich set of column transformations and filtering operation
10081008

10091009
### Enable strict mode import
10101010

1011-
The strict_mode attribute is used to set whether the import task runs in strict mode. This attribute affects the results of column mapping, transformation, and filtering, and it also controls the behavior of partial column updates. For specific instructions on strict mode, please refer to the [Handling Messy Data](../../../data-operate/import/handling-messy-data) documentation.
1011+
The strict_mode attribute is used to set whether the import task runs in strict mode. This attribute affects the results of column mapping, transformation, and filtering. For specific instructions on strict mode, please refer to the [Handling Messy Data](../../../data-operate/import/handling-messy-data) documentation.
10121012

10131013
### Perform partial column updates/flexible partial update during import
10141014

0 commit comments

Comments
 (0)