This is an automated email from the ASF dual-hosted git repository.
mmerli 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 7b06d3a [doc] Fix broken links to the info about schemas and Schema
Registry (#5205)
7b06d3a is described below
commit 7b06d3a48da41ad54c25a911da19d94a7a4d6b43
Author: Sergii Zhevzhyk <[email protected]>
AuthorDate: Mon Oct 7 17:41:45 2019 +0200
[doc] Fix broken links to the info about schemas and Schema Registry (#5205)
* Fix broken links to the info about schemas and Schema Registry
* Fix broken links to the info about schemas and Schema Registry in the
2.4.1 version
---
site2/docs/client-libraries-java.md | 2 +-
site2/docs/concepts-messaging.md | 2 +-
site2/docs/concepts-overview.md | 1 -
site2/docs/sql-overview.md | 2 +-
site2/website/versioned_docs/version-2.4.1/client-libraries-java.md | 2 +-
site2/website/versioned_docs/version-2.4.1/concepts-messaging.md | 2 +-
6 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/site2/docs/client-libraries-java.md
b/site2/docs/client-libraries-java.md
index 74aa773..3cc914e 100644
--- a/site2/docs/client-libraries-java.md
+++ b/site2/docs/client-libraries-java.md
@@ -612,7 +612,7 @@ boolean|`resetIncludeHead`|If set to true, the first
message to be returned is t
## Schema
-In Pulsar, all message data consists of byte arrays "under the hood." [Message
schemas](concepts-schema-registry.md) enable you to use other types of data
when constructing and handling messages (from simple types like strings to more
complex, application-specific types). If you construct, say, a
[producer](#producers) without specifying a schema, then the producer can only
produce messages of type `byte[]`. Here's an example:
+In Pulsar, all message data consists of byte arrays "under the hood." [Message
schemas](schema-get-started.md) enable you to use other types of data when
constructing and handling messages (from simple types like strings to more
complex, application-specific types). If you construct, say, a
[producer](#producers) without specifying a schema, then the producer can only
produce messages of type `byte[]`. Here's an example:
```java
Producer<byte[]> producer = client.newProducer()
diff --git a/site2/docs/concepts-messaging.md b/site2/docs/concepts-messaging.md
index 50ac13f..3eb3564 100644
--- a/site2/docs/concepts-messaging.md
+++ b/site2/docs/concepts-messaging.md
@@ -14,7 +14,7 @@ Messages are the basic "unit" of Pulsar. They're what
producers publish to topic
Component | Purpose
:---------|:-------
-Value / data payload | The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data
[schemas](concepts-schema-registry.md)
+Value / data payload | The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data
[schemas](schema-get-started.md)
Key | Messages can optionally be tagged with keys, which can be useful for
things like [topic compaction](concepts-topic-compaction.md)
Properties | An optional key/value map of user-defined properties
Producer name | The name of the producer that produced the message (producers
are automatically given default names, but you can apply your own explicitly as
well)
diff --git a/site2/docs/concepts-overview.md b/site2/docs/concepts-overview.md
index 22aa35c..0614290 100644
--- a/site2/docs/concepts-overview.md
+++ b/site2/docs/concepts-overview.md
@@ -28,4 +28,3 @@ Key features of Pulsar are listed below:
- [Authentication and Authorization](concepts-authentication.md)
- [Topic Compaction](concepts-topic-compaction.md)
- [Tiered Storage](concepts-tiered-storage.md)
-- [Schema Registry](concepts-schema-registry.md)
diff --git a/site2/docs/sql-overview.md b/site2/docs/sql-overview.md
index 76ce57c..d40df95 100644
--- a/site2/docs/sql-overview.md
+++ b/site2/docs/sql-overview.md
@@ -4,7 +4,7 @@ title: Pulsar SQL Overview
sidebar_label: Overview
---
-One of the common use cases of Pulsar is storing streams of event data. Often
the event data is structured which predefined fields. There is tremendous
value for users to be able to query the existing data that is already stored in
Pulsar topics. With the implementation of the [Schema
Registry](concepts-schema-registry.md), structured data can be stored in Pulsar
and allows for the potential to query that data via SQL language.
+One of the common use cases of Pulsar is storing streams of event data. Often
the event data is structured which predefined fields. There is tremendous
value for users to be able to query the existing data that is already stored in
Pulsar topics. With the implementation of the [Schema
Registry](schema-get-started.md), structured data can be stored in Pulsar and
allows for the potential to query that data via SQL language.
By leveraging [Presto](https://prestosql.io/), we have created a method for
users to be able to query structured data stored within Pulsar in a very
efficient and scalable manner. We will discuss why this very efficient and
scalable in the [Performance](#performance) section below.
diff --git
a/site2/website/versioned_docs/version-2.4.1/client-libraries-java.md
b/site2/website/versioned_docs/version-2.4.1/client-libraries-java.md
index c8f0631..dc5509b 100644
--- a/site2/website/versioned_docs/version-2.4.1/client-libraries-java.md
+++ b/site2/website/versioned_docs/version-2.4.1/client-libraries-java.md
@@ -551,7 +551,7 @@ The code sample above shows pointing the `Reader` object to
a specific message (
## Schemas
-In Pulsar, all message data consists of byte arrays "under the hood." [Message
schemas](concepts-schema-registry.md) enable you to use other types of data
when constructing and handling messages (from simple types like strings to more
complex, application-specific types). If you construct, say, a
[producer](#producers) without specifying a schema, then the producer can only
produce messages of type `byte[]`. Here's an example:
+In Pulsar, all message data consists of byte arrays "under the hood." [Message
schemas](schema-get-started.md) enable you to use other types of data when
constructing and handling messages (from simple types like strings to more
complex, application-specific types). If you construct, say, a
[producer](#producers) without specifying a schema, then the producer can only
produce messages of type `byte[]`. Here's an example:
```java
Producer<byte[]> producer = client.newProducer()
diff --git a/site2/website/versioned_docs/version-2.4.1/concepts-messaging.md
b/site2/website/versioned_docs/version-2.4.1/concepts-messaging.md
index d711e26..6e323ae 100644
--- a/site2/website/versioned_docs/version-2.4.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.4.1/concepts-messaging.md
@@ -15,7 +15,7 @@ Messages are the basic "unit" of Pulsar. They're what
producers publish to topic
Component | Purpose
:---------|:-------
-Value / data payload | The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data
[schemas](concepts-schema-registry.md)
+Value / data payload | The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data
[schemas](schema-get-started.md)
Key | Messages can optionally be tagged with keys, which can be useful for
things like [topic compaction](concepts-topic-compaction.md)
Properties | An optional key/value map of user-defined properties
Producer name | The name of the producer that produced the message (producers
are automatically given default names, but you can apply your own explicitly as
well)
