You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by mo...@apache.org on 2026/01/26 04:32:15 UTC
(doris-website) branch master updated: (add)(maxcompute)add maxcompute note for Resource Usage Control. (#3293)
This is an automated email from the ASF dual-hosted git repository.
morningman 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 6b8243d6dca (add)(maxcompute)add maxcompute note for Resource Usage Control. (#3293)
6b8243d6dca is described below
commit 6b8243d6dcaad320f20e7aad6066ebdc2e546de8
Author: daidai <20...@qq.com>
AuthorDate: Mon Jan 26 12:32:09 2026 +0800
(add)(maxcompute)add maxcompute note for Resource Usage Control. (#3293)
## Versions
- [x] dev
- [x] 4.x
- [x] 3.x
- [x] 2.1
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
docs/lakehouse/catalogs/maxcompute-catalog.md | 13 ++++++++++++-
.../current/lakehouse/catalogs/maxcompute-catalog.md | 13 ++++++++++++-
.../version-2.1/lakehouse/catalogs/maxcompute-catalog.md | 13 ++++++++++++-
.../version-3.x/lakehouse/catalogs/maxcompute-catalog.md | 13 ++++++++++++-
.../version-4.x/lakehouse/catalogs/maxcompute-catalog.md | 12 +++++++++++-
.../version-2.1/lakehouse/catalogs/maxcompute-catalog.md | 13 ++++++++++++-
.../version-3.x/lakehouse/catalogs/maxcompute-catalog.md | 13 ++++++++++++-
.../version-4.x/lakehouse/catalogs/maxcompute-catalog.md | 13 ++++++++++++-
8 files changed, 95 insertions(+), 8 deletions(-)
diff --git a/docs/lakehouse/catalogs/maxcompute-catalog.md b/docs/lakehouse/catalogs/maxcompute-catalog.md
index 375cdb27d03..7c023530c1e 100644
--- a/docs/lakehouse/catalogs/maxcompute-catalog.md
+++ b/docs/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ Only the public cloud version of MaxCompute is supported. For support with the p
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -217,3 +217,14 @@ The generated endpoint formats are as follows:
Users can also manually specify `mc.odps_endpoint` and `mc.tunnel_endpoint` to customize the service addresses. This is particularly useful for private deployments of MaxCompute environments.
For details on configuring MaxCompute Endpoint and Tunnel Endpoint, refer to the documentation on [Endpoints for Different Regions and Network Connection Methods](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints).
+
+
+### Resource Usage Control
+
+Users can adjust the `parallel_pipeline_task_num` and `num_scanner_threads` session variables to control the [table-level request concurrency](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2) and manage resource consumption in the data transmission service. The corresponding concurrency equals `max(parallel_pipeline_task_num * be num * num_scanner_threads)`.
+
+Note:
+
+1. This method can only control the concurrent request count for a single table in a single query, and cannot control resource usage across multiple SQL statements.
+
+2. Reducing the concurrency will increase the query time.
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/maxcompute-catalog.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/maxcompute-catalog.md
index be09f76b13f..77d29c1301f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/maxcompute-catalog.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -218,4 +218,15 @@ SELECT * FROM mc_ctl.mc_db.mc_tbl LIMIT 10;
MaxCompute Endpoint 和 Tunnel Endpoint 的配置请参见[各地域及不同网络连接方式下的 Endpoint](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints)。
+### 资源使用控制
+
+用户可以通过调整 `parallel_pipeline_task_num`、`num_scanner_threads` 这两个 session variable 来调整[表级别请求并发数量](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2)， 以控制数据传输服务中的资源消耗。其对应的并发数量等于 `max(parallel_pipeline_task_num * be num * num_scanner_threads)`。
+
+需要注意：
+
+1. 该方法只能控制单个query中单张表的并发请求数量，无法控制多个sql的资源使用量;
+
+2. 降低并发数量意味着会提高query的查询时间。
+
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md
index be09f76b13f..77d29c1301f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -218,4 +218,15 @@ SELECT * FROM mc_ctl.mc_db.mc_tbl LIMIT 10;
MaxCompute Endpoint 和 Tunnel Endpoint 的配置请参见[各地域及不同网络连接方式下的 Endpoint](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints)。
+### 资源使用控制
+
+用户可以通过调整 `parallel_pipeline_task_num`、`num_scanner_threads` 这两个 session variable 来调整[表级别请求并发数量](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2)， 以控制数据传输服务中的资源消耗。其对应的并发数量等于 `max(parallel_pipeline_task_num * be num * num_scanner_threads)`。
+
+需要注意：
+
+1. 该方法只能控制单个query中单张表的并发请求数量，无法控制多个sql的资源使用量;
+
+2. 降低并发数量意味着会提高query的查询时间。
+
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md
index be09f76b13f..77d29c1301f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -218,4 +218,15 @@ SELECT * FROM mc_ctl.mc_db.mc_tbl LIMIT 10;
MaxCompute Endpoint 和 Tunnel Endpoint 的配置请参见[各地域及不同网络连接方式下的 Endpoint](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints)。
+### 资源使用控制
+
+用户可以通过调整 `parallel_pipeline_task_num`、`num_scanner_threads` 这两个 session variable 来调整[表级别请求并发数量](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2)， 以控制数据传输服务中的资源消耗。其对应的并发数量等于 `max(parallel_pipeline_task_num * be num * num_scanner_threads)`。
+
+需要注意：
+
+1. 该方法只能控制单个query中单张表的并发请求数量，无法控制多个sql的资源使用量;
+
+2. 降低并发数量意味着会提高query的查询时间。
+
+
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md
index be09f76b13f..bc7f154989e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ CREATE CATALOG [IF NOT EXISTS] catalog_name PROPERTIES (
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -218,4 +218,14 @@ SELECT * FROM mc_ctl.mc_db.mc_tbl LIMIT 10;
MaxCompute Endpoint 和 Tunnel Endpoint 的配置请参见[各地域及不同网络连接方式下的 Endpoint](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints)。
+### 资源使用控制
+
+用户可以通过调整 `parallel_pipeline_task_num`、`num_scanner_threads` 这两个 session variable 来调整[表级别请求并发数量](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2)， 以控制数据传输服务中的资源消耗。其对应的并发数量等于 `max(parallel_pipeline_task_num * be num * num_scanner_threads)`。
+
+需要注意：
+
+1. 该方法只能控制单个query中单张表的并发请求数量，无法控制多个sql的资源使用量;
+
+2. 降低并发数量意味着会提高query的查询时间。
+
diff --git a/versioned_docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md b/versioned_docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md
index 375cdb27d03..7c023530c1e 100644
--- a/versioned_docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md
+++ b/versioned_docs/version-2.1/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ Only the public cloud version of MaxCompute is supported. For support with the p
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -217,3 +217,14 @@ The generated endpoint formats are as follows:
Users can also manually specify `mc.odps_endpoint` and `mc.tunnel_endpoint` to customize the service addresses. This is particularly useful for private deployments of MaxCompute environments.
For details on configuring MaxCompute Endpoint and Tunnel Endpoint, refer to the documentation on [Endpoints for Different Regions and Network Connection Methods](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints).
+
+
+### Resource Usage Control
+
+Users can adjust the `parallel_pipeline_task_num` and `num_scanner_threads` session variables to control the [table-level request concurrency](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2) and manage resource consumption in the data transmission service. The corresponding concurrency equals `max(parallel_pipeline_task_num * be num * num_scanner_threads)`.
+
+Note:
+
+1. This method can only control the concurrent request count for a single table in a single query, and cannot control resource usage across multiple SQL statements.
+
+2. Reducing the concurrency will increase the query time.
diff --git a/versioned_docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md b/versioned_docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md
index 375cdb27d03..7c023530c1e 100644
--- a/versioned_docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md
+++ b/versioned_docs/version-3.x/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ Only the public cloud version of MaxCompute is supported. For support with the p
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -217,3 +217,14 @@ The generated endpoint formats are as follows:
Users can also manually specify `mc.odps_endpoint` and `mc.tunnel_endpoint` to customize the service addresses. This is particularly useful for private deployments of MaxCompute environments.
For details on configuring MaxCompute Endpoint and Tunnel Endpoint, refer to the documentation on [Endpoints for Different Regions and Network Connection Methods](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints).
+
+
+### Resource Usage Control
+
+Users can adjust the `parallel_pipeline_task_num` and `num_scanner_threads` session variables to control the [table-level request concurrency](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2) and manage resource consumption in the data transmission service. The corresponding concurrency equals `max(parallel_pipeline_task_num * be num * num_scanner_threads)`.
+
+Note:
+
+1. This method can only control the concurrent request count for a single table in a single query, and cannot control resource usage across multiple SQL statements.
+
+2. Reducing the concurrency will increase the query time.
diff --git a/versioned_docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md b/versioned_docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md
index 375cdb27d03..7c023530c1e 100644
--- a/versioned_docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md
+++ b/versioned_docs/version-4.x/lakehouse/catalogs/maxcompute-catalog.md
@@ -108,7 +108,7 @@ Only the public cloud version of MaxCompute is supported. For support with the p
| bigint | bigint | |
| float | float | |
| double | double | |
-| decimal(P, S) | decimal(P, S) | |
+| decimal(P, S) | decimal(P, S) | 1 <= P <= 38 ,0 <= scale <= 18 |
| char(N) | char(N) | |
| varchar(N) | varchar(N) | |
| string | string | |
@@ -217,3 +217,14 @@ The generated endpoint formats are as follows:
Users can also manually specify `mc.odps_endpoint` and `mc.tunnel_endpoint` to customize the service addresses. This is particularly useful for private deployments of MaxCompute environments.
For details on configuring MaxCompute Endpoint and Tunnel Endpoint, refer to the documentation on [Endpoints for Different Regions and Network Connection Methods](https://help.aliyun.com/zh/maxcompute/user-guide/endpoints).
+
+
+### Resource Usage Control
+
+Users can adjust the `parallel_pipeline_task_num` and `num_scanner_threads` session variables to control the [table-level request concurrency](https://help.aliyun.com/zh/maxcompute/user-guide/data-transfer-service-quota-manage?spm=a2c4g.11186623.help-menu-search-27797.d_2) and manage resource consumption in the data transmission service. The corresponding concurrency equals `max(parallel_pipeline_task_num * be num * num_scanner_threads)`.
+
+Note:
+
+1. This method can only control the concurrent request count for a single table in a single query, and cannot control resource usage across multiple SQL statements.
+
+2. Reducing the concurrency will increase the query time.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org