This is an automated email from the ASF dual-hosted git repository.
visortelle pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 8eeb8405a8ed specifies that the Node client supports schemas (#869)
8eeb8405a8ed is described below
commit 8eeb8405a8edcb2fac1f40b41eaa340ddf865ec9
Author: Julien Jakubowski <[email protected]>
AuthorDate: Mon Mar 25 19:12:21 2024 +0100
specifies that the Node client supports schemas (#869)
---
docs/schema-overview.md | 6 +++---
versioned_docs/version-2.11.x/schema-overview.md | 2 +-
versioned_docs/version-3.0.x/schema-overview.md | 2 +-
versioned_docs/version-3.1.x/schema-overview.md | 2 +-
versioned_docs/version-3.2.x/schema-overview.md | 6 +++---
5 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/schema-overview.md b/docs/schema-overview.md
index a9a503b9d472..0eba5172a7f3 100644
--- a/docs/schema-overview.md
+++ b/docs/schema-overview.md
@@ -17,7 +17,7 @@ Pulsar uses a schema registry as a central repository to
store the registered sc
:::note
-Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [C++
clients](client-libraries-cpp.md), and [C# clients](client-libraries-dotnet.md).
+Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [Node.js
clients](client-libraries-node.md), [C++ clients](client-libraries-cpp.md), and
[C# clients](client-libraries-dotnet.md).
:::
@@ -42,7 +42,7 @@ This diagram illustrates how Pulsar schema works on the
producer side.

-Below are explanations for each step.
+Below are explanations for each step.
1. The application uses a schema instance to construct a producer instance.
The schema instance defines the schema for the data being produced using
the producer instance. Take Avro as an example, Pulsar extracts the schema
definition from the POJO class and constructs the `SchemaInfo`.
@@ -67,7 +67,7 @@ This diagram illustrates how schema works on the consumer
side.

-Below are explanations for each step.
+Below are explanations for each step.
1. The application uses a schema instance to construct a consumer instance.
diff --git a/versioned_docs/version-2.11.x/schema-overview.md
b/versioned_docs/version-2.11.x/schema-overview.md
index 4065a76978d5..994b111f0196 100644
--- a/versioned_docs/version-2.11.x/schema-overview.md
+++ b/versioned_docs/version-2.11.x/schema-overview.md
@@ -23,7 +23,7 @@ Pulsar uses a schema registry as a central repository to
store the registered sc
:::note
-Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [C++
clients](client-libraries-cpp.md), and [C# clients](client-libraries-dotnet.md).
+Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [Node.js
clients](client-libraries-node.md), [C++ clients](client-libraries-cpp.md), and
[C# clients](client-libraries-dotnet.md).
:::
diff --git a/versioned_docs/version-3.0.x/schema-overview.md
b/versioned_docs/version-3.0.x/schema-overview.md
index d117818dc0f7..dfc094d5db4b 100644
--- a/versioned_docs/version-3.0.x/schema-overview.md
+++ b/versioned_docs/version-3.0.x/schema-overview.md
@@ -23,7 +23,7 @@ Pulsar uses a schema registry as a central repository to
store the registered sc
:::note
-Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [C++
clients](client-libraries-cpp.md), and [C# clients](client-libraries-dotnet.md).
+Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [Node.js
clients](client-libraries-node.md), [C++ clients](client-libraries-cpp.md), and
[C# clients](client-libraries-dotnet.md).
:::
diff --git a/versioned_docs/version-3.1.x/schema-overview.md
b/versioned_docs/version-3.1.x/schema-overview.md
index d117818dc0f7..dfc094d5db4b 100644
--- a/versioned_docs/version-3.1.x/schema-overview.md
+++ b/versioned_docs/version-3.1.x/schema-overview.md
@@ -23,7 +23,7 @@ Pulsar uses a schema registry as a central repository to
store the registered sc
:::note
-Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [C++
clients](client-libraries-cpp.md), and [C# clients](client-libraries-dotnet.md).
+Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [Node.js
clients](client-libraries-node.md), [C++ clients](client-libraries-cpp.md), and
[C# clients](client-libraries-dotnet.md).
:::
diff --git a/versioned_docs/version-3.2.x/schema-overview.md
b/versioned_docs/version-3.2.x/schema-overview.md
index a9a503b9d472..0eba5172a7f3 100644
--- a/versioned_docs/version-3.2.x/schema-overview.md
+++ b/versioned_docs/version-3.2.x/schema-overview.md
@@ -17,7 +17,7 @@ Pulsar uses a schema registry as a central repository to
store the registered sc
:::note
-Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [C++
clients](client-libraries-cpp.md), and [C# clients](client-libraries-dotnet.md).
+Currently, Pulsar schema is available for [Java
clients](client-libraries-java.md), [Go clients](client-libraries-go.md),
[Python clients](client-libraries-python.md), [Node.js
clients](client-libraries-node.md), [C++ clients](client-libraries-cpp.md), and
[C# clients](client-libraries-dotnet.md).
:::
@@ -42,7 +42,7 @@ This diagram illustrates how Pulsar schema works on the
producer side.

-Below are explanations for each step.
+Below are explanations for each step.
1. The application uses a schema instance to construct a producer instance.
The schema instance defines the schema for the data being produced using
the producer instance. Take Avro as an example, Pulsar extracts the schema
definition from the POJO class and constructs the `SchemaInfo`.
@@ -67,7 +67,7 @@ This diagram illustrates how schema works on the consumer
side.

-Below are explanations for each step.
+Below are explanations for each step.
1. The application uses a schema instance to construct a consumer instance.