This is an automated email from the ASF dual-hosted git repository.
mmerli pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f3d5960 Updated site at revision d7012aeb39
f3d5960 is described below
commit f3d5960d49948b8c8e2dfc6728bb407c0840fde3
Author: jenkins <[email protected]>
AuthorDate: Tue Oct 8 09:58:33 2019 +0000
Updated site at revision d7012aeb39
---
content/docs/en/client-libraries-java.html | 2 +-
content/docs/en/client-libraries-java/index.html | 2 +-
content/docs/en/concepts-messaging.html | 2 +-
content/docs/en/concepts-messaging/index.html | 2 +-
content/docs/en/next/client-libraries-java.html | 2 +-
.../docs/en/next/client-libraries-java/index.html | 2 +-
content/docs/en/next/concepts-messaging.html | 2 +-
content/docs/en/next/concepts-messaging/index.html | 2 +-
content/docs/en/next/concepts-overview.html | 1 -
content/docs/en/next/concepts-overview/index.html | 1 -
content/docs/en/next/sql-overview.html | 4 +-
content/docs/en/next/sql-overview/index.html | 4 +-
content/docs/fr/client-libraries-java.html | 2 +-
content/docs/fr/client-libraries-java/index.html | 2 +-
content/docs/fr/concepts-messaging.html | 2 +-
content/docs/fr/concepts-messaging/index.html | 2 +-
content/docs/fr/next/client-libraries-java.html | 2 +-
.../docs/fr/next/client-libraries-java/index.html | 2 +-
content/docs/fr/next/concepts-messaging.html | 2 +-
content/docs/fr/next/concepts-messaging/index.html | 2 +-
content/docs/fr/next/concepts-overview.html | 1 -
content/docs/fr/next/concepts-overview/index.html | 1 -
content/docs/fr/next/sql-overview.html | 4 +-
content/docs/fr/next/sql-overview/index.html | 4 +-
content/docs/ja/client-libraries-java.html | 2 +-
content/docs/ja/client-libraries-java/index.html | 2 +-
content/docs/ja/concepts-messaging.html | 2 +-
content/docs/ja/concepts-messaging/index.html | 2 +-
content/docs/ja/next/client-libraries-java.html | 2 +-
.../docs/ja/next/client-libraries-java/index.html | 2 +-
content/docs/ja/next/concepts-messaging.html | 2 +-
content/docs/ja/next/concepts-messaging/index.html | 2 +-
content/docs/ja/next/concepts-overview.html | 1 -
content/docs/ja/next/concepts-overview/index.html | 1 -
content/docs/ja/next/sql-overview.html | 4 +-
content/docs/ja/next/sql-overview/index.html | 4 +-
content/docs/zh-CN/client-libraries-java.html | 2 +-
.../docs/zh-CN/client-libraries-java/index.html | 2 +-
content/docs/zh-CN/concepts-messaging.html | 2 +-
content/docs/zh-CN/concepts-messaging/index.html | 2 +-
content/docs/zh-CN/next/client-libraries-java.html | 2 +-
.../zh-CN/next/client-libraries-java/index.html | 2 +-
content/docs/zh-CN/next/concepts-messaging.html | 2 +-
.../docs/zh-CN/next/concepts-messaging/index.html | 2 +-
content/docs/zh-CN/next/concepts-overview.html | 1 -
.../docs/zh-CN/next/concepts-overview/index.html | 1 -
content/docs/zh-CN/next/sql-overview.html | 4 +-
content/docs/zh-CN/next/sql-overview/index.html | 4 +-
content/swagger/2.5.0-SNAPSHOT/swagger.json | 48 +++++++++++++---------
.../swagger/2.5.0-SNAPSHOT/swaggerfunctions.json | 36 ++++++++--------
content/swagger/master/swagger.json | 48 +++++++++++++---------
content/swagger/master/swaggerfunctions.json | 36 ++++++++--------
52 files changed, 142 insertions(+), 130 deletions(-)
diff --git a/content/docs/en/client-libraries-java.html
b/content/docs/en/client-libraries-java.html
index 4e2e551..1588012 100644
--- a/content/docs/en/client-libraries-java.html
+++ b/content/docs/en/client-libraries-java.html
@@ -499,7 +499,7 @@ Reader reader = pulsarClient.newReader()
<p>In the example above, a <code>Reader</code> object is instantiated for a
specific topic and message (by ID); the reader then iterates over each message
in the topic after the message identified by <code>msgIdBytes</code> (how that
value is obtained depends on the application).</p>
<p>The code sample above shows pointing the <code>Reader</code> object to a
specific message (by ID), but you can also use <code>MessageId.earliest</code>
to point to the earliest available message on the topic of
<code>MessageId.latest</code> to point to the most recent available message.</p>
<h2><a class="anchor" aria-hidden="true" id="schemas"></a><a href="#schemas"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
-<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="concepts-schema-registry.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="/docs/en/schema-get-started">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/en/client-libraries-java/index.html
b/content/docs/en/client-libraries-java/index.html
index 4e2e551..1588012 100644
--- a/content/docs/en/client-libraries-java/index.html
+++ b/content/docs/en/client-libraries-java/index.html
@@ -499,7 +499,7 @@ Reader reader = pulsarClient.newReader()
<p>In the example above, a <code>Reader</code> object is instantiated for a
specific topic and message (by ID); the reader then iterates over each message
in the topic after the message identified by <code>msgIdBytes</code> (how that
value is obtained depends on the application).</p>
<p>The code sample above shows pointing the <code>Reader</code> object to a
specific message (by ID), but you can also use <code>MessageId.earliest</code>
to point to the earliest available message on the topic of
<code>MessageId.latest</code> to point to the most recent available message.</p>
<h2><a class="anchor" aria-hidden="true" id="schemas"></a><a href="#schemas"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
-<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="concepts-schema-registry.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="/docs/en/schema-get-started">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/en/concepts-messaging.html
b/content/docs/en/concepts-messaging.html
index e51592c..96eabf9 100644
--- a/content/docs/en/concepts-messaging.html
+++ b/content/docs/en/concepts-messaging.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/en/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/en/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/en/concepts-messaging/index.html
b/content/docs/en/concepts-messaging/index.html
index e51592c..96eabf9 100644
--- a/content/docs/en/concepts-messaging/index.html
+++ b/content/docs/en/concepts-messaging/index.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/en/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/en/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/en/next/client-libraries-java.html
b/content/docs/en/next/client-libraries-java.html
index 4a18bd3..27f236a 100644
--- a/content/docs/en/next/client-libraries-java.html
+++ b/content/docs/en/next/client-libraries-java.html
@@ -568,7 +568,7 @@ Reader reader = pulsarClient.newReader()
</tbody>
</table>
<h2><a class="anchor" aria-hidden="true" id="schema"></a><a href="#schema"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
-<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="concepts-schema-registry.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="/docs/en/next/schema-get-started">Message schemas</a>
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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/en/next/client-libraries-java/index.html
b/content/docs/en/next/client-libraries-java/index.html
index 4a18bd3..27f236a 100644
--- a/content/docs/en/next/client-libraries-java/index.html
+++ b/content/docs/en/next/client-libraries-java/index.html
@@ -568,7 +568,7 @@ Reader reader = pulsarClient.newReader()
</tbody>
</table>
<h2><a class="anchor" aria-hidden="true" id="schema"></a><a href="#schema"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
-<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="concepts-schema-registry.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="/docs/en/next/schema-get-started">Message schemas</a>
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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/en/next/concepts-messaging.html
b/content/docs/en/next/concepts-messaging.html
index ef72799..d5b71ae 100644
--- a/content/docs/en/next/concepts-messaging.html
+++ b/content/docs/en/next/concepts-messaging.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/en/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/en/next/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/en/next/concepts-messaging/index.html
b/content/docs/en/next/concepts-messaging/index.html
index ef72799..d5b71ae 100644
--- a/content/docs/en/next/concepts-messaging/index.html
+++ b/content/docs/en/next/concepts-messaging/index.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/en/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/en/next/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/en/next/concepts-overview.html
b/content/docs/en/next/concepts-overview.html
index fb302f3..706678b 100644
--- a/content/docs/en/next/concepts-overview.html
+++ b/content/docs/en/next/concepts-overview.html
@@ -97,7 +97,6 @@
<li><a href="/docs/en/next/concepts-authentication">Authentication and
Authorization</a></li>
<li><a href="/docs/en/next/concepts-topic-compaction">Topic Compaction</a></li>
<li><a href="/docs/en/next/concepts-tiered-storage">Tiered Storage</a></li>
-<li><a href="concepts-schema-registry.md">Schema Registry</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/en/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/en/next/concepts-messaging"><span>Messaging</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a
href="#contents">Contents</a></li></ul></nav></div><footer class="nav-footer"
id="foot [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/en/next/concepts-overview/index.html
b/content/docs/en/next/concepts-overview/index.html
index fb302f3..706678b 100644
--- a/content/docs/en/next/concepts-overview/index.html
+++ b/content/docs/en/next/concepts-overview/index.html
@@ -97,7 +97,6 @@
<li><a href="/docs/en/next/concepts-authentication">Authentication and
Authorization</a></li>
<li><a href="/docs/en/next/concepts-topic-compaction">Topic Compaction</a></li>
<li><a href="/docs/en/next/concepts-tiered-storage">Tiered Storage</a></li>
-<li><a href="concepts-schema-registry.md">Schema Registry</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/en/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/en/next/concepts-messaging"><span>Messaging</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a
href="#contents">Contents</a></li></ul></nav></div><footer class="nav-footer"
id="foot [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/en/next/sql-overview.html
b/content/docs/en/next/sql-overview.html
index ab32334..678938f 100644
--- a/content/docs/en/next/sql-overview.html
+++ b/content/docs/en/next/sql-overview.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exis [...]
+<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exis [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -74,7 +74,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://github.com/apache/incubator-pulsar/edit/master/site2/docs/sql-overview.md";
target="_blank" rel="noreferrer noopener">Edit</a><h1
class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structur [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://github.com/apache/incubator-pulsar/edit/master/site2/docs/sql-overview.md";
target="_blank" rel="noreferrer noopener">Edit</a><h1
class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structur [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, 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 <a href="#performance">Performance</a> section below.</p>
<p>At the core of this Pulsar SQL is the Presto Pulsar connector which allows
Presto workers within a Presto cluster to query data from Pulsar.</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="The Pulsar consumer and
reader interfaces"></p>
diff --git a/content/docs/en/next/sql-overview/index.html
b/content/docs/en/next/sql-overview/index.html
index ab32334..678938f 100644
--- a/content/docs/en/next/sql-overview/index.html
+++ b/content/docs/en/next/sql-overview/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exis [...]
+<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exis [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -74,7 +74,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://github.com/apache/incubator-pulsar/edit/master/site2/docs/sql-overview.md";
target="_blank" rel="noreferrer noopener">Edit</a><h1
class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structur [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://github.com/apache/incubator-pulsar/edit/master/site2/docs/sql-overview.md";
target="_blank" rel="noreferrer noopener">Edit</a><h1
class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structur [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, 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 <a href="#performance">Performance</a> section below.</p>
<p>At the core of this Pulsar SQL is the Presto Pulsar connector which allows
Presto workers within a Presto cluster to query data from Pulsar.</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="The Pulsar consumer and
reader interfaces"></p>
diff --git a/content/docs/fr/client-libraries-java.html
b/content/docs/fr/client-libraries-java.html
index 2f7a1b8..d1c9c71 100644
--- a/content/docs/fr/client-libraries-java.html
+++ b/content/docs/fr/client-libraries-java.html
@@ -487,7 +487,7 @@ Reader reader = pulsarClient.newReader()
<p>Dans l'exemple ci-dessus, un objet <code>Reader</code> est instancié avec
un topic et un id de message spécifiques; le lecteur itère ensuite sur chaque
message dans le topic après le message identifié par <code>msgIdBytes</code>
(la façon dont cette valeur est obtenue dépend de l'application).</p>
<p>L'exemple de code ci-dessus montre l'objet <code>Reader</code>pointant vers
un message spécifique (identifié par un ID), mais vous pouvez également
utiliser <code>MessageId.earliest</code> pour pointer vers le message
disponible le plus ancien sur le topic ou <code>MessageId.latest</code> pour
pointer vers le message disponible le plus récent.</p>
<h2><a class="anchor" aria-hidden="true" id="schemas"></a><a href="#schemas"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
-<p>Dans Pulsar, en interne, toutes les données de message se composent de
tableaux d'octets. <a href="concepts-schema-registry.md">Les schémas de
messages</a> vous permettent d'utiliser d'autres types de données lors de la
construction et la manipulation de messages (de types simples comme des strings
à des types plus complexes et spécifiques à l'application). Si vous
construisez, par exemple, un <a href="#producers">producteur</a> sans spécifier
un schéma, alors le producteur ne peut pr [...]
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="schema-get-started.md">Message schemas</a> enable you to
use other types of data when constructing and handling messages (from simple
types like strings to more complex, application-specific types). Si vous
construisez, par exemple, un <a href="#producers">producteur</a> sans spécifier
un schéma, alors le producteur ne peut produire que des messages de type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/fr/client-libraries-java/index.html
b/content/docs/fr/client-libraries-java/index.html
index 2f7a1b8..d1c9c71 100644
--- a/content/docs/fr/client-libraries-java/index.html
+++ b/content/docs/fr/client-libraries-java/index.html
@@ -487,7 +487,7 @@ Reader reader = pulsarClient.newReader()
<p>Dans l'exemple ci-dessus, un objet <code>Reader</code> est instancié avec
un topic et un id de message spécifiques; le lecteur itère ensuite sur chaque
message dans le topic après le message identifié par <code>msgIdBytes</code>
(la façon dont cette valeur est obtenue dépend de l'application).</p>
<p>L'exemple de code ci-dessus montre l'objet <code>Reader</code>pointant vers
un message spécifique (identifié par un ID), mais vous pouvez également
utiliser <code>MessageId.earliest</code> pour pointer vers le message
disponible le plus ancien sur le topic ou <code>MessageId.latest</code> pour
pointer vers le message disponible le plus récent.</p>
<h2><a class="anchor" aria-hidden="true" id="schemas"></a><a href="#schemas"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
-<p>Dans Pulsar, en interne, toutes les données de message se composent de
tableaux d'octets. <a href="concepts-schema-registry.md">Les schémas de
messages</a> vous permettent d'utiliser d'autres types de données lors de la
construction et la manipulation de messages (de types simples comme des strings
à des types plus complexes et spécifiques à l'application). Si vous
construisez, par exemple, un <a href="#producers">producteur</a> sans spécifier
un schéma, alors le producteur ne peut pr [...]
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="schema-get-started.md">Message schemas</a> enable you to
use other types of data when constructing and handling messages (from simple
types like strings to more complex, application-specific types). Si vous
construisez, par exemple, un <a href="#producers">producteur</a> sans spécifier
un schéma, alors le producteur ne peut produire que des messages de type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/fr/concepts-messaging.html
b/content/docs/fr/concepts-messaging.html
index 286217b..edf7114 100644
--- a/content/docs/fr/concepts-messaging.html
+++ b/content/docs/fr/concepts-messaging.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/fr/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/fr/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/fr/concepts-messaging/index.html
b/content/docs/fr/concepts-messaging/index.html
index 286217b..edf7114 100644
--- a/content/docs/fr/concepts-messaging/index.html
+++ b/content/docs/fr/concepts-messaging/index.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/fr/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/fr/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/fr/next/client-libraries-java.html
b/content/docs/fr/next/client-libraries-java.html
index 5522bf4..5887e35 100644
--- a/content/docs/fr/next/client-libraries-java.html
+++ b/content/docs/fr/next/client-libraries-java.html
@@ -761,7 +761,7 @@ Pour utiliser une configuration différente de celle par
défaut, il existe une
## Schema
- Dans Pulsar, en interne, toutes les données de message se composent de
tableaux d'octets. [Les schémas de messages](concepts-schema-registry.md) vous
permettent d'utiliser d'autres types de données lors de la construction et la
manipulation de messages (de types simples comme des strings à des types plus
complexes et spécifiques à l'application). Si vous construisez, par exemple, un
[producteur](#producers) sans spécifier un schéma, alors le producteur ne peut
produire que des messages [...]
+ 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). Si vous construisez, par
exemple, un [producteur](#producers) sans spécifier un schéma, alors le
producteur ne peut produire que des messages de type `byte[]`. Here's an
example:
```java
Producer<byte[]> producer = client.newProducer()
diff --git a/content/docs/fr/next/client-libraries-java/index.html
b/content/docs/fr/next/client-libraries-java/index.html
index 5522bf4..5887e35 100644
--- a/content/docs/fr/next/client-libraries-java/index.html
+++ b/content/docs/fr/next/client-libraries-java/index.html
@@ -761,7 +761,7 @@ Pour utiliser une configuration différente de celle par
défaut, il existe une
## Schema
- Dans Pulsar, en interne, toutes les données de message se composent de
tableaux d'octets. [Les schémas de messages](concepts-schema-registry.md) vous
permettent d'utiliser d'autres types de données lors de la construction et la
manipulation de messages (de types simples comme des strings à des types plus
complexes et spécifiques à l'application). Si vous construisez, par exemple, un
[producteur](#producers) sans spécifier un schéma, alors le producteur ne peut
produire que des messages [...]
+ 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). Si vous construisez, par
exemple, un [producteur](#producers) sans spécifier un schéma, alors le
producteur ne peut produire que des messages de type `byte[]`. Here's an
example:
```java
Producer<byte[]> producer = client.newProducer()
diff --git a/content/docs/fr/next/concepts-messaging.html
b/content/docs/fr/next/concepts-messaging.html
index 43fad26..a3fc028 100644
--- a/content/docs/fr/next/concepts-messaging.html
+++ b/content/docs/fr/next/concepts-messaging.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/fr/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/fr/next/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/fr/next/concepts-messaging/index.html
b/content/docs/fr/next/concepts-messaging/index.html
index 43fad26..a3fc028 100644
--- a/content/docs/fr/next/concepts-messaging/index.html
+++ b/content/docs/fr/next/concepts-messaging/index.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/fr/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/fr/next/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/fr/next/concepts-overview.html
b/content/docs/fr/next/concepts-overview.html
index b0b9b96..469370b 100644
--- a/content/docs/fr/next/concepts-overview.html
+++ b/content/docs/fr/next/concepts-overview.html
@@ -97,7 +97,6 @@
<li><a href="/docs/fr/next/concepts-authentication">Authentication and
Authorization</a></li>
<li><a href="/docs/fr/next/concepts-topic-compaction">Topic Compaction</a></li>
<li><a href="/docs/fr/next/concepts-tiered-storage">Tiered Storage</a></li>
-<li><a href="concepts-schema-registry.md">Schema Registry</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/fr/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/fr/next/concepts-messaging"><span>Messaging</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a
href="#contents">Contents</a></li></ul></nav></div><footer class="nav-footer"
id="foot [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/fr/next/concepts-overview/index.html
b/content/docs/fr/next/concepts-overview/index.html
index b0b9b96..469370b 100644
--- a/content/docs/fr/next/concepts-overview/index.html
+++ b/content/docs/fr/next/concepts-overview/index.html
@@ -97,7 +97,6 @@
<li><a href="/docs/fr/next/concepts-authentication">Authentication and
Authorization</a></li>
<li><a href="/docs/fr/next/concepts-topic-compaction">Topic Compaction</a></li>
<li><a href="/docs/fr/next/concepts-tiered-storage">Tiered Storage</a></li>
-<li><a href="concepts-schema-registry.md">Schema Registry</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/fr/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/fr/next/concepts-messaging"><span>Messaging</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a
href="#contents">Contents</a></li></ul></nav></div><footer class="nav-footer"
id="foot [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/fr/next/sql-overview.html
b/content/docs/fr/next/sql-overview.html
index 8a1f511..00c04c8 100644
--- a/content/docs/fr/next/sql-overview.html
+++ b/content/docs/fr/next/sql-overview.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="fr"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
+<!DOCTYPE html><html lang="fr"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -74,7 +74,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/fr"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/fr"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, 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 <a href="#performance">Performance</a> section below.</p>
<p>At the core of this Pulsar SQL is the Presto Pulsar connector which allows
Presto workers within a Presto cluster to query data from Pulsar.</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="The Pulsar consumer and
reader interfaces"></p>
diff --git a/content/docs/fr/next/sql-overview/index.html
b/content/docs/fr/next/sql-overview/index.html
index 8a1f511..00c04c8 100644
--- a/content/docs/fr/next/sql-overview/index.html
+++ b/content/docs/fr/next/sql-overview/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="fr"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
+<!DOCTYPE html><html lang="fr"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -74,7 +74,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/fr"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/fr"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, 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 <a href="#performance">Performance</a> section below.</p>
<p>At the core of this Pulsar SQL is the Presto Pulsar connector which allows
Presto workers within a Presto cluster to query data from Pulsar.</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="The Pulsar consumer and
reader interfaces"></p>
diff --git a/content/docs/ja/client-libraries-java.html
b/content/docs/ja/client-libraries-java.html
index ac07349..999b3ca 100644
--- a/content/docs/ja/client-libraries-java.html
+++ b/content/docs/ja/client-libraries-java.html
@@ -488,7 +488,7 @@ Reader reader = pulsarClient.newReader()
<p>In the example above, a <code>Reader</code> object is instantiated for a
specific topic and message (by ID); the reader then iterates over each message
in the topic after the message identified by <code>msgIdBytes</code> (how that
value is obtained depends on the application).</p>
<p>The code sample above shows pointing the <code>Reader</code> object to a
specific message (by ID), but you can also use <code>MessageId.earliest</code>
to point to the earliest available message on the topic of
<code>MessageId.latest</code> to point to the most recent available message.</p>
<h2><a class="anchor" aria-hidden="true" id="schemas"></a><a href="#schemas"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
-<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="concepts-schema-registry.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="schema-get-started.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/ja/client-libraries-java/index.html
b/content/docs/ja/client-libraries-java/index.html
index ac07349..999b3ca 100644
--- a/content/docs/ja/client-libraries-java/index.html
+++ b/content/docs/ja/client-libraries-java/index.html
@@ -488,7 +488,7 @@ Reader reader = pulsarClient.newReader()
<p>In the example above, a <code>Reader</code> object is instantiated for a
specific topic and message (by ID); the reader then iterates over each message
in the topic after the message identified by <code>msgIdBytes</code> (how that
value is obtained depends on the application).</p>
<p>The code sample above shows pointing the <code>Reader</code> object to a
specific message (by ID), but you can also use <code>MessageId.earliest</code>
to point to the earliest available message on the topic of
<code>MessageId.latest</code> to point to the most recent available message.</p>
<h2><a class="anchor" aria-hidden="true" id="schemas"></a><a href="#schemas"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
-<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="concepts-schema-registry.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="schema-get-started.md">Message schemas</a> 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 <a href="#producers">producer</a> without specifying a
schema, then the producer can only produce messages of type
<code>byte[]</code>. Here's an example:</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/ja/concepts-messaging.html
b/content/docs/ja/concepts-messaging.html
index 758d904..1d9bc66 100644
--- a/content/docs/ja/concepts-messaging.html
+++ b/content/docs/ja/concepts-messaging.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/ja/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/ja/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/ja/concepts-messaging/index.html
b/content/docs/ja/concepts-messaging/index.html
index 758d904..1d9bc66 100644
--- a/content/docs/ja/concepts-messaging/index.html
+++ b/content/docs/ja/concepts-messaging/index.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/ja/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/ja/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/ja/next/client-libraries-java.html
b/content/docs/ja/next/client-libraries-java.html
index c5260b0..e7bf6f9 100644
--- a/content/docs/ja/next/client-libraries-java.html
+++ b/content/docs/ja/next/client-libraries-java.html
@@ -762,7 +762,7 @@ To use a non-default configuration, there's a variety of
configurable parameters
## 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/content/docs/ja/next/client-libraries-java/index.html
b/content/docs/ja/next/client-libraries-java/index.html
index c5260b0..e7bf6f9 100644
--- a/content/docs/ja/next/client-libraries-java/index.html
+++ b/content/docs/ja/next/client-libraries-java/index.html
@@ -762,7 +762,7 @@ To use a non-default configuration, there's a variety of
configurable parameters
## 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/content/docs/ja/next/concepts-messaging.html
b/content/docs/ja/next/concepts-messaging.html
index 2e6289f..16584f2 100644
--- a/content/docs/ja/next/concepts-messaging.html
+++ b/content/docs/ja/next/concepts-messaging.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/ja/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/ja/next/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/ja/next/concepts-messaging/index.html
b/content/docs/ja/next/concepts-messaging/index.html
index 2e6289f..16584f2 100644
--- a/content/docs/ja/next/concepts-messaging/index.html
+++ b/content/docs/ja/next/concepts-messaging/index.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">Purpose</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/ja/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td style="text-align:left">Messages
can optionally be tagged with keys, which can be useful for things like <a
href="/docs/ja/next/concepts-topic-compaction">topic compaction</a></td></tr>
<tr><td style="text-align:left">Properties</td><td style="text-align:left">An
optional key/value map of user-defined properties</td></tr>
<tr><td style="text-align:left">Producer name</td><td
style="text-align:left">The name of the producer that produced the message
(producers are automatically given default names, but you can apply your own
explicitly as well)</td></tr>
diff --git a/content/docs/ja/next/concepts-overview.html
b/content/docs/ja/next/concepts-overview.html
index e4f653b..e19b0f5 100644
--- a/content/docs/ja/next/concepts-overview.html
+++ b/content/docs/ja/next/concepts-overview.html
@@ -97,7 +97,6 @@
<li><a href="/docs/ja/next/concepts-authentication">Authentication and
Authorization</a></li>
<li><a href="/docs/ja/next/concepts-topic-compaction">Topic Compaction</a></li>
<li><a href="/docs/ja/next/concepts-tiered-storage">Tiered Storage</a></li>
-<li><a href="concepts-schema-registry.md">Schema Registry</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/ja/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/ja/next/concepts-messaging"><span>Messaging</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a
href="#contents">Contents</a></li></ul></nav></div><footer class="nav-footer"
id="foot [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/ja/next/concepts-overview/index.html
b/content/docs/ja/next/concepts-overview/index.html
index e4f653b..e19b0f5 100644
--- a/content/docs/ja/next/concepts-overview/index.html
+++ b/content/docs/ja/next/concepts-overview/index.html
@@ -97,7 +97,6 @@
<li><a href="/docs/ja/next/concepts-authentication">Authentication and
Authorization</a></li>
<li><a href="/docs/ja/next/concepts-topic-compaction">Topic Compaction</a></li>
<li><a href="/docs/ja/next/concepts-tiered-storage">Tiered Storage</a></li>
-<li><a href="concepts-schema-registry.md">Schema Registry</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/ja/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/ja/next/concepts-messaging"><span>Messaging</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a
href="#contents">Contents</a></li></ul></nav></div><footer class="nav-footer"
id="foot [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/ja/next/sql-overview.html
b/content/docs/ja/next/sql-overview.html
index 029708a..7c2c2c7 100644
--- a/content/docs/ja/next/sql-overview.html
+++ b/content/docs/ja/next/sql-overview.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="ja"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
+<!DOCTYPE html><html lang="ja"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -74,7 +74,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/ja"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/ja"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, 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 <a href="#performance">Performance</a> section below.</p>
<p>At the core of this Pulsar SQL is the Presto Pulsar connector which allows
Presto workers within a Presto cluster to query data from Pulsar.</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="The Pulsar consumer and
reader interfaces"></p>
diff --git a/content/docs/ja/next/sql-overview/index.html
b/content/docs/ja/next/sql-overview/index.html
index 029708a..7c2c2c7 100644
--- a/content/docs/ja/next/sql-overview/index.html
+++ b/content/docs/ja/next/sql-overview/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="ja"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
+<!DOCTYPE html><html lang="ja"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL Overview ·
Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description" content="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 exist [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -74,7 +74,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/ja"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/ja"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
Overview</h1></header><article><div><span><p>One of the common use cases of
Pulsar is storing streams of event data. Often the event data is structured
which predefined fields. Ther [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, 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 <a href="#performance">Performance</a> section below.</p>
<p>At the core of this Pulsar SQL is the Presto Pulsar connector which allows
Presto workers within a Presto cluster to query data from Pulsar.</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="The Pulsar consumer and
reader interfaces"></p>
diff --git a/content/docs/zh-CN/client-libraries-java.html
b/content/docs/zh-CN/client-libraries-java.html
index e90f1cf..9402dc2 100644
--- a/content/docs/zh-CN/client-libraries-java.html
+++ b/content/docs/zh-CN/client-libraries-java.html
@@ -488,7 +488,7 @@ Reader reader = pulsarClient.newReader()
<p>在上面的示例中，实例化一个<code>Reader</code>对象对指定的主题和消息（ID）;
reader将遍历主题中<code>msgIdBytes</code>(取值方式取决于应用程序) 之后的消息。</p>
<p>上面的示例代码展示了<code>Reader</code>对象指向特定的消息(ID)，但你也可以使用<code>MessageId.earliest</code>来指向topic上最早可用的消息，使用<code>MessageId.latest</code>指向最新的消息。</p>
<h2><a class="anchor" aria-hidden="true" id="schema"></a><a href="#schema"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
-<p>在Pulsar中，所有的消息数据都在字节数组中，<a
href="concepts-schema-registry.md">消息schema</a>允许在构造和处理消息时使用其他类型的数据（从简单类型(如字符串)到更复杂的特定应用程序的类型）。
如果在不指定schema的情况下构造 <a href="#producers">生产者</a>，则生产者只能生成类型为
<code>byte[]</code>的消息。 下面是一个示例：</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="schema-get-started.md">Message schemas</a> enable you to
use other types of data when constructing and handling messages (from simple
types like strings to more complex, application-specific types).
如果在不指定schema的情况下构造 <a href="#producers">生产者</a>，则生产者只能生成类型为
<code>byte[]</code>的消息。 下面是一个示例：</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/zh-CN/client-libraries-java/index.html
b/content/docs/zh-CN/client-libraries-java/index.html
index e90f1cf..9402dc2 100644
--- a/content/docs/zh-CN/client-libraries-java/index.html
+++ b/content/docs/zh-CN/client-libraries-java/index.html
@@ -488,7 +488,7 @@ Reader reader = pulsarClient.newReader()
<p>在上面的示例中，实例化一个<code>Reader</code>对象对指定的主题和消息（ID）;
reader将遍历主题中<code>msgIdBytes</code>(取值方式取决于应用程序) 之后的消息。</p>
<p>上面的示例代码展示了<code>Reader</code>对象指向特定的消息(ID)，但你也可以使用<code>MessageId.earliest</code>来指向topic上最早可用的消息，使用<code>MessageId.latest</code>指向最新的消息。</p>
<h2><a class="anchor" aria-hidden="true" id="schema"></a><a href="#schema"
aria-hidden="true" class="hash-link"><svg class="hash-link-icon"
aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16"
width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4
3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10
5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2
2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
-<p>在Pulsar中，所有的消息数据都在字节数组中，<a
href="concepts-schema-registry.md">消息schema</a>允许在构造和处理消息时使用其他类型的数据（从简单类型(如字符串)到更复杂的特定应用程序的类型）。
如果在不指定schema的情况下构造 <a href="#producers">生产者</a>，则生产者只能生成类型为
<code>byte[]</code>的消息。 下面是一个示例：</p>
+<p>In Pulsar, all message data consists of byte arrays "under the
hood." <a href="schema-get-started.md">Message schemas</a> enable you to
use other types of data when constructing and handling messages (from simple
types like strings to more complex, application-specific types).
如果在不指定schema的情况下构造 <a href="#producers">生产者</a>，则生产者只能生成类型为
<code>byte[]</code>的消息。 下面是一个示例：</p>
<pre><code class="hljs css language-java">Producer<<span
class="hljs-keyword">byte</span>[]> producer = client.newProducer()
.topic(topic)
.create();
diff --git a/content/docs/zh-CN/concepts-messaging.html
b/content/docs/zh-CN/concepts-messaging.html
index 266e188..012634b 100644
--- a/content/docs/zh-CN/concepts-messaging.html
+++ b/content/docs/zh-CN/concepts-messaging.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">作用</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/zh-CN/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td
style="text-align:left">消息可以被Key打标签。这对诸如<a
href="/docs/zh-CN/concepts-topic-compaction">topic压缩</a>之类的事情有作用</td></tr>
<tr><td style="text-align:left">Properties</td><td
style="text-align:left">可选的，用户定义属性 的key/value map</td></tr>
<tr><td style="text-align:left">Producer名称</td><td
style="text-align:left">生产消息的producer名称(producer被自动赋予默认名称，但你也可以自己指定)</td></tr>
diff --git a/content/docs/zh-CN/concepts-messaging/index.html
b/content/docs/zh-CN/concepts-messaging/index.html
index 266e188..012634b 100644
--- a/content/docs/zh-CN/concepts-messaging/index.html
+++ b/content/docs/zh-CN/concepts-messaging/index.html
@@ -83,7 +83,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">作用</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="concepts-schema-registry.md">schemas</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/zh-CN/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td
style="text-align:left">消息可以被Key打标签。这对诸如<a
href="/docs/zh-CN/concepts-topic-compaction">topic压缩</a>之类的事情有作用</td></tr>
<tr><td style="text-align:left">Properties</td><td
style="text-align:left">可选的，用户定义属性 的key/value map</td></tr>
<tr><td style="text-align:left">Producer名称</td><td
style="text-align:left">生产消息的producer名称(producer被自动赋予默认名称，但你也可以自己指定)</td></tr>
diff --git a/content/docs/zh-CN/next/client-libraries-java.html
b/content/docs/zh-CN/next/client-libraries-java.html
index 603d049..ae47059 100644
--- a/content/docs/zh-CN/next/client-libraries-java.html
+++ b/content/docs/zh-CN/next/client-libraries-java.html
@@ -763,7 +763,7 @@ client.close();</p>
## Schema
-
在Pulsar中，所有的消息数据都在字节数组中，[消息schema](concepts-schema-registry.md)允许在构造和处理消息时使用其他类型的数据（从简单类型(如字符串)到更复杂的特定应用程序的类型）。
如果在不指定schema的情况下构造 [生产者](#producers)，则生产者只能生成类型为 `byte[] `的消息。 下面是一个示例：
+ 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). 如果在不指定schema的情况下构造
[生产者](#producers)，则生产者只能生成类型为 `byte[] `的消息。 下面是一个示例：
```java
Producer<byte[]> producer = client.newProducer()
diff --git a/content/docs/zh-CN/next/client-libraries-java/index.html
b/content/docs/zh-CN/next/client-libraries-java/index.html
index 603d049..ae47059 100644
--- a/content/docs/zh-CN/next/client-libraries-java/index.html
+++ b/content/docs/zh-CN/next/client-libraries-java/index.html
@@ -763,7 +763,7 @@ client.close();</p>
## Schema
-
在Pulsar中，所有的消息数据都在字节数组中，[消息schema](concepts-schema-registry.md)允许在构造和处理消息时使用其他类型的数据（从简单类型(如字符串)到更复杂的特定应用程序的类型）。
如果在不指定schema的情况下构造 [生产者](#producers)，则生产者只能生成类型为 `byte[] `的消息。 下面是一个示例：
+ 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). 如果在不指定schema的情况下构造
[生产者](#producers)，则生产者只能生成类型为 `byte[] `的消息。 下面是一个示例：
```java
Producer<byte[]> producer = client.newProducer()
diff --git a/content/docs/zh-CN/next/concepts-messaging.html
b/content/docs/zh-CN/next/concepts-messaging.html
index 0c8ed3b..bcca6eb 100644
--- a/content/docs/zh-CN/next/concepts-messaging.html
+++ b/content/docs/zh-CN/next/concepts-messaging.html
@@ -84,7 +84,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">作用</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">消息携带的数据。所有pulsar的消息携带原始bytes，但是消息数据也需要遵循数据<a
href="concepts-schema-registry.md">shcema</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/zh-CN/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td
style="text-align:left">消息可以被Key打标签。这对诸如<a
href="/docs/zh-CN/next/concepts-topic-compaction">topic压缩</a>之类的事情有作用</td></tr>
<tr><td style="text-align:left">Properties</td><td
style="text-align:left">可选的，用户定义属性 的key/value map</td></tr>
<tr><td style="text-align:left">Producer名称</td><td
style="text-align:left">生产消息的producer名称(producer被自动赋予默认名称，但你也可以自己指定)</td></tr>
diff --git a/content/docs/zh-CN/next/concepts-messaging/index.html
b/content/docs/zh-CN/next/concepts-messaging/index.html
index 0c8ed3b..bcca6eb 100644
--- a/content/docs/zh-CN/next/concepts-messaging/index.html
+++ b/content/docs/zh-CN/next/concepts-messaging/index.html
@@ -84,7 +84,7 @@
<tr><th style="text-align:left">Component</th><th
style="text-align:left">作用</th></tr>
</thead>
<tbody>
-<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">消息携带的数据。所有pulsar的消息携带原始bytes，但是消息数据也需要遵循数据<a
href="concepts-schema-registry.md">shcema</a></td></tr>
+<tr><td style="text-align:left">Value / data payload</td><td
style="text-align:left">The data carried by the message. All Pulsar messages
carry raw bytes, although message data can also conform to data <a
href="/docs/zh-CN/next/schema-get-started">schemas</a></td></tr>
<tr><td style="text-align:left">Key</td><td
style="text-align:left">消息可以被Key打标签。这对诸如<a
href="/docs/zh-CN/next/concepts-topic-compaction">topic压缩</a>之类的事情有作用</td></tr>
<tr><td style="text-align:left">Properties</td><td
style="text-align:left">可选的，用户定义属性 的key/value map</td></tr>
<tr><td style="text-align:left">Producer名称</td><td
style="text-align:left">生产消息的producer名称(producer被自动赋予默认名称，但你也可以自己指定)</td></tr>
diff --git a/content/docs/zh-CN/next/concepts-overview.html
b/content/docs/zh-CN/next/concepts-overview.html
index cdca82d..4e6d1e6 100644
--- a/content/docs/zh-CN/next/concepts-overview.html
+++ b/content/docs/zh-CN/next/concepts-overview.html
@@ -98,7 +98,6 @@
<li><a href="/docs/zh-CN/next/concepts-authentication">身份验证和授权</a></li>
<li><a href="/docs/zh-CN/next/concepts-topic-compaction">消息压缩</a></li>
<li><a href="/docs/zh-CN/next/concepts-tiered-storage">层级存储</a></li>
-<li><a href="concepts-schema-registry.md">Schema管理服务</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/zh-CN/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/zh-CN/next/concepts-messaging"><span>消息传送</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a href="#内容">内容</a></li></ul></nav></div><footer
class="nav-footer" id="footer"><sectio [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/next/concepts-overview/index.html
b/content/docs/zh-CN/next/concepts-overview/index.html
index cdca82d..4e6d1e6 100644
--- a/content/docs/zh-CN/next/concepts-overview/index.html
+++ b/content/docs/zh-CN/next/concepts-overview/index.html
@@ -98,7 +98,6 @@
<li><a href="/docs/zh-CN/next/concepts-authentication">身份验证和授权</a></li>
<li><a href="/docs/zh-CN/next/concepts-topic-compaction">消息压缩</a></li>
<li><a href="/docs/zh-CN/next/concepts-tiered-storage">层级存储</a></li>
-<li><a href="concepts-schema-registry.md">Schema管理服务</a></li>
</ul>
</span></div></article></div><div class="docs-prevnext"><a class="docs-prev
button" href="/docs/zh-CN/next/client-libraries"><span class="arrow-prev">←
</span><span>Use Pulsar with client libraries</span></a><a class="docs-next
button" href="/docs/zh-CN/next/concepts-messaging"><span>消息传送</span><span
class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul
class="toc-headings"><li><a href="#内容">内容</a></li></ul></nav></div><footer
class="nav-footer" id="footer"><sectio [...]
const community =
document.querySelector("a[href='#community']").parentNode;
diff --git a/content/docs/zh-CN/next/sql-overview.html
b/content/docs/zh-CN/next/sql-overview.html
index c02cfd7..81c3f01 100644
--- a/content/docs/zh-CN/next/sql-overview.html
+++ b/content/docs/zh-CN/next/sql-overview.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL 概述 · Apache
Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description"
content="Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。 用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。
通过内嵌的[schema
registry](concepts-schema-registry.md)，结构化数据可以存储在Pulsar中，并允许通过SQL语言查询该数据。"/><meta
name="docsearch:version" content=" [...]
+<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL 概述 · Apache
Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description"
content="Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。 用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。
With the implementation of the [Schema
Registry](/docs/zh-CN/next/schema-get-started), structured data can be stored
in Pulsar an [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -75,7 +75,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/zh-CN"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
概述</h1></header><article><div><span><p>Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。
用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。 通过内嵌的<a
href="concepts-schema-registry.md">schema registry</a>，结构化数据 [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/zh-CN"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
概述</h1></header><article><div><span><p>Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。
用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。 With the implementation of the <a
href="/docs/zh-CN/next/schema-get- [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, we have created a
method for users to be able to query structured data stored within Pulsar in a
very efficient and scalable manner. 我们将在下面的<a
href="#performance">性能</a>部分讨论为什么Pulsar可以做到如此高效和可扩展。</p>
<p>Pulsar SQL的核心是Presto Pulsar连接器，它允许Presto worker从Pulsar查询数据。</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="Pulsar的消费者和读取器接口"></p>
diff --git a/content/docs/zh-CN/next/sql-overview/index.html
b/content/docs/zh-CN/next/sql-overview/index.html
index c02cfd7..81c3f01 100644
--- a/content/docs/zh-CN/next/sql-overview/index.html
+++ b/content/docs/zh-CN/next/sql-overview/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL 概述 · Apache
Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description"
content="Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。 用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。
通过内嵌的[schema
registry](concepts-schema-registry.md)，结构化数据可以存储在Pulsar中，并允许通过SQL语言查询该数据。"/><meta
name="docsearch:version" content=" [...]
+<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta
http-equiv="X-UA-Compatible" content="IE=edge"/><title>Pulsar SQL 概述 · Apache
Pulsar</title><meta name="viewport" content="width=device-width"/><meta
name="generator" content="Docusaurus"/><meta name="description"
content="Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。 用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。
With the implementation of the [Schema
Registry](/docs/zh-CN/next/schema-get-started), structured data can be stored
in Pulsar an [...]
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -75,7 +75,7 @@
};
}
});
- </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/zh-CN"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
概述</h1></header><article><div><span><p>Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。
用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。 通过内嵌的<a
href="concepts-schema-registry.md">schema registry</a>，结构化数据 [...]
+ </script></nav></div><div class="container mainContainer"><div
class="wrapper"><div class="post"><header class="postHeader"><a
class="edit-page-link button"
href="https://crowdin.com/project/apache-pulsar/zh-CN"; target="_blank"
rel="noreferrer noopener">Translate</a><h1 class="postHeaderTitle">Pulsar SQL
概述</h1></header><article><div><span><p>Pulsar的一个常见用例是存储事件数据流。 通常，事件数据由预定义字段构成。
用户查询已存储在Pulsar主题中的现有数据具有巨大的价值。 With the implementation of the <a
href="/docs/zh-CN/next/schema-get- [...]
<p>By leveraging <a href="https://prestosql.io/";>Presto</a>, we have created a
method for users to be able to query structured data stored within Pulsar in a
very efficient and scalable manner. 我们将在下面的<a
href="#performance">性能</a>部分讨论为什么Pulsar可以做到如此高效和可扩展。</p>
<p>Pulsar SQL的核心是Presto Pulsar连接器，它允许Presto worker从Pulsar查询数据。</p>
<p><img src="/docs/assets/pulsar-sql-arch-2.png" alt="Pulsar的消费者和读取器接口"></p>
diff --git a/content/swagger/2.5.0-SNAPSHOT/swagger.json
b/content/swagger/2.5.0-SNAPSHOT/swagger.json
index a35355c..52aa32f 100644
--- a/content/swagger/2.5.0-SNAPSHOT/swagger.json
+++ b/content/swagger/2.5.0-SNAPSHOT/swagger.json
@@ -4797,7 +4797,7 @@
"200" : {
"description" : "successful operation",
"schema" : {
- "$ref" : "#/definitions/NonPersistentTopicStats"
+ "$ref" : "#/definitions/TopicStats"
}
},
"401" : {
@@ -8447,6 +8447,16 @@
"example" : "broker1:8080",
"description" : "The broker name"
},
+ "policyName" : {
+ "type" : "string",
+ "example" : "my-policy",
+ "description" : "Policy name"
+ },
+ "isPrimary" : {
+ "type" : "boolean",
+ "example" : false,
+ "description" : "Is Primary broker"
+ },
"namespaceRegex" : {
"type" : "array",
"description" : "The namespace-isolation policies attached to this
broker",
@@ -8541,10 +8551,10 @@
"type" : "string"
}
},
- "connectedSince" : {
+ "clientVersion" : {
"type" : "string"
},
- "clientVersion" : {
+ "connectedSince" : {
"type" : "string"
},
"address" : {
@@ -8907,13 +8917,6 @@
"memory" : {
"$ref" : "#/definitions/ResourceUsage"
},
- "cpu" : {
- "$ref" : "#/definitions/ResourceUsage"
- },
- "msgThroughputIn" : {
- "type" : "number",
- "format" : "double"
- },
"directMemory" : {
"$ref" : "#/definitions/ResourceUsage"
},
@@ -8921,10 +8924,17 @@
"type" : "integer",
"format" : "int64"
},
+ "msgThroughputIn" : {
+ "type" : "number",
+ "format" : "double"
+ },
"msgThroughputOut" : {
"type" : "number",
"format" : "double"
},
+ "cpu" : {
+ "$ref" : "#/definitions/ResourceUsage"
+ },
"underLoaded" : {
"type" : "boolean"
},
@@ -9100,15 +9110,15 @@
"type" : "number",
"format" : "double"
},
- "connectedSince" : {
- "type" : "string"
- },
"clientVersion" : {
"type" : "string"
},
"producerName" : {
"type" : "string"
},
+ "connectedSince" : {
+ "type" : "string"
+ },
"address" : {
"type" : "string"
}
@@ -9775,15 +9785,15 @@
"type" : "string"
}
},
- "connectedSince" : {
- "type" : "string"
- },
"clientVersion" : {
"type" : "string"
},
"producerName" : {
"type" : "string"
},
+ "connectedSince" : {
+ "type" : "string"
+ },
"address" : {
"type" : "string"
}
@@ -9883,11 +9893,11 @@
"ResourceUnit" : {
"type" : "object",
"properties" : {
- "availableResource" : {
- "$ref" : "#/definitions/ResourceDescription"
- },
"resourceId" : {
"type" : "string"
+ },
+ "availableResource" : {
+ "$ref" : "#/definitions/ResourceDescription"
}
}
},
diff --git a/content/swagger/2.5.0-SNAPSHOT/swaggerfunctions.json
b/content/swagger/2.5.0-SNAPSHOT/swaggerfunctions.json
index e74985c..fd8ad17 100644
--- a/content/swagger/2.5.0-SNAPSHOT/swaggerfunctions.json
+++ b/content/swagger/2.5.0-SNAPSHOT/swaggerfunctions.json
@@ -1348,24 +1348,24 @@
"Message" : {
"type" : "object",
"properties" : {
- "keyBytes" : {
- "type" : "array",
- "items" : {
- "type" : "string",
- "format" : "byte"
- }
+ "replicated" : {
+ "type" : "boolean"
},
- "eventTime" : {
+ "publishTime" : {
"type" : "integer",
"format" : "int64"
},
- "replicated" : {
- "type" : "boolean"
+ "eventTime" : {
+ "type" : "integer",
+ "format" : "int64"
},
"topicName" : {
"type" : "string"
},
- "publishTime" : {
+ "messageId" : {
+ "$ref" : "#/definitions/MessageId"
+ },
+ "sequenceId" : {
"type" : "integer",
"format" : "int64"
},
@@ -1390,18 +1390,18 @@
"format" : "byte"
}
},
- "producerName" : {
- "type" : "string"
- },
"replicatedFrom" : {
"type" : "string"
},
- "messageId" : {
- "$ref" : "#/definitions/MessageId"
+ "producerName" : {
+ "type" : "string"
},
- "sequenceId" : {
- "type" : "integer",
- "format" : "int64"
+ "keyBytes" : {
+ "type" : "array",
+ "items" : {
+ "type" : "string",
+ "format" : "byte"
+ }
},
"data" : {
"type" : "array",
diff --git a/content/swagger/master/swagger.json
b/content/swagger/master/swagger.json
index a35355c..52aa32f 100644
--- a/content/swagger/master/swagger.json
+++ b/content/swagger/master/swagger.json
@@ -4797,7 +4797,7 @@
"200" : {
"description" : "successful operation",
"schema" : {
- "$ref" : "#/definitions/NonPersistentTopicStats"
+ "$ref" : "#/definitions/TopicStats"
}
},
"401" : {
@@ -8447,6 +8447,16 @@
"example" : "broker1:8080",
"description" : "The broker name"
},
+ "policyName" : {
+ "type" : "string",
+ "example" : "my-policy",
+ "description" : "Policy name"
+ },
+ "isPrimary" : {
+ "type" : "boolean",
+ "example" : false,
+ "description" : "Is Primary broker"
+ },
"namespaceRegex" : {
"type" : "array",
"description" : "The namespace-isolation policies attached to this
broker",
@@ -8541,10 +8551,10 @@
"type" : "string"
}
},
- "connectedSince" : {
+ "clientVersion" : {
"type" : "string"
},
- "clientVersion" : {
+ "connectedSince" : {
"type" : "string"
},
"address" : {
@@ -8907,13 +8917,6 @@
"memory" : {
"$ref" : "#/definitions/ResourceUsage"
},
- "cpu" : {
- "$ref" : "#/definitions/ResourceUsage"
- },
- "msgThroughputIn" : {
- "type" : "number",
- "format" : "double"
- },
"directMemory" : {
"$ref" : "#/definitions/ResourceUsage"
},
@@ -8921,10 +8924,17 @@
"type" : "integer",
"format" : "int64"
},
+ "msgThroughputIn" : {
+ "type" : "number",
+ "format" : "double"
+ },
"msgThroughputOut" : {
"type" : "number",
"format" : "double"
},
+ "cpu" : {
+ "$ref" : "#/definitions/ResourceUsage"
+ },
"underLoaded" : {
"type" : "boolean"
},
@@ -9100,15 +9110,15 @@
"type" : "number",
"format" : "double"
},
- "connectedSince" : {
- "type" : "string"
- },
"clientVersion" : {
"type" : "string"
},
"producerName" : {
"type" : "string"
},
+ "connectedSince" : {
+ "type" : "string"
+ },
"address" : {
"type" : "string"
}
@@ -9775,15 +9785,15 @@
"type" : "string"
}
},
- "connectedSince" : {
- "type" : "string"
- },
"clientVersion" : {
"type" : "string"
},
"producerName" : {
"type" : "string"
},
+ "connectedSince" : {
+ "type" : "string"
+ },
"address" : {
"type" : "string"
}
@@ -9883,11 +9893,11 @@
"ResourceUnit" : {
"type" : "object",
"properties" : {
- "availableResource" : {
- "$ref" : "#/definitions/ResourceDescription"
- },
"resourceId" : {
"type" : "string"
+ },
+ "availableResource" : {
+ "$ref" : "#/definitions/ResourceDescription"
}
}
},
diff --git a/content/swagger/master/swaggerfunctions.json
b/content/swagger/master/swaggerfunctions.json
index e74985c..fd8ad17 100644
--- a/content/swagger/master/swaggerfunctions.json
+++ b/content/swagger/master/swaggerfunctions.json
@@ -1348,24 +1348,24 @@
"Message" : {
"type" : "object",
"properties" : {
- "keyBytes" : {
- "type" : "array",
- "items" : {
- "type" : "string",
- "format" : "byte"
- }
+ "replicated" : {
+ "type" : "boolean"
},
- "eventTime" : {
+ "publishTime" : {
"type" : "integer",
"format" : "int64"
},
- "replicated" : {
- "type" : "boolean"
+ "eventTime" : {
+ "type" : "integer",
+ "format" : "int64"
},
"topicName" : {
"type" : "string"
},
- "publishTime" : {
+ "messageId" : {
+ "$ref" : "#/definitions/MessageId"
+ },
+ "sequenceId" : {
"type" : "integer",
"format" : "int64"
},
@@ -1390,18 +1390,18 @@
"format" : "byte"
}
},
- "producerName" : {
- "type" : "string"
- },
"replicatedFrom" : {
"type" : "string"
},
- "messageId" : {
- "$ref" : "#/definitions/MessageId"
+ "producerName" : {
+ "type" : "string"
},
- "sequenceId" : {
- "type" : "integer",
- "format" : "int64"
+ "keyBytes" : {
+ "type" : "array",
+ "items" : {
+ "type" : "string",
+ "format" : "byte"
+ }
},
"data" : {
"type" : "array",
