pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mme...@apache.org
Subject [pulsar] branch asf-site updated: Updated site at revision d13fe5b
Date Mon, 29 Oct 2018 10:26:28 GMT
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 5a72a65  Updated site at revision d13fe5b
5a72a65 is described below

commit 5a72a65f35458f70646f8cca4c752fe30e9d58b1
Author: jenkins <builds@apache.org>
AuthorDate: Mon Oct 29 10:26:20 2018 +0000

    Updated site at revision d13fe5b
---
 .../docs/latest/adaptors/PulsarSpark/index.html    |  2 +-
 .../docs/latest/adaptors/PulsarStorm/index.html    |  2 +-
 content/docs/latest/admin-api/overview/index.html  |  8 ++--
 content/docs/latest/clients/Java/index.html        |  2 +-
 .../latest/cookbooks/PartitionedTopics/index.html  |  2 +-
 .../latest/cookbooks/RetentionExpiry/index.html    |  2 +-
 .../docs/latest/cookbooks/compaction/index.html    |  2 +-
 .../cookbooks/message-deduplication/index.html     |  2 +-
 .../docs/latest/cookbooks/message-queue/index.html |  2 +-
 .../latest/cookbooks/tiered-storage/index.html     |  2 +-
 .../docs/latest/deployment/aws-cluster/index.html  |  2 +-
 content/docs/latest/deployment/cluster/index.html  |  2 +-
 content/docs/latest/deployment/instance/index.html |  2 +-
 content/docs/latest/reference/CliTools/index.html  |  4 +-
 .../docs/latest/security/authorization/index.html  |  4 +-
 .../zh-CN/2.1.0-incubating/admin-api-schemas.html  |  4 +-
 .../2.1.0-incubating/admin-api-schemas/index.html  |  4 +-
 .../2.1.0-incubating/concepts-schema-registry.html | 26 ++++++-------
 .../concepts-schema-registry/index.html            | 26 ++++++-------
 .../2.1.1-incubating/concepts-schema-registry.html | 26 ++++++-------
 .../concepts-schema-registry/index.html            | 26 ++++++-------
 content/docs/zh-CN/concepts-schema-registry.html   | 26 ++++++-------
 .../docs/zh-CN/concepts-schema-registry/index.html | 26 ++++++-------
 content/docs/zh-CN/next/admin-api-schemas.html     |  4 +-
 .../docs/zh-CN/next/admin-api-schemas/index.html   |  4 +-
 .../docs/zh-CN/next/concepts-schema-registry.html  | 26 ++++++-------
 .../zh-CN/next/concepts-schema-registry/index.html | 26 ++++++-------
 content/swagger/swagger.json                       | 44 +++++++++++-----------
 28 files changed, 154 insertions(+), 154 deletions(-)

