[dolphinscheduler-website] branch asf-site updated: Automated deployment: 678ab6a4773118b398ba57430aa0cd6bdc09b9ec

Thu, 21 Oct 2021 20:43:18 -0700 

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 0a71e03  Automated deployment: 678ab6a4773118b398ba57430aa0cd6bdc09b9ec
0a71e03 is described below

commit 0a71e0350c2db0407ed950e8d6a188463e56ce37
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Oct 22 03:42:12 2021 +0000

    Automated deployment: 678ab6a4773118b398ba57430aa0cd6bdc09b9ec
---
 en-us/docs/dev/user_doc/globalParams.html            | 4 ++--
 en-us/docs/dev/user_doc/globalParams.json            | 2 +-
 en-us/docs/dev/user_doc/guide/parameter/context.html | 2 +-
 en-us/docs/dev/user_doc/guide/parameter/context.json | 2 +-
 zh-cn/docs/dev/user_doc/globalParams.html            | 4 ++--
 zh-cn/docs/dev/user_doc/globalParams.json            | 2 +-
 zh-cn/docs/dev/user_doc/guide/parameter/context.html | 2 +-
 zh-cn/docs/dev/user_doc/guide/parameter/context.json | 2 +-
 8 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/en-us/docs/dev/user_doc/globalParams.html 
b/en-us/docs/dev/user_doc/globalParams.html
index a1c6c9f..33567f2 100644
--- a/en-us/docs/dev/user_doc/globalParams.html
+++ b/en-us/docs/dev/user_doc/globalParams.html
@@ -42,8 +42,8 @@
 </code></pre>
 <h6>SHELL node</h6>
 <p>The result of the processor execution is returned as 
Map&lt;String,String&gt;.</p>
-<p>The user needs to define $setValue(key=value) in the output when defining 
the shell script.</p>
-<p>Remove $setValue() when processing parameters, split by &quot;=&quot;, with 
the 0th being the key and the 1st being the value.</p>
+<p>The user needs to define ${setValue(key=value)} in the output when defining 
the shell script.</p>
+<p>Remove ${setValue()} when processing parameters, split by &quot;=&quot;, 
with the 0th being the key and the 1st being the value.</p>
 <p>Similarly match the OUT parameter name and key defined by the user when 
defining the task, and use value as the value of that parameter.</p>
 <ul>
 <li>Return parameter processing</li>
