mxsm commented on code in PR #438:
URL: https://github.com/apache/rocketmq-site/pull/438#discussion_r1070290025


##########
i18n/en/docusaurus-plugin-content-docs/current/08-数据集成/26RocketMQ Connect 
Concept.md:
##########
@@ -1,28 +1,26 @@
-# 概念
+# RocketMQ Connect Concept
 
 ## Connector
 
-连接器,定义数据从哪复制到哪,是从源数据系统读取数据写入RocketMQ,这种是SourceConnector
-,或从RocketMQ读数据写入到目标系统,这种是SinkConnector。Connector决定需要创建任务的数量,从Worker接收配置传递给任务。
+The connector defines where the data is copied from and where it is copied to. 
It reads data from the source system and writes it to RocketMQ, which is the 
SourceConnector, or reads data from RocketMQ and writes it to the target 
system, which is the SinkConnector. The Connector decides the number of tasks 
to be created, and receives configuration from the Worker and passes it to the 
task.
 
 ## Task
 
-是Connector任务分片的最小分配单位,是实际将源数据源数据复制数据到RocketMQ(SourceTask),或者将数据从RocketMQ读取数据写入到目标系统(SinkTask)真正的执行者,Task是无状态的可以动态的启停任务,多个Task是可以并行执行的,Connector复制数据的并行度主要体现在Task数量上。
+Task is the minimum allocation unit of Connector task sharding, which is 
responsible for actually copying the source data to RocketMQ (SourceTask), or 
reading data from RocketMQ and writing it to the target system (SinkTask). 
Tasks are stateless, and can be started and stopped dynamically. Multiple tasks 
can be executed in parallel, and the parallelism of data copying by the 
Connector is mainly reflected in the number of tasks.
 
-![RocketMQ基本模型](../picture/32rocketmq-connect/Connector-Task-Concept.png)
+![RocketMQ基本模型](E:/develop/github/contribution/rocketmq-site/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/32rocketmq-connect/Connector-Task-Concept.png)

Review Comment:
   my fault, i will fix it and re-submit later



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to