This is an automated email from the ASF dual-hosted git repository.
casion pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/linkis-website.git
The following commit(s) were added to refs/heads/dev by this push:
new f9042d2d875 issue-4705: beautify task-flow key content display (#739)
f9042d2d875 is described below
commit f9042d2d875e2f72f21904536f4fe9c961d1a909
Author: 赵文恺 <[email protected]>
AuthorDate: Thu Jul 13 11:00:56 2023 +0800
issue-4705: beautify task-flow key content display (#739)
* Update task-flow.md#4705
wrap Keywords for line 9 to line 15
* Update task-flow.md#4705
Fixed the line feed problem for the current branch
* Update task-flow.md#4705
Modified the English version of the keywords
* Update task-flow.md#4705
Added a period at the end of the sentence
* Update task-flow.md#4705
Added a period at the end of the sentence
* Update task-flow.md#4705
* Update task-flow.md#4705
* Update task-flow.md
* Update task-flow.md#4705
Modified the English version of the keywords.
* Update task-flow.md#4705
* Update task-flow.md#4705
* Update task-flow.md#4705
* Update task-flow.md#4705
---
docs/architecture/task-flow.md | 22 ++++++++++++++--------
.../current/architecture/task-flow.md | 20 +++++++++++++-------
.../version-1.3.2/architecture/task-flow.md | 20 +++++++++++++-------
.../version-1.3.2/architecture/task-flow.md | 22 ++++++++++++++--------
4 files changed, 54 insertions(+), 30 deletions(-)
diff --git a/docs/architecture/task-flow.md b/docs/architecture/task-flow.md
index 3d8f866c143..115bb5c4f18 100644
--- a/docs/architecture/task-flow.md
+++ b/docs/architecture/task-flow.md
@@ -7,13 +7,19 @@ sidebar_position: 0.1
> Linkis task execution is the core function of Linkis. It calls to Linkis's
> computing governance service, public enhancement service, and three-tier
> services of microservice governance. Now it supports the execution of tasks
> of OLAP, OLTP, Streaming and other engine types. This article will discuss
> OLAP The process of task submission, preparation, execution, and result
> return of the type engine is introduced.
## Keywords:
-LinkisMaster: The management service in the computing governance service layer
of Linkis mainly includes several management and control services such as
AppManager, ResourceManager, and LabelManager. Formerly known as LinkisManager
service
-Entrance: The entry service in the computing governance service layer, which
completes the functions of task scheduling, status control, task information
push, etc.
-Orchestrator: Linkis' orchestration service provides powerful orchestration
and computing strategy capabilities to meet the needs of multiple application
scenarios such as multi-active, active-standby, transaction, replay, current
limiting, heterogeneous and mixed computing. At this stage, Orchestrator is
relied on by the Entrance service
-EngineConn (EC): Engine connector, responsible for accepting tasks and
submitting them to underlying engines such as Spark, hive, Flink, Presto,
trino, etc. for execution
-EngineConnManager (ECM): Linkis' EC process management service, responsible
for controlling the life cycle of EngineConn (start, stop)
-LinkisEnginePluginServer: This service is responsible for managing the startup
materials and configuration of each engine, and also provides the startup
command acquisition of each EngineConn, as well as the resources required by
each EngineConn
-PublicEnhencementService (PES): A public enhancement service, a module that
provides functions such as unified configuration management, context service,
material library, data source management, microservice management, and
historical task query for other microservice modules
+LinkisMaster: The management service in the computing governance service layer
of Linkis mainly includes several management and control services such as
AppManager, ResourceManager, and LabelManager. Formerly known as LinkisManager
service.
+
+Entrance: The entry service in the computing governance service layer, which
completes the functions of task scheduling, status control, task information
push, etc.
+
+Orchestrator: Linkis' orchestration service provides powerful orchestration
and computing strategy capabilities to meet the needs of multiple application
scenarios such as multi-active, active-standby, transaction, replay, current
limiting, heterogeneous and mixed computing. At this stage, Orchestrator is
relied on by the Entrance service.
+
+EngineConn (EC): Engine connector, responsible for accepting tasks and
submitting them to underlying engines such as Spark, hive, Flink, Presto,
trino, etc. for execution.
+
+EngineConnManager (ECM): Linkis' EC process management service, responsible
for controlling the life cycle of EngineConn (start, stop).
+
+LinkisEnginePluginServer: This service is responsible for managing the startup
materials and configuration of each engine, and also provides the startup
command acquisition of each EngineConn, as well as the resources required by
each EngineConn.
+
+PublicEnhencementService (PES): A public enhancement service, a module that
provides functions such as unified configuration management, context service,
material library, data source management, microservice management, and
historical task query for other microservice modules.
## 1. Linkis interactive task execution architecture
### 1.1, Task execution thinking
@@ -179,4 +185,4 @@ ResultSetReader: The key class for reading the result set
## 3. Summary
Above we mainly introduced the entire execution
process of the OLAP task of the Linkis Computing Governance Service Group CGS.
According to the processing process of the task request, the task is divided
into four parts: submit, prepare, execute, and return the result stage. CGS is
mainly designed and implemented according to these 4 stages, serves these 4
stages, and provides powerful and flexible capabilities for each stage. In the
submission stage, it mainly pr [...]
-
\ No newline at end of file
+
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/task-flow.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/task-flow.md
index a6d7111744a..0dd9d2a3ede 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/task-flow.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/task-flow.md
@@ -6,13 +6,19 @@ sidebar_position: 2
>
> Linkis任务执行是Linkis的核心功能，调用到Linkis的计算治理服务、公共增强服务，微服务治理的三层服务，现在已经支持了OLAP、OLTP、Streaming等引擎类型的任务执行，本文将对OLAP类型引擎的任务提交、准备、执行、结果返回等流程进行介绍。
## 关键名词：
-LinkisMaster：Linkis的计算治理服务层架中的管理服务，主要包含了AppManager、ResourceManager、LabelManager等几个管控服务。原名LinkisManager服务
-Entrance：计算治理服务层架中的入口服务，完成任务的调度、状态管控、任务信息推送等功能
-Orchestrator：Linkis的编排服务，提供强大的编排和计算策略能力，满足多活、主备、事务、重放、限流、异构和混算等多种应用场景的需求。现阶段Orchestrator被Entrance服务所依赖
-EngineConn（EC）：引擎连接器，负责接受任务并提交给底层引擎如Spark、hive、Flink、Presto、trino等进行执行
-EngineConnManager（ECM）：Linkis 的EC进程管理服务，负责管控EngineConn的生命周期（启动、停止）
-LinkisEnginePluginServer：该服务负责管理各个引擎的启动物料和配置，另外提供每个EngineConn的启动命令获取，以及每个EngineConn所需要的资源
-PublicEnhencementService（PES）：
公共增强服务，为其他微服务模块提供统一配置管理、上下文服务、物料库、数据源管理、微服务管理和历史任务查询等功能的模块
+LinkisMaster：Linkis的计算治理服务层架中的管理服务，主要包含了AppManager、ResourceManager、LabelManager等几个管控服务。原名LinkisManager服务。
+
+Entrance：计算治理服务层架中的入口服务，完成任务的调度、状态管控、任务信息推送等功能。
+
+Orchestrator：Linkis的编排服务，提供强大的编排和计算策略能力，满足多活、主备、事务、重放、限流、异构和混算等多种应用场景的需求。现阶段Orchestrator被Entrance服务所依赖。
+
+EngineConn（EC）：引擎连接器，负责接受任务并提交给底层引擎如Spark、hive、Flink、Presto、trino等进行执行。
+
+EngineConnManager（ECM）：Linkis 的EC进程管理服务，负责管控EngineConn的生命周期（启动、停止）。
+
+LinkisEnginePluginServer：该服务负责管理各个引擎的启动物料和配置，另外提供每个EngineConn的启动命令获取，以及每个EngineConn所需要的资源。
+
+PublicEnhencementService（PES）：
公共增强服务，为其他微服务模块提供统一配置管理、上下文服务、物料库、数据源管理、微服务管理和历史任务查询等功能的模块。
## 一、Linkis交互式任务执行架构
### 1.1、任务执行思考
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.3.2/architecture/task-flow.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.3.2/architecture/task-flow.md
index a6d7111744a..0dd9d2a3ede 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.3.2/architecture/task-flow.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.3.2/architecture/task-flow.md
@@ -6,13 +6,19 @@ sidebar_position: 2
>
> Linkis任务执行是Linkis的核心功能，调用到Linkis的计算治理服务、公共增强服务，微服务治理的三层服务，现在已经支持了OLAP、OLTP、Streaming等引擎类型的任务执行，本文将对OLAP类型引擎的任务提交、准备、执行、结果返回等流程进行介绍。
## 关键名词：
-LinkisMaster：Linkis的计算治理服务层架中的管理服务，主要包含了AppManager、ResourceManager、LabelManager等几个管控服务。原名LinkisManager服务
-Entrance：计算治理服务层架中的入口服务，完成任务的调度、状态管控、任务信息推送等功能
-Orchestrator：Linkis的编排服务，提供强大的编排和计算策略能力，满足多活、主备、事务、重放、限流、异构和混算等多种应用场景的需求。现阶段Orchestrator被Entrance服务所依赖
-EngineConn（EC）：引擎连接器，负责接受任务并提交给底层引擎如Spark、hive、Flink、Presto、trino等进行执行
-EngineConnManager（ECM）：Linkis 的EC进程管理服务，负责管控EngineConn的生命周期（启动、停止）
-LinkisEnginePluginServer：该服务负责管理各个引擎的启动物料和配置，另外提供每个EngineConn的启动命令获取，以及每个EngineConn所需要的资源
-PublicEnhencementService（PES）：
公共增强服务，为其他微服务模块提供统一配置管理、上下文服务、物料库、数据源管理、微服务管理和历史任务查询等功能的模块
+LinkisMaster：Linkis的计算治理服务层架中的管理服务，主要包含了AppManager、ResourceManager、LabelManager等几个管控服务。原名LinkisManager服务。
+
+Entrance：计算治理服务层架中的入口服务，完成任务的调度、状态管控、任务信息推送等功能。
+
+Orchestrator：Linkis的编排服务，提供强大的编排和计算策略能力，满足多活、主备、事务、重放、限流、异构和混算等多种应用场景的需求。现阶段Orchestrator被Entrance服务所依赖。
+
+EngineConn（EC）：引擎连接器，负责接受任务并提交给底层引擎如Spark、hive、Flink、Presto、trino等进行执行。
+
+EngineConnManager（ECM）：Linkis 的EC进程管理服务，负责管控EngineConn的生命周期（启动、停止）。
+
+LinkisEnginePluginServer：该服务负责管理各个引擎的启动物料和配置，另外提供每个EngineConn的启动命令获取，以及每个EngineConn所需要的资源。
+
+PublicEnhencementService（PES）：
公共增强服务，为其他微服务模块提供统一配置管理、上下文服务、物料库、数据源管理、微服务管理和历史任务查询等功能的模块。
## 一、Linkis交互式任务执行架构
### 1.1、任务执行思考
diff --git a/versioned_docs/version-1.3.2/architecture/task-flow.md
b/versioned_docs/version-1.3.2/architecture/task-flow.md
index 3d8f866c143..115bb5c4f18 100644
--- a/versioned_docs/version-1.3.2/architecture/task-flow.md
+++ b/versioned_docs/version-1.3.2/architecture/task-flow.md
@@ -7,13 +7,19 @@ sidebar_position: 0.1
> Linkis task execution is the core function of Linkis. It calls to Linkis's
> computing governance service, public enhancement service, and three-tier
> services of microservice governance. Now it supports the execution of tasks
> of OLAP, OLTP, Streaming and other engine types. This article will discuss
> OLAP The process of task submission, preparation, execution, and result
> return of the type engine is introduced.
## Keywords:
-LinkisMaster: The management service in the computing governance service layer
of Linkis mainly includes several management and control services such as
AppManager, ResourceManager, and LabelManager. Formerly known as LinkisManager
service
-Entrance: The entry service in the computing governance service layer, which
completes the functions of task scheduling, status control, task information
push, etc.
-Orchestrator: Linkis' orchestration service provides powerful orchestration
and computing strategy capabilities to meet the needs of multiple application
scenarios such as multi-active, active-standby, transaction, replay, current
limiting, heterogeneous and mixed computing. At this stage, Orchestrator is
relied on by the Entrance service
-EngineConn (EC): Engine connector, responsible for accepting tasks and
submitting them to underlying engines such as Spark, hive, Flink, Presto,
trino, etc. for execution
-EngineConnManager (ECM): Linkis' EC process management service, responsible
for controlling the life cycle of EngineConn (start, stop)
-LinkisEnginePluginServer: This service is responsible for managing the startup
materials and configuration of each engine, and also provides the startup
command acquisition of each EngineConn, as well as the resources required by
each EngineConn
-PublicEnhencementService (PES): A public enhancement service, a module that
provides functions such as unified configuration management, context service,
material library, data source management, microservice management, and
historical task query for other microservice modules
+LinkisMaster: The management service in the computing governance service layer
of Linkis mainly includes several management and control services such as
AppManager, ResourceManager, and LabelManager. Formerly known as LinkisManager
service.
+
+Entrance: The entry service in the computing governance service layer, which
completes the functions of task scheduling, status control, task information
push, etc.
+
+Orchestrator: Linkis' orchestration service provides powerful orchestration
and computing strategy capabilities to meet the needs of multiple application
scenarios such as multi-active, active-standby, transaction, replay, current
limiting, heterogeneous and mixed computing. At this stage, Orchestrator is
relied on by the Entrance service.
+
+EngineConn (EC): Engine connector, responsible for accepting tasks and
submitting them to underlying engines such as Spark, hive, Flink, Presto,
trino, etc. for execution.
+
+EngineConnManager (ECM): Linkis' EC process management service, responsible
for controlling the life cycle of EngineConn (start, stop).
+
+LinkisEnginePluginServer: This service is responsible for managing the startup
materials and configuration of each engine, and also provides the startup
command acquisition of each EngineConn, as well as the resources required by
each EngineConn.
+
+PublicEnhencementService (PES): A public enhancement service, a module that
provides functions such as unified configuration management, context service,
material library, data source management, microservice management, and
historical task query for other microservice modules.
## 1. Linkis interactive task execution architecture
### 1.1, Task execution thinking
@@ -179,4 +185,4 @@ ResultSetReader: The key class for reading the result set
## 3. Summary
Above we mainly introduced the entire execution
process of the OLAP task of the Linkis Computing Governance Service Group CGS.
According to the processing process of the task request, the task is divided
into four parts: submit, prepare, execute, and return the result stage. CGS is
mainly designed and implemented according to these 4 stages, serves these 4
stages, and provides powerful and flexible capabilities for each stage. In the
submission stage, it mainly pr [...]
-
\ No newline at end of file
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