diff --git a/content/docs/latest/adaptors/PulsarSpark/index.html b/content/docs/latest/adaptors/PulsarSpark/index.html
index c00dd49..a30d928 100644
--- a/content/docs/latest/adaptors/PulsarSpark/index.html
+++ b/content/docs/latest/adaptors/PulsarSpark/index.html
@@ -1673,9 +1673,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/adaptors/PulsarStorm/index.html b/content/docs/latest/adaptors/PulsarStorm/index.html
index a100055..3059cf5 100644
--- a/content/docs/latest/adaptors/PulsarStorm/index.html
+++ b/content/docs/latest/adaptors/PulsarStorm/index.html
@@ -1427,9 +1427,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/admin-api/overview/index.html b/content/docs/latest/admin-api/overview/index.html
index 994ad01..80a6f28 100644
--- a/content/docs/latest/admin-api/overview/index.html
+++ b/content/docs/latest/admin-api/overview/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
@@ -1439,9 +1439,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
@@ -1685,9 +1685,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
@@ -1941,9 +1941,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/clients/Java/index.html b/content/docs/latest/clients/Java/index.html
index 8ce7177..b938e5f 100644
--- a/content/docs/latest/clients/Java/index.html
+++ b/content/docs/latest/clients/Java/index.html
@@ -1437,9 +1437,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/cookbooks/PartitionedTopics/index.html b/content/docs/latest/cookbooks/PartitionedTopics/index.html
index 25ce2c6..c5c0499 100644
--- a/content/docs/latest/cookbooks/PartitionedTopics/index.html
+++ b/content/docs/latest/cookbooks/PartitionedTopics/index.html
@@ -1681,9 +1681,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/cookbooks/RetentionExpiry/index.html b/content/docs/latest/cookbooks/RetentionExpiry/index.html
index 0a51438..763a81c 100644
--- a/content/docs/latest/cookbooks/RetentionExpiry/index.html
+++ b/content/docs/latest/cookbooks/RetentionExpiry/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/cookbooks/compaction/index.html b/content/docs/latest/cookbooks/compaction/index.html
index fd7475c..e0c2266 100644
--- a/content/docs/latest/cookbooks/compaction/index.html
+++ b/content/docs/latest/cookbooks/compaction/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/cookbooks/message-deduplication/index.html b/content/docs/latest/cookbooks/message-deduplication/index.html
index 03df0bf..7767ce8 100644
--- a/content/docs/latest/cookbooks/message-deduplication/index.html
+++ b/content/docs/latest/cookbooks/message-deduplication/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/cookbooks/message-queue/index.html b/content/docs/latest/cookbooks/message-queue/index.html
index 3655ec9..32e4e8f 100644
--- a/content/docs/latest/cookbooks/message-queue/index.html
+++ b/content/docs/latest/cookbooks/message-queue/index.html
@@ -1437,9 +1437,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/cookbooks/tiered-storage/index.html b/content/docs/latest/cookbooks/tiered-storage/index.html
index 92718d6..d2419ee 100644
--- a/content/docs/latest/cookbooks/tiered-storage/index.html
+++ b/content/docs/latest/cookbooks/tiered-storage/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/deployment/aws-cluster/index.html b/content/docs/latest/deployment/aws-cluster/index.html
index 31cfc51..47a5a53 100644
--- a/content/docs/latest/deployment/aws-cluster/index.html
+++ b/content/docs/latest/deployment/aws-cluster/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/deployment/cluster/index.html b/content/docs/latest/deployment/cluster/index.html
index 0a12601..3113ea1 100644
--- a/content/docs/latest/deployment/cluster/index.html
+++ b/content/docs/latest/deployment/cluster/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/deployment/instance/index.html b/content/docs/latest/deployment/instance/index.html
index e4d8219..9a49d19 100644
--- a/content/docs/latest/deployment/instance/index.html
+++ b/content/docs/latest/deployment/instance/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/reference/CliTools/index.html b/content/docs/latest/reference/CliTools/index.html
index cc20bbd..1f6ea9f 100644
--- a/content/docs/latest/reference/CliTools/index.html
+++ b/content/docs/latest/reference/CliTools/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
@@ -1439,9 +1439,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/latest/security/authorization/index.html b/content/docs/latest/security/authorization/index.html
index 755417d..538bda7 100644
--- a/content/docs/latest/security/authorization/index.html
+++ b/content/docs/latest/security/authorization/index.html
@@ -1189,9 +1189,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
@@ -2435,9 +2435,9 @@
           
           
           
-          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
+          <li><a href="/docs/latest/admin-api/overview/">The Pulsar admin interface</a></li>
           
           
           
diff --git a/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas.html b/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas.html
index ccc858d..2b23f48 100644
--- a/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas.html
+++ b/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas.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>Managing Schemas · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/2.1.0-incubating/admin-api-overview)."/><meta name="docsearch:version" content="2.1.0-incubating"/><meta nam [...]
+<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>管理Schema · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/2.1.0-incubating/admin-api-overview)."/><meta name="docsearch:version" content="2.1.0-incubating"/><meta name="docse [...]
               (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)
@@ -45,7 +45,7 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer docMainContainer"><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">Managing Schemas</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/2.1.0-incubating/admin-api-overvi [...]
+        </script></nav></div><div class="container mainContainer docMainContainer"><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">管理Schema</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/2.1.0-incubating/admin-api-overview">admi [...]
 <h2><a class="anchor" aria-hidden="true" id="schema-resources"></a><a href="#schema-resources" 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. [...]
 <p>A Pulsar schema is a fairly simple data structure stored in Pulsar for representing the structure of messages stored in a Pulsar topic. The schema structure consists of:</p>
 <ul>
diff --git a/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas/index.html b/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas/index.html
index ccc858d..2b23f48 100644
--- a/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas/index.html
+++ b/content/docs/zh-CN/2.1.0-incubating/admin-api-schemas/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>Managing Schemas · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/2.1.0-incubating/admin-api-overview)."/><meta name="docsearch:version" content="2.1.0-incubating"/><meta nam [...]
+<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>管理Schema · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/2.1.0-incubating/admin-api-overview)."/><meta name="docsearch:version" content="2.1.0-incubating"/><meta name="docse [...]
               (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)
