This is an automated email from the ASF dual-hosted git repository.
liuyu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new eee038870db [fix][doc] Updated example section (#15727)
eee038870db is described below
commit eee038870db95e009abde32e89b9d736a9e9cd1c
Author: mans2singh <[email protected]>
AuthorDate: Tue May 24 21:54:34 2022 -0400
[fix][doc] Updated example section (#15727)
---
site2/docs/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.10.0/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.4.1/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.4.2/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.5.0/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.5.1/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.5.2/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.6.0/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.6.1/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.6.2/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.6.3/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.6.4/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.7.0/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.7.1/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.7.2/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.7.3/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.7.4/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.8.0/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.8.1/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.8.2/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.8.3/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.9.0/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.9.1/schema-understand.md | 2 +-
site2/website/versioned_docs/version-2.9.2/schema-understand.md | 2 +-
24 files changed, 24 insertions(+), 24 deletions(-)
diff --git a/site2/docs/schema-understand.md b/site2/docs/schema-understand.md
index ab44a85e7fe..4679c847896 100644
--- a/site2/docs/schema-understand.md
+++ b/site2/docs/schema-understand.md
@@ -429,7 +429,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.10.0/schema-understand.md
b/site2/website/versioned_docs/version-2.10.0/schema-understand.md
index 7e5ec8d3069..4fe190bd58b 100644
--- a/site2/website/versioned_docs/version-2.10.0/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.10.0/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.4.1/schema-understand.md
b/site2/website/versioned_docs/version-2.4.1/schema-understand.md
index 98114e39ff9..ba2e370ed37 100644
--- a/site2/website/versioned_docs/version-2.4.1/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.4.1/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.4.2/schema-understand.md
b/site2/website/versioned_docs/version-2.4.2/schema-understand.md
index 0d5894e7ef7..9c8257f53ac 100644
--- a/site2/website/versioned_docs/version-2.4.2/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.4.2/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.5.0/schema-understand.md
b/site2/website/versioned_docs/version-2.5.0/schema-understand.md
index df46d06625e..77b52a690e0 100644
--- a/site2/website/versioned_docs/version-2.5.0/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.5.0/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.5.1/schema-understand.md
b/site2/website/versioned_docs/version-2.5.1/schema-understand.md
index 609f6499880..b344263da7e 100644
--- a/site2/website/versioned_docs/version-2.5.1/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.5.1/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.5.2/schema-understand.md
b/site2/website/versioned_docs/version-2.5.2/schema-understand.md
index 609f6499880..b344263da7e 100644
--- a/site2/website/versioned_docs/version-2.5.2/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.5.2/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.6.0/schema-understand.md
b/site2/website/versioned_docs/version-2.6.0/schema-understand.md
index 609f6499880..b344263da7e 100644
--- a/site2/website/versioned_docs/version-2.6.0/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.6.0/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.6.1/schema-understand.md
b/site2/website/versioned_docs/version-2.6.1/schema-understand.md
index 609f6499880..b344263da7e 100644
--- a/site2/website/versioned_docs/version-2.6.1/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.6.1/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.6.2/schema-understand.md
b/site2/website/versioned_docs/version-2.6.2/schema-understand.md
index 609f6499880..b344263da7e 100644
--- a/site2/website/versioned_docs/version-2.6.2/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.6.2/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.6.3/schema-understand.md
b/site2/website/versioned_docs/version-2.6.3/schema-understand.md
index 609f6499880..b344263da7e 100644
--- a/site2/website/versioned_docs/version-2.6.3/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.6.3/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.6.4/schema-understand.md
b/site2/website/versioned_docs/version-2.6.4/schema-understand.md
index 609f6499880..b344263da7e 100644
--- a/site2/website/versioned_docs/version-2.6.4/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.6.4/schema-understand.md
@@ -343,7 +343,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.7.0/schema-understand.md
b/site2/website/versioned_docs/version-2.7.0/schema-understand.md
index 4fdb49db222..9f0f8e357d9 100644
--- a/site2/website/versioned_docs/version-2.7.0/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.7.0/schema-understand.md
@@ -351,7 +351,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.7.1/schema-understand.md
b/site2/website/versioned_docs/version-2.7.1/schema-understand.md
index 4fdb49db222..9f0f8e357d9 100644
--- a/site2/website/versioned_docs/version-2.7.1/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.7.1/schema-understand.md
@@ -351,7 +351,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.7.2/schema-understand.md
b/site2/website/versioned_docs/version-2.7.2/schema-understand.md
index 4fdb49db222..9f0f8e357d9 100644
--- a/site2/website/versioned_docs/version-2.7.2/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.7.2/schema-understand.md
@@ -351,7 +351,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.7.3/schema-understand.md
b/site2/website/versioned_docs/version-2.7.3/schema-understand.md
index 4fdb49db222..9f0f8e357d9 100644
--- a/site2/website/versioned_docs/version-2.7.3/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.7.3/schema-understand.md
@@ -351,7 +351,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.7.4/schema-understand.md
b/site2/website/versioned_docs/version-2.7.4/schema-understand.md
index 4fdb49db222..9f0f8e357d9 100644
--- a/site2/website/versioned_docs/version-2.7.4/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.7.4/schema-understand.md
@@ -351,7 +351,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.8.0/schema-understand.md
b/site2/website/versioned_docs/version-2.8.0/schema-understand.md
index 1db62df70bd..7fef07a604f 100644
--- a/site2/website/versioned_docs/version-2.8.0/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.8.0/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.8.1/schema-understand.md
b/site2/website/versioned_docs/version-2.8.1/schema-understand.md
index 1db62df70bd..7fef07a604f 100644
--- a/site2/website/versioned_docs/version-2.8.1/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.8.1/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.8.2/schema-understand.md
b/site2/website/versioned_docs/version-2.8.2/schema-understand.md
index 1db62df70bd..7fef07a604f 100644
--- a/site2/website/versioned_docs/version-2.8.2/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.8.2/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.8.3/schema-understand.md
b/site2/website/versioned_docs/version-2.8.3/schema-understand.md
index 1db62df70bd..7fef07a604f 100644
--- a/site2/website/versioned_docs/version-2.8.3/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.8.3/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.9.0/schema-understand.md
b/site2/website/versioned_docs/version-2.9.0/schema-understand.md
index 7e5ec8d3069..4fe190bd58b 100644
--- a/site2/website/versioned_docs/version-2.9.0/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.9.0/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.9.1/schema-understand.md
b/site2/website/versioned_docs/version-2.9.1/schema-understand.md
index 7e5ec8d3069..4fe190bd58b 100644
--- a/site2/website/versioned_docs/version-2.9.1/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.9.1/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
diff --git a/site2/website/versioned_docs/version-2.9.2/schema-understand.md
b/site2/website/versioned_docs/version-2.9.2/schema-understand.md
index 7e5ec8d3069..4fe190bd58b 100644
--- a/site2/website/versioned_docs/version-2.9.2/schema-understand.md
+++ b/site2/website/versioned_docs/version-2.9.2/schema-understand.md
@@ -430,7 +430,7 @@ Suppose that:
* You have a consumer (for example, MySQL) receiving messages from the topic
_P_.
-* You application reads the messages from _P_ and writes the messages to MySQL.
+* Your application reads the messages from _P_ and writes the messages to
MySQL.
In this case, you can use `AUTO_CONSUME` to verify whether the bytes produced
by _P_ can be sent to MySQL or not.
