This is an automated email from the ASF dual-hosted git repository.
jiafengzheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-doris.git
The following commit(s) were added to refs/heads/master by this push:
new 8d0f06e49a [docs][typo] Fixed Chinese and English "advance-usage.md"
files. (#9099)
8d0f06e49a is described below
commit 8d0f06e49ab26aa8ba87518af853a43123ceecb4
Author: liuzhuang2017 <[email protected]>
AuthorDate: Wed Apr 20 14:14:39 2022 +0800
[docs][typo] Fixed Chinese and English "advance-usage.md" files. (#9099)
Fixed Chinese and English "advance-usage.md" files
---
docs/en/getting-started/advance-usage.md | 10 +++++-----
docs/zh-CN/getting-started/advance-usage.md | 14 +++++++-------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/docs/en/getting-started/advance-usage.md
b/docs/en/getting-started/advance-usage.md
index cfaa54dffe..3a47a2f7db 100644
--- a/docs/en/getting-started/advance-usage.md
+++ b/docs/en/getting-started/advance-usage.md
@@ -82,11 +82,11 @@ The following command can be used to cancel the job
currently being executed:
`CANCEL ALTER TABLE COLUMN FROM table1`
-For more help, see `HELP ALTER TABLE'.
+For more help, see `HELP ALTER TABLE`.
## 2 Rollup
-Rollup can be understood as a materialized index structure of Table. **
materialized ** because data is store as a concrete ("materialized") table
independently, and ** indexing ** means that Rollup can adjust column order to
increase the hit rate of prefix index, or reduce key column to increase data
aggregation.
+Rollup can be understood as a materialized index structure of Table.
**materialized** because data is store as a concrete ("materialized") table
independently, and **indexing** means that Rollup can adjust column order to
increase the hit rate of prefix index, or reduce key column to increase data
aggregation.
Examples are given below.
@@ -137,7 +137,7 @@ The following command can be used to cancel the job
currently being executed:
`CANCEL ALTER TABLE ROLLUP FROM table1;`
-After Rollup is established, the query does not need to specify Rollup to
query. Or specify the original table for query. The program automatically
determines whether Rollup should be used. Whether Rollup is hit or not can be
viewed by the `EXPLAIN your_sql;'command.
+After Rollup is established, the query does not need to specify Rollup to
query. Or specify the original table for query. The program automatically
determines whether Rollup should be used. Whether Rollup is hit or not can be
viewed by the `EXPLAIN your_sql;`.
For more help, see `HELP ALTER TABLE`.
@@ -215,9 +215,9 @@ Shuffle join: tables in both side are Hash according to
Join's key, and then dis
Broadcast join is perfermance better when right hand table size is really
small, vice versa.
-Doris will try to use Broadcast Join first. You can specify how each join
operator is implemented explicitly. System provides configurable parameter
`auto_broadcast_join_threshold` to configure the maximum percentage of execute
memory could used for build hash table for broadcast join. The meaningful
values range from 0 to 1, and the default value is 0.8. System will use shuffle
join when broadcast join used memory more than it.
+Doris will try to use Broadcast Join first. You can specify how each join
operator is implemented explicitly. System provides configurable parameter
`auto_broadcast_join_threshold` to configure the maximum percentage of execute
memory could used for build hash table for broadcast join. The meaningful
values range from `0` to `1`, and the default value is `0.8`. System will use
shuffle join when broadcast join used memory more than it.
-You can turn off broadcast join by set `auto_broadcast_join_threshold` to
negative or zero.
+You can turn off broadcast join by set `auto_broadcast_join_threshold` to
negative or `0`.
Choose join implementation automaticaly (default):
diff --git a/docs/zh-CN/getting-started/advance-usage.md
b/docs/zh-CN/getting-started/advance-usage.md
index 8be1eb5ee2..c7395e64b3 100644
--- a/docs/zh-CN/getting-started/advance-usage.md
+++ b/docs/zh-CN/getting-started/advance-usage.md
@@ -151,7 +151,7 @@ Rollup 建立之后，查询不需要指定 Rollup 进行查询。还是指定
遇到内存超限时，用户应该尽量通过优化自己的 sql 语句来解决。
-如果确切发现2GB内存不能满足，可以手动设置内存参数。
+如果确切发现 2GB 内存不能满足，可以手动设置内存参数。
显示查询内存限制:
@@ -207,17 +207,17 @@ mysql> SHOW VARIABLES LIKE "%query_timeout%";
### 2.3 Broadcast/Shuffle Join
-系统提供了两种Join的实现方式，broadcast join和shuffle join（partitioned Join）。
+系统提供了两种 Join 的实现方式，broadcast join 和 shuffle join（partitioned Join）。
-broadcast join是指将小表进行条件过滤后，将其广播到大表所在的各个节点上，形成一个内存 Hash 表，然后流式读出大表的数据进行Hash
Join。
+broadcast join 是指将小表进行条件过滤后，将其广播到大表所在的各个节点上，形成一个内存 Hash 表，然后流式读出大表的数据进行 Hash
Join。
-shuffle join是指将小表和大表都按照 Join 的 key 进行 Hash，然后进行分布式的 Join。
+shuffle join 是指将小表和大表都按照 Join 的 key 进行 Hash，然后进行分布式的 Join。
-当小表的数据量较小时，broadcast join拥有更好的性能。反之，则shuffle join拥有更好的性能。
+当小表的数据量较小时，broadcast join 拥有更好的性能。反之，则 shuffle join 拥有更好的性能。
-系统会自动尝试进行 Broadcast
Join，也可以显式指定每个join算子的实现方式。系统提供了可配置的参数`auto_broadcast_join_threshold`，指定使用broadcast
join时，hash table使用的内存占整体执行内存比例的上限，取值范围为0到1，默认值为0.8。当系统计算hash
table使用的内存会超过此限制时，会自动转换为使用shuffle join。
+系统会自动尝试进行 Broadcast Join，也可以显式指定每个 join
算子的实现方式。系统提供了可配置的参数`auto_broadcast_join_threshold`，指定使用 broadcast join 时，hash
table 使用的内存占整体执行内存比例的上限，取值范围为 `0` 到 `1`，默认值为`0.8`。当系统计算 hash table
使用的内存会超过此限制时，会自动转换为使用 shuffle join。
-当`auto_broadcast_join_threshold`被设置为小于等于0时，所有的join都将使用shuffle join。
+当`auto_broadcast_join_threshold`被设置为小于等于`0`时，所有的 join 都将使用 shuffle join。
自动选择join方式（默认）:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
