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 7f62e59b4 Automated deployment:
1da5b7e9900d7f2819b185dfca1076c2bc384958
7f62e59b4 is described below
commit 7f62e59b4ae162f854f2c9ce7ac553fa0aa3abd1
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jul 4 05:14:16 2022 +0000
Automated deployment: 1da5b7e9900d7f2819b185dfca1076c2bc384958
---
.../dev/user_doc/guide/project/project-list.html | 45 ++++++++++++++--
.../dev/user_doc/guide/project/project-list.json | 2 +-
.../dev/user_doc/guide/project/task-instance.html | 4 +-
.../dev/user_doc/guide/project/task-instance.json | 2 +-
.../guide/project/workflow-definition.html | 58 ++++++++++-----------
.../guide/project/workflow-definition.json | 2 +-
.../user_doc/guide/project/workflow-instance.html | 10 ++--
.../user_doc/guide/project/workflow-instance.json | 2 +-
.../{task-instance.html => workflow-relation.html} | 17 ++----
.../user_doc/guide/project/workflow-relation.json | 6 +++
en-us/docs/dev/user_doc/guide/task/conditions.html | 2 +-
en-us/docs/dev/user_doc/guide/task/conditions.json | 2 +-
en-us/docs/dev/user_doc/guide/task/emr.html | 2 +-
en-us/docs/dev/user_doc/guide/task/emr.json | 2 +-
en-us/docs/dev/user_doc/guide/task/flink.html | 30 -----------
en-us/docs/dev/user_doc/guide/task/flink.json | 2 +-
en-us/docs/dev/user_doc/guide/task/http.html | 2 +-
en-us/docs/dev/user_doc/guide/task/http.json | 2 +-
en-us/docs/dev/user_doc/guide/task/jupyter.html | 4 +-
en-us/docs/dev/user_doc/guide/task/jupyter.json | 2 +-
en-us/docs/dev/user_doc/guide/task/mlflow.html | 20 ++++++-
en-us/docs/dev/user_doc/guide/task/mlflow.json | 2 +-
img/new_ui/dev/project/work-relation.png | Bin 0 -> 64892 bytes
23 files changed, 121 insertions(+), 99 deletions(-)
diff --git a/en-us/docs/dev/user_doc/guide/project/project-list.html
b/en-us/docs/dev/user_doc/guide/project/project-list.html
index 9a39a4acb..ede5f1fad 100644
--- a/en-us/docs/dev/user_doc/guide/project/project-list.html
+++ b/en-us/docs/dev/user_doc/guide/project/project-list.html
@@ -10,10 +10,45 @@
<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>This page describes details regarding Project screen in Apache
DolphinScheduler. Here, you will see all the functions which can be handled in
this screen. The following table explains commonly used terms in Apache
DolphinScheduler:</p>
+<table>
+<thead>
+<tr>
+<th>Glossary</th>
+<th></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>DAG</td>
+<td>Tasks in a workflow are assembled in form of Directed Acyclic Graph (DAG).
A topological traversal is performed from nodes with zero degrees of entry
until there are no subsequent nodes.</td>
+</tr>
+<tr>
+<td>Workflow Definition</td>
+<td>Visualization formed by dragging task nodes and establishing task node
associations (DAG).</td>
+</tr>
+<tr>
+<td>Workflow Instance</td>
+<td>Instantiation of the workflow definition, which can be generated by manual
start or scheduled scheduling. Each time the process definition runs, a
workflow instance is generated.</td>
+</tr>
+<tr>
+<td>Workflow Relation</td>
+<td>Shows dynamic status of all the workflows in a project.</td>
+</tr>
+<tr>
+<td>Task</td>
+<td>Task is a discrete action in a Workflow. Apache DolphinScheduler supports
SHELL, SQL, SUB_PROCESS (sub-process), PROCEDURE, MR, SPARK, PYTHON, DEPENDENT
( depends), and plans to support dynamic plug-in expansion, (SUB_PROCESS). It
is also a separate process definition that can be started and executed
separately.</td>
+</tr>
+<tr>
+<td>Task Instance</td>
+<td>Instantiation of the task node in the process definition, which identifies
the specific task execution status.</td>
+</tr>
+</tbody>
+</table>
<h2>Create Project</h2>
<ul>
-<li>Click "Project Management" to enter the project management page,
click the "Create Project" button, enter the project name, project
description, and click "Submit" to create a new project.</li>
+<li>Click <code>Project Management</code> to enter the project management
page, click the <code>Create Project</code> button, enter the project name,
project description, and click "Submit" to create a new project.</li>
</ul>
<p><img src="/img/new_ui/dev/project/project-list.png" alt="project-list"></p>
<h2>Project Home</h2>
@@ -22,13 +57,13 @@
<p>Click the project name link on the project management page to enter the
project home page, as shown in the figure below, the project home page contains
the task status statistics, process status statistics, and workflow definition
statistics of the project. The introduction for those metrics:</p>
</li>
<li>
-<p>Task status statistics: within the specified time range, count the number
of task instances status as successful submission, running, ready to pause,
pause, ready to stop, stop, failure, success, need fault tolerance, kill and
waiting threads</p>
+<p>Task status statistics: Within the specified time range, count the number
of task instances status as successful submission, running, ready to pause,
pause, ready to stop, stop, failure, success, need fault tolerance, kill and
waiting threads</p>
</li>
<li>
-<p>Process status statistics: within the specified time range, count the
number of workflow instances status as submission success, running, ready to
pause, pause, ready to stop, stop, failure, success, need fault tolerance, kill
and waiting threads</p>
+<p>Process status statistics: Within the specified time range, count the
number of workflow instances status as submission success, running, ready to
pause, pause, ready to stop, stop, failure, success, need fault tolerance, kill
and waiting threads</p>
</li>
<li>
-<p>Workflow definition statistics: count the workflow definitions created by
this user and granted by the administrator</p>
+<p>Workflow definition statistics: Count the workflow definitions created by
this user and granted by the administrator</p>
</li>
</ul>
<p><img src="/img/new_ui/dev/project/project-overview.png"
alt="project-overview"></p>
diff --git a/en-us/docs/dev/user_doc/guide/project/project-list.json
b/en-us/docs/dev/user_doc/guide/project/project-list.json
index 2c4514b55..efb46c185 100644
--- a/en-us/docs/dev/user_doc/guide/project/project-list.json
+++ b/en-us/docs/dev/user_doc/guide/project/project-list.json
@@ -1,6 +1,6 @@
{
"filename": "project-list.md",
- "__html": "<h1>Project Management</h1>\n<h2>Create
Project</h2>\n<ul>\n<li>Click "Project Management" to enter the
project management page, click the "Create Project" button, enter the
project name, project description, and click "Submit" to create a new
project.</li>\n</ul>\n<p><img src=\"/img/new_ui/dev/project/project-list.png\"
alt=\"project-list\"></p>\n<h2>Project Home</h2>\n<ul>\n<li>\n<p>Click the
project name link on the project management page to [...]
+ "__html": "<h1>Project</h1>\n<p>This page describes details regarding
Project screen in Apache DolphinScheduler. Here, you will see all the functions
which can be handled in this screen. The following table explains commonly used
terms in Apache
DolphinScheduler:</p>\n<table>\n<thead>\n<tr>\n<th>Glossary</th>\n<th></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>DAG</td>\n<td>Tasks
in a workflow are assembled in form of Directed Acyclic Graph (DAG). A
topological traversal is performed from [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/project/project-list.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/project/task-instance.html
b/en-us/docs/dev/user_doc/guide/project/task-instance.html
index fe00e3688..2c5272642 100644
--- a/en-us/docs/dev/user_doc/guide/project/task-instance.html
+++ b/en-us/docs/dev/user_doc/guide/project/task-instance.html
@@ -12,11 +12,11 @@
<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=" [...]
<ul>
-<li>Click Project Management -> Workflow -> Task Instance. Enter the
task instance page, as shown in the figure below, click workflow instance name,
you can jump to the workflow instance DAG chart to view the task status.</li>
+<li>Click <code>Project Management -> Workflow -> Task Instance</code>.
Enter the <code>Task Instance</code> page, as shown in the figure below, click
workflow instance name, you can jump to the workflow instance DAG chart to view
the task status.</li>
</ul>
<p><img src="/img/new_ui/dev/project/task-instance.png"
alt="task-instance"></p>
<ul>
-<li>View log：Click the "view log" button in the operation column to
view task execution log.</li>
+<li>View log：Click the <code>View Log</code> button in the operation column to
view task execution log.</li>
</ul>
<p><img src="/img/new_ui/dev/project/task-log.png" alt="task-log"></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 [...]
diff --git a/en-us/docs/dev/user_doc/guide/project/task-instance.json
b/en-us/docs/dev/user_doc/guide/project/task-instance.json
index 8ee01fa8e..581f83d29 100644
--- a/en-us/docs/dev/user_doc/guide/project/task-instance.json
+++ b/en-us/docs/dev/user_doc/guide/project/task-instance.json
@@ -1,6 +1,6 @@
{
"filename": "task-instance.md",
- "__html": "<h2>Task Instance</h2>\n<ul>\n<li>Click Project Management ->
Workflow -> Task Instance. Enter the task instance page, as shown in the
figure below, click workflow instance name, you can jump to the workflow
instance DAG chart to view the task status.</li>\n</ul>\n<p><img
src=\"/img/new_ui/dev/project/task-instance.png\"
alt=\"task-instance\"></p>\n<ul>\n<li>View log：Click the "view log"
button in the operation column to view task execution log.</li>\n</ul>\n [...]
+ "__html": "<h2>Task Instance</h2>\n<ul>\n<li>Click <code>Project Management
-> Workflow -> Task Instance</code>. Enter the <code>Task Instance</code>
page, as shown in the figure below, click workflow instance name, you can jump
to the workflow instance DAG chart to view the task
status.</li>\n</ul>\n<p><img src=\"/img/new_ui/dev/project/task-instance.png\"
alt=\"task-instance\"></p>\n<ul>\n<li>View log：Click the <code>View Log</code>
button in the operation column to view task e [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/project/task-instance.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
b/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
index 51efff135..e095b2c59 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
@@ -14,7 +14,7 @@
<h2>Create workflow definition</h2>
<ul>
<li>
-<p>Click Project Management -> Workflow -> Workflow Definition, enter
the workflow definition page, and click the "Create Workflow" button
to enter the <strong>workflow DAG edit</strong> page, as shown in the following
figure:</p>
+<p>Click <code>Project Management -> Workflow -> Workflow
Definition</code>, enter the <code>Workflow Definition</code> page, and click
the <code>Create Workflow</code> button to enter the <strong>workflow DAG
edit</strong> page, as shown in the following figure:</p>
<p><img src="/img/new_ui/dev/project/workflow-dag.png" alt="workflow-dag"></p>
</li>
<li>
@@ -26,13 +26,13 @@
</li>
</ul>
<ol>
-<li>Fill in the "Node Name", "Description" and
"Script" fields;</li>
-<li>Check “Normal” for “Run Flag”. If “Prohibit Execution” is checked, the
task will not execute when the workflow runs;</li>
-<li>Select "Task Priority": when the number of worker threads is
insufficient, high priority tasks will execute first in the execution queue,
and tasks with the same priority will execute in the order of first in, first
out;</li>
+<li>Fill in the <code>Node Name</code>, <code>Description</code> and
<code>Script</code> fields;</li>
+<li>Check “<code>Normal</code>” for “<code>Run Flag</code>”. If
“<code>Prohibit Execution</code>” is checked, the task will not execute when
the workflow runs;</li>
+<li>Select <code>Task Priority</code>: when the number of worker threads is
insufficient, high priority tasks will execute first in the execution queue,
and tasks with the same priority will execute in the order of first in, first
out;</li>
<li>Timeout alarm (optional): check the timeout alarm, timeout failure, and
fill in the "timeout period". When the task execution time exceeds
<strong>timeout period</strong>, an alert email will send and the task timeout
fails;</li>
-<li>Resources (optional). Resources are files create or upload in the Resource
Center -> File Management page. For example, the file name is
<code>test.sh</code>, and the command to call the resource in the script is
<code>sh test.sh</code>;</li>
+<li>Resources (optional). Resources are files create or upload in the
<code>Resource Center -> File Management</code> page. For example, the file
name is <code>test.sh</code>, and the command to call the resource in the
script is <code>sh test.sh</code>;</li>
<li>Customize parameters (optional);</li>
-<li>Click the "Confirm Add" button to save the task settings.</li>
+<li>Click the <code>Confirm Add</code> button to save the task settings.</li>
</ol>
<ul>
<li>
@@ -44,7 +44,7 @@
<p><img src="/img/new_ui/dev/project/workflow-delete.png"
alt="workflow-delete"></p>
</li>
<li>
-<p><strong>Save workflow definition:</strong> Click the "Save"
button, and the "Set DAG chart name" window pops up, as shown in the
figure below. Enter the workflow definition name, workflow definition
description, and set global parameters (optional, refer to <a
href="../parameter/global.md">global parameters</a>), click the "Add"
button to finish workflow definition creation.</p>
+<p><strong>Save workflow definition:</strong> Click the <code>Save</code>
button, and the "Set DAG chart name" window pops up, as shown in the
figure below. Enter the workflow definition name, workflow definition
description, and set global parameters (optional, refer to <a
href="../parameter/global.md">global parameters</a>), click the
<code>Add</code> button to finish workflow definition creation.</p>
<p><img src="/img/new_ui/dev/project/workflow-save.png"
alt="workflow-save"></p>
</li>
</ul>
@@ -52,60 +52,60 @@
<p>For other types of tasks, please refer to <a href="#TaskParamers">Task Node
Type and Parameter Settings</a>. <!-- markdown-link-check-disable-line --></p>
</blockquote>
<h2>Workflow Definition Operation Function</h2>
-<p>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, as shown below:</p>
+<p>Click <code>Project Management -> Workflow -> Workflow
Definition</code> to enter the workflow definition page, as shown below:</p>
<p><img src="/img/new_ui/dev/project/workflow-list.png"
alt="workflow-list"></p>
<p>The following are the operation functions of the workflow definition
list:</p>
<ul>
<li><strong>Edit:</strong> Only "Offline" workflow definitions can
be edited. Workflow DAG editing is the same as <a href="#creatDag">Create
Workflow Definition</a> <!-- markdown-link-check-disable-line --></li>
-<li><strong>Online:</strong> When the workflow status is "Offline",
used to make workflow online. Only the workflow in the "Online" state
can run, but cannot edit</li>
-<li><strong>Offline:</strong> When the workflow status is "Online",
used to make workflow offline. Only the workflow in the "Offline"
state can be edited, but cannot run</li>
+<li><strong>Online:</strong> When the workflow status is "Offline",
used to make workflow online. Only the workflow in the "Online" state
can run, but cannot edit.</li>
+<li><strong>Offline:</strong> When the workflow status is "Online",
used to make workflow offline. Only the workflow in the "Offline"
state can be edited, but cannot run.</li>
<li><strong>Run:</strong> Only workflow in the online state can run. See <a
href="#run-the-workflow">2.3.3 Run Workflow</a> for the operation steps.</li>
-<li><strong>Timing:</strong> Timing can only set to online workflows, and the
system automatically schedules to run the workflow on time. The status after
creating a timing setting is "offline", and the timing must set
online on the timing management page to make effect. See <a
href="#workflow-timing">2.3.4 Workflow Timing</a> for timing operation
steps</li>
-<li><strong>Timing Management:</strong> The timing management page can edit,
online or offline and delete timing</li>
+<li><strong>Timing:</strong> Timing can only set to online workflows, and the
system automatically schedules to run the workflow on time. The status after
creating a timing setting is "offline", and the timing must set
online on the timing management page to make effect. See <a
href="#workflow-timing">2.3.4 Workflow Timing</a> for timing operation
steps.</li>
+<li><strong>Timing Management:</strong> The timing management page can edit,
online or offline and delete timing.</li>
<li><strong>Delete:</strong> Delete the workflow definition. In the same
project, only the workflow definition created by yourself can be deleted, and
the workflow definition of other users cannot be deleted. If you need to delete
it, please contact the user who created it or the administrator.</li>
-<li><strong>Download:</strong> Download workflow definition to local</li>
+<li><strong>Download:</strong> Download workflow definition to local.</li>
<li><strong>Tree Diagram:</strong> Display the task node type and task status
in a tree structure, as shown in the figure below:</li>
</ul>
<p><img src="/img/new_ui/dev/project/workflow-tree.png"
alt="workflow-tree"></p>
<h2>Run the Workflow</h2>
<ul>
-<li>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, as shown in the figure below, click the "Go
Online" button <img src="/img/online.png" width="35"/>to make workflow
online.</li>
+<li>Click <code>Project Management -> Workflow -> Workflow
Definition</code> to enter the workflow definition page, as shown in the figure
below, click the "Go Online" button <img src="/img/online.png"
width="35"/>to make workflow online.</li>
</ul>
<p><img src="/img/new_ui/dev/project/workflow-online.png"
alt="workflow-online"></p>
<ul>
-<li>Click the "Run" button to pop up the startup parameter setting
window, as shown in the figure below, set the startup parameters, click the
"Run" button in the pop-up box, the workflow starts running, and the
workflow instance page generates a workflow instance.</li>
+<li>Click the <code>Run</code> button to pop up the startup parameter setting
window, as shown in the figure below, set the startup parameters, click the
<code>Run</code> button in the pop-up box, the workflow starts running, and the
workflow instance page generates a workflow instance.</li>
</ul>
<p><img src="/img/new_ui/dev/project/workflow-run.png" alt="workflow-run"></p>
<p>Description of workflow operating parameters:</p>
<ul>
<li>
-<p>Failure strategy: When a task node fails to execute, other parallel task
nodes need to execute this strategy. "Continue" means: after a
certain task fails, other task nodes execute normally; "End" means:
terminate all tasks execution, and terminate the entire process</p>
+<p>Failure strategy: When a task node fails to execute, other parallel task
nodes need to execute this strategy. "Continue" means: after a
certain task fails, other task nodes execute normally; "End" means:
terminate all tasks execution, and terminate the entire process.</p>
</li>
<li>
-<p>Notification strategy: When the process is over, send the process execution
result notification email according to the process status, options including no
send, send if sucess, send of failure, send whatever result</p>
+<p>Notification strategy: When the process is over, send the process execution
result notification email according to the process status, options including no
send, send if sucess, send of failure, send whatever result.</p>
</li>
<li>
-<p>Process priority: The priority of process operation, divide into five
levels: highest (HIGHEST), high (HIGH), medium (MEDIUM), low (LOW), and lowest
(LOWEST). When the number of master threads is insufficient, high priority
processes will execute first in the execution queue, and processes with the
same priority will execute in the order of first in, first out;</p>
+<p>Process priority: The priority of process operation, divide into five
levels: highest (HIGHEST), high (HIGH), medium (MEDIUM), low (LOW), and lowest
(LOWEST). When the number of master threads is insufficient, high priority
processes will execute first in the execution queue, and processes with the
same priority will execute in the order of first in, first out.</p>
</li>
<li>
-<p>Worker group: The process can only be executed in the specified worker
machine group. The default is <code>Default</code>, which can execute on any
worker</p>
+<p>Worker group: The process can only be executed in the specified worker
machine group. The default is <code>Default</code>, which can execute on any
worker.</p>
</li>
<li>
-<p>Notification group: select notification strategy||timeout alarm||when fault
tolerance occurs, process result information or email will send to all members
in the notification group</p>
+<p>Notification group: select notification strategy||timeout alarm||when fault
tolerance occurs, process result information or email will send to all members
in the notification group.</p>
</li>
<li>
-<p>Recipient: select notification policy||timeout alarm||when fault tolerance
occurs, process result information or alarm email will be sent to the recipient
list</p>
+<p>Recipient: select notification policy||timeout alarm||when fault tolerance
occurs, process result information or alarm email will be sent to the recipient
list.</p>
</li>
<li>
-<p>Cc: select notification policy||timeout alarm||when fault tolerance occurs,
the process result information or warning email will be copied to the CC
list</p>
+<p>Cc: select notification policy||timeout alarm||when fault tolerance occurs,
the process result information or warning email will be copied to the CC
list.</p>
</li>
<li>
-<p>Startup parameter: Set or overwrite global parameter values when starting a
new process instance</p>
+<p>Startup parameter: Set or overwrite global parameter values when starting a
new process instance.</p>
</li>
<li>
<p>Complement: includes serial complement and parallel complement and supports
manual date input and date selection. Serial complement defines, within the
specified time range, executes the complements from the start date to the end
date by sequential and N process instances are generated in sequence. Parallel
complement defines executing the complement concurrently in the multiple days
to generate N process instances within the specified time range. Manual date
input defines: manually i [...]
<ul>
-<li>Dependent Mode: Trigger the complement of workflow instances that the
downstream dependent node depends on the current workflow(It is required that
the scheduled status of the workflow instance of the current replenishment is
online, and only the downstream supplement directly dependent on the current
workflow will be triggered)</li>
+<li>Dependent Mode: Trigger the complement of workflow instances that the
downstream dependent node depends on the current workflow(It is required that
the scheduled status of the workflow instance of the current replenishment is
online, and only the downstream supplement directly dependent on the current
workflow will be triggered).</li>
<li>You can select complement time range (When the scheduled configuration is
not online, the daily complement will be performed by default according to the
selected time range.If the timing configuration is online, it will be
complemented according to the selected time range in combination with the
timing configuration) when executing a timing workflow definition. For example,
need to fill in the data from 1st May to 10th May, as shown in the figure
below:</li>
</ul>
<p><img src="/img/new_ui/dev/project/workflow-date.png"
alt="workflow-date"></p>
@@ -129,17 +129,17 @@
</ul>
<h2>Run the task alone</h2>
<ul>
-<li>Right-click the task and click the "Start" button (only online
tasks can be clicked to run)</li>
+<li>Right-click the task and click the <code>Start</code> button (only online
tasks can be clicked to run).</li>
</ul>
<p><img src="/img/new_ui/dev/project/workflow-task-run.png"
alt="workflow-task-run"></p>
<ul>
-<li>The startup parameter setting dialog box is displayed, and the parameter
description is the same as <a href="#run-the-workflow">run the workflow</a></li>
+<li>The startup parameter setting dialog box is displayed, and the parameter
description is the same as <a href="#run-the-workflow">run the
workflow</a>.</li>
</ul>
<p><img src="/img/new_ui/dev/project/workflow-task-run-config.png"
alt="workflow-task-run-config"></p>
<h2>Workflow Timing</h2>
<ul>
<li>
-<p>Create timing: Click Project Management->Workflow->Workflow
Definition, enter the workflow definition page, make the workflow online, click
the "timing" button <img src="/img/timing.png" width="35"/> , the
timing parameter setting dialog box pops up, as shown in the figure below:</p>
+<p>Create timing: Click <code>Project Management -> Workflow-> Workflow
Definition</code>, enter the workflow definition page, make the workflow
online, click the "timing" button <img src="/img/timing.png"
width="35"/> , the timing parameter setting dialog box pops up, as shown in the
figure below:</p>
<p><img src="/img/new_ui/dev/project/workflow-time01.png"
alt="workflow-time01"></p>
</li>
<li>
@@ -156,12 +156,12 @@
<p>Click the "Create" button to create the timing. Now the timing
status is "<strong>Offline</strong>" and the timing needs to be
<strong>Online</strong> to make effect.</p>
</li>
<li>
-<p>Timing online: Click the "Timing Management" button <img
src="/img/timeManagement.png" width="35"/>, enter the timing management page,
click the "online" button, the timing status will change to
"online", as shown in the below figure, the workflow makes effect
regularly.</p>
+<p>Timing online: Click the <code>Timing Management</code> button <img
src="/img/timeManagement.png" width="35"/>, enter the timing management page,
click the <code>online</code> button, the timing status will change to
<code>online</code>, as shown in the below figure, the workflow makes effect
regularly.</p>
<p><img src="/img/new_ui/dev/project/workflow-time03.png"
alt="workflow-time03"></p>
</li>
</ul>
<h2>Import Workflow</h2>
-<p>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, click the "Import Workflow" button to
import the local workflow file, the workflow definition list displays the
imported workflow and the status is offline.</p>
+<p>Click <code>Project Management -> Workflow -> Workflow
Definition</code> to enter the workflow definition page, click the <code>Import
Workflow</code> button to import the local workflow file, the workflow
definition list displays the imported workflow and the status is offline.</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>
<script src="/asset/js/react/react-dom.min.js"></script>
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
b/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
index 5d45cd6c9..4b8016240 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
@@ -1,6 +1,6 @@
{
"filename": "workflow-definition.md",
- "__html": "<h1>Workflow Definition</h1>\n<h2>Create workflow
definition</h2>\n<ul>\n<li>\n<p>Click Project Management -> Workflow ->
Workflow Definition, enter the workflow definition page, and click the
"Create Workflow" button to enter the <strong>workflow DAG
edit</strong> page, as shown in the following figure:</p>\n<p><img
src=\"/img/new_ui/dev/project/workflow-dag.png\"
alt=\"workflow-dag\"></p>\n</li>\n<li>\n<p>Drag from the toolbar <img
src=\"/img/tasks/icons/sh [...]
+ "__html": "<h1>Workflow Definition</h1>\n<h2>Create workflow
definition</h2>\n<ul>\n<li>\n<p>Click <code>Project Management -> Workflow
-> Workflow Definition</code>, enter the <code>Workflow Definition</code>
page, and click the <code>Create Workflow</code> button to enter the
<strong>workflow DAG edit</strong> page, as shown in the following
figure:</p>\n<p><img src=\"/img/new_ui/dev/project/workflow-dag.png\"
alt=\"workflow-dag\"></p>\n</li>\n<li>\n<p>Drag from the toolbar <im [...]
"link":
"/dist/en-us/docs/dev/user_doc/guide/project/workflow-definition.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
b/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
index c15c430f2..24cd1a261 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
@@ -13,7 +13,7 @@
<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>View Workflow Instance</h2>
<ul>
-<li>Click Project Management -> Workflow -> Workflow Instance, enter the
Workflow Instance page, as shown in the figure below:</li>
+<li>Click <code>Project Management -> Workflow -> Workflow
Instance</code>, enter the Workflow Instance page, as shown in the figure
below:</li>
</ul>
<p><img src="/img/new_ui/dev/project/workflow-instance.png"
alt="workflow-instance"></p>
<ul>
@@ -31,18 +31,18 @@
<p><img src="/img/new_ui/dev/project/instance-log02.png"
alt="instance-log02"></p>
<h2>View Task History</h2>
<ul>
-<li>Click Project Management -> Workflow -> Workflow Instance, enter the
workflow instance page, and click the workflow name to enter the workflow DAG
page;</li>
-<li>Double-click the task node, as shown in the figure below, click "View
History" to jump to the task instance page, and display a list of task
instances running by the workflow instance</li>
+<li>Click <code>Project Management -> Workflow -> Workflow
Instance</code>, enter the workflow instance page, and click the workflow name
to enter the workflow DAG page;</li>
+<li>Double-click the task node, as shown in the figure below, click <code>View
History</code> to jump to the task instance page, and display a list of task
instances running by the workflow instance.</li>
</ul>
<p><img src="/img/new_ui/dev/project/instance-history.png"
alt="instance-history"></p>
<h2>View Operation Parameters</h2>
<ul>
-<li>Click Project Management -> Workflow -> Workflow Instance, enter the
workflow instance page, and click the workflow name to enter the workflow DAG
page;</li>
+<li>Click <code>Project Management -> Workflow -> Workflow
Instance</code>, enter the workflow instance page, and click the workflow name
to enter the workflow DAG page;</li>
<li>Click the icon in the upper left corner <img
src="/img/run_params_button.png" width="35"/>，View the startup parameters of
the workflow instance; click the icon <img src="/img/global_param.png"
width="35"/>，View the global and local parameters of the workflow instance, as
shown in the following figure:</li>
</ul>
<p><img src="/img/new_ui/dev/project/instance-parameter.png"
alt="instance-parameter"></p>
<h2>Workflow Instance Operation Function</h2>
-<p>Click Project Management -> Workflow -> Workflow Instance, enter the
workflow instance page, as shown in the figure below:</p>
+<p>Click <code>Project Management -> Workflow -> Workflow
Instance</code>, enter the workflow instance page, as shown in the figure
below:</p>
<p><img src="/img/new_ui/dev/project/workflow-instance.png"
alt="workflow-instance"></p>
<ul>
<li><strong>Edit：</strong> only processes with success/failed/stop status can
be edited. Click the "Edit" button or the workflow instance name to
enter the DAG edit page. After the edit, click the "Save" button to
confirm, as shown in the figure below. In the pop-up box, check "Whether
to update the workflow definition", after saving, the information modified
by the instance will be updated to the workflow definition; if not checked, the
workflow definition [...]
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
b/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
index 0bc00126d..060778e9f 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
@@ -1,6 +1,6 @@
{
"filename": "workflow-instance.md",
- "__html": "<h1>Workflow Instance</h1>\n<h2>View Workflow
Instance</h2>\n<ul>\n<li>Click Project Management -> Workflow -> Workflow
Instance, enter the Workflow Instance page, as shown in the figure
below:</li>\n</ul>\n<p><img
src=\"/img/new_ui/dev/project/workflow-instance.png\"
alt=\"workflow-instance\"></p>\n<ul>\n<li>Click the workflow name to enter the
DAG view page, and check the task execution status, as shown in the figure
below:</li>\n</ul>\n<p><img src=\"/img/new_ui/dev/ [...]
+ "__html": "<h1>Workflow Instance</h1>\n<h2>View Workflow
Instance</h2>\n<ul>\n<li>Click <code>Project Management -> Workflow ->
Workflow Instance</code>, enter the Workflow Instance page, as shown in the
figure below:</li>\n</ul>\n<p><img
src=\"/img/new_ui/dev/project/workflow-instance.png\"
alt=\"workflow-instance\"></p>\n<ul>\n<li>Click the workflow name to enter the
DAG view page, and check the task execution status, as shown in the figure
below:</li>\n</ul>\n<p><img src=\"/im [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/project/workflow-instance.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/project/task-instance.html
b/en-us/docs/dev/user_doc/guide/project/workflow-relation.html
similarity index 97%
copy from en-us/docs/dev/user_doc/guide/project/task-instance.html
copy to en-us/docs/dev/user_doc/guide/project/workflow-relation.html
index fe00e3688..9013e427b 100644
--- a/en-us/docs/dev/user_doc/guide/project/task-instance.html
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-relation.html
@@ -3,22 +3,15 @@
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0,
maximum-scale=1.0, user-scalable=no">
- <meta name="keywords" content="task-instance">
- <meta name="description" content="task-instance">
- <title>task-instance</title>
+ <meta name="keywords" content="workflow-relation">
+ <meta name="description" content="workflow-relation">
+ <title>workflow-relation</title>
<link rel="shortcut icon" href="/img/favicon.ico">
<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=" [...]
-<ul>
-<li>Click Project Management -> Workflow -> Task Instance. Enter the
task instance page, as shown in the figure below, click workflow instance name,
you can jump to the workflow instance DAG chart to view the task status.</li>
-</ul>
-<p><img src="/img/new_ui/dev/project/task-instance.png"
alt="task-instance"></p>
-<ul>
-<li>View log：Click the "view log" button in the operation column to
view task execution log.</li>
-</ul>
-<p><img src="/img/new_ui/dev/project/task-log.png" alt="task-log"></p>
+ <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><img src="/img/new_ui/dev/project/work-relation.png" alt=""></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>
<script src="/asset/js/react/react-dom.min.js"></script>
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-relation.json
b/en-us/docs/dev/user_doc/guide/project/workflow-relation.json
new file mode 100644
index 000000000..d81efe108
--- /dev/null
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-relation.json
@@ -0,0 +1,6 @@
+{
+ "filename": "workflow-relation.md",
+ "__html": "<p>Workflow Relation screen shows all the existing workflows in a
project and their status.</p>\n<p><img
src=\"/img/new_ui/dev/project/work-relation.png\" alt=\"\"></p>\n",
+ "link": "/dist/en-us/docs/dev/user_doc/guide/project/workflow-relation.html",
+ "meta": {}
+}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/task/conditions.html
b/en-us/docs/dev/user_doc/guide/task/conditions.html
index 71661bb5f..2cb315a1f 100644
--- a/en-us/docs/dev/user_doc/guide/task/conditions.html
+++ b/en-us/docs/dev/user_doc/guide/task/conditions.html
@@ -14,7 +14,7 @@
<p>Condition is a conditional node, that determines which downstream task
should run based on the condition of the upstream task. Currently, the
Conditions support multiple upstream tasks, but only two downstream tasks. When
the number of upstream tasks exceeds one, achieve complex upstream dependencies
by through <code>and</code> and <code>or</code> operators.</p>
<h2>Create Task</h2>
<ul>
-<li>Click <code>Project Management -> Project Name -> Workflow
Definition</code>, and click the "<code>Create Workflow</code>"
button to enter the DAG editing page.</li>
+<li>Click <code>Project Management -> Project Name -> Workflow
Definition</code>, and click the <code>Create Workflow</code> button to enter
the DAG editing page.</li>
<li>Drag from the toolbar <img src="/img/conditions.png" width="20"/> task
node to canvas.</li>
</ul>
<h2>Task Parameters</h2>
diff --git a/en-us/docs/dev/user_doc/guide/task/conditions.json
b/en-us/docs/dev/user_doc/guide/task/conditions.json
index a57484a6a..72e91bff0 100644
--- a/en-us/docs/dev/user_doc/guide/task/conditions.json
+++ b/en-us/docs/dev/user_doc/guide/task/conditions.json
@@ -1,6 +1,6 @@
{
"filename": "conditions.md",
- "__html": "<h1>Conditions</h1>\n<p>Condition is a conditional node, that
determines which downstream task should run based on the condition of the
upstream task. Currently, the Conditions support multiple upstream tasks, but
only two downstream tasks. When the number of upstream tasks exceeds one,
achieve complex upstream dependencies by through <code>and</code> and
<code>or</code> operators.</p>\n<h2>Create Task</h2>\n<ul>\n<li>Click
<code>Project Management -> Project Name -> W [...]
+ "__html": "<h1>Conditions</h1>\n<p>Condition is a conditional node, that
determines which downstream task should run based on the condition of the
upstream task. Currently, the Conditions support multiple upstream tasks, but
only two downstream tasks. When the number of upstream tasks exceeds one,
achieve complex upstream dependencies by through <code>and</code> and
<code>or</code> operators.</p>\n<h2>Create Task</h2>\n<ul>\n<li>Click
<code>Project Management -> Project Name -> W [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/task/conditions.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/task/emr.html
b/en-us/docs/dev/user_doc/guide/task/emr.html
index 6afbd318d..784ebb7e8 100644
--- a/en-us/docs/dev/user_doc/guide/task/emr.html
+++ b/en-us/docs/dev/user_doc/guide/task/emr.html
@@ -15,7 +15,7 @@
<p>Amazon EMR task type, for creating EMR clusters on AWS and running
computing tasks. Using <a
href="https://aws.amazon.com/cn/sdk-for-java/";>aws-java-sdk</a> in the
background code, to transfer JSON parameters to <a
href="https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/elasticmapreduce/model/RunJobFlowRequest.html";>RunJobFlowRequest</a>
object and submit to AWS.</p>
<h2>Create Task</h2>
<ul>
-<li>Click <code>Project Management -> Project Name -> Workflow
Definition</code>, click the "<code>Create Workflow</code>" button to
enter the DAG editing page.</li>
+<li>Click <code>Project Management -> Project Name -> Workflow
Definition</code>, click the <code>Create Workflow</code> button to enter the
DAG editing page.</li>
<li>Drag <code>AmazonEMR</code> task from the toolbar to the artboard to
complete the creation.</li>
</ul>
<h2>Task Parameters</h2>
diff --git a/en-us/docs/dev/user_doc/guide/task/emr.json
b/en-us/docs/dev/user_doc/guide/task/emr.json
index 76dda3607..df6ec3e7c 100644
--- a/en-us/docs/dev/user_doc/guide/task/emr.json
+++ b/en-us/docs/dev/user_doc/guide/task/emr.json
@@ -1,6 +1,6 @@
{
"filename": "emr.md",
- "__html": "<h1>Amazon EMR</h1>\n<h2>Overview</h2>\n<p>Amazon EMR task type,
for creating EMR clusters on AWS and running computing tasks. Using <a
href=\"https://aws.amazon.com/cn/sdk-for-java/\";>aws-java-sdk</a> in the
background code, to transfer JSON parameters to <a
href=\"https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/elasticmapreduce/model/RunJobFlowRequest.html\";>RunJobFlowRequest</a>
object and submit to AWS.</p>\n<h2>Create Task</h2>\n<ul>\n<li>C [...]
+ "__html": "<h1>Amazon EMR</h1>\n<h2>Overview</h2>\n<p>Amazon EMR task type,
for creating EMR clusters on AWS and running computing tasks. Using <a
href=\"https://aws.amazon.com/cn/sdk-for-java/\";>aws-java-sdk</a> in the
background code, to transfer JSON parameters to <a
href=\"https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/elasticmapreduce/model/RunJobFlowRequest.html\";>RunJobFlowRequest</a>
object and submit to AWS.</p>\n<h2>Create Task</h2>\n<ul>\n<li>C [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/task/emr.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/task/flink.html
b/en-us/docs/dev/user_doc/guide/task/flink.html
index 29ebf68bc..000f561da 100644
--- a/en-us/docs/dev/user_doc/guide/task/flink.html
+++ b/en-us/docs/dev/user_doc/guide/task/flink.html
@@ -149,36 +149,6 @@
</tr>
</tbody>
</table>
-<ul>
-<li><strong>Node name</strong>: The node name in a workflow definition is
unique.</li>
-<li><strong>Run flag</strong>: Identifies whether this node schedules
normally, if it does not need to execute, select the <code>prohibition
execution</code>.</li>
-<li><strong>Descriptive information</strong>: Describe the function of the
node.</li>
-<li><strong>Task priority</strong>: When the number of worker threads is
insufficient, execute in the order of priority from high to low, and tasks with
the same priority will execute in a first-in first-out order.</li>
-<li><strong>Worker grouping</strong>: Assign tasks to the machines of the
worker group to execute. If <code>Default</code> is selected, randomly select a
worker machine for execution.</li>
-<li><strong>Environment Name</strong>: Configure the environment name in which
run the script.</li>
-<li><strong>Times of failed retry attempts</strong>: The number of times the
task failed to resubmit.</li>
-<li><strong>Failed retry interval</strong>: The time interval (unit minute)
for resubmitting the task after a failed task.</li>
-<li><strong>Delayed execution time</strong>: The time (unit minute) that a
task delays in execution.</li>
-<li><strong>Timeout alarm</strong>: Check the timeout alarm and timeout
failure. When the task runs exceed the "timeout", an alarm email will
send and the task execution will fail.</li>
-<li><strong>Program type</strong>: Support Java, Scala, Python and SQL four
languages.</li>
-<li><strong>The class of main function</strong>: The <strong>full
path</strong> of Main Class, the entry point of the Flink program.</li>
-<li><strong>Main jar package</strong>: The jar package of the Flink program
(upload by Resource Center).</li>
-<li><strong>Deployment mode</strong>: Support 3 deployment modes: cluster,
local and application (Flink 1.11 and later. See also <a
href="https://nightlies.apache.org/flink/flink-docs-release-1.11/ops/deployment/yarn_setup.html#run-an-application-in-application-mode";>Run
an application in Application Mode</a>).</li>
-<li><strong>Initialization script</strong>: Script file to initialize session
context.</li>
-<li><strong>Script</strong>: The sql script file developed by the user that
should be executed.</li>
-<li><strong>Flink version</strong>: Select version according to the execution
env.</li>
-<li><strong>Task name</strong> (optional): Flink task name.</li>
-<li><strong>JobManager memory size</strong>: Used to set the size of
jobManager memories, which can be set according to the actual production
environment.</li>
-<li><strong>Number of slots</strong>: Used to set the number of slots, which
can be set according to the actual production environment.</li>
-<li><strong>TaskManager memory size</strong>: Used to set the size of
taskManager memories, which can be set according to the actual production
environment.</li>
-<li><strong>Number of TaskManager</strong>: Used to set the number of
taskManagers, which can be set according to the actual production
environment.</li>
-<li><strong>Parallelism</strong>: Used to set the degree of parallelism for
executing Flink tasks.</li>
-<li><strong>Main program parameters</strong>: Set the input parameters for the
Flink program and support the substitution of custom parameter variables.</li>
-<li><strong>Optional parameters</strong>: Support <code>--jar</code>,
<code>--files</code>,<code>--archives</code>, <code>--conf</code> format.</li>
-<li><strong>Resource</strong>: Appoint resource files in the
<code>Resource</code> if parameters refer to them.</li>
-<li><strong>Custom parameter</strong>: It is a local user-defined parameter
for Flink, and will replace the content with <code>${variable}</code> in the
script.</li>
-<li><strong>Predecessor task</strong>: Selecting a predecessor task for the
current task, will set the selected predecessor task as upstream of the current
task.</li>
-</ul>
<h2>Task Example</h2>
<h3>Execute the WordCount Program</h3>
<p>This is a common introductory case in the big data ecosystem, which often
apply to computational frameworks such as MapReduce, Flink and Spark. The main
purpose is to count the number of identical words in the input text. (Flink's
releases attach this example job)</p>
diff --git a/en-us/docs/dev/user_doc/guide/task/flink.json
b/en-us/docs/dev/user_doc/guide/task/flink.json
index 34ceefe9e..a5bdb4473 100644
--- a/en-us/docs/dev/user_doc/guide/task/flink.json
+++ b/en-us/docs/dev/user_doc/guide/task/flink.json
@@ -1,6 +1,6 @@
{
"filename": "flink.md",
- "__html": "<h1>Flink Node</h1>\n<h2>Overview</h2>\n<p>Flink task type, used
to execute Flink programs. For Flink nodes:</p>\n<ol>\n<li>\n<p>When the
program type is Java, Scala or Python, the worker submits the task <code>flink
run</code> using the Flink command. See <a
href=\"https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/cli/\";>flink
cli</a> for more details.</p>\n</li>\n<li>\n<p>When the program type is SQL,
the worker submit tasks using <code>sql-client. [...]
+ "__html": "<h1>Flink Node</h1>\n<h2>Overview</h2>\n<p>Flink task type, used
to execute Flink programs. For Flink nodes:</p>\n<ol>\n<li>\n<p>When the
program type is Java, Scala or Python, the worker submits the task <code>flink
run</code> using the Flink command. See <a
href=\"https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/cli/\";>flink
cli</a> for more details.</p>\n</li>\n<li>\n<p>When the program type is SQL,
the worker submit tasks using <code>sql-client. [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/task/flink.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/task/http.html
b/en-us/docs/dev/user_doc/guide/task/http.html
index e0ba22508..57f7c3d83 100644
--- a/en-us/docs/dev/user_doc/guide/task/http.html
+++ b/en-us/docs/dev/user_doc/guide/task/http.html
@@ -15,7 +15,7 @@
<p>This node is used to perform http type tasks such as the common POST and
GET request types, and also supports http request validation and other
functions.</p>
<h2>Create Task</h2>
<ul>
-<li>Click <code>Project Management -> Project Name -> Workflow
Definition</code>, and click the "<code>Create Workflow</code>"
button to enter the DAG editing page.</li>
+<li>Click <code>Project Management -> Project Name -> Workflow
Definition</code>, and click the <code>Create Workflow</code> button to enter
the DAG editing page.</li>
<li>Drag the <img src="/img/tasks/icons/http.png" width="15"/> from the
toolbar to the drawing board.</li>
</ul>
<h2>Task Parameters</h2>
diff --git a/en-us/docs/dev/user_doc/guide/task/http.json
b/en-us/docs/dev/user_doc/guide/task/http.json
index 523a79177..ffa385957 100644
--- a/en-us/docs/dev/user_doc/guide/task/http.json
+++ b/en-us/docs/dev/user_doc/guide/task/http.json
@@ -1,6 +1,6 @@
{
"filename": "http.md",
- "__html": "<h1>HTTP Node</h1>\n<h2>Overview</h2>\n<p>This node is used to
perform http type tasks such as the common POST and GET request types, and also
supports http request validation and other functions.</p>\n<h2>Create
Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name ->
Workflow Definition</code>, and click the "<code>Create
Workflow</code>" button to enter the DAG editing page.</li>\n<li>Drag the
<img src=\"/img/tasks/icons/http.png\" width=\"15 [...]
+ "__html": "<h1>HTTP Node</h1>\n<h2>Overview</h2>\n<p>This node is used to
perform http type tasks such as the common POST and GET request types, and also
supports http request validation and other functions.</p>\n<h2>Create
Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name ->
Workflow Definition</code>, and click the <code>Create Workflow</code> button
to enter the DAG editing page.</li>\n<li>Drag the <img
src=\"/img/tasks/icons/http.png\" width=\"15\"/> from th [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/task/http.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/task/jupyter.html
b/en-us/docs/dev/user_doc/guide/task/jupyter.html
index 4aadcea23..5506ba60e 100644
--- a/en-us/docs/dev/user_doc/guide/task/jupyter.html
+++ b/en-us/docs/dev/user_doc/guide/task/jupyter.html
@@ -50,13 +50,13 @@ If you unpack your packed conda environment, the directory
structure should be t
└── ssl
</code></pre>
<blockquote>
-<p>NOTE: Please follow the <code>conda pack</code> instructions above
strictly, and DO NOT modify <code>bin/activate</code>.
+<p>NOTICE: Please follow the <code>conda pack</code> instructions above
strictly, and DO NOT modify <code>bin/activate</code>.
<code>Jupyter Task Plugin</code> uses <code>source</code> command to activate
your packed conda environment.
If you are concerned about using <code>source</code>, choose other options to
manage your python dependency.</p>
</blockquote>
<h2>Create Task</h2>
<ul>
-<li>Click <code>Project Management-Project Name-Workflow Definition</code>,
and click the "<code>Create Workflow</code>" button to enter the DAG
editing page.</li>
+<li>Click <code>Project Management-Project Name-Workflow Definition</code>,
and click the <code>Create Workflow</code> button to enter the DAG editing
page.</li>
<li>Drag <img src="/img/tasks/icons/jupyter.png" width="15"/> from the toolbar
to the canvas.</li>
</ul>
<h2>Task Parameters</h2>
diff --git a/en-us/docs/dev/user_doc/guide/task/jupyter.json
b/en-us/docs/dev/user_doc/guide/task/jupyter.json
index c71307bfb..428ba6d10 100644
--- a/en-us/docs/dev/user_doc/guide/task/jupyter.json
+++ b/en-us/docs/dev/user_doc/guide/task/jupyter.json
@@ -1,6 +1,6 @@
{
"filename": "jupyter.md",
- "__html": "<h1>Jupyter</h1>\n<h2>Overview</h2>\n<p>Use <code>Jupyter
Task</code> to create a jupyter-type task and execute jupyter notes. When the
worker executes <code>Jupyter Task</code>,\nit will use <code>papermill</code>
to evaluate jupyter notes. Click <a
href=\"https://papermill.readthedocs.io/en/latest/\";>here</a> for details about
<code>papermill</code>.</p>\n<h2>Conda Configuration</h2>\n<ul>\n<li>Config
<code>conda.path</code> in <code>common.properties</code> to the path of [...]
+ "__html": "<h1>Jupyter</h1>\n<h2>Overview</h2>\n<p>Use <code>Jupyter
Task</code> to create a jupyter-type task and execute jupyter notes. When the
worker executes <code>Jupyter Task</code>,\nit will use <code>papermill</code>
to evaluate jupyter notes. Click <a
href=\"https://papermill.readthedocs.io/en/latest/\";>here</a> for details about
<code>papermill</code>.</p>\n<h2>Conda Configuration</h2>\n<ul>\n<li>Config
<code>conda.path</code> in <code>common.properties</code> to the path of [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/task/jupyter.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/task/mlflow.html
b/en-us/docs/dev/user_doc/guide/task/mlflow.html
index a6b30682a..9fe2a5509 100644
--- a/en-us/docs/dev/user_doc/guide/task/mlflow.html
+++ b/en-us/docs/dev/user_doc/guide/task/mlflow.html
@@ -236,8 +236,26 @@ reproducibility, deployment, and a central model
registry.</p>
<p><img src="/img/tasks/demo/mlflow-models-docker.png"
alt="mlflow-models-docker"></p>
<h4>DOCKER COMPOSE</h4>
<p><img src="/img/tasks/demo/mlflow-models-docker-compose.png"
alt="mlflow-models-docker-compose"></p>
+<table>
+<thead>
+<tr>
+<th><strong>Parameter</strong></th>
+<th><strong>Description</strong></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Max Cpu Limit</td>
+<td>For example, <code>1.0</code> or <code>0.5</code>, the same as docker
compose.</td>
+</tr>
+<tr>
+<td>Max Memory Limit</td>
+<td>For example <code>1G</code> or <code>500M</code>, the same as docker
compose.</td>
+</tr>
+</tbody>
+</table>
<h2>Environment to Prepare</h2>
-<h3>Conda environment</h3>
+<h3>Conda Environment</h3>
<p>You need to enter the admin account to configure a conda environment
variable（Please
install <a href="https://docs.continuum.io/anaconda/install/";>anaconda</a>
or <a
href="https://docs.conda.io/en/latest/miniconda.html#installing";>miniconda</a>
in advance).</p>
diff --git a/en-us/docs/dev/user_doc/guide/task/mlflow.json
b/en-us/docs/dev/user_doc/guide/task/mlflow.json
index 0df08d6d0..3d5419c4a 100644
--- a/en-us/docs/dev/user_doc/guide/task/mlflow.json
+++ b/en-us/docs/dev/user_doc/guide/task/mlflow.json
@@ -1,6 +1,6 @@
{
"filename": "mlflow.md",
- "__html": "<h1>MLflow Node</h1>\n<h2>Overview</h2>\n<p><a
href=\"https://mlflow.org\";>MLflow</a> is an excellent open source platform to
manage the ML lifecycle, including experimentation,\nreproducibility,
deployment, and a central model registry.</p>\n<p>MLflow task plugin used to
execute MLflow tasks，Currently contains MLflow Projects and MLflow Models.
(Model Registry will soon be rewarded for support)</p>\n<ul>\n<li>MLflow
Projects: Package data science code in a format to reprodu [...]
+ "__html": "<h1>MLflow Node</h1>\n<h2>Overview</h2>\n<p><a
href=\"https://mlflow.org\";>MLflow</a> is an excellent open source platform to
manage the ML lifecycle, including experimentation,\nreproducibility,
deployment, and a central model registry.</p>\n<p>MLflow task plugin used to
execute MLflow tasks，Currently contains MLflow Projects and MLflow Models.
(Model Registry will soon be rewarded for support)</p>\n<ul>\n<li>MLflow
Projects: Package data science code in a format to reprodu [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/task/mlflow.html",
"meta": {}
}
\ No newline at end of file
diff --git a/img/new_ui/dev/project/work-relation.png
b/img/new_ui/dev/project/work-relation.png
new file mode 100644
index 000000000..ab459e685
Binary files /dev/null and b/img/new_ui/dev/project/work-relation.png differ
