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 df789188c Automated deployment:
28448c5195d1af7def227719db7f25b902fc2bc3
df789188c is described below
commit df789188c043af73e7fc3086dfadfc33aacb5f2a
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Apr 6 05:05:57 2022 +0000
Automated deployment: 28448c5195d1af7def227719db7f25b902fc2bc3
---
en-us/docs/2.0.0/user_doc/guide/parameter/context.html | 2 +-
en-us/docs/2.0.0/user_doc/guide/parameter/context.json | 2 +-
en-us/docs/2.0.1/user_doc/guide/parameter/context.html | 2 +-
en-us/docs/2.0.1/user_doc/guide/parameter/context.json | 2 +-
en-us/docs/2.0.2/user_doc/guide/parameter/context.html | 2 +-
en-us/docs/2.0.2/user_doc/guide/parameter/context.json | 2 +-
en-us/docs/2.0.3/user_doc/guide/parameter/context.html | 2 +-
en-us/docs/2.0.3/user_doc/guide/parameter/context.json | 2 +-
en-us/docs/2.0.5/user_doc/guide/parameter/context.html | 2 +-
en-us/docs/2.0.5/user_doc/guide/parameter/context.json | 2 +-
en-us/docs/latest/user_doc/guide/parameter/context.html | 2 +-
en-us/docs/latest/user_doc/guide/parameter/context.json | 2 +-
12 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/en-us/docs/2.0.0/user_doc/guide/parameter/context.html
b/en-us/docs/2.0.0/user_doc/guide/parameter/context.html
index 2150a2009..ca3d4e36c 100644
--- a/en-us/docs/2.0.0/user_doc/guide/parameter/context.html
+++ b/en-us/docs/2.0.0/user_doc/guide/parameter/context.html
@@ -41,7 +41,7 @@
<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>
<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>For example, <code>echo '${setValue (trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
+<p>For example, <code>echo '${setValue(trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
<p>When the shell node is defined, when the log detects the format of
${setValue (key = value1)}, value1 will be assigned to the key, and the
downstream node can directly use the value of the variable key. Similarly, you
can find the corresponding node instance on the workflow instance page to view
the value of the variable.</p>
<img src="/img/globalParam/use-parameter-shell.png" alt="use-parameter-shell"
style="zoom:50%;" />
diff --git a/en-us/docs/2.0.0/user_doc/guide/parameter/context.json
b/en-us/docs/2.0.0/user_doc/guide/parameter/context.json
index 4aaa23686..33595a949 100644
--- a/en-us/docs/2.0.0/user_doc/guide/parameter/context.json
+++ b/en-us/docs/2.0.0/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/2.0.0/user_doc/guide/parameter/context.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/2.0.1/user_doc/guide/parameter/context.html
b/en-us/docs/2.0.1/user_doc/guide/parameter/context.html
index cb1527eb8..771001e0c 100644
--- a/en-us/docs/2.0.1/user_doc/guide/parameter/context.html
+++ b/en-us/docs/2.0.1/user_doc/guide/parameter/context.html
@@ -41,7 +41,7 @@
<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>
<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>For example, <code>echo '${setValue (trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
+<p>For example, <code>echo '${setValue(trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
<p>When the shell node is defined, when the log detects the format of
${setValue (key = value1)}, value1 will be assigned to the key, and the
downstream node can directly use the value of the variable key. Similarly, you
can find the corresponding node instance on the workflow instance page to view
the value of the variable.</p>
<img src="/img/globalParam/use-parameter-shell.png" alt="use-parameter-shell"
style="zoom:50%;" />
diff --git a/en-us/docs/2.0.1/user_doc/guide/parameter/context.json
b/en-us/docs/2.0.1/user_doc/guide/parameter/context.json
index e4075df3c..d050f6256 100644
--- a/en-us/docs/2.0.1/user_doc/guide/parameter/context.json
+++ b/en-us/docs/2.0.1/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/2.0.1/user_doc/guide/parameter/context.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/2.0.2/user_doc/guide/parameter/context.html
b/en-us/docs/2.0.2/user_doc/guide/parameter/context.html
index c36244ffd..8148490e8 100644
--- a/en-us/docs/2.0.2/user_doc/guide/parameter/context.html
+++ b/en-us/docs/2.0.2/user_doc/guide/parameter/context.html
@@ -41,7 +41,7 @@
<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>
<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>For example, <code>echo '${setValue (trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
+<p>For example, <code>echo '${setValue(trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
<p>When the shell node is defined, when the log detects the format of
${setValue (key = value1)}, value1 will be assigned to the key, and the
downstream node can directly use the value of the variable key. Similarly, you
can find the corresponding node instance on the workflow instance page to view
the value of the variable.</p>
<img src="/img/globalParam/use-parameter-shell.png" alt="use-parameter-shell"
style="zoom:50%;" />
diff --git a/en-us/docs/2.0.2/user_doc/guide/parameter/context.json
b/en-us/docs/2.0.2/user_doc/guide/parameter/context.json
index 574a2de28..7a2799e50 100644
--- a/en-us/docs/2.0.2/user_doc/guide/parameter/context.json
+++ b/en-us/docs/2.0.2/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/2.0.2/user_doc/guide/parameter/context.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/2.0.3/user_doc/guide/parameter/context.html
b/en-us/docs/2.0.3/user_doc/guide/parameter/context.html
index d9e769b28..b07fb3e9c 100644
--- a/en-us/docs/2.0.3/user_doc/guide/parameter/context.html
+++ b/en-us/docs/2.0.3/user_doc/guide/parameter/context.html
@@ -41,7 +41,7 @@
<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>
<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>For example, <code>echo '${setValue (trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
+<p>For example, <code>echo '${setValue(trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
<p>When the shell node is defined, when the log detects the format of
${setValue (key = value1)}, value1 will be assigned to the key, and the
downstream node can directly use the value of the variable key. Similarly, you
can find the corresponding node instance on the workflow instance page to view
the value of the variable.</p>
<img src="/img/globalParam/use-parameter-shell.png" alt="use-parameter-shell"
style="zoom:50%;" />
diff --git a/en-us/docs/2.0.3/user_doc/guide/parameter/context.json
b/en-us/docs/2.0.3/user_doc/guide/parameter/context.json
index 22086a7a5..bc99a03fe 100644
--- a/en-us/docs/2.0.3/user_doc/guide/parameter/context.json
+++ b/en-us/docs/2.0.3/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/2.0.3/user_doc/guide/parameter/context.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/2.0.5/user_doc/guide/parameter/context.html
b/en-us/docs/2.0.5/user_doc/guide/parameter/context.html
index 7197aeb74..210b20209 100644
--- a/en-us/docs/2.0.5/user_doc/guide/parameter/context.html
+++ b/en-us/docs/2.0.5/user_doc/guide/parameter/context.html
@@ -41,7 +41,7 @@
<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>
<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>For example, <code>echo '${setValue (trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
+<p>For example, <code>echo '${setValue(trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
<p>When the shell node is defined, when the log detects the format of
${setValue (key = value1)}, value1 will be assigned to the key, and the
downstream node can directly use the value of the variable key. Similarly, you
can find the corresponding node instance on the workflow instance page to view
the value of the variable.</p>
<img src="/img/globalParam/use-parameter-shell.png" alt="use-parameter-shell"
style="zoom:50%;" />
diff --git a/en-us/docs/2.0.5/user_doc/guide/parameter/context.json
b/en-us/docs/2.0.5/user_doc/guide/parameter/context.json
index 6bbf26a75..378a6878d 100644
--- a/en-us/docs/2.0.5/user_doc/guide/parameter/context.json
+++ b/en-us/docs/2.0.5/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/2.0.5/user_doc/guide/parameter/context.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/latest/user_doc/guide/parameter/context.html
b/en-us/docs/latest/user_doc/guide/parameter/context.html
index 7197aeb74..210b20209 100644
--- a/en-us/docs/latest/user_doc/guide/parameter/context.html
+++ b/en-us/docs/latest/user_doc/guide/parameter/context.html
@@ -41,7 +41,7 @@
<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>
<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>For example, <code>echo '${setValue (trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
+<p>For example, <code>echo '${setValue(trans = Hello trans)}'</code>, set
"trans" to "Hello trans", and the variable trans can be
used in downstream tasks:</p>
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
<p>When the shell node is defined, when the log detects the format of
${setValue (key = value1)}, value1 will be assigned to the key, and the
downstream node can directly use the value of the variable key. Similarly, you
can find the corresponding node instance on the workflow instance page to view
the value of the variable.</p>
<img src="/img/globalParam/use-parameter-shell.png" alt="use-parameter-shell"
style="zoom:50%;" />
diff --git a/en-us/docs/latest/user_doc/guide/parameter/context.json
b/en-us/docs/latest/user_doc/guide/parameter/context.json
index 6bbf26a75..378a6878d 100644
--- a/en-us/docs/latest/user_doc/guide/parameter/context.json
+++ b/en-us/docs/latest/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/2.0.5/user_doc/guide/parameter/context.html",
"meta": {}
}
\ No newline at end of file
