This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 184225964 Automated deployment:
0676b465e39519742f5d4f4e76914a97c8463595
184225964 is described below
commit 1842259648921e6a951ce03cdae8d1357a8a44d6
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Jun 30 05:11:38 2022 +0000
Automated deployment: 0676b465e39519742f5d4f4e76914a97c8463595
---
.../dev/user_doc/guide/parameter/built-in.html | 84 +++++++++++++---------
.../dev/user_doc/guide/parameter/built-in.json | 2 +-
.../docs/dev/user_doc/guide/parameter/context.html | 2 +-
.../docs/dev/user_doc/guide/parameter/context.json | 2 +-
.../docs/dev/user_doc/guide/parameter/global.html | 1 +
.../docs/dev/user_doc/guide/parameter/global.json | 2 +-
en-us/docs/dev/user_doc/guide/parameter/local.html | 24 +++----
en-us/docs/dev/user_doc/guide/parameter/local.json | 2 +-
.../dev/user_doc/guide/parameter/priority.html | 10 +--
.../dev/user_doc/guide/parameter/priority.json | 2 +-
10 files changed, 73 insertions(+), 58 deletions(-)
diff --git a/en-us/docs/dev/user_doc/guide/parameter/built-in.html
b/en-us/docs/dev/user_doc/guide/parameter/built-in.html
index 84520e545..994cfa174 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/built-in.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/built-in.html
@@ -13,22 +13,30 @@
<div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="banner-tips"><div>🤔
Have queries regarding Apache DolphinScheduler, Join Slack channel to disscuss
them <a class="link-tips"
href="https://s.apache.org/dolphinscheduler-slack";>join #dolphinscheduler
channel</a>! 🌟</div></div><div class="header-body"><span class="mobile-menu-btn
mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo"
src=" [...]
<h2>Basic Built-in Parameter</h2>
<table>
- <tr><th>Variable</th><th>Declaration Method</th><th>Meaning</th></tr>
- <tr>
- <td>system.biz.date</td>
- <td>${system.biz.date}</td>
- <td>The day before the schedule time of the daily scheduling instance,
the format is yyyyMMdd</td>
- </tr>
- <tr>
- <td>system.biz.curdate</td>
- <td>${system.biz.curdate}</td>
- <td>The schedule time of the daily scheduling instance, the format is
yyyyMMdd</td>
- </tr>
- <tr>
- <td>system.datetime</td>
- <td>${system.datetime}</td>
- <td>The schedule time of the daily scheduling instance, the format is
yyyyMMddHHmmss</td>
- </tr>
+<thead>
+<tr>
+<th>Variable</th>
+<th>Declaration Method</th>
+<th>Meaning</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>system.biz.date</td>
+<td><code>${system.biz.date}</code></td>
+<td>The day before the schedule time of the daily scheduling instance, the
format is <code>yyyyMMdd</code></td>
+</tr>
+<tr>
+<td>system.biz.curdate</td>
+<td><code>${system.biz.curdate}</code></td>
+<td>The schedule time of the daily scheduling instance, the format is
<code>yyyyMMdd</code></td>
+</tr>
+<tr>
+<td>system.datetime</td>
+<td><code>${system.datetime}</code></td>
+<td>The schedule time of the daily scheduling instance, the format is
<code>yyyyMMddHHmmss</code></td>
+</tr>
+</tbody>
</table>
<h2>Extended Built-in Parameter</h2>
<ul>
@@ -39,24 +47,32 @@
<p>Benchmark variable defines as <code>$[...]</code> format, time format
<code>$[yyyyMMddHHmmss]</code> can be decomposed and combined arbitrarily, such
as: <code>$[yyyyMMdd]</code>, <code>$[HHmmss]</code>,
<code>$[yyyy-MM-dd]</code>, etc.</p>
</li>
<li>
-<p>Or define by the 2 following ways:</p>
-<pre><code>1. Use add_month(yyyyMMdd, offset) function to add or minus number
of months
-the first parameter of this function is [yyyyMMdd], represents the time format
-the second parameter is offset, represents the number of months the user wants
to add or minus
-* Next N years：$[add_months(yyyyMMdd,12*N)]
-* N years before：$[add_months(yyyyMMdd,-12*N)]
-* Next N months：$[add_months(yyyyMMdd,N)]
-* N months before：$[add_months(yyyyMMdd,-N)]
-*********************************************************************************************************
-1. Add or minus numbers directly after the time format
-* Next N weeks：$[yyyyMMdd+7*N]
-* First N weeks：$[yyyyMMdd-7*N]
-* Next N days：$[yyyyMMdd+N]
-* N days before：$[yyyyMMdd-N]
-* Next N hours：$[HHmmss+N/24]
-* First N hours：$[HHmmss-N/24]
-* Next N minutes：$[HHmmss+N/24/60]
-* First N minutes：$[HHmmss-N/24/60]</code></pre>
+<p>Or define by the following two ways:</p>
+<ol>
+<li>
+<p>Use add_month(yyyyMMdd, offset) function to add or minus number of months.
+The first parameter of this function is [yyyyMMdd], represents the time format
and the second parameter is offset, represents the number of months the user
wants to add or minus.</p>
+<ul>
+<li>Next N years：<code>$[add_months(yyyyMMdd,12*N)]</code></li>
+<li>N years before：<code>$[add_months(yyyyMMdd,-12*N)]</code></li>
+<li>Next N months：<code>$[add_months(yyyyMMdd,N)]</code></li>
+<li>N months before：<code>$[add_months(yyyyMMdd,-N)]</code></li>
+</ul>
+</li>
+<li>
+<p>Add or minus numbers directly after the time format.</p>
+<ul>
+<li>Next N weeks：<code>$[yyyyMMdd+7*N]</code></li>
+<li>First N weeks：<code>$[yyyyMMdd-7*N]</code></li>
+<li>Next N days：<code>$[yyyyMMdd+N]</code></li>
+<li>N days before：<code>$[yyyyMMdd-N]</code></li>
+<li>Next N hours：<code>$[HHmmss+N/24]</code></li>
+<li>First N hours：<code>$[HHmmss-N/24]</code></li>
+<li>Next N minutes：<code>$[HHmmss+N/24/60]</code></li>
+<li>First N minutes：<code>$[HHmmss-N/24/60]</code></li>
+</ul>
+</li>
+</ol>
</li>
</ul>
</div></section><footer class="footer-container"><div
class="footer-body"><div><h3>About us</h3><h4>Do you need feedback? Please
contact us through the following ways.</h4></div><div
class="contact-container"><ul><li><a
href="/en-us/community/development/subscribe.html"><img class="img-base"
src="/img/emailgray.png"/><img class="img-change"
src="/img/emailblue.png"/><p>Email List</p></a></li><li><a
href="https://twitter.com/dolphinschedule";><img class="img-base"
src="/img/twittergray.png [...]
diff --git a/en-us/docs/dev/user_doc/guide/parameter/built-in.json
b/en-us/docs/dev/user_doc/guide/parameter/built-in.json
index b75f881d2..0f3d585a5 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/built-in.json
+++ b/en-us/docs/dev/user_doc/guide/parameter/built-in.json
@@ -1,6 +1,6 @@
{
"filename": "built-in.md",
- "__html": "<h1>Built-in Parameter</h1>\n<h2>Basic Built-in
Parameter</h2>\n<table>\n <tr><th>Variable</th><th>Declaration
Method</th><th>Meaning</th></tr>\n <tr>\n <td>system.biz.date</td>\n
<td>${system.biz.date}</td>\n <td>The day before the schedule time
of the daily scheduling instance, the format is yyyyMMdd</td>\n </tr>\n
<tr>\n <td>system.biz.curdate</td>\n
<td>${system.biz.curdate}</td>\n <td>The schedule time of the daily s
[...]
+ "__html": "<h1>Built-in Parameter</h1>\n<h2>Basic Built-in
Parameter</h2>\n<table>\n<thead>\n<tr>\n<th>Variable</th>\n<th>Declaration
Method</th>\n<th>Meaning</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>system.biz.date</td>\n<td><code>${system.biz.date}</code></td>\n<td>The
day before the schedule time of the daily scheduling instance, the format is
<code>yyyyMMdd</code></td>\n</tr>\n<tr>\n<td>system.biz.curdate</td>\n<td><code>${system.biz.curdate}</code></td>\n<td>The
schedule time of [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/parameter/built-in.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/parameter/context.html
b/en-us/docs/dev/user_doc/guide/parameter/context.html
index 086922538..5f2624ea4 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/context.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/context.html
@@ -10,7 +10,7 @@
<link rel="stylesheet" href="/build/vendor.eeae4ed.css">
</head>
<body>
- <div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="banner-tips"><div>🤔
Have queries regarding Apache DolphinScheduler, Join Slack channel to disscuss
them <a class="link-tips"
href="https://s.apache.org/dolphinscheduler-slack";>join #dolphinscheduler
channel</a>! 🌟</div></div><div class="header-body"><span class="mobile-menu-btn
mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo"
src=" [...]
+ <div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="banner-tips"><div>🤔
Have queries regarding Apache DolphinScheduler, Join Slack channel to disscuss
them <a class="link-tips"
href="https://s.apache.org/dolphinscheduler-slack";>join #dolphinscheduler
channel</a>! 🌟</div></div><div class="header-body"><span class="mobile-menu-btn
mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo"
src=" [...]
<p>DolphinScheduler provides the ability to refer to each other between
parameters, including local parameters refer to global parameters and upstream
and downstream parameter transfer. Due to the existence of references, it
involves the priority of parameters when the parameter names are the same. see
also <a href="priority.md">Parameter Priority</a></p>
<h2>Local Task Refers to Global Parameter</h2>
<p>The premise of local tasks referring global parameters is that you have
already defined <a href="global.md">Global Parameter</a>. The usage is similar
to the usage in <a href="local.md">local parameters</a>, but the value of the
parameter needs to be configured as the key of the global parameter.</p>
diff --git a/en-us/docs/dev/user_doc/guide/parameter/context.json
b/en-us/docs/dev/user_doc/guide/parameter/context.json
index 1607fc95a..db8add0b9 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/context.json
+++ b/en-us/docs/dev/user_doc/guide/parameter/context.json
@@ -1,6 +1,6 @@
{
"filename": "context.md",
- "__html": "<h1>Refer to Parameter Context</h1>\n<p>DolphinScheduler provides
the ability to refer to each other between parameters, including local
parameters refer to global parameters and upstream and downstream parameter
transfer. Due to the existence of references, it involves the priority of
parameters when the parameter names are the same. see also <a
href=\"priority.md\">Parameter Priority</a></p>\n<h2>Local Task Refers to
Global Parameter</h2>\n<p>The premise of local tasks ref [...]
+ "__html": "<h1>Parameter Context</h1>\n<p>DolphinScheduler provides the
ability to refer to each other between parameters, including local parameters
refer to global parameters and upstream and downstream parameter transfer. Due
to the existence of references, it involves the priority of parameters when the
parameter names are the same. see also <a href=\"priority.md\">Parameter
Priority</a></p>\n<h2>Local Task Refers to Global Parameter</h2>\n<p>The
premise of local tasks referring gl [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/parameter/context.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/parameter/global.html
b/en-us/docs/dev/user_doc/guide/parameter/global.html
index a6794a15a..395ffdf78 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/global.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/global.html
@@ -15,6 +15,7 @@
<p>Global parameters are parameters that are valid for all task nodes of the
entire workflow. It can be configured on the workflow definition page.</p>
<h2>Usage</h2>
<p>The specific use method can be determined according to the actual
production situation. This example uses a shell task to print out the date
value of yesterday.</p>
+<h2>Example</h2>
<h3>Create a Shell task</h3>
<p>Create a shell task and enter <code>echo ${dt}</code> in the script
content. In this case, dt is the global parameter we need to declare. As shown
below:</p>
<p><img src="/img/new_ui/dev/parameter/global_parameter01.png"
alt="global-parameter01"></p>
diff --git a/en-us/docs/dev/user_doc/guide/parameter/global.json
b/en-us/docs/dev/user_doc/guide/parameter/global.json
index 80aea6aab..d444029c1 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/global.json
+++ b/en-us/docs/dev/user_doc/guide/parameter/global.json
@@ -1,6 +1,6 @@
{
"filename": "global.md",
- "__html": "<h1>Global Parameter</h1>\n<h2>Scope</h2>\n<p>Global parameters
are parameters that are valid for all task nodes of the entire workflow. It can
be configured on the workflow definition page.</p>\n<h2>Usage</h2>\n<p>The
specific use method can be determined according to the actual production
situation. This example uses a shell task to print out the date value of
yesterday.</p>\n<h3>Create a Shell task</h3>\n<p>Create a shell task and enter
<code>echo ${dt}</code> in the scri [...]
+ "__html": "<h1>Global Parameter</h1>\n<h2>Scope</h2>\n<p>Global parameters
are parameters that are valid for all task nodes of the entire workflow. It can
be configured on the workflow definition page.</p>\n<h2>Usage</h2>\n<p>The
specific use method can be determined according to the actual production
situation. This example uses a shell task to print out the date value of
yesterday.</p>\n<h2>Example</h2>\n<h3>Create a Shell task</h3>\n<p>Create a
shell task and enter <code>echo ${dt}< [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/parameter/global.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/parameter/local.html
b/en-us/docs/dev/user_doc/guide/parameter/local.html
index 91c445b56..2e132cac8 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/local.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/local.html
@@ -15,12 +15,12 @@
<p>Parameters configured on the task definition page, the scope of this
parameter is inside this task only. But if you configure according to <a
href="context.md">Refer to Parameter Context</a>, it could pass to downstream
tasks.</p>
<h2>Usage</h2>
<ul>
-<li>If you want to use parameter in single task, see <a
href="#use-local-parameter-by-custom-parameter">local parameter with custom
parameter</a></li>
+<li>If you want to use parameter in single task, see <a
href="#use-local-parameter-by-custom-parameter">local parameter with custom
parameter</a>.</li>
<li>If you want to use set parameter in task and use them in downstream tasks:
<ul>
-<li>For simple use without using custom parameter, see <a
href="#export-local-parameter-by-setvalue">export parameter via
<code>setValue</code></a></li>
-<li>Using custom parameter, see <a
href="#export-local-parameter-by-setvalue-and-custom-parameter">export
parameter via <code>setValue</code> and custom parameter</a></li>
-<li>Using bash variable, see <a
href="#export-local-parameter-by-setvalue-and-bash-variable">export parameter
via <code>setValue</code> and bash variable</a></li>
+<li>For simple use without using custom parameter, see <a
href="#export-local-parameter-by-setvalue">export parameter via
<code>setValue</code></a>.</li>
+<li>Using custom parameter, see <a
href="#export-local-parameter-by-setvalue-and-custom-parameter">export
parameter via <code>setValue</code> and custom parameter</a>.</li>
+<li>Using bash variable, see <a
href="#export-local-parameter-by-setvalue-and-bash-variable">export parameter
via <code>setValue</code> and bash variable</a>.</li>
</ul>
</li>
</ul>
@@ -31,22 +31,20 @@
<p><img src="/img/new_ui/dev/parameter/local_parameter01.png"
alt="local-parameter01"></p>
<p>Parameters:</p>
<ul>
-<li>dt: indicates the parameter name</li>
-<li>in: IN indicates that local parameters can only be used on the current
node, and OUT indicates that local parameters can be transmitted to the
downstream</li>
-<li>DATE: indicates the DATE of the data type</li>
-<li>$[YYYY-MM-DD] : indicates a built-in parameter derived from a user-defined
format</li>
+<li>dt: indicates the parameter name.</li>
+<li>in: IN indicates that local parameters can only be used on the current
node, and OUT indicates that local.parameters can be transmitted to the
downstream.</li>
+<li>DATE: indicates the DATE of the data type.</li>
+<li>$[YYYY-MM-DD] : indicates a built-in parameter derived from a user-defined
format.</li>
</ul>
<p>Save the workflow and run it. View Shell task's log.</p>
<p><img src="/img/new_ui/dev/parameter/local_parameter02.png"
alt="local-parameter02"></p>
<blockquote>
-<p>Note: The local parameter can be used in the workflow of the current task
node. If it is set to OUT, it can be passed to the downstream workflow. Please
refer to: <a href="context.md">Parameter Context</a></p>
+<p>Note: The local parameter can be used in the workflow of the current task
node. If it is set to OUT, it can be passed to the downstream workflow. Please
refer to: <a href="context.md">Parameter Context</a>.</p>
</blockquote>
<h3>Export Local Parameter by <code>setValue</code></h3>
-<p>If you want to simple export parameters and then use them in downstream
tasks, you could use <code>setValue</code> in your task, which
-you can manage your parameters into one single task. You can use syntax
<code>echo '${setValue(set_val=123)}'</code>(<strong>do not forget the
-single quote</strong>) in Shell task and add new <code>OUT</code> custom
parameter to export it.</p>
+<p>If you want to simple export parameters and then use them in downstream
tasks, you could use <code>setValue</code> in your task. And you can manage
your parameters into one single task. You can use syntax <code>echo
'${setValue(set_val=123)}'</code>(<strong>do not forget the single
quote</strong>) in Shell task and add new <code>OUT</code> custom parameter to
export it.</p>
<p><img src="/img/new_ui/dev/parameter/local_param_set_val.png"
alt="local-parameter-set-val"></p>
-<p>You could get this value in downstream task using syntax <code>echo
'${set_val}'</code>.</p>
+<p>You can get this value in downstream task using syntax <code>echo
'${set_val}'</code>.</p>
<h3>Export Local Parameter by <code>setValue</code> and Custom Parameter</h3>
<p>If you want to export parameters with custom parameter instead of constants
value, and then use them in downstream tasks,
you could use <code>setValue</code> in your task, which easier to maintain by
change "custom parameter" block when you want to
diff --git a/en-us/docs/dev/user_doc/guide/parameter/local.json
b/en-us/docs/dev/user_doc/guide/parameter/local.json
index 04aa81351..3a6d1f235 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/local.json
+++ b/en-us/docs/dev/user_doc/guide/parameter/local.json
@@ -1,6 +1,6 @@
{
"filename": "local.md",
- "__html": "<h1>Local Parameter</h1>\n<h2>Scope</h2>\n<p>Parameters
configured on the task definition page, the scope of this parameter is inside
this task only. But if you configure according to <a href=\"context.md\">Refer
to Parameter Context</a>, it could pass to downstream
tasks.</p>\n<h2>Usage</h2>\n<ul>\n<li>If you want to use parameter in single
task, see <a href=\"#use-local-parameter-by-custom-parameter\">local parameter
with custom parameter</a></li>\n<li>If you want to use s [...]
+ "__html": "<h1>Local Parameter</h1>\n<h2>Scope</h2>\n<p>Parameters
configured on the task definition page, the scope of this parameter is inside
this task only. But if you configure according to <a href=\"context.md\">Refer
to Parameter Context</a>, it could pass to downstream
tasks.</p>\n<h2>Usage</h2>\n<ul>\n<li>If you want to use parameter in single
task, see <a href=\"#use-local-parameter-by-custom-parameter\">local parameter
with custom parameter</a>.</li>\n<li>If you want to use [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/parameter/local.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/parameter/priority.html
b/en-us/docs/dev/user_doc/guide/parameter/priority.html
index 7a136940f..145db120b 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/priority.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/priority.html
@@ -13,18 +13,18 @@
<div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="banner-tips"><div>🤔
Have queries regarding Apache DolphinScheduler, Join Slack channel to disscuss
them <a class="link-tips"
href="https://s.apache.org/dolphinscheduler-slack";>join #dolphinscheduler
channel</a>! 🌟</div></div><div class="header-body"><span class="mobile-menu-btn
mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo"
src=" [...]
<p>DolphinScheduler has three parameter types:</p>
<ul>
-<li><a href="global.md">Global Parameter</a>: parameters defined at the
workflow define page</li>
-<li><a href="context.md">Parameter Context</a>: parameters passed by upstream
task nodes</li>
+<li><a href="global.md">Global Parameter</a>: parameters defined at the
workflow define page.</li>
+<li><a href="context.md">Parameter Context</a>: parameters passed by upstream
task nodes.</li>
<li><a href="local.md">Local Parameter</a>: parameters belong to its node,
which is the parameters defined by the user in [Custom Parameters]. The user
can define part of the parameters when creating workflow definitions.</li>
</ul>
-<p>Due to there are multiple sources of the parameter value, there will raise
parameter priority issues when the parameter name is the same. The priority of
DolphinScheduler parameters from high to low is: <code>Local Parameter >
Parameter Context > Global Parameter</code></p>
+<p>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: <code>Local Parameter >
Parameter Context > Global Parameter</code>.</p>
<p>In the case of upstream tasks can pass parameters to the downstream, there
may be multiple tasks upstream that pass the same parameter name:</p>
<ul>
<li>Downstream nodes prefer to use parameters with non-empty values</li>
<li>If there are multiple parameters with non-empty values, select the value
from the upstream task with the earliest completion time</li>
</ul>
<h2>Example</h2>
-<p>Followings are examples shows task parameters priority
problems:#############</p>
+<p>Followings are examples showing task parameters priority problems:</p>
<p>1: Use shell nodes to explain the first case.</p>
<p><img src="/img/new_ui/dev/parameter/priority_parameter01.png"
alt="priority-parameter01"></p>
<p>The [useParam] node can use the parameters which are set in the
[createParam] node. The [useParam] node cannot obtain the parameters from the
[noUseParam] node due to there is no dependency between them. Other task node
types have the same usage rules with the Shell example here.</p>
@@ -34,7 +34,7 @@
<p><img src="/img/new_ui/dev/parameter/priority_parameter03.png"
alt="priority-parameter03"></p>
<p>The following shows the definition of the [use_create] node:</p>
<p><img src="/img/new_ui/dev/parameter/priority_parameter04.png"
alt="priority-parameter04"></p>
-<p>"status" is the own parameters of the node set by the current
node. However, the user also sets the "status" parameter (global
parameter) when saving the process definition and assign its value to -1. Then
the value of status will be 2 with higher priority when the SQL executes. The
global parameter value is discarded.</p>
+<p>"status" is own parameter of the node set by the current node.
However, the user also sets the "status" parameter (global parameter)
when saving the process definition and assign its value to -1. Then the value
of status will be 2, with higher priority when the SQL executes. The global
parameter value is discarded.</p>
<p>The "ID" here is the parameter set by the upstream node. The user
sets the parameters of the same parameter name "ID" for the
[createparam1] node and [createparam2] node. And the [use_create] node uses the
value of [createParam1] which is finished first.</p>
</div></section><footer class="footer-container"><div
class="footer-body"><div><h3>About us</h3><h4>Do you need feedback? Please
contact us through the following ways.</h4></div><div
class="contact-container"><ul><li><a
href="/en-us/community/development/subscribe.html"><img class="img-base"
src="/img/emailgray.png"/><img class="img-change"
src="/img/emailblue.png"/><p>Email List</p></a></li><li><a
href="https://twitter.com/dolphinschedule";><img class="img-base"
src="/img/twittergray.png [...]
<script src="/asset/js/react/react-with-addons.min.js"></script>
diff --git a/en-us/docs/dev/user_doc/guide/parameter/priority.json
b/en-us/docs/dev/user_doc/guide/parameter/priority.json
index c0e6fe8f3..9f56f62ed 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/priority.json
+++ b/en-us/docs/dev/user_doc/guide/parameter/priority.json
@@ -1,6 +1,6 @@
{
"filename": "priority.md",
- "__html": "<h1>Parameter Priority</h1>\n<p>DolphinScheduler has three
parameter types:</p>\n<ul>\n<li><a href=\"global.md\">Global Parameter</a>:
parameters defined at the workflow define page</li>\n<li><a
href=\"context.md\">Parameter Context</a>: parameters passed by upstream task
nodes</li>\n<li><a href=\"local.md\">Local Parameter</a>: parameters belong to
its node, which is the parameters defined by the user in [Custom Parameters].
The user can define part of the parameters when c [...]
+ "__html": "<h1>Parameter Priority</h1>\n<p>DolphinScheduler has three
parameter types:</p>\n<ul>\n<li><a href=\"global.md\">Global Parameter</a>:
parameters defined at the workflow define page.</li>\n<li><a
href=\"context.md\">Parameter Context</a>: parameters passed by upstream task
nodes.</li>\n<li><a href=\"local.md\">Local Parameter</a>: parameters belong to
its node, which is the parameters defined by the user in [Custom Parameters].
The user can define part of the parameters when [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/parameter/priority.html",
"meta": {}
}
\ No newline at end of file