diff --git a/en-us/docs/dev/user_doc/globalParams.json 
b/en-us/docs/dev/user_doc/globalParams.json
index 1e573cf..d2b1ba8 100644
--- a/en-us/docs/dev/user_doc/globalParams.json
+++ b/en-us/docs/dev/user_doc/globalParams.json
@@ -1,6 +1,6 @@
 {
   "filename": "globalParams.md",
-  "__html": "<h1>Development documentation</h1>\n<p>After the user defines the 
parameter with the direction OUT, it is saved in the localParam of the 
task.</p>\n<h5>The use of parameters:</h5>\n<p>Getting the direct predecessor 
node preTasks of the current taskInstance to be created from the DAG, get the 
varPool of preTasks, merge this varPool (List) into one varPool, and in the 
merging process, if parameters with the same parameter name are found, they 
will be handled according to the f [...]
+  "__html": "<h1>Development documentation</h1>\n<p>After the user defines the 
parameter with the direction OUT, it is saved in the localParam of the 
task.</p>\n<h5>The use of parameters:</h5>\n<p>Getting the direct predecessor 
node preTasks of the current taskInstance to be created from the DAG, get the 
varPool of preTasks, merge this varPool (List) into one varPool, and in the 
merging process, if parameters with the same parameter name are found, they 
will be handled according to the f [...]
   "link": "/dist/en-us/docs/dev/user_doc/globalParams.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 eae292b..39bf448 100644
--- a/en-us/docs/dev/user_doc/guide/parameter/context.html
+++ b/en-us/docs/dev/user_doc/guide/parameter/context.html
@@ -40,7 +40,7 @@
 <p><img 
src="https://dolphinscheduler.apache.org/img/globalParam/image-20210723105255850.png";
 alt="png08"></p>
 <p>There is only the value of &quot;id&quot;. Although the user-defined sql 
looks up the fields &quot;id&quot; and &quot;database_name&quot;, only one 
parameter is set because only one parameter &quot;id&quot; is defined for out. 
For display reasons, the length of the list is already checked for you here as 
10.</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>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>For example, in the figure below:</p>
 <p><img 
src="https://dolphinscheduler.apache.org/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>
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 11b1556..1b448e4 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>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  [...]
   "link": "/dist/en-us/docs/dev/user_doc/guide/parameter/context.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/zh-cn/docs/dev/user_doc/globalParams.html 
b/zh-cn/docs/dev/user_doc/globalParams.html
index abad2cb..51e7d13 100644
--- a/zh-cn/docs/dev/user_doc/globalParams.html
+++ b/zh-cn/docs/dev/user_doc/globalParams.html
@@ -49,8 +49,8 @@
 </code></pre>
 <h6>SHELL 节点：</h6>
 <p>processor 执行后的结果返回为 Map&lt;String,String&gt;</p>
-<p>用户在定义 shell 脚本时需要在输出中定义 $setValue(key=value)</p>
-<p>在参数处理时去掉 $setValue()，按照 “=” 进行拆分，第 0 个为 key，第 1 个为 value。</p>
+<p>用户在定义 shell 脚本时需要在输出中定义 ${setValue(key=value)}</p>
+<p>在参数处理时去掉 ${setValue()}，按照 “=” 进行拆分，第 0 个为 key，第 1 个为 value。</p>
 <p>同样匹配用户定义 task 时定义的 OUT 参数名与 key，将 value 作为该参数的值。</p>
 <ul>
 <li>
diff --git a/zh-cn/docs/dev/user_doc/globalParams.json 
b/zh-cn/docs/dev/user_doc/globalParams.json
index 4659873..63f6707 100644
--- a/zh-cn/docs/dev/user_doc/globalParams.json
+++ b/zh-cn/docs/dev/user_doc/globalParams.json
@@ -1,6 +1,6 @@
 {
   "filename": "globalParams.md",
-  "__html": "<h1>开发文档</h1>\n<p>用户在定义方向为 OUT 的参数后，会保存在 task 的 localParam 
中。</p>\n<h5>参数的使用：</h5>\n<p>从 DAG 中获取当前需要创建的 taskInstance 的直接前置节点 preTasks，获取 
preTasks 的 varPool，将该 varPool（List<Property>）合并为一个 
varPool，在合并过程中，如果发现有相同的变量名的变量，按照以下逻辑处理</p>\n<ol>\n<li>\n<p>若所有的值都是 null，则合并后的值为 
null</p>\n</li>\n<li>\n<p>若有且只有一个值为非 null，则合并后的值为该非 null 
值</p>\n</li>\n<li>\n<p>若所有的值都不是 null，则根据取 varPool 的 taskInstance 的 endtime 
最早的一个</p>\n</li>\n</ol>\n<p>在合并过程中将所有的合并过来的 Property 的方向更新为 IN</p>\n<p>合并后的结果保存 
[...]
+  "__html": "<h1>开发文档</h1>\n<p>用户在定义方向为 OUT 的参数后，会保存在 task 的 localParam 
中。</p>\n<h5>参数的使用：</h5>\n<p>从 DAG 中获取当前需要创建的 taskInstance 的直接前置节点 preTasks，获取 
preTasks 的 varPool，将该 varPool（List<Property>）合并为一个 
varPool，在合并过程中，如果发现有相同的变量名的变量，按照以下逻辑处理</p>\n<ol>\n<li>\n<p>若所有的值都是 null，则合并后的值为 
null</p>\n</li>\n<li>\n<p>若有且只有一个值为非 null，则合并后的值为该非 null 
值</p>\n</li>\n<li>\n<p>若所有的值都不是 null，则根据取 varPool 的 taskInstance 的 endtime 
最早的一个</p>\n</li>\n</ol>\n<p>在合并过程中将所有的合并过来的 Property 的方向更新为 IN</p>\n<p>合并后的结果保存 
[...]
   "link": "/dist/zh-cn/docs/dev/user_doc/globalParams.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/zh-cn/docs/dev/user_doc/guide/parameter/context.html 
b/zh-cn/docs/dev/user_doc/guide/parameter/context.html
index 2bda0e0..ca9b355 100644
--- a/zh-cn/docs/dev/user_doc/guide/parameter/context.html
+++ b/zh-cn/docs/dev/user_doc/guide/parameter/context.html
@@ -42,7 +42,7 @@
 <p>这里只有 &quot;id&quot; 的值。尽管用户定义的 sql 查到的是 &quot;id&quot; 和 
&quot;database_name&quot; 两个字段，但是由于只定义了一个为 out 的变量 
&quot;id&quot;，所以只会设置一个变量。由于显示的原因，这里已经替您查好了该 list 的长度为 10。</p>
 <h3>SHELL</h3>
 <p>prop 为用户指定；方向选择为 OUT，只有当方向为 OUT 时才会被定义为变量输出；数据类型可以根据需要选择不同数据结构；value 
部分不需要填写。</p>
-<p>用户需要传递参数，在定义 shell 脚本时，需要输出格式为 $setValue(key=value) 的语句，key 为对应参数的 
prop，value 为该参数的值。</p>
+<p>用户需要传递参数，在定义 shell 脚本时，需要输出格式为 ${setValue(key=value)} 的语句，key 为对应参数的 
prop，value 为该参数的值。</p>
 <p>例如下图中：</p>
 <img src="/img/globalParam/image-20210723101242216.png" 
alt="image-20210723101242216" style="zoom:50%;" />
 <p>shell 节点定义时当日志检测到 ${setValue(key=value1)} 的格式时，会将 value1 赋值给 
key，下游节点便可以直接使用变量 key 的值。同样，您可以在【工作流实例】页面，找到对应的节点实例，便可以查看该变量的值。</p>
diff --git a/zh-cn/docs/dev/user_doc/guide/parameter/context.json 
b/zh-cn/docs/dev/user_doc/guide/parameter/context.json
index f478e26..22132f4 100644
--- a/zh-cn/docs/dev/user_doc/guide/parameter/context.json
+++ b/zh-cn/docs/dev/user_doc/guide/parameter/context.json
@@ -1,6 +1,6 @@
 {
   "filename": "context.md",
-  "__html": "<h1>参数的引用</h1>\n<p>DolphinScheduler 
提供参数间相互引用的能力，包括：本地参数引用全局参数、上下游参数传递。因为有引用的存在，就涉及当参数名相同时，参数的优先级问题，详见<a 
href=\"priority.md\">参数优先级</a></p>\n<h2>本地任务引用全局参数</h2>\n<p>本地任务引用全局参数的前提是，你已经定义了<a
 href=\"global.md\">全局参数</a>，使用方式和<a 
href=\"local.md\">本地参数</a>中的使用方式类似，但是参数的值需要配置成全局参数中的key</p>\n<p><img 
src=\"/img/global_parameter.png\" 
alt=\"parameter-call-global-in-local\"></p>\n<p>如上图中的<code>${biz_date}</code>以及<code>${curdate}</code>，就是本地参数引用全局参数的例子。观察上图的最后一行，local_param_bizdate通过$
 [...]
+  "__html": "<h1>参数的引用</h1>\n<p>DolphinScheduler 
提供参数间相互引用的能力，包括：本地参数引用全局参数、上下游参数传递。因为有引用的存在，就涉及当参数名相同时，参数的优先级问题，详见<a 
href=\"priority.md\">参数优先级</a></p>\n<h2>本地任务引用全局参数</h2>\n<p>本地任务引用全局参数的前提是，你已经定义了<a
 href=\"global.md\">全局参数</a>，使用方式和<a 
href=\"local.md\">本地参数</a>中的使用方式类似，但是参数的值需要配置成全局参数中的key</p>\n<p><img 
src=\"/img/global_parameter.png\" 
alt=\"parameter-call-global-in-local\"></p>\n<p>如上图中的<code>${biz_date}</code>以及<code>${curdate}</code>，就是本地参数引用全局参数的例子。观察上图的最后一行，local_param_bizdate通过$
 [...]
   "link": "/dist/zh-cn/docs/dev/user_doc/guide/parameter/context.html",
   "meta": {}
 }
\ No newline at end of file

Reply via email to