This is an automated email from the ASF dual-hosted git repository.
urfree 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 89634a4ff31 Docs sync done from apache/pulsar(#3e68fa4)
89634a4ff31 is described below
commit 89634a4ff315050902ae30cc92cf61db1432b51d
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Sat Jul 23 06:01:49 2022 +0000
Docs sync done from apache/pulsar(#3e68fa4)
---
site2/website-next/docs/administration-geo.md | 6 +++++-
site2/website-next/docs/functions-cli.md | 1 +
site2/website-next/docs/reference-configuration.md | 3 ++-
.../versioned_docs/version-2.10.0/administration-geo.md | 6 +++++-
.../versioned_docs/version-2.10.0/reference-configuration.md | 3 ++-
.../versioned_docs/version-2.10.1/reference-configuration.md | 3 ++-
6 files changed, 17 insertions(+), 5 deletions(-)
diff --git a/site2/website-next/docs/administration-geo.md
b/site2/website-next/docs/administration-geo.md
index 68ed9edab55..778b5f61137 100644
--- a/site2/website-next/docs/administration-geo.md
+++ b/site2/website-next/docs/administration-geo.md
@@ -143,7 +143,11 @@ $ bin/pulsar-admin topics set-replication-clusters
--clusters us-west,us-east,us
- You can change the replication clusters for a namespace at any time, without
disruption to ongoing traffic. Replication channels are immediately set up or
stopped in all clusters as soon as the configuration changes.
- Once you create a geo-replication namespace, any topics that producers or
consumers create within that namespace are replicated across clusters.
Typically, each application uses the `serviceUrl` for the local cluster.
-
+- If you are using Pulsar version `2.10.x`, to enable geo-replication at topic
level, you need to change the following configurations in the
`conf/broker.conf` or `conf/standalone.conf` file to enable topic policies
service.
+```shell
+systemTopicEnabled=true
+topicLevelPoliciesEnabled=true
+```
:::
### Use topics with geo-replication
diff --git a/site2/website-next/docs/functions-cli.md
b/site2/website-next/docs/functions-cli.md
index f36e47f33de..316266ab069 100644
--- a/site2/website-next/docs/functions-cli.md
+++ b/site2/website-next/docs/functions-cli.md
@@ -26,6 +26,7 @@ You can configure a function by using a predefined YAML file.
The following tabl
| namespace | String | `--namespace`
| The namespace of a function.|
| name | String | `--name`
| The name of a function.|
| className | String | `--classname`
| The class name of a function. |
+| functionType | String | `--function-type`
| The built-in function type. |
| inputs | List`<String>` | `-i`, `--inputs`
| The input topics of a function. Multiple topics can be specified as a
comma-separated list. |
| customSerdeInputs | Map`<String,String>` |
`--custom-serde-inputs` | The mapping from input topics to SerDe class
names. |
| topicsPattern | String | `--topics-pattern`
| The topic pattern to consume from a list of topics under a namespace. <br
/>**Note:** `--input` and `--topic-pattern` are mutually exclusive. For Java
functions, you need to add the SerDe class name for a pattern in
`--custom-serde-inputs`. |
diff --git a/site2/website-next/docs/reference-configuration.md
b/site2/website-next/docs/reference-configuration.md
index ac9c7530968..e42ace8acf2 100644
--- a/site2/website-next/docs/reference-configuration.md
+++ b/site2/website-next/docs/reference-configuration.md
@@ -142,6 +142,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|statsUpdateFrequencyInSecs||60|
|statsUpdateInitialDelayInSecs||60|
|metadataStoreUrl| Metadata store quorum connection string ||
+| metadataStoreConfigPath | The configuration file path of the local metadata
store. See [Configure metadata store](administration-metadata-store.md) for
details. |N/A|
|metadataStoreCacheExpirySeconds|Metadata store cache expiry time in
seconds|300|
|configurationMetadataStoreUrl| Configuration store connection string (as a
comma-separated list) ||
|brokerServicePort| Broker data port |6650|
@@ -737,7 +738,7 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
|haProxyProtocolEnabled | Enable or disable the
[HAProxy](http://www.haproxy.org/) protocol. |false|
|bookieId | If you want to custom a bookie ID or use a dynamic network address
for a bookie, you can set the `bookieId`. <br /><br />Bookie advertises itself
using the `bookieId` rather than the `BookieSocketAddress` (`hostname:port` or
`IP:port`).<br /><br /> The `bookieId` is a non-empty string that can contain
ASCII digits and letters ([a-zA-Z9-0]), colons, dashes, and dots. <br /><br
/>For more information about `bookieId`, see
[here](http://bookkeeper.apache.org/bps/BP-41-bookieid/).|/|
| maxTopicsPerNamespace | The maximum number of persistent topics that can be
created in the namespace. When the number of topics reaches this threshold, the
broker rejects the request of creating a new topic, including the auto-created
topics by the producer or consumer, until the number of connected consumers
decreases. The default value 0 disables the check. | 0 |
-| metadataStoreConfigPath | The configuration file path of the local metadata
store. Standalone Pulsar uses [RocksDB](http://rocksdb.org/) as the local
metadata store. The format is `/xxx/xx/rocksdb.ini`. |N/A|
+| metadataStoreConfigPath | The configuration file path of the local metadata
store. See [Configure metadata store](administration-metadata-store.md) for
details. |N/A|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced| Whether to enable schema validation, when schema
validation is enabled, if a producer without a schema attempts to produce the
message to a topic with schema, the producer is rejected and
disconnected.|false|
|isAllowAutoUpdateSchemaEnabled|Allow schema to be auto updated at broker
level.|true|
diff --git
a/site2/website-next/versioned_docs/version-2.10.0/administration-geo.md
b/site2/website-next/versioned_docs/version-2.10.0/administration-geo.md
index 4f5b5565eca..2d64f0b643f 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/administration-geo.md
+++ b/site2/website-next/versioned_docs/version-2.10.0/administration-geo.md
@@ -144,7 +144,11 @@ $ bin/pulsar-admin topics set-replication-clusters
--clusters us-west,us-east,us
- You can change the replication clusters for a namespace at any time, without
disruption to ongoing traffic. Replication channels are immediately set up or
stopped in all clusters as soon as the configuration changes.
- Once you create a geo-replication namespace, any topics that producers or
consumers create within that namespace are replicated across clusters.
Typically, each application uses the `serviceUrl` for the local cluster.
-
+- If you are using Pulsar version `2.10.x`, to enable geo-replication at topic
level, you need to change the following configurations in the
`conf/broker.conf` or `conf/standalone.conf` file to enable topic policies
service.
+```shell
+systemTopicEnabled=true
+topicLevelPoliciesEnabled=true
+```
:::
### Use topics with geo-replication
diff --git
a/site2/website-next/versioned_docs/version-2.10.0/reference-configuration.md
b/site2/website-next/versioned_docs/version-2.10.0/reference-configuration.md
index 14d07285292..fced1f9e937 100644
---
a/site2/website-next/versioned_docs/version-2.10.0/reference-configuration.md
+++
b/site2/website-next/versioned_docs/version-2.10.0/reference-configuration.md
@@ -143,6 +143,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|statsUpdateFrequencyInSecs||60|
|statsUpdateInitialDelayInSecs||60|
|metadataStoreUrl| Metadata store quorum connection string ||
+| metadataStoreConfigPath | The configuration file path of the local metadata
store. See [Configure metadata store](administration-metadata-store.md) for
details. |N/A|
|metadataStoreCacheExpirySeconds|Metadata store cache expiry time in
seconds|300|
|configurationMetadataStoreUrl| Configuration store connection string (as a
comma-separated list) ||
|brokerServicePort| Broker data port |6650|
@@ -702,7 +703,7 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
|haProxyProtocolEnabled | Enable or disable the
[HAProxy](http://www.haproxy.org/) protocol. |false|
|bookieId | If you want to custom a bookie ID or use a dynamic network address
for a bookie, you can set the `bookieId`. <br /><br />Bookie advertises itself
using the `bookieId` rather than the `BookieSocketAddress` (`hostname:port` or
`IP:port`).<br /><br /> The `bookieId` is a non-empty string that can contain
ASCII digits and letters ([a-zA-Z9-0]), colons, dashes, and dots. <br /><br
/>For more information about `bookieId`, see
[here](http://bookkeeper.apache.org/bps/BP-41-bookieid/).|/|
| maxTopicsPerNamespace | The maximum number of persistent topics that can be
created in the namespace. When the number of topics reaches this threshold, the
broker rejects the request of creating a new topic, including the auto-created
topics by the producer or consumer, until the number of connected consumers
decreases. The default value 0 disables the check. | 0 |
-| metadataStoreConfigPath | The configuration file path of the local metadata
store. Standalone Pulsar uses [RocksDB](http://rocksdb.org/) as the local
metadata store. The format is `/xxx/xx/rocksdb.ini`. |N/A|
+| metadataStoreConfigPath | The configuration file path of the local metadata
store. See [Configure metadata store](administration-metadata-store.md) for
details. |N/A|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced| Whether to enable schema validation, when schema
validation is enabled, if a producer without a schema attempts to produce the
message to a topic with schema, the producer is rejected and
disconnected.|false|
|isAllowAutoUpdateSchemaEnabled|Allow schema to be auto updated at broker
level.|true|
diff --git
a/site2/website-next/versioned_docs/version-2.10.1/reference-configuration.md
b/site2/website-next/versioned_docs/version-2.10.1/reference-configuration.md
index b261317782b..7d8eea35b80 100644
---
a/site2/website-next/versioned_docs/version-2.10.1/reference-configuration.md
+++
b/site2/website-next/versioned_docs/version-2.10.1/reference-configuration.md
@@ -143,6 +143,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|statsUpdateFrequencyInSecs||60|
|statsUpdateInitialDelayInSecs||60|
|metadataStoreUrl| Metadata store quorum connection string ||
+| metadataStoreConfigPath | The configuration file path of the local metadata
store. See [Configure metadata store](administration-metadata-store.md) for
details. |N/A|
|metadataStoreCacheExpirySeconds|Metadata store cache expiry time in
seconds|300|
|configurationMetadataStoreUrl| Configuration store connection string (as a
comma-separated list) ||
|brokerServicePort| Broker data port |6650|
@@ -716,7 +717,7 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
|haProxyProtocolEnabled | Enable or disable the
[HAProxy](http://www.haproxy.org/) protocol. |false|
|bookieId | If you want to custom a bookie ID or use a dynamic network address
for a bookie, you can set the `bookieId`. <br /><br />Bookie advertises itself
using the `bookieId` rather than the `BookieSocketAddress` (`hostname:port` or
`IP:port`).<br /><br /> The `bookieId` is a non-empty string that can contain
ASCII digits and letters ([a-zA-Z9-0]), colons, dashes, and dots. <br /><br
/>For more information about `bookieId`, see
[here](http://bookkeeper.apache.org/bps/BP-41-bookieid/).|/|
| maxTopicsPerNamespace | The maximum number of persistent topics that can be
created in the namespace. When the number of topics reaches this threshold, the
broker rejects the request of creating a new topic, including the auto-created
topics by the producer or consumer, until the number of connected consumers
decreases. The default value 0 disables the check. | 0 |
-| metadataStoreConfigPath | The configuration file path of the local metadata
store. Standalone Pulsar uses [RocksDB](http://rocksdb.org/) as the local
metadata store. The format is `/xxx/xx/rocksdb.ini`. |N/A|
+| metadataStoreConfigPath | The configuration file path of the local metadata
store. See [Configure metadata store](administration-metadata-store.md) for
details. |N/A|
|schemaRegistryStorageClassName|The schema storage implementation used by this
broker.|org.apache.pulsar.broker.service.schema.BookkeeperSchemaStorageFactory|
|isSchemaValidationEnforced| Whether to enable schema validation, when schema
validation is enabled, if a producer without a schema attempts to produce the
message to a topic with schema, the producer is rejected and
disconnected.|false|
|isAllowAutoUpdateSchemaEnabled|Allow schema to be auto updated at broker
level.|true|
