This is an automated email from the ASF dual-hosted git repository.
tison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 20e60da50f3 [fix][doc] resolve doc issues in schema, client, and
reference (#450)
20e60da50f3 is described below
commit 20e60da50f372c9934846a9e7299da0ebd813811
Author: Anonymitaet <[email protected]>
AuthorDate: Fri Mar 3 15:57:03 2023 +0800
[fix][doc] resolve doc issues in schema, client, and reference (#450)
---
docs/admin-api-schemas.md | 8 ++++++++
static/reference/next/pulsar-daemon/pulsar-daemon.md | 6 ++----
versioned_docs/version-2.10.x/schema-manage.md | 6 +++---
versioned_docs/version-2.11.x/admin-api-schemas.md | 8 ++++++++
versioned_docs/version-2.2.0/schema-manage.md | 6 +++---
versioned_docs/version-2.2.1/schema-manage.md | 6 +++---
versioned_docs/version-2.3.0/schema-manage.md | 6 +++---
versioned_docs/version-2.3.1/schema-manage.md | 6 +++---
versioned_docs/version-2.3.2/schema-manage.md | 6 +++---
versioned_docs/version-2.4.0/schema-manage.md | 6 +++---
versioned_docs/version-2.4.1/schema-manage.md | 6 +++---
versioned_docs/version-2.4.2/schema-manage.md | 6 +++---
versioned_docs/version-2.5.0/schema-manage.md | 6 +++---
versioned_docs/version-2.5.1/schema-manage.md | 6 +++---
versioned_docs/version-2.5.2/schema-manage.md | 6 +++---
versioned_docs/version-2.6.0/schema-manage.md | 6 +++---
versioned_docs/version-2.6.1/schema-manage.md | 6 +++---
versioned_docs/version-2.6.2/schema-manage.md | 6 +++---
versioned_docs/version-2.6.3/schema-manage.md | 6 +++---
versioned_docs/version-2.6.4/schema-manage.md | 6 +++---
versioned_docs/version-2.7.0/schema-manage.md | 6 +++---
versioned_docs/version-2.7.1/schema-manage.md | 6 +++---
versioned_docs/version-2.7.2/schema-manage.md | 6 +++---
versioned_docs/version-2.7.3/schema-manage.md | 6 +++---
versioned_docs/version-2.7.4/schema-manage.md | 6 +++---
versioned_docs/version-2.7.5/schema-manage.md | 6 +++---
versioned_docs/version-2.8.x/schema-manage.md | 6 +++---
versioned_docs/version-2.9.x/schema-manage.md | 6 +++---
28 files changed, 93 insertions(+), 79 deletions(-)
diff --git a/docs/admin-api-schemas.md b/docs/admin-api-schemas.md
index 4843e173bc1..ca4414177bb 100644
--- a/docs/admin-api-schemas.md
+++ b/docs/admin-api-schemas.md
@@ -51,6 +51,14 @@ The `schema-definition-file` is in JSON format.
}
```
+The `schema-definition-file` includes the following fields:
+
+| Field | Description |
+| --- | --- |
+| `type` | The schema type. |
+| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a **primitive** schema, this field should be
blank. </li><li>If the schema is a **struct** schema, this field should be a
JSON string of the Avro schema definition. </li> |
+| `properties` | The additional properties associated with the schema. |
+
The following is an example of the `schema-definition-file` for a JSON schema.
**Example**
diff --git a/static/reference/next/pulsar-daemon/pulsar-daemon.md
b/static/reference/next/pulsar-daemon/pulsar-daemon.md
index 66a9926cfa7..ffd690d62bd 100644
--- a/static/reference/next/pulsar-daemon/pulsar-daemon.md
+++ b/static/reference/next/pulsar-daemon/pulsar-daemon.md
@@ -7,11 +7,9 @@ pulsar-daemon has a similar interface to the pulsar command
but adds start and s
### `start`
Start a service in the background using nohup.
-:::tip
+**Tip**
-You can use flags to perform more tasks. For example, `pulsar-daemon start
standalone -nfw -nss` can start Pulsar faster in the background (without
function workers and stream storage). `pulsar-daemon start standalone` flags
are the same as `pulsar standalone` flags. For the complete flag list, see
flags of the `pulsar standalone` command on the [Pulsar Reference
Site](https://pulsar.apache.org/reference).
-
-:::
+> You can use flags to perform more tasks. For example, `pulsar-daemon start
standalone -nfw -nss` can start Pulsar faster in the background (without
function workers and stream storage). `pulsar-daemon start standalone` flags
are the same as `pulsar standalone` flags. For the complete flag list, see
flags of the `pulsar standalone` command on the [Pulsar Reference
Site](https://pulsar.apache.org/reference).
Usage
diff --git a/versioned_docs/version-2.10.x/schema-manage.md
b/versioned_docs/version-2.10.x/schema-manage.md
index e62818c7e82..03949b362d9 100644
--- a/versioned_docs/version-2.10.x/schema-manage.md
+++ b/versioned_docs/version-2.10.x/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.11.x/admin-api-schemas.md
b/versioned_docs/version-2.11.x/admin-api-schemas.md
index 4843e173bc1..ca4414177bb 100644
--- a/versioned_docs/version-2.11.x/admin-api-schemas.md
+++ b/versioned_docs/version-2.11.x/admin-api-schemas.md
@@ -51,6 +51,14 @@ The `schema-definition-file` is in JSON format.
}
```
+The `schema-definition-file` includes the following fields:
+
+| Field | Description |
+| --- | --- |
+| `type` | The schema type. |
+| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a **primitive** schema, this field should be
blank. </li><li>If the schema is a **struct** schema, this field should be a
JSON string of the Avro schema definition. </li> |
+| `properties` | The additional properties associated with the schema. |
+
The following is an example of the `schema-definition-file` for a JSON schema.
**Example**
diff --git a/versioned_docs/version-2.2.0/schema-manage.md
b/versioned_docs/version-2.2.0/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.2.0/schema-manage.md
+++ b/versioned_docs/version-2.2.0/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.2.1/schema-manage.md
b/versioned_docs/version-2.2.1/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.2.1/schema-manage.md
+++ b/versioned_docs/version-2.2.1/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.3.0/schema-manage.md
b/versioned_docs/version-2.3.0/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.3.0/schema-manage.md
+++ b/versioned_docs/version-2.3.0/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.3.1/schema-manage.md
b/versioned_docs/version-2.3.1/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.3.1/schema-manage.md
+++ b/versioned_docs/version-2.3.1/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.3.2/schema-manage.md
b/versioned_docs/version-2.3.2/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.3.2/schema-manage.md
+++ b/versioned_docs/version-2.3.2/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.4.0/schema-manage.md
b/versioned_docs/version-2.4.0/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.4.0/schema-manage.md
+++ b/versioned_docs/version-2.4.0/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.4.1/schema-manage.md
b/versioned_docs/version-2.4.1/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.4.1/schema-manage.md
+++ b/versioned_docs/version-2.4.1/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.4.2/schema-manage.md
b/versioned_docs/version-2.4.2/schema-manage.md
index f0199571010..77b74ded836 100644
--- a/versioned_docs/version-2.4.2/schema-manage.md
+++ b/versioned_docs/version-2.4.2/schema-manage.md
@@ -175,7 +175,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -228,7 +228,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -245,7 +245,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.5.0/schema-manage.md
b/versioned_docs/version-2.5.0/schema-manage.md
index 84d0ccdc231..805d1d4d49e 100644
--- a/versioned_docs/version-2.5.0/schema-manage.md
+++ b/versioned_docs/version-2.5.0/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.5.1/schema-manage.md
b/versioned_docs/version-2.5.1/schema-manage.md
index 580598c6edd..42fafd2f7c9 100644
--- a/versioned_docs/version-2.5.1/schema-manage.md
+++ b/versioned_docs/version-2.5.1/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.5.2/schema-manage.md
b/versioned_docs/version-2.5.2/schema-manage.md
index 7a3e3d75366..028b94437e0 100644
--- a/versioned_docs/version-2.5.2/schema-manage.md
+++ b/versioned_docs/version-2.5.2/schema-manage.md
@@ -199,7 +199,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -252,7 +252,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -269,7 +269,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.6.0/schema-manage.md
b/versioned_docs/version-2.6.0/schema-manage.md
index 84d0ccdc231..805d1d4d49e 100644
--- a/versioned_docs/version-2.6.0/schema-manage.md
+++ b/versioned_docs/version-2.6.0/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.6.1/schema-manage.md
b/versioned_docs/version-2.6.1/schema-manage.md
index cf706961b39..043bfc121c4 100644
--- a/versioned_docs/version-2.6.1/schema-manage.md
+++ b/versioned_docs/version-2.6.1/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.6.2/schema-manage.md
b/versioned_docs/version-2.6.2/schema-manage.md
index 84d0ccdc231..805d1d4d49e 100644
--- a/versioned_docs/version-2.6.2/schema-manage.md
+++ b/versioned_docs/version-2.6.2/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.6.3/schema-manage.md
b/versioned_docs/version-2.6.3/schema-manage.md
index 84d0ccdc231..805d1d4d49e 100644
--- a/versioned_docs/version-2.6.3/schema-manage.md
+++ b/versioned_docs/version-2.6.3/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.6.4/schema-manage.md
b/versioned_docs/version-2.6.4/schema-manage.md
index 84d0ccdc231..805d1d4d49e 100644
--- a/versioned_docs/version-2.6.4/schema-manage.md
+++ b/versioned_docs/version-2.6.4/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.7.0/schema-manage.md
b/versioned_docs/version-2.7.0/schema-manage.md
index 84d0ccdc231..805d1d4d49e 100644
--- a/versioned_docs/version-2.7.0/schema-manage.md
+++ b/versioned_docs/version-2.7.0/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.7.1/schema-manage.md
b/versioned_docs/version-2.7.1/schema-manage.md
index c588aae619e..3429af8116f 100644
--- a/versioned_docs/version-2.7.1/schema-manage.md
+++ b/versioned_docs/version-2.7.1/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.7.2/schema-manage.md
b/versioned_docs/version-2.7.2/schema-manage.md
index 5984fdbeaaa..270d0a52b55 100644
--- a/versioned_docs/version-2.7.2/schema-manage.md
+++ b/versioned_docs/version-2.7.2/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.7.3/schema-manage.md
b/versioned_docs/version-2.7.3/schema-manage.md
index 5984fdbeaaa..270d0a52b55 100644
--- a/versioned_docs/version-2.7.3/schema-manage.md
+++ b/versioned_docs/version-2.7.3/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.7.4/schema-manage.md
b/versioned_docs/version-2.7.4/schema-manage.md
index 5984fdbeaaa..270d0a52b55 100644
--- a/versioned_docs/version-2.7.4/schema-manage.md
+++ b/versioned_docs/version-2.7.4/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.7.5/schema-manage.md
b/versioned_docs/version-2.7.5/schema-manage.md
index 5984fdbeaaa..270d0a52b55 100644
--- a/versioned_docs/version-2.7.5/schema-manage.md
+++ b/versioned_docs/version-2.7.5/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.8.x/schema-manage.md
b/versioned_docs/version-2.8.x/schema-manage.md
index c588aae619e..3429af8116f 100644
--- a/versioned_docs/version-2.8.x/schema-manage.md
+++ b/versioned_docs/version-2.8.x/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
diff --git a/versioned_docs/version-2.9.x/schema-manage.md
b/versioned_docs/version-2.9.x/schema-manage.md
index c588aae619e..3429af8116f 100644
--- a/versioned_docs/version-2.9.x/schema-manage.md
+++ b/versioned_docs/version-2.9.x/schema-manage.md
@@ -200,7 +200,7 @@ The `schema-definition-file` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here are examples of the `schema-definition-file` for a JSON schema.
@@ -253,7 +253,7 @@ The post payload includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
</TabItem>
@@ -270,7 +270,7 @@ The `PostSchemaPayload` includes the following fields:
| Field | Description |
| --- | --- |
| `type` | The schema type. |
-| `schema` | The schema definition data, which is encoded in UTF 8
charset. <li>If the schema is a </li>**primitive**<li>schema, this field should
be blank. </li><li>If the schema is a </li>**struct**<li>schema, this field
should be a JSON string of the Avro schema definition. </li> |
+| `schema` | The schema definition data, which is encoded in UTF 8 charset.
<li>If the schema is a **primitive** schema, this field should be blank.
</li><li>If the schema is a **struct** schema, this field should be a JSON
string of the Avro schema definition. </li> |
| `properties` | The additional properties associated with the schema. |
Here is an example of `PostSchemaPayload`:
