This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
The following commit(s) were added to refs/heads/master by this push:
new 448226674d [INLONG-922][Doc] Update the introduction page (#923)
448226674d is described below
commit 448226674def2fb4b74c8efa7d122cbe12333a93
Author: Charles Zhang <[email protected]>
AuthorDate: Wed Feb 21 16:51:56 2024 +0800
[INLONG-922][Doc] Update the introduction page (#923)
---
docs/design_and_concept/the_format_in_inlong.md | 2 +-
docs/introduction.md | 6 +++---
.../current/design_and_concept/the_format_in_inlong.md | 2 +-
.../docusaurus-plugin-content-docs/current/introduction.md | 10 +++++-----
4 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/design_and_concept/the_format_in_inlong.md
b/docs/design_and_concept/the_format_in_inlong.md
index 8e2f9d939e..e203792f95 100644
--- a/docs/design_and_concept/the_format_in_inlong.md
+++ b/docs/design_and_concept/the_format_in_inlong.md
@@ -14,7 +14,7 @@ Format provides two interfaces : SerializationSchema and
DeserializationSchema :
- When Flink reads data from MQ , it works vice versa . It reads data from MQ
with format Byte[] . Then deserializes them into Format and finally converts
them into Flink row .
> See
-> details:
[`inlong-sort/sort-formats`](https://github.com/apache/inlong/tree/release-1.5.0/inlong-sort/sort-formats)
+> details:
[`inlong-sort/sort-formats`](https://github.com/apache/inlong/tree/master/inlong-sort/sort-formats)
## The format in InLong
diff --git a/docs/introduction.md b/docs/introduction.md
index 6aa0f60ce5..3d6dc7ff96 100644
--- a/docs/introduction.md
+++ b/docs/introduction.md
@@ -48,7 +48,7 @@ values={[
<TabItem value="standard"> Standard Architecture: contains all InLong
components such as InLong Agent, Manager, MQ, Sort, Dashboard, which supports
`Data Ingestion`, `Data Synchronization` and `Data Subscription` at the same
time.
<img src="/img/inlong-structure-en.png" align="center" alt="Apache InLong"/>
</TabItem>
-<TabItem value="lightweight"> Lightweight Architecture: contains only one
component of InLong Sort, which also can be used with Manager, Dashboard, and
it is simple and flexible, only support `Data Synchronization`.
+<TabItem value="lightweight"> Lightweight Architecture: contains only one
component of InLong Sort, which also can be used with Manager, Dashboard, and
it is simple and flexible, support `Data Synchronization`.
<img src="/img/inlong-structure-light.png" align="center" style={{objectFit:
'cover', height: '460px', width: '860px'}} alt="Apache InLong"/>
</TabItem>
</Tabs>
@@ -59,9 +59,9 @@ Apache InLong serves the entire life cycle from data
collection to landing, and
- **inlong-agent**, data collection services, including file collection, DB
collection, etc.
- **inlong-dataproxy**, a Proxy component based on Flume-ng, supports data
transmission blocking, placing retransmission, and has the ability to forward
received data to different MQ (message queues).
- **inlong-tubemq**, Tencent's self-developed message queuing service,
focuses on high-performance storage and transmission of massive data in big
data scenarios and has a relatively good core advantage in mass practice and
low cost.
-- **inlong-sort**, after consuming data from different MQ services, perform
ETL processing, and then aggregate and write the data into Apache Hive,
ClickHouse, Hbase, IceBerg, Hudi, etc.
+- **inlong-sort**, after consuming data from different MQ services, perform
ETL processing, and then aggregate and write the data into Apache Hive,
ClickHouse, HBase, IceBerg, Hudi, etc.
- **inlong-manager**, provides complete data service management and control
capabilities, including metadata, OpenAPI, task flow, authority, etc.
-- **inlong-dashboard**, a front-end page for managing data access,
simplifying the use of the entire InLong control platform.
+- **inlong-dashboard**, a front-end page for managing data integration task,
simplifying the use of the entire InLong control platform.
- **inlong-audit**, performs real-time audit and reconciliation on the
incoming and outgoing traffic of the Agent, DataProxy, and Sort modules of the
InLong system.
## Supported Data Nodes (Updating)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/the_format_in_inlong.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/the_format_in_inlong.md
index faa148f236..0b2bcd9cd1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/the_format_in_inlong.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/the_format_in_inlong.md
@@ -16,7 +16,7 @@ Flink 的 Format 提供了两种接口：SerializationSchema 和 Deserialization
这时调用了 `SerializationSchema#serialize` 方法，数据会序列化成 `Byte[]`，写入到 `MQ`。
- 当 Flink 读取 MQ 的数据时，该过程则相反：从 MQ 读取数据，数据格式为 `byte[]`，反序列化为`Format`，再转换为 `Flink
row`。
-> 详情请查看代码
[`inlong-sort/sort-formats`](https://github.com/apache/inlong/tree/release-1.5.0/inlong-sort/sort-formats)
+> 详情请查看代码
[`inlong-sort/sort-formats`](https://github.com/apache/inlong/tree/master/inlong-sort/sort-formats)
## InLong 中的 Format
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md
index 8f2778055c..80927caad1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md
@@ -17,7 +17,7 @@ Apache InLong 依托 10 万亿级别的数据接入和处理能力，整合了
## 特性
- 简单易用
- 基于SaaS模式对外服务，用户只需要按主题发布和订阅数据即可完成数据的上报，传输和分发工作
+ 基于 SaaS 模式对外服务，用户只需要按主题发布和订阅数据即可完成数据的上报，传输和分发工作
- 稳定可靠
@@ -25,7 +25,7 @@ Apache InLong 依托 10 万亿级别的数据接入和处理能力，整合了
- 功能完善
- 支持各种类型的数据接入方式，多种不同类型的MQ集成，以及基于配置规则的实时数据ETL和数据分拣落地，并支持以可插拔方式扩展系统能力
+ 支持各种类型的数据接入方式，多种不同类型的 MQ 集成，以及基于配置规则的实时数据 ETL 和数据分拣落地，并支持以可插拔方式扩展系统能力
- 服务集成
@@ -45,7 +45,7 @@ values={[
<TabItem value="standard"> 标准架构：包含 InLong Agent、Manager、MQ、Sort、Dashboard 等所有
InLong 组件，同时支持`数据接入`、`数据同步`和`数据订阅`。
<img src="/img/inlong-structure-zh.png" align="center" alt="Apache InLong"/>
</TabItem>
-<TabItem value="lightweight"> 轻量化架构：只包含 InLong Sort 一个组件，也可以搭配
Manager，Dashboard 一起使用。轻量化架构简单、灵活，只支持`数据同步`。
+<TabItem value="lightweight"> 轻量化架构：只包含 InLong Sort 一个组件，也可以搭配
Manager，Dashboard 一起使用。轻量化架构简单、灵活，支持`数据同步`。
<img src="/img/inlong-structure-light.png" align="center" style={{objectFit:
'cover', height: '460px', width: '860px'}} alt="Apache InLong"/>
</TabItem>
</Tabs>
@@ -56,9 +56,9 @@ Apache InLong 服务于数据采集到落地的整个生命周期，按数据的
- **inlong-agent**，数据采集服务，包括文件采集、DB 采集等。
- **inlong-dataproxy**，一个基于 Flume-ng 的 Proxy 组件，支持数据发送阻塞和落盘重发，拥有将接收到的数据转发到不同
MQ（消息队列）的能力。
- **inlong-tubemq**，腾讯自研的消息队列服务，专注于大数据场景下海量数据的高性能存储和传输，在海量实践和低成本方面有着良好的核心优势。
-- **inlong-sort**，对从不同的 MQ 消费到的数据进行 ETL 处理，然后汇聚并写入
Hive、ClickHouse、Hbase、Iceberg、Hudi 等存储系统。
+- **inlong-sort**，对从不同的 MQ 消费到的数据进行 ETL 处理，然后汇聚并写入
Hive、ClickHouse、HBase、Iceberg、Hudi 等存储系统。
- **inlong-manager**，提供完整的数据服务管控能力，包括元数据、任务流、权限，OpenAPI 等。
-- **inlong-dashboard**，用于管理数据接入的前端页面，简化整个 InLong 管控平台的使用。
+- **inlong-dashboard**，用于管理数据集成任务的前端页面，简化整个 InLong 管控平台的使用。
- **inlong-audit**，对 InLong 系统的 Agent、DataProxy、Sort 模块的入流量、出流量进行实时审计对账。
## 已支持数据节点（更新中）
