You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by gi...@apache.org on 2022/03/10 03:04:36 UTC
[dolphinscheduler-website] branch asf-site updated: Automated deployment: 13d472f5c644064aa4d490321a5b0c6332827fd3
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 c408eef Automated deployment: 13d472f5c644064aa4d490321a5b0c6332827fd3
c408eef is described below
commit c408eef2523594b746effe757b2af95cd3186b9b
Author: github-actions[bot] <gi...@users.noreply.github.com>
AuthorDate: Thu Mar 10 03:03:35 2022 +0000
Automated deployment: 13d472f5c644064aa4d490321a5b0c6332827fd3
---
.../dev/user_doc/guide/parameter/built-in.html | 22 ++++++-------
.../dev/user_doc/guide/parameter/built-in.json | 2 +-
.../docs/dev/user_doc/guide/parameter/context.html | 38 ++++++++++++----------
.../docs/dev/user_doc/guide/parameter/context.json | 2 +-
.../docs/dev/user_doc/guide/parameter/global.html | 6 ++--
.../docs/dev/user_doc/guide/parameter/global.json | 2 +-
en-us/docs/dev/user_doc/guide/parameter/local.html | 6 ++--
en-us/docs/dev/user_doc/guide/parameter/local.json | 2 +-
.../dev/user_doc/guide/parameter/priority.html | 28 ++++++++--------
.../dev/user_doc/guide/parameter/priority.json | 2 +-
.../dev/user_doc/guide/parameter/priority.html | 2 +-
.../dev/user_doc/guide/parameter/priority.json | 2 +-
12 files changed, 58 insertions(+), 56 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 81607e9..916b15f 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,42 +13,42 @@
<div id="root"><div class="md2html docs-page" data-reactroot=""><header class="header-container header-container-dark"><div class="header-body"><span class="mobile-menu-btn mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div class="search search-dark"><span class="icon-search"></span></div><span class="language-switch language-switch-dark">中</span><div class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant- [...]
<h2>Basic Built-in Parameter</h2>
<table>
- <tr><th>variable</th><th>declaration method</th><th>meaning</th></tr>
+ <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 scheduled time of the daily scheduling instance, the format is yyyyMMdd</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 timing time of the daily scheduling instance, the format is yyyyMMdd</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 timing time of the daily scheduling instance, the format is yyyyMMddHHmmss</td>
+ <td>The schedule time of the daily scheduling instance, the format is yyyyMMddHHmmss</td>
</tr>
</table>
<h2>Extended Built-in Parameter</h2>
<ul>
<li>
-<p>Support custom variable names in the code, declaration method: ${variable name}. It can refer to <a href="#basic-built-in-parameter">basic built-in parameter</a> or specify "constants".</p>
+<p>Support custom variables in the code, declaration way: <code>${variable name}</code>. Refers to "System Parameter".</p>
</li>
<li>
-<p>We define this benchmark variable as $[...] format, $[yyyyMMddHHmmss] can be decomposed and combined arbitrarily, such as: $[yyyyMMdd], $[HHmmss], $[yyyy-MM-dd], etc.</p>
+<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 the 2 following methods may be useful:</p>
-<pre><code>1. use add_month(yyyyMMdd, offset) function to add/minus number of months
-the first parameter of this function is yyyyMMdd, representing the time format user will get
-the second is offset, representing the number of months the user wants to add or minus
+<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 numbers directly after the time format
+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]
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 4188c9d..b75f881 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 scheduled 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 timing time of the daily sc [...]
+ "__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 [...]
"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 cbccf76..1340fbf 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/context.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/context.html
@@ -10,40 +10,42 @@
<link rel="stylesheet" href="/build/vendor.23870e5.css">
</head>
<body>
- <div id="root"><div class="md2html docs-page" data-reactroot=""><header class="header-container header-container-dark"><div class="header-body"><span class="mobile-menu-btn mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div class="search search-dark"><span class="icon-search"></span></div><span class="language-switch language-switch-dark">中</span><div class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant- [...]
-<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. Because of 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 Use Global Parameter</h2>
-<p>The premise of local tasks referencing 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 in the global parameter</p>
+ <div id="root"><div class="md2html docs-page" data-reactroot=""><header class="header-container header-container-dark"><div class="header-body"><span class="mobile-menu-btn mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div class="search search-dark"><span class="icon-search"></span></div><span class="language-switch language-switch-dark">中</span><div class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant- [...]
+<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>
<p><img src="/img/global_parameter.png" alt="parameter-call-global-in-local"></p>
-<p>As shown in the figure above, <code>${biz_date}</code> and <code>${curdate}</code> are examples of local parameters referencing global parameters. Observe the last line of the above figure, local_param_bizdate uses ${global_bizdate} to refer to the global parameter. In the shell script, you can use ${local_param_bizdate} to refer to the value of the global variable global_bizdate, or set the value of local_param_bizdate directly through JDBC. In the same way, local_param refers to the [...]
+<p>As the figure above shows, <code>${biz_date}</code> and <code>${curdate}</code> are examples of local parameters that refer to global parameters. Observe the last line of the above figure, <code>local_param_bizdate</code> uses <code>${global_bizdate}</code> to refer to the global parameter. In the shell script, you can use <code>${local_param_bizdate}</code> to refer to the value of the global variable <code>global_bizdate</code>, or set the value of <code>local_param_bizdate</code> d [...]
<h2>Pass Parameter From Upstream Task to Downstream</h2>
-<p>DolphinScheduler Parameter transfer between tasks is allowed, and the current transfer direction only supports one-way transfer from upstream to downstream. The task types currently supporting this feature are：</p>
+<p>DolphinScheduler allows parameter transfer between tasks. Currently, transfer direction only supports one-way transfer from upstream to downstream. The task types that support this feature are：</p>
<ul>
<li><a href="../task/shell.md">Shell</a></li>
<li><a href="../task/sql.md">SQL</a></li>
<li><a href="../task/stored-procedure.md">Procedure</a></li>
</ul>
-<p>When defining an upstream node, if there is a need to transmit the result of that node to a downstream node that has a dependency. You need to set a parameter whose direction is OUT in [Custom Parameters] of [Current Node Settings]. At present, we mainly focus on the function of SQL and SHELL nodes that can input parameters.</p>
-<p>prop is user-specified; the direction is selected as OUT, and will be defined as parameter output only when the direction is OUT. The data type can be chosen from different data structures as needed; the value part is not required.</p>
-<p>If the result of the SQL node has only one row, one or more fields, the name of the prop needs to be the same as the field name. The data type can be chosen to be something other than LIST. The parameter will select the value corresponding to the column with the same name as this parameter in the column name in the SQL query result.</p>
-<p>If the result of the SQL node is multiple rows, one or more fields, the name of the prop needs to be the same as the name of the field. The data type is selected as LIST, and the SQL query result will be converted to LIST, and the result will be converted to JSON as the value of the corresponding parameter.</p>
-<p>Let's take another example of the process that contains the SQL node in the above picture:</p>
-<p>The [createParam1] node in the above figure is defined as follows:</p>
+<p>When defining an upstream node, if there is a need to transmit the result of that node to a dependency related downstream node. You need to set an <code>OUT</code> direction parameter to [Custom Parameters] of the [Current Node Settings]. At present, we mainly focus on the SQL and shell nodes to pass parameters downstream.</p>
+<h3>SQL</h3>
+<p><code>prop</code> is user-specified; the direction selects <code>OUT</code>, and will define as an export parameter only when the direction is <code>OUT</code>. Choose data structures for data type according to the scenario, and the leave the value part blank.</p>
+<p>If the result of the SQL node has only one row, one or multiple fields, the name of the <code>prop</code> needs to be the same as the field name. The data type can choose structure except <code>LIST</code>. The parameter assigns the value according to the same column name in the SQL query result.</p>
+<p>If the result of the SQL node has multiple rows, one or more fields, the name of the <code>prop</code> needs to be the same as the field name. Choose the data type structure as <code>LIST</code>, and the SQL query result will be converted to <code>LIST<VARCHAR></code>, and forward to convert to JSON as the parameter value.</p>
+<p>Let's make an example of the SQL node process in the above picture:</p>
+<p>The [createParam1] node in the above figure defines as follows:</p>
<p><img src="/img/globalParam/image-20210723104957031.png" alt="png05"></p>
-<p>[createParam2] node is defined as follows:</p>
+<p>The [createParam2] node defines as follows:</p>
<p><img src="/img/globalParam/image-20210723105026924.png" alt="png06"></p>
-<p>You can find the value of the variable in the [Workflow Instance] page to find the corresponding node instance.</p>
+<p>Find the value of the variable in the [Workflow Instance] page corresponding to the node instance.</p>
<p>Node instance [createparam1] is as follows:</p>
<p><img src="/img/globalParam/image-20210723105131381.png" alt="png07"></p>
-<p>Here, the value of "id" is equal to 12.</p>
+<p>Here, the value of "id" is 12.</p>
<p>Let's see the case of the node instance [createparam2].</p>
<p><img src="/img/globalParam/image-20210723105255850.png" alt="png08"></p>
-<p>There is only the value of "id". Although the user-defined sql looks up the fields "id" and "database_name", only one parameter is set because only one parameter "id" is defined for out. For display reasons, the length of the list is already checked for you here as 10.</p>
+<p>There is only the "id" value. Although the user-defined SQL query both "id" and "database_name" field, only set the <code>OUT</code> parameter <code>id</code> due to only one parameter "id" is defined for output. The length of the result list is 10 due to display reasons.</p>
<h3>SHELL</h3>
-<p>prop is user-specified. The direction is selected as OUT. The output is defined as a parameter only when the direction is OUT. Data type can choose different data structures as needed; the value part is not required to be filled. The user needs to pass the parameter, and when defining the shell script, the output format of ${setValue(key=value)} statement is required, key is the prop of the corresponding parameter, and value is the value of the parameter.</p>
+<p><code>prop</code> is user-specified and the direction is <code>OUT</code>. The output is defined as an export parameter only when the direction is <code>OUT</code>. Choose data structures for data type according to the scenario, and leave the value part blank.
+The user needs to pass the parameter when creating the shell script, the output statement format is <code>${setValue(key=value)}</code>, the key is the <code>prop</code> of the corresponding parameter, and value is the value of the parameter.</p>
<p>For example, in the figure below:</p>
<p><img src="/img/globalParam/image-20210723101242216.png" alt="png09"></p>
-<p>When the log detects the ${setValue(key=value1)} format in the shell node definition, it will assign value1 to key, and the downstream node can use the value of the variable key directly. Similarly, you can find the corresponding node instance on the [Workflow Instance] page to see the value of the variable.</p>
+<p>When the log detects the <code>${setValue(key=value1)}</code> format in the shell node definition, it will assign value1 to the key, and downstream nodes can use the variable key directly. Similarly, you can find the corresponding node instance on the [Workflow Instance] page to see the value of the variable.</p>
<p><img src="/img/globalParam/image-20210723102522383.png" alt="png10"></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="//cdn.jsdelivr.net/npm/react@15.6.2/dist/react-with-addons.min.js"></script>
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 408e71e..7f1c7cb 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>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. Because of 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 Use Global Parameter</h2>\n<p>The premise of local tasks referencing [...]
+ "__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 [...]
"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 956de60..e67e1be 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/global.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/global.html
@@ -12,16 +12,16 @@
<body>
<div id="root"><div class="md2html docs-page" data-reactroot=""><header class="header-container header-container-dark"><div class="header-body"><span class="mobile-menu-btn mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div class="search search-dark"><span class="icon-search"></span></div><span class="language-switch language-switch-dark">中</span><div class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant- [...]
<h2>Scope</h2>
-<p>The parameters configured on the workflow definition dialog, the whole workflow is it's scope.</p>
+<p>The parameters defined on the process definition page can apply to all the scope of the process tasks.</p>
<h2>Usage</h2>
-<p>the approach to set global parameters is, after defining the workflow, click the 'save' button, then click the '+' button below the 'Set global':</p>
+<p>Usage of global parameters is: at the process define page, click the '+' beside the 'Set global' and fill in the key and value to save:</p>
<p align="center">
<img src="/img/supplement_global_parameter_en.png" width="80%" />
</p>
<p align="center">
<img src="/img/local_parameter_en.png" width="80%" />
</p>
-<p>The global_bizdate parameter defined here can be referenced by local parameters of any other task node, and the value of global_bizdate is set to the figure obtained by referencing the system parameter system.biz.date</p>
+<p>The <code>global_bizdate</code> parameter defined here can be referenced by local parameters of any other task node, and set the value of <code>global_bizdate</code> by referencing the system parameter <code>system.biz.date</code>.</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="//cdn.jsdelivr.net/npm/react@15.6.2/dist/react-with-addons.min.js"></script>
<script src="//cdn.jsdelivr.net/npm/react-dom@15.6.2/dist/react-dom.min.js"></script>
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 3c07966..0e9d998 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>The parameters configured on the workflow definition dialog, the whole workflow is it's scope.</p>\n<h2>Usage</h2>\n<p>the approach to set global parameters is, after defining the workflow, click the 'save' button, then click the '+' button below the 'Set global':</p>\n<p align=\"center\">\n <img src=\"/img/supplement_global_parameter_en.png\" width=\"80%\" />\n </p>\n<p align=\"center\">\n <img src=\"/img/local_parameter_en. [...]
+ "__html": "<h1>Global Parameter</h1>\n<h2>Scope</h2>\n<p>The parameters defined on the process definition page can apply to all the scope of the process tasks.</p>\n<h2>Usage</h2>\n<p>Usage of global parameters is: at the process define page, click the '+' beside the 'Set global' and fill in the key and value to save:</p>\n<p align=\"center\">\n <img src=\"/img/supplement_global_parameter_en.png\" width=\"80%\" />\n </p>\n<p align=\"center\">\n <img src=\"/img/local_parameter_en.pn [...]
"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 8b2f6e5..1c656d5 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/local.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/local.html
@@ -12,16 +12,16 @@
<body>
<div id="root"><div class="md2html docs-page" data-reactroot=""><header class="header-container header-container-dark"><div class="header-body"><span class="mobile-menu-btn mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div class="search search-dark"><span class="icon-search"></span></div><span class="language-switch language-switch-dark">中</span><div class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant- [...]
<h2>Scope</h2>
-<p>Parameters configured on the task definition dialog, the scope of this parameter only for this task, but if you configured follow <a href="context.md">Parameter Context</a>, it could passed follow task.</p>
+<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>
-<p>The approach to set local parameters is, double-click on any node while defining the workflow and click the '+' button next to the 'Custom Parameters':</p>
+<p>Usage of local parameters is: at the task define page, click the '+' beside the 'Custom Parameters' and fill in the key and value to save:</p>
<p align="center">
<img src="/img/supplement_local_parameter_en.png" width="80%" />
</p>
<p align="center">
<img src="/img/global_parameter_en.png" width="80%" />
</p>
-<p>If you want to call the <a href="built-in.md">built-in parameter</a> in the local parameters, fill in the value corresponding to the built-in parameters in <code>value</code>, as in the above figure, <code>${biz_date}</code> and <code>${curdate}</code></p>
+<p>If you want to call the <a href="built-in.md">built-in parameter</a> in the local parameters, fill in thevalue of built-in parameters in <code>value</code>. As in the above figure, <code>${biz_date}</code> and <code>${curdate}</code>.</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="//cdn.jsdelivr.net/npm/react@15.6.2/dist/react-with-addons.min.js"></script>
<script src="//cdn.jsdelivr.net/npm/react-dom@15.6.2/dist/react-dom.min.js"></script>
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 8093b43..6009565 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 dialog, the scope of this parameter only for this task, but if you configured follow <a href=\"context.md\">Parameter Context</a>, it could passed follow task.</p>\n<h2>Usage</h2>\n<p>The approach to set local parameters is, double-click on any node while defining the workflow and click the '+' button next to the 'Custom Parameters':</p>\n<p align=\"center\">\n <img src=\"/img/suppl [...]
+ "__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<p>Usage of local parameters is: at the task define page, click the '+' beside the 'Custom Parameters' and fill in the key and value to save:</p>\n<p align=\"center\">\n <img src=\ [...]
"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 406a069..7eef68b 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/priority.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/priority.html
@@ -11,30 +11,30 @@
</head>
<body>
<div id="root"><div class="md2html docs-page" data-reactroot=""><header class="header-container header-container-dark"><div class="header-body"><span class="mobile-menu-btn mobile-menu-btn-dark"></span><a href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div class="search search-dark"><span class="icon-search"></span></div><span class="language-switch language-switch-dark">中</span><div class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant- [...]
-<p>DolphinScheduler definition of parameter values involved in may come from three types:</p>
+<p>DolphinScheduler has three parameter types:</p>
<ul>
-<li><a href="global.md">Global Parameter</a>: Parameters defined when the workflow saves page definitions</li>
-<li><a href="context.md">Parameter Context</a>: Parameters passed by upstream nodes</li>
-<li><a href="local.md">Local Parameter</a>：The node's own parameters, which is the parameters defined by the user in [Custom Parameters]. The user can define the value of this part of the parameters at the time of workflow definition.</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>Because the value of a parameter has multiple sources, when the parameter name is the same, there needs to be a parameter priority problem. The priority of DolphinScheduler parameters from high to low is: <code>Global Parameter > Parameter Context > Local Parameter</code></p>
-<p>In the case of parameters passed by the upstream task, there may be multiple tasks upstream to pass parameters to the downstream. When the parameter names passed upstream are the same:</p>
+<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>Global Parameter > Parameter Context > Local 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 will preferentially use parameters with non-empty values</li>
-<li>If there are multiple parameters with non-empty values, sort according to the completion time of the upstream task, and select the parameter corresponding to the upstream task with the earliest completion time</li>
+<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>For example, the relationships are shown in the figures below:</p>
-<p>1: The first case is explained by the shell nodes.</p>
+<p>Followings are examples shows task parameters priority problems:#############</p>
+<p>1: Use shell nodes to explain the first case.</p>
<p><img src="/img/globalParam/image-20210723102938239.png" alt="png01"></p>
-<p>The [useParam] node can use the parameters which is set in the [createParam] node. The [useParam] node does not have a dependency on the [noUseParam] node, so it does not get the parameters of the [noUseParam] node. The above picture is just an example of a shell node, other types of nodes have the same usage rules.</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 shell example here.</p>
<p><img src="/img/globalParam/image-20210723103316896.png" alt="png02"></p>
-<p>Among all, the [createParam] node can use parameters directly. In addition, the node sets two parameters named "key" and "key1". Here the user defines a parameter named "key1" with the same name as the one passed by the upstream node and copies the value "12". However, due to the priority we set, the value "12" here would be discarded and the parameter value set by the upstream node would be finally used.</p>
-<p>2: Let's explain another situation in SQL nodes.</p>
+<p>The [createParam] node can use parameters directly. In addition, the node creates two parameters named "key" and "key1" and "key1" has the same name as the one passed by the upstream node and assign value "12". However, due to the priority rules, the value assignment "12" is discarded and the value from the upstream node is finally used.</p>
+<p>2: Use SQL nodes to explain another case.</p>
<p><img src="/img/globalParam/image-20210723103937052.png" alt="png03"></p>
<p>The definition of the [use_create] node is as follows:</p>
<p><img src="/img/globalParam/image-20210723104411489.png" alt="png04"></p>
-<p>"status" is the own parameters of the node set by the current node. However, the user also sets the "status" parameter when saving, assigning its value to -1. Then the value of status will be -1 with higher priority when the SQL is executed. The value of the node's own variable is discarded.</p>
+<p>"status" is the own parameters of the node and set by the current node. However, the user also sets the "status" parameter when saving, assigning its value to -1. Then the value of status will be -1 with higher priority when the SQL is executed. The value of the node's own variable 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="//cdn.jsdelivr.net/npm/react@15.6.2/dist/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 582c8f4..f7ce3bf 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 definition of parameter values involved in may come from three types:</p>\n<ul>\n<li><a href=\"global.md\">Global Parameter</a>: Parameters defined when the workflow saves page definitions</li>\n<li><a href=\"context.md\">Parameter Context</a>: Parameters passed by upstream nodes</li>\n<li><a href=\"local.md\">Local Parameter</a>：The node's own parameters, which is the parameters defined by the user in [Custom Parameters]. T [...]
+ "__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 [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/parameter/priority.html",
"meta": {}
}
\ No newline at end of file
diff --git a/zh-cn/docs/dev/user_doc/guide/parameter/priority.html b/zh-cn/docs/dev/user_doc/guide/parameter/priority.html
index f729a30..33dad6c 100644
--- a/zh-cn/docs/dev/user_doc/guide/parameter/priority.html
+++ b/zh-cn/docs/dev/user_doc/guide/parameter/priority.html
@@ -29,7 +29,7 @@
<img src="/img/globalParam/image-20210723102938239.png" alt="image-20210723102938239" style="zoom:50%;" />
<p>节点 【useParam】可以使用到节点【createParam】中设置的变量。而节点 【useParam】与节点【noUseParam】中并没有依赖关系，所以并不会获取到节点【noUseParam】的变量。上图中只是以 shell 节点作为例子，其他类型节点具有相同的使用规则。</p>
<img src="/img/globalParam/image-20210723103316896.png" alt="image-20210723103316896" style="zoom:50%;" />
-<p>其中节点【createParam】在使用变量时直接使用即可。另外该节点设置了 "key" 和 "key1" 两个变量，这里用户用定义了一个与上游节点传递的变量名相同的变量 key1，并且复制了值为 "12"，但是由于我们设置的优先级的关系，这里的值 "12" 会被抛弃，最终使用上游节点设置的变量值。</p>
+<p>其中节点【createParam】在使用变量时直接使用即可。另外该节点设置了 "key" 和 "key1" 两个变量，这里用户用定义了一个与上游节点传递的变量名相同的变量 key1，并且赋值为 "12"，但是由于我们设置的优先级的关系，这里的值 "12" 会被抛弃，最终使用上游节点设置的变量值。</p>
<p>2：我们再以 sql 节点来解释另外一种情况</p>
<img src="/img/globalParam/image-20210723103937052.png" alt="image-20210723103937052" style="zoom:50%;" />
<p>节点【use_create】的定义如下：</p>
diff --git a/zh-cn/docs/dev/user_doc/guide/parameter/priority.json b/zh-cn/docs/dev/user_doc/guide/parameter/priority.json
index 8186fc7..37db34c 100644
--- a/zh-cn/docs/dev/user_doc/guide/parameter/priority.json
+++ b/zh-cn/docs/dev/user_doc/guide/parameter/priority.json
@@ -1,6 +1,6 @@
{
"filename": "priority.md",
- "__html": "<h1>参数优先级</h1>\n<p>DolphinScheduler 中所涉及的参数值的定义可能来自三种类型：</p>\n<ul>\n<li><a href=\"global.md\">全局参数</a>：在工作流保存页面定义时定义的变量</li>\n<li><a href=\"context.md\">上游任务传递的参数</a>：上游任务传递过来的参数</li>\n<li><a href=\"local.md\">本地参数</a>：节点的自有变量，用户在“自定义参数”定义的变量，并且用户可以在工作流定义时定义该部分变量的值</li>\n</ul>\n<p>因为参数的值存在多个来源，当参数名相同时，就需要会存在参数优先级的问题。DolphinScheduler 参数的优先级从高到低为：<code>全局参数 > 上游任务传递的参数 > 本地参数</code></p>\n<p>在上游任务传递的参数的情况下，由于上游可能存在多个任务向下游传递参数。当上游传递的参数名称相同时：</p>\n<ul>\n<li>下游节点会优先使用值为非空的参数 [...]
+ "__html": "<h1>参数优先级</h1>\n<p>DolphinScheduler 中所涉及的参数值的定义可能来自三种类型：</p>\n<ul>\n<li><a href=\"global.md\">全局参数</a>：在工作流保存页面定义时定义的变量</li>\n<li><a href=\"context.md\">上游任务传递的参数</a>：上游任务传递过来的参数</li>\n<li><a href=\"local.md\">本地参数</a>：节点的自有变量，用户在“自定义参数”定义的变量，并且用户可以在工作流定义时定义该部分变量的值</li>\n</ul>\n<p>因为参数的值存在多个来源，当参数名相同时，就需要会存在参数优先级的问题。DolphinScheduler 参数的优先级从高到低为：<code>全局参数 > 上游任务传递的参数 > 本地参数</code></p>\n<p>在上游任务传递的参数的情况下，由于上游可能存在多个任务向下游传递参数。当上游传递的参数名称相同时：</p>\n<ul>\n<li>下游节点会优先使用值为非空的参数 [...]
"link": "/dist/zh-cn/docs/dev/user_doc/guide/parameter/priority.html",
"meta": {}
}
\ No newline at end of file