@@ -45,7 +45,7 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer docMainContainer"><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">Managing Schemas</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/2.1.0-incubating/admin-api-overvi [...]
+        </script></nav></div><div class="container mainContainer docMainContainer"><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">管理Schema</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/2.1.0-incubating/admin-api-overview">admi [...]
 <h2><a class="anchor" aria-hidden="true" id="schema-resources"></a><a href="#schema-resources" 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. [...]
 <p>A Pulsar schema is a fairly simple data structure stored in Pulsar for representing the structure of messages stored in a Pulsar topic. The schema structure consists of:</p>
 <ul>
diff --git a/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry.html b/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry.html
index c274439..1fc874a 100644
--- a/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry.html
+++ b/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/2.1.0-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages. [...]
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/2.1.0-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/2.1.0-incubating/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/2.1.0-incubating/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.0-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.0-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/2.1.0-incubating/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.0-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.0-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry/index.html b/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry/index.html
index c274439..1fc874a 100644
--- a/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry/index.html
+++ b/content/docs/zh-CN/2.1.0-incubating/concepts-schema-registry/index.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/2.1.0-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages. [...]
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/2.1.0-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/2.1.0-incubating/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/2.1.0-incubating/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.0-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.0-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/2.1.0-incubating/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.0-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.0-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry.html b/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry.html
index 191ab6d..c4571cf 100644
--- a/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry.html
+++ b/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/2.1.1-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages. [...]
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/2.1.1-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/2.1.1-incubating/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/2.1.1-incubating/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.1-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.1-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/2.1.1-incubating/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.1-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.1-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry/index.html b/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry/index.html
index 191ab6d..c4571cf 100644
--- a/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry/index.html
+++ b/content/docs/zh-CN/2.1.1-incubating/concepts-schema-registry/index.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/2.1.1-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages. [...]
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/2.1.1-incubating/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/2.1.1-incubating/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/2.1.1-incubating/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.1-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.1-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/2.1.1-incubating/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.1.1-incubating/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/2.1.1-incubating/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a>< [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/docs/zh-CN/concepts-schema-registry.html b/content/docs/zh-CN/concepts-schema-registry.html
index 5acd6bc..b09cd87 100644
--- a/content/docs/zh-CN/concepts-schema-registry.html
+++ b/content/docs/zh-CN/concepts-schema-registry.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema版本">Schema [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema版本">Schema [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/docs/zh-CN/concepts-schema-registry/index.html b/content/docs/zh-CN/concepts-schema-registry/index.html
index 5acd6bc..b09cd87 100644
--- a/content/docs/zh-CN/concepts-schema-registry/index.html
+++ b/content/docs/zh-CN/concepts-schema-registry/index.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema版本">Schema [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema版本">Schema [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/docs/zh-CN/next/admin-api-schemas.html b/content/docs/zh-CN/next/admin-api-schemas.html
index 5e5b42c..cc80093 100644
--- a/content/docs/zh-CN/next/admin-api-schemas.html
+++ b/content/docs/zh-CN/next/admin-api-schemas.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>Managing Schemas · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/next/admin-api-overview)."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" c [...]
+<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>管理Schema · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/next/admin-api-overview)."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" content=" [...]
               (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)
@@ -45,7 +45,7 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer docMainContainer"><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">Managing Schemas</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/next/admin-api-overview">admin AP [...]
+        </script></nav></div><div class="container mainContainer docMainContainer"><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">管理Schema</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/next/admin-api-overview">admin API</a>.</p>
 <h2><a class="anchor" aria-hidden="true" id="schema-resources"></a><a href="#schema-resources" 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. [...]
 <p>A Pulsar schema is a fairly simple data structure stored in Pulsar for representing the structure of messages stored in a Pulsar topic. The schema structure consists of:</p>
 <ul>
diff --git a/content/docs/zh-CN/next/admin-api-schemas/index.html b/content/docs/zh-CN/next/admin-api-schemas/index.html
index 5e5b42c..cc80093 100644
--- a/content/docs/zh-CN/next/admin-api-schemas/index.html
+++ b/content/docs/zh-CN/next/admin-api-schemas/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>Managing Schemas · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/next/admin-api-overview)."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" c [...]
+<!DOCTYPE html><html lang="zh-CN"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>管理Schema · Apache Pulsar</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="Schemas, like other entities in Pulsar, can be managed using the [admin API](/docs/zh-CN/next/admin-api-overview)."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" content=" [...]
               (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)
