This is an automated email from the ASF dual-hosted git repository.
mikexue pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/eventmesh-site.git
The following commit(s) were added to refs/heads/master by this push:
new c9813488 [ISSUE #136] Fix typos in Knative connector docs and some
optimization (#137)
c9813488 is described below
commit c9813488526d2319d4f332fef5c26905ca84f402
Author: Pil0tXia <[email protected]>
AuthorDate: Fri Oct 27 16:45:54 2023 +0800
[ISSUE #136] Fix typos in Knative connector docs and some optimization
(#137)
* remove empty draw.io projects
* Fix typo and optimize format
* Fix 'stateless' typo to 'stateful'
* unify the code block markdown usage
* unify the code block markdown usage - en
---
.../07-knative-connector.md | 8 +--
docs/instruction/03-runtime.md | 2 +-
eventmesh.drawio | 1 -
.../07-knative-connector.md | 57 +++++++++++++++-------
.../current/instruction/03-runtime.md | 2 +-
.../version-v1.0.0/instruction/03-runtime.md | 2 +-
.../version-v1.1.1/instruction/03-runtime.md | 2 +-
.../version-v1.2.0/instruction/03-runtime.md | 2 +-
.../version-v1.3.0/instruction/03-runtime.md | 2 +-
.../version-v1.4.0/instruction/03-runtime.md | 2 +-
.../version-v1.5.0/instruction/03-runtime.md | 2 +-
.../version-v1.6.0/instruction/03-runtime.md | 2 +-
.../version-v1.7.0/instruction/03-runtime.md | 2 +-
.../version-v1.8.0/instruction/03-runtime.md | 2 +-
.../version-v1.9.0/instruction/03-runtime.md | 2 +-
.../version-v1.0.0/instruction/03-runtime.md | 2 +-
.../version-v1.1.1/instruction/03-runtime.md | 2 +-
.../version-v1.2.0/instruction/03-runtime.md | 2 +-
.../version-v1.3.0/instruction/03-runtime.md | 2 +-
.../version-v1.4.0/instruction/03-runtime.md | 2 +-
.../version-v1.5.0/instruction/03-runtime.md | 2 +-
.../version-v1.6.0/instruction/03-runtime.md | 2 +-
.../version-v1.7.0/instruction/03-runtime.md | 2 +-
.../version-v1.8.0/instruction/03-runtime.md | 2 +-
.../version-v1.9.0/instruction/03-runtime.md | 2 +-
...275\345\220\215\347\273\230\345\233\276.drawio" | 1 -
26 files changed, 66 insertions(+), 45 deletions(-)
diff --git
a/docs/design-document/01-event-handling-and-integration/07-knative-connector.md
b/docs/design-document/01-event-handling-and-integration/07-knative-connector.md
index a8e722da..2fa83bf9 100644
---
a/docs/design-document/01-event-handling-and-integration/07-knative-connector.md
+++
b/docs/design-document/01-event-handling-and-integration/07-knative-connector.md
@@ -34,7 +34,7 @@ application {
mainClass = project.hasProperty("mainClass") ?
project.getProperty("mainClass") : 'NULL'
}
```
-- Set ```eventMesh.connector.plugin.type=knative``` in
[eventmesh-runtime/conf/eventmesh.properties](https://github.com/apache/eventmesh/blob/master/eventmesh-runtime/conf/eventmesh.properties)
file.
+- Set `eventMesh.connector.plugin.type=knative` in
[eventmesh-runtime/conf/eventmesh.properties](https://github.com/apache/eventmesh/blob/master/eventmesh-runtime/conf/eventmesh.properties)
file.
## Demo
### Publish an Event Message from Knative and Subscribe from EventMesh
@@ -50,14 +50,14 @@ $ curl -i
http://cloudevents-player.default.127.0.0.1.sslip.io -H "Content-Type:
```
#### Step 3: Subscribe from an EventMesh
-- Set ```public static final String EVENTMESH_HTTP_ASYNC_TEST_TOPIC =
"messages";``` in
[ExampleConstants.java](https://github.com/apache/eventmesh/blob/master/eventmesh-examples/src/main/java/org/apache/eventmesh/common/ExampleConstants.java)
file.
+- Set `public static final String EVENTMESH_HTTP_ASYNC_TEST_TOPIC =
"messages";` in
[ExampleConstants.java](https://github.com/apache/eventmesh/blob/master/eventmesh-examples/src/main/java/org/apache/eventmesh/common/ExampleConstants.java)
file.
```bash
$ cd eventmesh-examples
$ ../gradlew
-PmainClass=org.apache.eventmesh.http.demo.sub.SpringBootDemoApplication run
```
#### Expected Result
-The following message with ```data``` field as ```Hello CloudEvents!``` will
be printed on the console of EventMesh server.
+The following message with `data` field as `Hello CloudEvents!` will be
printed on the console of EventMesh server.
```bash
2022-09-05 16:37:58,237 INFO [eventMesh-clientManage-]
DefaultConsumer(DefaultConsumer.java:60) - \
[{"event":{"attributes":{"datacontenttype":"application/json","id":"123456789","mediaType":"application/json",\
@@ -85,7 +85,7 @@ $ curl
http://cloudevents-player.default.127.0.0.1.sslip.io/messages
```
#### Expected Result
-The following message with ```data``` field as ```Hello Knative from
EventMesh!``` will be printed on the console of EventMesh server.
+The following message with `data` field as `Hello Knative from EventMesh!`
will be printed on the console of EventMesh server.
```bash
2022-09-05 16:52:41,633 INFO [eventMesh-clientManage-]
DefaultConsumer(DefaultConsumer.java:60) - \
[{"event":{"attributes":{"datacontenttype":"application/json","id":"1234","mediaType":"application/json",\
diff --git a/docs/instruction/03-runtime.md b/docs/instruction/03-runtime.md
index f3411a5c..f205f352 100644
--- a/docs/instruction/03-runtime.md
+++ b/docs/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
diff --git a/eventmesh.drawio b/eventmesh.drawio
deleted file mode 100644
index 8bf71161..00000000
--- a/eventmesh.drawio
+++ /dev/null
@@ -1 +0,0 @@
-<mxfile host="app.diagrams.net" modified="2022-01-16T08:34:47.494Z" agent="5.0
(Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/96.0.4664.55 Safari/537.36" version="14.7.0" etag="cAdWNbg2x_95eGoZQDBQ"
type="github"><diagram
id="c7ZOno8yMaTAqoGoMUIP">UzV2zq1wL0osyPDNT0nNUTV2VTV2LsrPL4GwciucU3NyVI0MMlNUjV1UjYwMgFjVyA2HrCFY1qAgsSg1rwSLBiADYTaQg2Y1AA==</diagram></mxfile>
\ No newline at end of file
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/07-knative-connector.md
b/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/07-knative-connector.md
index d7c67380..d75a6a62 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/07-knative-connector.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/07-knative-connector.md
@@ -1,11 +1,15 @@
-# Knative Connector插件
+# Knative Connector 插件
## 准备
-### 创建Knative Source和Sink
-我们使用 *cloudevents-player*
[Knative服务](https://knative.dev/docs/serving/)作为例子。如果您不知道如何创建
*cloudevents-player*
Knative服务作为source和sink，请按照这个[链接](https://knative.dev/docs/getting-started/first-source/#creating-your-first-source)的步骤进行创建。
-### EventMesh配置文件
+### 创建 Knative Source 和 Sink
+
+我们使用 *cloudevents-player* [Knative
服务](https://knative.dev/docs/serving/)作为例子。如果您不知道如何创建 *cloudevents-player*
Knative 服务作为 source 和
sink，请按照这个[链接](https://knative.dev/docs/getting-started/first-source/#creating-your-first-source)的步骤进行创建。
+
+### EventMesh 配置文件
+
- 将以下配置加入
[eventmesh-starter/build.gradle](https://github.com/apache/eventmesh/blob/master/eventmesh-starter/build.gradle)
文件
+
```bash
plugins {
id 'application'
@@ -23,7 +27,9 @@ dependencies {
implementation project(":eventmesh-runtime")
}
```
+
- 将以下配置加入
[eventmesh-examples/build.gradle](https://github.com/apache/eventmesh/blob/master/eventmesh-examples/build.gradle)文件
+
```bash
plugins {
id 'application'
@@ -33,29 +39,39 @@ application {
mainClass = project.hasProperty("mainClass") ?
project.getProperty("mainClass") : 'NULL'
}
```
-- 在
[eventmesh-runtime/conf/eventmesh.properties](https://github.com/apache/eventmesh/blob/master/eventmesh-runtime/conf/eventmesh.properties)
文件中设置```eventMesh.connector.plugin.type=knative```变量
+
+- 在
[eventmesh-runtime/conf/eventmesh.properties](https://github.com/apache/eventmesh/blob/master/eventmesh-runtime/conf/eventmesh.properties)
文件中设置`eventMesh.connector.plugin.type=knative`变量
## 演示
-### Knative发布事件消息/EventMesh订阅
-#### 步骤1：启动一台EventMesh服务器
+
+### Knative 发布事件消息 / EventMesh 订阅
+
+#### 步骤 1：启动一台 EventMesh 服务器
+
```bash
$ cd eventmesh-starter
$ ../gradlew -PmainClass=org.apache.eventmesh.starter.StartUp run
```
-#### 步骤2：从Knative Source发布一条消息
+#### 步骤 2：从 Knative Source 发布一条消息
+
```bash
$ curl -i http://cloudevents-player.default.127.0.0.1.sslip.io -H
"Content-Type: application/json" -H "Ce-Id: 123456789" -H "Ce-Specversion: 1.0"
-H "Ce-Type: some-type" -H "Ce-Source: command-line" -d '{"msg":"Hello
CloudEvents!"}'
```
-#### 步骤3：从EventMesh订阅
-- 在
[ExampleConstants.java](https://github.com/apache/eventmesh/blob/master/eventmesh-examples/src/main/java/org/apache/eventmesh/common/ExampleConstants.java)
文件中设置 ```public static final String EVENTMESH_HTTP_ASYNC_TEST_TOPIC =
"messages";```变量
+#### 步骤 3：从 EventMesh 订阅
+
+- 在
[ExampleConstants.java](https://github.com/apache/eventmesh/blob/master/eventmesh-examples/src/main/java/org/apache/eventmesh/common/ExampleConstants.java)
文件中设置 `public static final String EVENTMESH_HTTP_ASYNC_TEST_TOPIC =
"messages";`变量
+
```bash
$ cd eventmesh-examples
$ ../gradlew
-PmainClass=org.apache.eventmesh.http.demo.sub.SpringBootDemoApplication run
```
+
#### 预期结果
-以下```data```为```Hello CloudEvents!```的消息将会打印在EventMesh服务器的控制台上。
+
+以下`data`为`Hello CloudEvents!`的消息将会打印在 EventMesh 服务器的控制台上。
+
```bash
2022-09-05 16:37:58,237 INFO [eventMesh-clientManage-]
DefaultConsumer(DefaultConsumer.java:60) - \
[{"event":{"attributes":{"datacontenttype":"application/json","id":"123456789","mediaType":"application/json",\
@@ -63,27 +79,34 @@ $ ../gradlew
-PmainClass=org.apache.eventmesh.http.demo.sub.SpringBootDemoApplic
"id":"123456789","receivedAt":"2022-09-05T10:37:49.537658+02:00[Europe/Madrid]","type":"RECEIVED"}]
```
-### EventMessh发布事件消息/Knative订阅
-#### 步骤1：启动一台EventMesh服务器
+### EventMesh 发布事件消息 / Knative 订阅
+
+#### 步骤 1：启动一台 EventMesh 服务器
+
```bash
$ cd eventmesh-starter
$ ../gradlew -PmainClass=org.apache.eventmesh.starter.StartUp run
```
-#### 步骤2：从EventMesh发布一条消息
-我们用Knative Connector的测试程序来演示这个功能。
+#### 步骤 2：从 EventMesh 发布一条消息
+
+我们用 Knative Connector 的测试程序来演示这个功能。
+
```bash
$ cd eventmesh-connector-plugin/eventmesh-connector-knative
$ ../../gradlew clean test --tests KnativeProducerImplTest.testPublish
```
-#### 步骤3：从Knative订阅
+#### 步骤 3：从 Knative 订阅
+
```bash
$ curl http://cloudevents-player.default.127.0.0.1.sslip.io/messages
```
#### 预期结果
-以下```data```为```Hello Knative from EventMesh!```的消息将会打印在EventMesh服务器的控制台上。
+
+以下`data`为`Hello Knative from EventMesh!`的消息将会打印在 EventMesh 服务器的控制台上。
+
```bash
2022-09-05 16:52:41,633 INFO [eventMesh-clientManage-]
DefaultConsumer(DefaultConsumer.java:60) - \
[{"event":{"attributes":{"datacontenttype":"application/json","id":"1234","mediaType":"application/json",\
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/current/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/current/instruction/03-runtime.md
index 37236e0b..e6727e06 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/instruction/03-runtime.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.0.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.0.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.0.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.0.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.1.1/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.1.1/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.1.1/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.1.1/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.2.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.2.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.2.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.2.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.6.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.6.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.6.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.6.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/instruction/03-runtime.md
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/instruction/03-runtime.md
index 7fc4bbef..02756b4c 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/instruction/03-runtime.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-v1.9.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# Eventmesh-runtime 快速入门说明
-EventMesh Runtime 是 EventMesh 集群中无状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
+EventMesh Runtime 是 EventMesh 集群中有状态的 Mesh 节点，负责 Source Connector 与 Sink
Connector 之间的事件传输，并可以使用 EventMesh Storage 作为事件的存储队列。
## 1 本地构建运行
diff --git a/versioned_docs/version-v1.0.0/instruction/03-runtime.md
b/versioned_docs/version-v1.0.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.0.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.0.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.1.1/instruction/03-runtime.md
b/versioned_docs/version-v1.1.1/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.1.1/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.1.1/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.2.0/instruction/03-runtime.md
b/versioned_docs/version-v1.2.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.2.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.2.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.3.0/instruction/03-runtime.md
b/versioned_docs/version-v1.3.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.3.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.3.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.4.0/instruction/03-runtime.md
b/versioned_docs/version-v1.4.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.4.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.4.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.5.0/instruction/03-runtime.md
b/versioned_docs/version-v1.5.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.5.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.5.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.6.0/instruction/03-runtime.md
b/versioned_docs/version-v1.6.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.6.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.6.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.7.0/instruction/03-runtime.md
b/versioned_docs/version-v1.7.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.7.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.7.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.8.0/instruction/03-runtime.md
b/versioned_docs/version-v1.8.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.8.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.8.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git a/versioned_docs/version-v1.9.0/instruction/03-runtime.md
b/versioned_docs/version-v1.9.0/instruction/03-runtime.md
index 5eace571..0b0e4557 100644
--- a/versioned_docs/version-v1.9.0/instruction/03-runtime.md
+++ b/versioned_docs/version-v1.9.0/instruction/03-runtime.md
@@ -1,6 +1,6 @@
# EventMesh Runtime
-The EventMesh Runtime is a stateless mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
+The EventMesh Runtime is a stateful mesh node in an EventMesh cluster that is
responsible for event transfer between the Source Connector and the Sink
Connector, and can use EventMesh Storage as a storage queue for events.
## 1 Run on your local machine
diff --git
"a/\346\234\252\345\221\275\345\220\215\347\273\230\345\233\276.drawio"
"b/\346\234\252\345\221\275\345\220\215\347\273\230\345\233\276.drawio"
deleted file mode 100644
index cc31e589..00000000
--- "a/\346\234\252\345\221\275\345\220\215\347\273\230\345\233\276.drawio"
+++ /dev/null
@@ -1 +0,0 @@
-<mxfile host="app.diagrams.net" modified="2021-05-07T13:10:41.801Z" agent="5.0
(Macintosh; Intel Mac OS X 11_1_0) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/87.0.4280.141 Safari/537.36" version="14.6.6"
etag="M__-T_L9RKH3IeokVA34" type="github"><diagram
id="VSH4N70e9UW8oP_trlYu">UzV2zq1wL0osyPDNT0nNUTV2VTV2LsrPL4GwciucU3NyVI0MMlNUjV1UjYwMgFjVyA2HrCFY1qAgsSg1rwSLBiADYTaQg2Y1AA==</diagram></mxfile>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
