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 1d68ff0697e [fix][schema-understand][docs] Minor correction in
producer side step 1 (#16352)
1d68ff0697e is described below
commit 1d68ff0697e918e63bb48767e0fb95657bddd347
Author: mans2singh <[email protected]>
AuthorDate: Sun Jul 3 22:05:39 2022 -0400
[fix][schema-understand][docs] Minor correction in producer side step 1
(#16352)
---
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 4679c847896..ea8a140c4aa 100644
--- a/site2/docs/schema-understand.md
+++ b/site2/docs/schema-understand.md
@@ -516,7 +516,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 4fe190bd58b..f454dd6873e 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
@@ -517,7 +517,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 ba2e370ed37..69977851e6f 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
@@ -411,7 +411,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 9c8257f53ac..2a70971c48c 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
@@ -411,7 +411,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 77b52a690e0..81d6377613c 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
@@ -411,7 +411,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 b344263da7e..fda3d6dfecb 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
@@ -410,7 +410,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 b344263da7e..fda3d6dfecb 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
@@ -410,7 +410,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 b344263da7e..fda3d6dfecb 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
@@ -410,7 +410,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 b344263da7e..fda3d6dfecb 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
@@ -410,7 +410,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 b344263da7e..fda3d6dfecb 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
@@ -410,7 +410,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 b344263da7e..fda3d6dfecb 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
@@ -410,7 +410,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 b344263da7e..fda3d6dfecb 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
@@ -410,7 +410,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 9f0f8e357d9..333c902b583 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
@@ -418,7 +418,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 9f0f8e357d9..333c902b583 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
@@ -418,7 +418,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 9f0f8e357d9..333c902b583 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
@@ -418,7 +418,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 9f0f8e357d9..333c902b583 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
@@ -418,7 +418,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 9f0f8e357d9..333c902b583 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
@@ -418,7 +418,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 7fef07a604f..153d96e6e71 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
@@ -497,7 +497,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 7fef07a604f..153d96e6e71 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
@@ -497,7 +497,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 7fef07a604f..153d96e6e71 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
@@ -497,7 +497,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 7fef07a604f..153d96e6e71 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
@@ -497,7 +497,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 4fe190bd58b..f454dd6873e 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
@@ -517,7 +517,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 4fe190bd58b..f454dd6873e 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
@@ -517,7 +517,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
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 4fe190bd58b..f454dd6873e 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
@@ -517,7 +517,7 @@ This diagram illustrates how does schema work on the
Producer side.
The schema instance defines the schema for the data being produced using
the producer instance.
- Take AVRO as an example, Pulsar extract schema definition from the POJO
class and construct the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
+ Take AVRO as an example, Pulsar extracts schema definition from the POJO
class and constructs the `SchemaInfo` that the producer needs to pass to a
broker when it connects.
2. The producer connects to the broker with the `SchemaInfo` extracted from
the passed-in schema instance.
