This is an automated email from the ASF dual-hosted git repository.
ruanwenjun pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler.git
The following commit(s) were added to refs/heads/dev by this push:
new 63b837b032 [Improvement-18040] [Doc] Update the parameter priority
explanation in the docs. (#18321)
63b837b032 is described below
commit 63b837b032196b69e6474007d2876e8359a17a0a
Author: njnu-seafish <[email protected]>
AuthorDate: Fri Jun 5 15:10:47 2026 +0800
[Improvement-18040] [Doc] Update the parameter priority explanation in the
docs. (#18321)
---
docs/docs/en/guide/parameter/priority.md | 2 +-
docs/docs/zh/guide/parameter/priority.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/docs/en/guide/parameter/priority.md
b/docs/docs/en/guide/parameter/priority.md
index 51dcfa7400..03f06468bb 100644
--- a/docs/docs/en/guide/parameter/priority.md
+++ b/docs/docs/en/guide/parameter/priority.md
@@ -10,7 +10,7 @@ DolphinScheduler has three parameter types:
The user can define part of the parameters when creating workflow definitions.
-As there are multiple sources of the parameter value, it will raise parameter
priority issues when the parameter name is the same. The priority of
DolphinScheduler parameters from high to low is: `Startup Parameter > Local
Parameter > Parameter Context > Global Parameter > Project-level Parameter`.
+As there are multiple sources of the parameter value, it will raise parameter
priority issues when the parameter name is the same. The priority of
DolphinScheduler parameters from high to low is: `Parameter Context > Startup
Parameter > Local Parameter > Global Parameter > Project-level Parameter`.
In the case of upstream tasks can pass parameters to the downstream, there may
be multiple tasks upstream that pass the same parameter name:
diff --git a/docs/docs/zh/guide/parameter/priority.md
b/docs/docs/zh/guide/parameter/priority.md
index ab59c4e384..8226729b7c 100644
--- a/docs/docs/zh/guide/parameter/priority.md
+++ b/docs/docs/zh/guide/parameter/priority.md
@@ -8,7 +8,7 @@ DolphinScheduler 中所涉及的参数值的定义可能来自三种类型：
* [上游任务传递的参数](context.md)：上游任务传递过来的参数
* [本地参数](local.md)：节点的自有变量，用户在“自定义参数”定义的变量，并且用户可以在工作流定义时定义该部分变量的值
-因为参数的值存在多个来源，当参数名相同时，就需要会存在参数优先级的问题。DolphinScheduler 参数的优先级从高到低为：`启动参数 > 本地参数
> 上游任务传递的参数 > 全局参数 > 项目级别参数`
+因为参数的值存在多个来源，当参数名相同时，就需要会存在参数优先级的问题。DolphinScheduler 参数的优先级从高到低为：`上游任务传递的参数 >
启动参数 > 本地参数 > 全局参数 > 项目级别参数`
在上游任务传递的参数中，由于上游可能存在多个任务向下游传递参数，当上游传递的参数名称相同时：
