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.git
The following commit(s) were added to refs/heads/master by this push:
new 1497fd331 [ISSUE #4185] Correct eventmesh.properties comment grammar
mistake (#4187)
1497fd331 is described below
commit 1497fd3310170fc8b2574c815544221d45ce76b2
Author: Pil0tXia <[email protected]>
AuthorDate: Mon Jul 10 16:56:30 2023 +0800
[ISSUE #4185] Correct eventmesh.properties comment grammar mistake (#4187)
* doc: Correct eventmesh.properties comment grammar mistake
* doc: Correct README.md grammar sequence mistake
---
eventmesh-connectors/README.md | 2 +-
eventmesh-runtime/conf/eventmesh.properties | 2 +-
.../eventmesh-webhook-admin/src/test/resources/eventmesh.properties | 2 +-
.../eventmesh-webhook-receive/src/test/resources/eventmesh.properties | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/eventmesh-connectors/README.md b/eventmesh-connectors/README.md
index 1cba277ea..a52d5dd73 100644
--- a/eventmesh-connectors/README.md
+++ b/eventmesh-connectors/README.md
@@ -4,7 +4,7 @@
A connector is a bridge that interacts with a specific external service or
underlying data source (e.g., Databases) on behalf of user applications. A
connector is either a Source or a Sink.
## Source
-A source connector obtains data from an underlying data producer and delivers
it to targets, after original data has been transformed into CloudEvents. It
doesn't limit the way how a source retrieves data. (e.g., A source may pull
data from a message queue or act as an HTTP server waiting for data sent to it).
+A source connector obtains data from an underlying data producer, and delivers
it to targets after original data has been transformed into CloudEvents. It
doesn't limit the way how a source retrieves data. (e.g., A source may pull
data from a message queue or act as an HTTP server waiting for data sent to it).
## Sink
A sink connector receives CloudEvents and does some specific business logics.
(e.g., A MySQL Sink extracts useful data from CloudEvents and writes them to a
MySQL database).
diff --git a/eventmesh-runtime/conf/eventmesh.properties
b/eventmesh-runtime/conf/eventmesh.properties
index 4e5cbd54b..df272a01a 100644
--- a/eventmesh-runtime/conf/eventmesh.properties
+++ b/eventmesh-runtime/conf/eventmesh.properties
@@ -115,5 +115,5 @@ eventMesh.webHook.fileMode.filePath=
#{eventMeshHome}/webhook
# Nacos storage mode, and the configuration naming rule is eventmesh webHook.
nacosMode. {nacos native configuration key} please see the specific
configuration [nacos github
api](https://github.com/alibaba/nacos/blob/develop/api/src/main/java/com/alibaba/nacos/api/SystemPropertyKeyConst.java)
## Address of Nacos
eventMesh.webHook.nacosMode.serverAddr=127.0.0.1:8848
-# Webhook eventcloud sending mode. And eventmesh connector. plugin. The type
configuration is the same
+# Webhook CloudEvent sending mode. This property is the same as the
eventMesh.storage.plugin.type configuration.
eventMesh.webHook.producer.storage=standalone
diff --git
a/eventmesh-webhook/eventmesh-webhook-admin/src/test/resources/eventmesh.properties
b/eventmesh-webhook/eventmesh-webhook-admin/src/test/resources/eventmesh.properties
index cbf4371d8..b808436f9 100644
---
a/eventmesh-webhook/eventmesh-webhook-admin/src/test/resources/eventmesh.properties
+++
b/eventmesh-webhook/eventmesh-webhook-admin/src/test/resources/eventmesh.properties
@@ -24,5 +24,5 @@ eventMesh.webHook.fileMode.filePath=.
# Nacos storage mode, and the configuration naming rule is eventmesh webHook.
nacosMode. {nacos native configuration key} please see the specific
configuration [nacos github
api](https://github.com/alibaba/nacos/blob/develop/api/src/main/java/com/alibaba/nacos/api/SystemPropertyKeyConst.java)
## Address of Nacos
eventMesh.webHook.nacosMode.serverAddr=127.0.0.1:8848
-# Webhook eventcloud sending mode. And eventmesh storage. plugin. The type
configuration is the same
+# Webhook CloudEvent sending mode. This property is the same as the
eventMesh.storage.plugin.type configuration.
eventMesh.webHook.producer.storage=standalone
diff --git
a/eventmesh-webhook/eventmesh-webhook-receive/src/test/resources/eventmesh.properties
b/eventmesh-webhook/eventmesh-webhook-receive/src/test/resources/eventmesh.properties
index 90e359d58..bd700c26c 100644
---
a/eventmesh-webhook/eventmesh-webhook-receive/src/test/resources/eventmesh.properties
+++
b/eventmesh-webhook/eventmesh-webhook-receive/src/test/resources/eventmesh.properties
@@ -26,5 +26,5 @@ eventMesh.webHook.fileMode.filePath=.
# Nacos storage mode, and the configuration naming rule is eventmesh webHook.
nacosMode. {nacos native configuration key} please see the specific
configuration [nacos github
api](https://github.com/alibaba/nacos/blob/develop/api/src/main/java/com/alibaba/nacos/api/SystemPropertyKeyConst.java)
## Address of Nacos
eventMesh.webHook.nacosMode.serverAddr=127.0.0.1:8848
-# Webhook eventcloud sending mode. And eventmesh storage. plugin. The type
configuration is the same
+# Webhook CloudEvent sending mode. This property is the same as the
eventMesh.storage.plugin.type configuration.
eventMesh.webHook.producer.storage=standalone
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
