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

yiguolei 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 bb9cfa3acab fix rg (#1618)
bb9cfa3acab is described below

commit bb9cfa3acab6e17c240773f2196ba19907e877b5
Author: yiguolei <[email protected]>
AuthorDate: Thu Dec 26 00:05:30 2024 +0800

    fix rg (#1618)
    
    ## Versions
    
    - [x] dev
    - [x] 3.0
    - [x] 2.1
    - [ ] 2.0
    
    ## Languages
    
    - [x] Chinese
    - [ ] English
    
    ## Docs Checklist
    
    - [ ] Checked by AI
    - [ ] Test Cases Built
    
    Co-authored-by: yiguolei <[email protected]>
---
 .../workload-management/resource-group.md          | 28 +++++++++++-----------
 .../workload-management/resource-group.md          | 28 +++++++++++-----------
 .../workload-management/resource-group.md          | 28 +++++++++++-----------
 3 files changed, 42 insertions(+), 42 deletions(-)

diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/resource-group.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/resource-group.md
index 8d87bca23ee..fbe0b529cc6 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/resource-group.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/workload-management/resource-group.md
@@ -123,22 +123,22 @@ Resource Group本质上是一种Table副本的放置策略,所以它有以下
 
    那么可以使用如下语句创建 db1:
 
-      ```sql
-      CREATE DATABASE db1 PROPERTIES (
-      "replication_allocation" = "tag.location.group_c:1, 
tag.location.group_b:2"
-      )
-      ```
+   ```sql
+   CREATE DATABASE db1 PROPERTIES (
+   "replication_allocation" = "tag.location.group_c:1, tag.location.group_b:2"
+   )
+   ```
 
    使用如下语句创建 table1:
 
-      ```sql
-      CREATE TABLE table1
-      (k1 int, k2 int)
-      distributed by hash(k1) buckets 1
-      properties(
-      "replication_allocation"="tag.location.group_a:1, tag.location.group_b:2"
-      )
-      ```
+   ```sql
+   CREATE TABLE table1
+   (k1 int, k2 int)
+   distributed by hash(k1) buckets 1
+   properties(
+   "replication_allocation"="tag.location.group_a:1, tag.location.group_b:2"
+   )
+   ```
 
    table2,table3,table4 的建表语句无需再指定`replication_allocation`。
 
@@ -175,5 +175,5 @@ Resource Group本质上是一种Table副本的放置策略,所以它有以下
    
    2. 写入资源:负责数据编码、压缩并写入磁盘。
 
-   其中写入资源必须是数据副本所在的节点,而计算资源理论上可以选择任意节点完成,所以在导入的场景下,Resource Group 
只能限制计算部分使用的资源。
+   由于写入资源必须是数据副本所在的节点,而计算资源可以选择任意节点完成,所以在导入的场景下,Resource Group 只能限制计算部分使用的资源。
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/workload-management/resource-group.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/workload-management/resource-group.md
index 8d87bca23ee..fbe0b529cc6 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/workload-management/resource-group.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/workload-management/resource-group.md
@@ -123,22 +123,22 @@ Resource Group本质上是一种Table副本的放置策略,所以它有以下
 
    那么可以使用如下语句创建 db1:
 
-      ```sql
-      CREATE DATABASE db1 PROPERTIES (
-      "replication_allocation" = "tag.location.group_c:1, 
tag.location.group_b:2"
-      )
-      ```
+   ```sql
+   CREATE DATABASE db1 PROPERTIES (
+   "replication_allocation" = "tag.location.group_c:1, tag.location.group_b:2"
+   )
+   ```
 
    使用如下语句创建 table1:
 
-      ```sql
-      CREATE TABLE table1
-      (k1 int, k2 int)
-      distributed by hash(k1) buckets 1
-      properties(
-      "replication_allocation"="tag.location.group_a:1, tag.location.group_b:2"
-      )
-      ```
+   ```sql
+   CREATE TABLE table1
+   (k1 int, k2 int)
+   distributed by hash(k1) buckets 1
+   properties(
+   "replication_allocation"="tag.location.group_a:1, tag.location.group_b:2"
+   )
+   ```
 
    table2,table3,table4 的建表语句无需再指定`replication_allocation`。
 
@@ -175,5 +175,5 @@ Resource Group本质上是一种Table副本的放置策略,所以它有以下
    
    2. 写入资源:负责数据编码、压缩并写入磁盘。
 
-   其中写入资源必须是数据副本所在的节点,而计算资源理论上可以选择任意节点完成,所以在导入的场景下,Resource Group 
只能限制计算部分使用的资源。
+   由于写入资源必须是数据副本所在的节点,而计算资源可以选择任意节点完成,所以在导入的场景下,Resource Group 只能限制计算部分使用的资源。
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/admin-manual/workload-management/resource-group.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/admin-manual/workload-management/resource-group.md
index 8d87bca23ee..fbe0b529cc6 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/admin-manual/workload-management/resource-group.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/admin-manual/workload-management/resource-group.md
@@ -123,22 +123,22 @@ Resource Group本质上是一种Table副本的放置策略,所以它有以下
 
    那么可以使用如下语句创建 db1:
 
-      ```sql
-      CREATE DATABASE db1 PROPERTIES (
-      "replication_allocation" = "tag.location.group_c:1, 
tag.location.group_b:2"
-      )
-      ```
+   ```sql
+   CREATE DATABASE db1 PROPERTIES (
+   "replication_allocation" = "tag.location.group_c:1, tag.location.group_b:2"
+   )
+   ```
 
    使用如下语句创建 table1:
 
-      ```sql
-      CREATE TABLE table1
-      (k1 int, k2 int)
-      distributed by hash(k1) buckets 1
-      properties(
-      "replication_allocation"="tag.location.group_a:1, tag.location.group_b:2"
-      )
-      ```
+   ```sql
+   CREATE TABLE table1
+   (k1 int, k2 int)
+   distributed by hash(k1) buckets 1
+   properties(
+   "replication_allocation"="tag.location.group_a:1, tag.location.group_b:2"
+   )
+   ```
 
    table2,table3,table4 的建表语句无需再指定`replication_allocation`。
 
@@ -175,5 +175,5 @@ Resource Group本质上是一种Table副本的放置策略,所以它有以下
    
    2. 写入资源:负责数据编码、压缩并写入磁盘。
 
-   其中写入资源必须是数据副本所在的节点,而计算资源理论上可以选择任意节点完成,所以在导入的场景下,Resource Group 
只能限制计算部分使用的资源。
+   由于写入资源必须是数据副本所在的节点,而计算资源可以选择任意节点完成,所以在导入的场景下,Resource Group 只能限制计算部分使用的资源。
 


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

Reply via email to