This is an automated email from the ASF dual-hosted git repository.
wangbo 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 95527860df88 Add workload schedule policy document (#538)
95527860df88 is described below
commit 95527860df885308b1a7cd4aafb578bb19c0b41a
Author: wangbo <youseebiggirl_...@qq.com>
AuthorDate: Thu Apr 11 10:04:29 2024 +0800
Add workload schedule policy document (#538)
---
.../{ => workload-management}/workload-group.md | 0
.../workload-schedule-policy.md | 178 +++++++++++++++++++++
.../Create/CREATE-ASYNC-MATERIALIZED-VIEW.md | 2 +-
.../{ => workload-management}/workload-group.md | 0
.../workload-schedule-policy.md | 178 +++++++++++++++++++++
.../Create/CREATE-ASYNC-MATERIALIZED-VIEW.md | 2 +-
sidebars.json | 3 +-
7 files changed, 360 insertions(+), 3 deletions(-)
diff --git a/docs/admin-manual/workload-group.md
b/docs/admin-manual/workload-management/workload-group.md
similarity index 100%
rename from docs/admin-manual/workload-group.md
rename to docs/admin-manual/workload-management/workload-group.md
diff --git a/docs/admin-manual/workload-management/workload-schedule-policy.md
b/docs/admin-manual/workload-management/workload-schedule-policy.md
new file mode 100644
index 000000000000..93990223c04b
--- /dev/null
+++ b/docs/admin-manual/workload-management/workload-schedule-policy.md
@@ -0,0 +1,178 @@
+---
+{
+"title": "WORKLOAD SCHEDULE POLICY",
+"language": "zh-CN"
+}
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# WORKLOAD SCHEDULE POLICY
+
+<version since="dev"></version>
+
+## Backgroup
+The Workload Group solves the problem of isolation between different workload,
but it cannot solve negative impact of large queries on stability within the
same Group. When users encounter large queries that affect cluster stability,
they can only manually handle them.
+
+Therefore, Doris has implemented Workload Schedule Policy, which supports the
automation of query load management, such as automatically canceling queries
with running time exceeding 5 seconds.
+
+## Basic Concepts
+Provide an example of Workload Schedule Policy
+```
+create workload schedule policy test_cancel_policy
+conditions(query_time > 1000)
+actions(cancel_query)
+properties('enabled'='true');
+```
+Workload Schedule Policy mainly includes the following concepts:
+* policy，user-defined policies，Contains conditions for triggering policies and
actions after triggering policies.
+* conditions，represents the triggering conditions of the policy.A policy can
have multiple conditions, and there is an AND relationship between multiple
conditions.
+* actions，the action works when a policy is triggered, such as canceling a
query, currently only a policy can only have one action (except for
set_session_variable).
+* properties，defined the properties of the current policy, including whether
it is enabled and its priority.
+
+The meaning of the policy in the above example is to create a policy named
test_cancel_policy, which will cancel queries in the cluster that have been
running for more than 1 second, and it's enabled.
+
+## Basic Usage
+Due to the fact that some actions can only take effect in FE and others can
only take effect in BE, so the policy also needs to be distinguished between
the policy of FE and the policy of BE.
+
+### Policy used in FE
+#### Condition
+* username，When the username of a query is a certain value, the corresponding
action will be triggered.
+#### Action
+* set_session_variable，This action can execute a statement that sets session
variable. The same policy can have multiple set_session_variables, which means
that a policy can execute multiple statements that modify the session variable.
+
+The policy used in FE is mainly used to modify the session variable, and
currently does not support the ```set global```.
+
+### Policy used in BE
+#### Condition
+* be_scan_rows，The number of rows scanned by an SQL within a single BE
process, and if there are multiple concurrency, it is the cumulative value of
multiple concurrency.
+* be_scan_bytes，The number of bytes scanned by an SQL within a single BE
process, and if there are multiple concurrency, it is the cumulative value of
multiple concurrency.
+* query_time，The running time of an SQL on a single BE process, measured in
milliseconds.
+
+#### Action
+* cancel_query，cancel query
+
+At present, BE's policy is mainly used for managing BE workload, such as
canceling a query when the scan data volume is too large or the query time is
too long.
+
+### Properties
+* enabled，the value is either true or false. The default value is true,
indicating that the current policy is enabled, while false indicates that the
current policy is disabled.
+* priority，the value range is a positive integer from 0 to 100, with a default
value of 0. The higher the value, the higher the priority of the policy. The
main function of this attribute is to select the policy with the highest
priority when multiple policies are matched.
+
+### Attention
+1 Conditions and actions of the same policy are either used in FE or used in
BE at the same time, for example, set_session_variable and cancel_query cannot
be configured into the same policy. Condition be_scan_rows and condition
username cannot be configured into the same policy.
+
+2 Due to the current policy being executed by asynchronous threads at fixed
time intervals, there is a certain lag in the effectiveness of the policy. For
example, if a user has configured a strategy of canceling queries when the
number of scan rows exceeds one million, and the cluster resources are
relatively idle at this time, it is possible that the query may have ended
before the cancel policy takes effect. At present, the time interval is 500ms,
which means that queries with too sho [...]
+
+3 The currently supported workload types include select/insert select/stream
load/broker load/route load.
+
+4 A query may match multiple policies, but only the policy with the highest
priority will take effect.
+
+5 At present, it does not support modifying actions and conditions, and can
only be modified by deleting and creating new ones.
+
+## Example
+1 Change the workload group in all session variables with the username admin
to normal.
+```
+create workload schedule policy test_set_var_policy
+conditions(username='admin')
+actions(set_session_variable 'workload_group=normal')
+```
+
+2 Cancel SQL with scan rows greater than 1000 on a single BE.
+```
+create workload schedule policy test_cancel_query
+conditions(be_scan_rows > 1000)
+actions(cancel_query)
+```
+
+3 Cancel all SQL with scan bytes greater than 5GB and running time exceeding
1s.
+```
+create workload schedule policy test_cancel_big_query
+conditions(query_time > 1000, be_scan_bytes > 5368709120)
+actions(cancel_query)
+```
+
+4 Alter properties.
+```
+alter workload schedule policy test_cancel_big_query
properties('enabled'='false');
+```
+
+5 show all workload schedule policy.
+```
+mysql [(none)]>show workload schedule policy;
++-------+----------------------+-------------------+--------------+----------+---------+---------+
+| Id | Name | Condition | Action | Priority |
Enabled | Version |
++-------+----------------------+-------------------+--------------+----------+---------+---------+
+| 41057 | test_cancel_3s_query | query_time > 3000 | cancel_query | 0 |
true | 0 |
++-------+----------------------+-------------------+--------------+----------+---------+---------+
+1 row in set (0.00 sec)
+```
+
+## Test
+#### 1 set session variables
+Attempt to modify concurrency related parameters in the session variable of
the admin user.
+```
+// show variable parallel_fragment_exec_instance_num of admin user.
+mysql [(none)]>show variables like '%parallel_fragment_exec_instance_num%';
++-------------------------------------+-------+---------------+---------+
+| Variable_name | Value | Default_Value | Changed |
++-------------------------------------+-------+---------------+---------+
+| parallel_fragment_exec_instance_num | 8 | 8 | 0 |
++-------------------------------------+-------+---------------+---------+
+1 row in set (0.00 sec)
+
+// create a policy which reset session variable.
+create workload schedule policy test_set_var_policy
+conditions(username='admin')
+actions(set_session_variable 'parallel_fragment_exec_instance_num=1')
+
+
+// After a while, check the session variable of the admin.
+mysql [(none)]>show variables like '%parallel_fragment_exec_instance_num%';
++-------------------------------------+-------+---------------+---------+
+| Variable_name | Value | Default_Value | Changed |
++-------------------------------------+-------+---------------+---------+
+| parallel_fragment_exec_instance_num | 1 | 8 | 1 |
++-------------------------------------+-------+---------------+---------+
+1 row in set (0.01 sec)
+```
+
+#### 2 big query fusing test
+Test fusing queries that have run for more than 3 seconds. The following is
the audit log of a successful execution of q29 in Clickbench. It can be seen
that it takes 4.5 seconds for this SQL to run.
+```
+User=root|Ctl=internal|Db=hits|State=EOF|ErrorCode=0|ErrorMessage=|Time(ms)=4543|ScanBytes=15573090304|ScanRows=81032736|ReturnRows=11|StmtId=102|QueryId=391b02b55fdf4f59-becf6c17dfff1a65|IsQuery=true|isNereids=true|feIp=127.0.0.1|Stmt=SELECT
REGEXP_REPLACE(Referer, '^https?://(?:www\.)?([^/]+)/.*$', '\1') AS k,
AVG(length(Referer)) AS l, COUNT(*) AS c, MIN(Referer) FROM hits WHERE Referer
<> '' GROUP BY k HAVING COUNT(*) > 100000 ORDER BY l DESC LIMIT
25|CpuTimeMS=40454|ShuffleSendBytes [...]
+```
+
+Create a policy that cancels queries after running for more than 3 seconds
+```
+create workload schedule policy test_cancel_3s_query
+conditions(query_time > 3000)
+actions(cancel_query)
+```
+
+Executing SQL again will result in a direct error message.
+```
+mysql [hits]>SELECT REGEXP_REPLACE(Referer, '^https?://(?:www\.)?([^/]+)/.*$',
'\1') AS k, AVG(length(Referer)) AS l, COUNT(*) AS c, MIN(Referer) FROM hits
WHERE Referer <> '' GROUP BY k HAVING COUNT(*) > 100000 ORDER BY l DESC LIMIT
25;
+ERROR 1105 (HY000): errCode = 2, detailMessage = (10.16.10.8)[CANCELLED]query
canceled by workload scheduler
+```
+
+We can also find error message in fe.audit.log
+```
+Ctl=internal|Db=hits|State=ERR|ErrorCode=1105|ErrorMessage=errCode = 2,
detailMessage = (127.0.0.1)[CANCELLED]query canceled by workload
scheduler|Time(ms)=3118|ScanBytes=11013275648|ScanRows=59503712|ReturnRows=0|StmtId=107|QueryId=eee98eec821342a0-ac07ff18ea08026a|IsQuery=true|isNereids=true|feIp=10.16.10.8|Stmt=SELECT
REGEXP_REPLACE(Referer, '^https?://(?:www\.)?([^/]+)/.*$', '\1') AS k,
AVG(length(Referer)) AS l, COUNT(*) AS c, MIN(Referer) FROM hits WHERE Referer
<> '' GROUP BY k HA [...]
+```
\ No newline at end of file
diff --git
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
index 83ce5c02905a..1a7282d5c8ae 100644
---
a/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
+++
b/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
@@ -190,7 +190,7 @@ The properties unique to materialized views include:
`refresh_partition_num`: The number of partitions refreshed by a single insert
statement is set to 1 by default. When refreshing a materialized view, the
system first calculates the list of partitions to be refreshed and then splits
it into multiple insert statements that are executed in sequence according to
this configuration. If any insert statement fails, the entire task will stop
executing. The materialized view ensures the transactionality of individual
insert statements, meaning t [...]
-`workload_group`: The name of the workload_group used by the materialized view
when performing refresh tasks. This is used to limit the resources used for
refreshing data in the materialized view, in order to avoid affecting the
operation of other business processes. For details on how to create and use
workload_group, refer to
[WORKLOAD-GROUP](../../../../admin-manual/workload-group.md)
+`workload_group`: The name of the workload_group used by the materialized view
when performing refresh tasks. This is used to limit the resources used for
refreshing data in the materialized view, in order to avoid affecting the
operation of other business processes. For details on how to create and use
workload_group, refer to
[WORKLOAD-GROUP](../../../../admin-manual/workload-management/workload-group.md)
`partition_sync_limit`: When the partition field of the base table is time
(and if it's a string-type time, `partition_date_format` can be set), this
attribute can be used to configure the partition range for synchronizing the
base table. It works in conjunction with `partition_sync_time_unit`.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-group.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/workload-group.md
similarity index 100%
rename from
i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-group.md
rename to
i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/workload-group.md
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/workload-schedule-policy.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/workload-schedule-policy.md
new file mode 100644
index 000000000000..4e33f01fb4c7
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/workload-schedule-policy.md
@@ -0,0 +1,178 @@
+---
+{
+"title": "WORKLOAD SCHEDULE POLICY",
+"language": "zh-CN"
+}
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# WORKLOAD SCHEDULE POLICY
+
+<version since="dev"></version>
+
+## 功能背景
+Workload Group功能解决了不同负载间的隔离问题，但无法解决同一个Group内的大查询熔断的问题， 用户遇到大查询影响集群稳定性时只能手动处理。
+
+因此Doris实现了Workload Schedule
Policy的功能，支持查询负载管理的自动化，比如实现自动cancel运行时间超过5s的查询这样的功能。
+
+## 基础概念
+给出一个创建Workload Schedule Policy的语法
+```
+create workload schedule policy test_cancel_policy
+conditions(query_time > 1000)
+actions(cancel_query)
+properties('enabled'='true');
+```
+Workload Scheduler Policy主要包含以下几个概念：
+* policy，代表了用户定义的策略，包含触发策略的条件(conditions)和触发策略后的动作(actions)。
+*
conditions，代表了策略的触发条件，比如当查询时间大于3s，就触发当前policy的action。一个policy可以有多个condition，多个condition之间是“与”的关系。
+* actions，当policy被触发时所采取的动作，比如可以cancel
query，目前一个policy只能定义一个action(除了set_session_variable)。
+* properties，定义了当前policy的属性，包括是否启用和优先级。
+
+上面例子中policy的含义是，创建一个名为test_cancel_policy的policy，它会cancel掉集群中运行时间超过1s的查询，当前状态为启用。
+
+## 基本用法
+由于action的行为有的只能在FE生效，有的只能在BE生效，因此policy本身也有FE和BE的区别。
+
+### 适用于FE的policy
+#### Condition
+* username，当一个查询的username为某个值时，就会触发相应的action
+#### Action
+* set_session_variable，这个action可以执行一条set session
variable的语句。同一个policy可以有多个set_session_variable，也就是说一个policy可以执行多个修改session变量的语句。
+
+适用于FE的policy主要是用于修改某个user的session变量，目前不支持set global的用法。
+
+### 适用于BE的policy
+#### Condition
+* be_scan_rows，一个sql在单个BE进程内scan的行数，如果有多个并发那就是多个并发的累加值。
+* be_scan_bytes，一个sql在单个BE进程内scan的字节数，如果有多个并发那么就是多个并发的累加值。
+* query_time，一个sql在单个BE进程上的运行时间，时间单位是毫秒。
+
+#### Action
+* cancel_query，cancel查询。
+
+目前BE的policy主要是用于BE负载的管理，比如当某个query的scan数据量过大或者查询时间过长，就cancel这个query。
+
+### 属性
+* enabled，取值为true或false，默认值为true，表示当前policy处于启用状态，false表示当前policy处于禁用状态。
+*
priority，取值范围为0到100的正整数，默认值为0，代表policy的优先级，该值越大，优先级越高。这个属性的主要作用是，当匹配到多个policy时，选择优先级最高的policy。
+
+### 注意事项
+1
同一个policy的condition和action要么都是FE的，要么都是BE的，比如set_session_variable和cancel_query无法配置到同一个policy中。condition
be_scan_rows和condition username无法配置到同一个policy中。
+
+2
由于目前的policy是异步线程以固定时间间隔执行的，因此策略的生效存在一定的滞后性。比如用户配置了scan行数大于100万就cancel查询的策略，如果此时集群资源比较空闲，那么有可能在cancel策略生效之前查询就已经结束了。目前这个时间间隔为500ms，这意味着运行时间过短的查询可能会绕过策略的检查。
+
+3 当前支持的负载类型包括select/insert select/stream load/broker load/routine load。
+
+4 一个查询可能匹配到多个policy，但是只有优先级最高的policy会生效。
+
+5 目前不支持action和condition的修改，只能通过删除新建的方式修改。
+
+## 常见用法
+1 将用户名为admin的所有session变量中的workload group修改为normal
+```
+create workload schedule policy test_set_var_policy
+conditions(username='admin')
+actions(set_session_variable 'workload_group=normal')
+```
+
+2 cancel所有单个be上scan行数大于1000行的sql
+```
+create workload schedule policy test_cancel_query
+conditions(be_scan_rows > 1000)
+actions(cancel_query)
+```
+
+3 cancel所有scan字节数大于5G且运行时间超过1s的sql
+```
+create workload schedule policy test_cancel_big_query
+conditions(query_time > 1000, be_scan_bytes > 5368709120)
+actions(cancel_query)
+```
+
+4 修改属性
+```
+alter workload schedule policy test_cancel_big_query
properties('enabled'='false');
+```
+
+5 查看已创建的policy
+```
+mysql [(none)]>show workload schedule policy;
++-------+----------------------+-------------------+--------------+----------+---------+---------+
+| Id | Name | Condition | Action | Priority |
Enabled | Version |
++-------+----------------------+-------------------+--------------+----------+---------+---------+
+| 41057 | test_cancel_3s_query | query_time > 3000 | cancel_query | 0 |
true | 0 |
++-------+----------------------+-------------------+--------------+----------+---------+---------+
+1 row in set (0.00 sec)
+```
+
+## 效果测试
+#### 1 session变量修改测试
+尝试修改admin账户的session变量中的并发相关的参数
+```
+// 登录 admin账户查看并发参数
+mysql [(none)]>show variables like '%parallel_fragment_exec_instance_num%';
++-------------------------------------+-------+---------------+---------+
+| Variable_name | Value | Default_Value | Changed |
++-------------------------------------+-------+---------------+---------+
+| parallel_fragment_exec_instance_num | 8 | 8 | 0 |
++-------------------------------------+-------+---------------+---------+
+1 row in set (0.00 sec)
+
+// 创建修改admin账户并发参数的policy
+create workload schedule policy test_set_var_policy
+conditions(username='admin')
+actions(set_session_variable 'parallel_fragment_exec_instance_num=1')
+
+
+// 过段时间后再次查看admin账户的参数
+mysql [(none)]>show variables like '%parallel_fragment_exec_instance_num%';
++-------------------------------------+-------+---------------+---------+
+| Variable_name | Value | Default_Value | Changed |
++-------------------------------------+-------+---------------+---------+
+| parallel_fragment_exec_instance_num | 1 | 8 | 1 |
++-------------------------------------+-------+---------------+---------+
+1 row in set (0.01 sec)
+```
+
+#### 2 大查询熔断测试
+测试对运行时间超过3s的查询进行熔断，以下是一个ckbench的q29运行成功时的审计日志，可以看到这个sql跑完需要4.5s的时间
+```
+User=root|Ctl=internal|Db=hits|State=EOF|ErrorCode=0|ErrorMessage=|Time(ms)=4543|ScanBytes=15573090304|ScanRows=81032736|ReturnRows=11|StmtId=102|QueryId=391b02b55fdf4f59-becf6c17dfff1a65|IsQuery=true|isNereids=true|feIp=127.0.0.1|Stmt=SELECT
REGEXP_REPLACE(Referer, '^https?://(?:www\.)?([^/]+)/.*$', '\1') AS k,
AVG(length(Referer)) AS l, COUNT(*) AS c, MIN(Referer) FROM hits WHERE Referer
<> '' GROUP BY k HAVING COUNT(*) > 100000 ORDER BY l DESC LIMIT
25|CpuTimeMS=40454|ShuffleSendBytes [...]
+```
+
+创建一个运行时间超过3s就cancel查询的policy
+```
+create workload schedule policy test_cancel_3s_query
+conditions(query_time > 3000)
+actions(cancel_query)
+```
+
+再次执行sql可以看到SQL执行会直接报错
+```
+mysql [hits]>SELECT REGEXP_REPLACE(Referer, '^https?://(?:www\.)?([^/]+)/.*$',
'\1') AS k, AVG(length(Referer)) AS l, COUNT(*) AS c, MIN(Referer) FROM hits
WHERE Referer <> '' GROUP BY k HAVING COUNT(*) > 100000 ORDER BY l DESC LIMIT
25;
+ERROR 1105 (HY000): errCode = 2, detailMessage = (10.16.10.8)[CANCELLED]query
canceled by workload scheduler
+```
+
+审计日志中也会有相关报错
+```
+Ctl=internal|Db=hits|State=ERR|ErrorCode=1105|ErrorMessage=errCode = 2,
detailMessage = (127.0.0.1)[CANCELLED]query canceled by workload
scheduler|Time(ms)=3118|ScanBytes=11013275648|ScanRows=59503712|ReturnRows=0|StmtId=107|QueryId=eee98eec821342a0-ac07ff18ea08026a|IsQuery=true|isNereids=true|feIp=10.16.10.8|Stmt=SELECT
REGEXP_REPLACE(Referer, '^https?://(?:www\.)?([^/]+)/.*$', '\1') AS k,
AVG(length(Referer)) AS l, COUNT(*) AS c, MIN(Referer) FROM hits WHERE Referer
<> '' GROUP BY k HA [...]
+```
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
index f9f2ba2a896f..f00c53848158 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md
@@ -190,7 +190,7 @@ KEY(k1,k2)
`refresh_partition_num`：单次insert语句刷新的分区数量，默认为1。物化视图刷新时会先计算要刷新的分区列表，然后根据该配置拆分成多个insert语句顺序执行。遇到失败的insert语句，整个任务将停止执行。物化视图保证单个insert语句的事务性，失败的insert语句不会影响到已经刷新成功的分区。
-`workload_group`：物化视图执行刷新任务时使用的workload_group名称。用来限制物化视图刷新数据使用的资源，避免影响到其它业务的运行。workload_group创建及使用
[WORKLOAD-GROUP](../../../../admin-manual/workload-group.md)
+`workload_group`：物化视图执行刷新任务时使用的workload_group名称。用来限制物化视图刷新数据使用的资源，避免影响到其它业务的运行。workload_group创建及使用
[WORKLOAD-GROUP](../../../../admin-manual/workload-management/workload-group.md)
`partition_sync_limit`：当基表的分区字段为时间时（如果是字符串类型的时间，可以设置partition_date_format），可以用此属性配置同步基表的分区范围，配合`partition_sync_time_unit`一起使用。
例如设置为 2，`partition_sync_time_unit`设置为 MONTH，代表仅同步基表近2个月的分区和数据。最小值为1。
diff --git a/sidebars.json b/sidebars.json
index fbf25d1bdf6e..8e9f77b9b0b6 100644
--- a/sidebars.json
+++ b/sidebars.json
@@ -1347,7 +1347,8 @@
"admin-manual/system-table/rowsets"
]
},
- "admin-manual/workload-group",
+ "admin-manual/workload-management/workload-group",
+ "admin-manual/workload-management/workload-schedule-policy",
"admin-manual/multi-tenant",
{
"type": "category",
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