@@ -45,7 +45,7 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer docMainContainer"><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">Managing Schemas</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/next/admin-api-overview">admin AP [...]
+        </script></nav></div><div class="container mainContainer docMainContainer"><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">管理Schema</h1></header><article><div><span><p>Schemas, like other entities in Pulsar, can be managed using the <a href="/docs/zh-CN/next/admin-api-overview">admin API</a>.</p>
 <h2><a class="anchor" aria-hidden="true" id="schema-resources"></a><a href="#schema-resources" 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. [...]
 <p>A Pulsar schema is a fairly simple data structure stored in Pulsar for representing the structure of messages stored in a Pulsar topic. The schema structure consists of:</p>
 <ul>
diff --git a/content/docs/zh-CN/next/concepts-schema-registry.html b/content/docs/zh-CN/next/concepts-schema-registry.html
index d645763..50345f6 100644
--- a/content/docs/zh-CN/next/concepts-schema-registry.html
+++ b/content/docs/zh-CN/next/concepts-schema-registry.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/next/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/next/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/next/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/next/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/next/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/next/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/next/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/docs/zh-CN/next/concepts-schema-registry/index.html b/content/docs/zh-CN/next/concepts-schema-registry/index.html
index d645763..50345f6 100644
--- a/content/docs/zh-CN/next/concepts-schema-registry/index.html
+++ b/content/docs/zh-CN/next/concepts-schema-registry/index.html
@@ -91,33 +91,33 @@ Producer&lt;SensorReading&gt; producer = client.newProducer(JSONSchema.of(Sensor
 <tr><th style="text-align:left">场景</th><th style="text-align:left">发生了什么</th></tr>
 </thead>
 <tbody>
-<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">The producer is created using the given schema. The schema is transmitted to the broker and stored (since no existing schema is &quot;compatible&quot; with the <code>SensorReading</code> schema). Any consumer created using the same schema/topic can consume messages from the <code>sensor-data</code> topic.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using the same schema that's already stored</td><td style="text-align:left">The schema is transmitted to the Pulsar broker. The broker determines that the schema is compatible. The broker attempts to store the schema in <a href="/docs/zh-CN/next/concepts-architecture-overview#persistent-storage">BookKeeper</a> but then determines that it's already stored, so it's then used to tag produced messages.</td></tr>
-<tr><td style="text-align:left">A schema already exists; the producer connects using a new schema that is compatible</td><td style="text-align:left">The producer transmits the schema to the broker. The broker determines that the schema is compatible and stores the new schema as the current version (with a new version number).</td></tr>
+<tr><td style="text-align:left">该Topic不存在schema</td><td style="text-align:left">使用给定的schema创建了producer。 Schema传输到broker并被存储 (因为没有现成的schema与 <code>SensorReading</code> schema &quot;兼容&quot;)。 任何使用同样schema/topic的consumer可以消费<code>sensor-data</code> topic中的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用已经被保存过的schema进行连接</td><td style="text-align:left">Schema被传输到Pulsar broker。 Broker确认此schema是兼容的。 Broker尝试在<a href="/docs/zh-CN/next/concepts-architecture-overview#persistent-storage">BookKeeper</a>存储schema,但是发现它已经存在了,所以用它来标记生产的消息。</td></tr>
+<tr><td style="text-align:left">Schema已经存在;producer使用兼容的新schema进行连接。</td><td style="text-align:left">Producer传输schema到broker。broker发现这个schema是兼容的,随后保存这个新schema作为当前版本(使用新的版本号)。</td></tr>
 </tbody>
 </table>
 <blockquote>
-<p>Schemas are versioned in succession. Schema storage happens in the broker that handles the associated topic so that version assignments can be made. Once a version is assigned/fetched to/for a schema, all subsequent messages produced by that producer are tagged with the appropriate version.</p>
+<p>Schema版本是连续的。 Schema被处理关联topic的broker所保存,便于进行版本的分配。 一旦分配/提供了schema的版本,后续由该生产者生产的所有消息,都将被恰当的版本所标记。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="supported-schema-formats"></a><a href="#supported-schema-formats" 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-. [...]
-<p>The following formats are supported by the Pulsar schema registry:</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 [...]
+<p>以下格式被Pulsar schema注册所支持:</p>
 <ul>
-<li>None. If no schema is specified for a topic, producers and consumers will handle raw bytes.</li>
-<li><code>String</code> (used for UTF-8-encoded strings)</li>
+<li>无。如果没有为topic指定schema,producer和consumer将会处理原始字节。</li>
+<li><code>String</code> (用于 UTF-8-encoded 字符串)</li>
 <li><a href="https://www.json.org/">JSON</a></li>
 <li><a href="https://developers.google.com/protocol-buffers/">Protobuf</a></li>
 <li><a href="https://avro.apache.org/">Avro</a></li>
 </ul>
-<p>For usage instructions, see the documentation for your preferred client library:</p>
+<p>使用介绍,请参考你选择的客户端类库文档。</p>
 <ul>
 <li><a href="/docs/zh-CN/next/client-libraries-java#schemas">Java</a></li>
 </ul>
 <blockquote>
-<p>Support for other schema formats will be added in future releases of Pulsar.</p>
+<p>未来的Pulsar release将会支持其他更多schema格式。</p>
 </blockquote>
-<h2><a class="anchor" aria-hidden="true" id="managing-schemas"></a><a href="#managing-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. [...]
-<p>You can use Pulsar's <a href="/docs/zh-CN/next/admin-api-schemas">admin tools</a> for managing schemas for topics.</p>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/next/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema [...]
+<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  [...]
+<p>你可以使用Pulsar的<a href="/docs/zh-CN/next/admin-api-schemas">admin tools</a>来管理topic的schema</p>
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-tiered-storage"><span class="arrow-prev">← </span><span>上一页</span></a><a class="docs-next button" href="/docs/zh-CN/next/functions-overview"><span>下一页</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav docOnPageNav"><ul class="toc-headings"><li><a href="#基础架构">基础架构</a></li><li><a href="#schema是如何工作的">Schema是如何工作的</a></li><li><a href="#schema [...]
       const community = document.querySelector("a[href='#community']").parentNode;
       const communityMenu =
         '<li>' +
diff --git a/content/swagger/swagger.json b/content/swagger/swagger.json
index 04d5871..625a890 100644
--- a/content/swagger/swagger.json
+++ b/content/swagger/swagger.json
@@ -6790,11 +6790,12 @@
           "type" : "number",
           "format" : "double"
         },
-        "loadReportType" : {
-          "type" : "string"
+        "cpu" : {
+          "$ref" : "#/definitions/ResourceUsage"
         },
-        "underLoaded" : {
-          "type" : "boolean"
+        "lastUpdate" : {
+          "type" : "integer",
+          "format" : "int64"
         },
         "overLoaded" : {
           "type" : "boolean"
@@ -6803,19 +6804,18 @@
           "type" : "number",
           "format" : "double"
         },
-        "cpu" : {
-          "$ref" : "#/definitions/ResourceUsage"
+        "msgThroughputOut" : {
+          "type" : "number",
+          "format" : "double"
         },
         "bandwidthOut" : {
           "$ref" : "#/definitions/ResourceUsage"
         },
-        "lastUpdate" : {
-          "type" : "integer",
-          "format" : "int64"
+        "underLoaded" : {
+          "type" : "boolean"
         },
-        "msgThroughputOut" : {
-          "type" : "number",
-          "format" : "double"
+        "directMemory" : {
+          "$ref" : "#/definitions/ResourceUsage"
         },
         "bandwidthIn" : {
           "$ref" : "#/definitions/ResourceUsage"
@@ -6823,8 +6823,8 @@
         "memory" : {
           "$ref" : "#/definitions/ResourceUsage"
         },
-        "directMemory" : {
-          "$ref" : "#/definitions/ResourceUsage"
+        "loadReportType" : {
+          "type" : "string"
         }
       }
     },
@@ -6984,10 +6984,10 @@
           "type" : "number",
           "format" : "double"
         },
-        "connectedSince" : {
+        "producerName" : {
           "type" : "string"
         },
-        "producerName" : {
+        "connectedSince" : {
           "type" : "string"
         },
         "clientVersion" : {
@@ -7692,10 +7692,10 @@
             "type" : "string"
           }
         },
-        "connectedSince" : {
+        "producerName" : {
           "type" : "string"
         },
-        "producerName" : {
+        "connectedSince" : {
           "type" : "string"
         },
         "clientVersion" : {
@@ -7757,15 +7757,15 @@
     "ResourceDescription" : {
       "type" : "object",
       "properties" : {
+        "usagePct" : {
+          "type" : "integer",
+          "format" : "int32"
+        },
         "resourceUsage" : {
           "type" : "object",
           "additionalProperties" : {
             "$ref" : "#/definitions/ResourceUsage"
           }
-        },
-        "usagePct" : {
-          "type" : "integer",
-          "format" : "int32"
         }
       }
     },


Mime
View raw message