You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/05/30 12:07:03 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#29308e4)
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 f9b9eac4cdd Docs sync done from apache/pulsar(#29308e4)
f9b9eac4cdd is described below
commit f9b9eac4cdd3102319592ca8663e585876509650
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Mon May 30 12:06:59 2022 +0000
Docs sync done from apache/pulsar(#29308e4)
---
site2/website-next/docs/adaptors-kafka.md | 56 ++++++-------
site2/website-next/docs/admin-api-brokers.md | 10 +--
site2/website-next/docs/admin-api-clusters.md | 18 ++--
site2/website-next/docs/admin-api-functions.md | 42 +++++-----
site2/website-next/docs/admin-api-namespaces.md | 16 ++--
site2/website-next/docs/admin-api-overview.md | 8 +-
site2/website-next/docs/admin-api-packages.md | 4 +-
site2/website-next/docs/admin-api-permissions.md | 10 +--
site2/website-next/docs/admin-api-tenants.md | 14 ++--
site2/website-next/docs/admin-api-topics.md | 18 ++--
site2/website-next/docs/administration-geo.md | 8 +-
.../website-next/docs/administration-isolation.md | 10 +--
.../docs/administration-pulsar-manager.md | 4 +-
site2/website-next/docs/administration-zk-bk.md | 4 +-
site2/website-next/docs/client-libraries-java.md | 6 +-
site2/website-next/docs/client-libraries-node.md | 2 +-
site2/website-next/docs/client-libraries-python.md | 2 +-
.../docs/client-libraries-websocket.md | 14 ++--
site2/website-next/docs/client-libraries.md | 10 +--
site2/website-next/docs/concepts-messaging.md | 4 +-
site2/website-next/docs/concepts-multi-tenancy.md | 2 +-
site2/website-next/docs/concepts-tiered-storage.md | 2 +-
site2/website-next/docs/cookbooks-compaction.md | 2 +-
site2/website-next/docs/cookbooks-deduplication.md | 4 +-
.../website-next/docs/cookbooks-non-persistent.md | 2 +-
.../docs/cookbooks-retention-expiry.md | 18 ++--
.../docs/deploy-bare-metal-multi-cluster.md | 4 +-
site2/website-next/docs/deploy-bare-metal.md | 6 +-
site2/website-next/docs/deploy-monitoring.md | 4 +-
site2/website-next/docs/functions-debug.md | 4 +-
site2/website-next/docs/functions-deploy.md | 18 ++--
site2/website-next/docs/functions-develop.md | 2 +-
site2/website-next/docs/functions-overview.md | 4 +-
site2/website-next/docs/functions-package.md | 2 +-
site2/website-next/docs/functions-worker.md | 2 +-
site2/website-next/docs/getting-started-helm.md | 2 +-
site2/website-next/docs/getting-started-pulsar.md | 2 +-
.../docs/getting-started-standalone.md | 6 +-
site2/website-next/docs/io-cli.md | 2 +-
site2/website-next/docs/io-debug.md | 2 +-
site2/website-next/docs/io-kafka-source.md | 4 +-
site2/website-next/docs/io-overview.md | 2 +-
site2/website-next/docs/io-quickstart.md | 36 ++++----
site2/website-next/docs/io-use.md | 96 +++++++++++-----------
site2/website-next/docs/kubernetes-helm.md | 2 +-
site2/website-next/docs/performance-pulsar-perf.md | 4 +-
site2/website-next/docs/reference-cli-tools.md | 2 +-
site2/website-next/docs/reference-configuration.md | 2 +-
.../website-next/docs/reference-connector-admin.md | 2 +-
site2/website-next/docs/reference-pulsar-admin.md | 2 +-
.../docs/reference-rest-api-overview.md | 10 +--
site2/website-next/docs/schema-manage.md | 14 ++--
site2/website-next/docs/security-athenz.md | 2 +-
site2/website-next/docs/security-authorization.md | 2 +-
site2/website-next/docs/security-extending.md | 4 +-
site2/website-next/docs/security-jwt.md | 2 +-
.../docs/security-tls-authentication.md | 4 +-
site2/website-next/docs/standalone.md | 6 +-
site2/website-next/docs/tiered-storage-aliyun.md | 12 +--
site2/website-next/docs/tiered-storage-aws.md | 10 +--
site2/website-next/docs/tiered-storage-azure.md | 10 +--
.../website-next/docs/tiered-storage-filesystem.md | 8 +-
site2/website-next/docs/tiered-storage-gcs.md | 10 +--
site2/website-next/docs/txn-monitor.md | 4 +-
site2/website-next/docs/txn-use.md | 2 +-
site2/website-next/docs/txn-what.md | 2 +-
site2/website-next/docs/txn-why.md | 2 +-
67 files changed, 303 insertions(+), 303 deletions(-)
diff --git a/site2/website-next/docs/adaptors-kafka.md b/site2/website-next/docs/adaptors-kafka.md
index 27382e96194..c51fe8b7ca8 100644
--- a/site2/website-next/docs/adaptors-kafka.md
+++ b/site2/website-next/docs/adaptors-kafka.md
@@ -233,43 +233,43 @@ You can configure Pulsar authentication provider directly from the Kafka propert
| Config property | Default | Notes |
|:---------------------------------------|:--------|:---------------------------------------------------------------------------------------|
-| [`pulsar.authentication.class`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setAuthentication-org.apache.pulsar.client.api.Authentication-) | | Configure to auth provider. For example, `org.apache.pulsar.client.impl.auth.AuthenticationTls`.|
-| [`pulsar.authentication.params.map`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setAuthentication-java.lang.String-java.util.Map-) | | Map which represents parameters for the Authentication-Plugin. |
-| [`pulsar.authentication.params.string`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setAuthentication-java.lang.String-java.lang.String-) | | String which represents parameters for the Authentication-Plugin, for example, `key1:val1,key2:val2`. |
-| [`pulsar.use.tls`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setUseTls-boolean-) | `false` | Enable TLS transport encryption. |
-| [`pulsar.tls.trust.certs.file.path`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setTlsTrustCertsFilePath-java.lang.String-) | | Path for the TLS trust certificate store. |
-| [`pulsar.tls.allow.insecure.connection`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setTlsAllowInsecureConnection-boolean-) | `false` | Accept self-signed certificates from brokers. |
-| [`pulsar.operation.timeout.ms`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setOperationTimeout-int-java.util.concurrent.TimeUnit-) | `30000` | General operations timeout. |
-| [`pulsar.stats.interval.seconds`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setStatsInterval-long-java.util.concurrent.TimeUnit-) | `60` | Pulsar client lib stats printing interval. |
-| [`pulsar.num.io.threads`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setIoThreads-int-) | `1` | The number of Netty IO threads to use. |
-| [`pulsar.connections.per.broker`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setConnectionsPerBroker-int-) | `1` | The maximum number of connection to each broker. |
-| [`pulsar.use.tcp.nodelay`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setUseTcpNoDelay-boolean-) | `true` | TCP no-delay. |
-| [`pulsar.concurrent.lookup.requests`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setConcurrentLookupRequest-int-) | `50000` | The maximum number of concurrent topic lookups. |
-| [`pulsar.max.number.rejected.request.per.connection`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setMaxNumberOfRejectedRequestPerConnection-int-) | `50` | The threshold of errors to forcefully close a connection. |
-| [`pulsar.keepalive.interval.ms`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ClientBuilder.html#keepAliveInterval-int-java.util.concurrent.TimeUnit-)| `30000` | Keep alive interval for each client-broker-connection. |
+| [`pulsar.authentication.class`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setAuthentication-org.apache.pulsar.client.api.Authentication-) | | Configure to auth provider. For example, `org.apache.pulsar.client.impl.auth.AuthenticationTls`.|
+| [`pulsar.authentication.params.map`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setAuthentication-java.lang.String-java.util.Map-) | | Map which represents parameters for the Authentication-Plugin. |
+| [`pulsar.authentication.params.string`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setAuthentication-java.lang.String-java.lang.String-) | | String which represents parameters for the Authentication-Plugin, for example, `key1:val1,key2:val2`. |
+| [`pulsar.use.tls`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setUseTls-boolean-) | `false` | Enable TLS transport encryption. |
+| [`pulsar.tls.trust.certs.file.path`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setTlsTrustCertsFilePath-java.lang.String-) | | Path for the TLS trust certificate store. |
+| [`pulsar.tls.allow.insecure.connection`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setTlsAllowInsecureConnection-boolean-) | `false` | Accept self-signed certificates from brokers. |
+| [`pulsar.operation.timeout.ms`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setOperationTimeout-int-java.util.concurrent.TimeUnit-) | `30000` | General operations timeout. |
+| [`pulsar.stats.interval.seconds`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setStatsInterval-long-java.util.concurrent.TimeUnit-) | `60` | Pulsar client lib stats printing interval. |
+| [`pulsar.num.io.threads`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setIoThreads-int-) | `1` | The number of Netty IO threads to use. |
+| [`pulsar.connections.per.broker`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setConnectionsPerBroker-int-) | `1` | The maximum number of connection to each broker. |
+| [`pulsar.use.tcp.nodelay`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setUseTcpNoDelay-boolean-) | `true` | TCP no-delay. |
+| [`pulsar.concurrent.lookup.requests`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setConcurrentLookupRequest-int-) | `50000` | The maximum number of concurrent topic lookups. |
+| [`pulsar.max.number.rejected.request.per.connection`](/api/client/org/apache/pulsar/client/api/ClientConfiguration.html#setMaxNumberOfRejectedRequestPerConnection-int-) | `50` | The threshold of errors to forcefully close a connection. |
+| [`pulsar.keepalive.interval.ms`](/api/client/org/apache/pulsar/client/api/ClientBuilder.html#keepAliveInterval-int-java.util.concurrent.TimeUnit-)| `30000` | Keep alive interval for each client-broker-connection. |
### Pulsar producer properties
| Config property | Default | Notes |
|:---------------------------------------|:--------|:---------------------------------------------------------------------------------------|
-| [`pulsar.producer.name`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setProducerName-java.lang.String-) | | Specify the producer name. |
-| [`pulsar.producer.initial.sequence.id`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setInitialSequenceId-long-) | | Specify baseline for sequence ID of this producer. |
-| [`pulsar.producer.max.pending.messages`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setMaxPendingMessages-int-) | `1000` | Set the maximum size of the message queue pending to receive an acknowledgment from the broker. |
-| [`pulsar.producer.max.pending.messages.across.partitions`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setMaxPendingMessagesAcrossPartitions-int-) | `50000` | Set the maximum number of pending messages across all the partitions. |
-| [`pulsar.producer.batching.enabled`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setBatchingEnabled-boolean-) | `true` | Control whether automatic batching of messages is enabled for the producer. |
-| [`pulsar.producer.batching.max.messages`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setBatchingMaxMessages-int-) | `1000` | The maximum number of messages in a batch. |
-| [`pulsar.block.if.producer.queue.full`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setBlockIfQueueFull-boolean-) | | Specify the block producer if queue is full. |
-| [`pulsar.crypto.reader.factory.class.name`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setCryptoKeyReader-org.apache.pulsar.client.api.CryptoKeyReader-) | | Specify the CryptoReader-Factory(`CryptoKeyReaderFactory`) classname which allows producer to create CryptoKeyReader. |
+| [`pulsar.producer.name`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setProducerName-java.lang.String-) | | Specify the producer name. |
+| [`pulsar.producer.initial.sequence.id`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setInitialSequenceId-long-) | | Specify baseline for sequence ID of this producer. |
+| [`pulsar.producer.max.pending.messages`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setMaxPendingMessages-int-) | `1000` | Set the maximum size of the message queue pending to receive an acknowledgment from the broker. |
+| [`pulsar.producer.max.pending.messages.across.partitions`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setMaxPendingMessagesAcrossPartitions-int-) | `50000` | Set the maximum number of pending messages across all the partitions. |
+| [`pulsar.producer.batching.enabled`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setBatchingEnabled-boolean-) | `true` | Control whether automatic batching of messages is enabled for the producer. |
+| [`pulsar.producer.batching.max.messages`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setBatchingMaxMessages-int-) | `1000` | The maximum number of messages in a batch. |
+| [`pulsar.block.if.producer.queue.full`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setBlockIfQueueFull-boolean-) | | Specify the block producer if queue is full. |
+| [`pulsar.crypto.reader.factory.class.name`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setCryptoKeyReader-org.apache.pulsar.client.api.CryptoKeyReader-) | | Specify the CryptoReader-Factory(`CryptoKeyReaderFactory`) classname which allows producer to create CryptoKeyReader. |
### Pulsar consumer Properties
| Config property | Default | Notes |
|:---------------------------------------|:--------|:---------------------------------------------------------------------------------------|
-| [`pulsar.consumer.name`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setConsumerName-java.lang.String-) | | Specify the consumer name. |
-| [`pulsar.consumer.receiver.queue.size`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setReceiverQueueSize-int-) | 1000 | Set the size of the consumer receiver queue. |
-| [`pulsar.consumer.acknowledgments.group.time.millis`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#acknowledgmentGroupTime-long-java.util.concurrent.TimeUnit-) | 100 | Set the maximum amount of group time for consumers to send the acknowledgments to the broker. |
-| [`pulsar.consumer.total.receiver.queue.size.across.partitions`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setMaxTotalReceiverQueueSizeAcrossPartitions-int-) | 50000 | Set the maximum size of the total receiver queue across partitions. |
-| [`pulsar.consumer.subscription.topics.mode`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#subscriptionTopicsMode-Mode-) | PersistentOnly | Set the subscription topic mode for consumers. |
-| [`pulsar.crypto.reader.factory.class.name`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setCryptoKeyReader-org.apache.pulsar.client.api.CryptoKeyReader-) | | Specify the CryptoReader-Factory(`CryptoKeyReaderFactory`) classname which allows consumer to create CryptoKeyReader. |
+| [`pulsar.consumer.name`](/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setConsumerName-java.lang.String-) | | Specify the consumer name. |
+| [`pulsar.consumer.receiver.queue.size`](/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setReceiverQueueSize-int-) | 1000 | Set the size of the consumer receiver queue. |
+| [`pulsar.consumer.acknowledgments.group.time.millis`](/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#acknowledgmentGroupTime-long-java.util.concurrent.TimeUnit-) | 100 | Set the maximum amount of group time for consumers to send the acknowledgments to the broker. |
+| [`pulsar.consumer.total.receiver.queue.size.across.partitions`](/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setMaxTotalReceiverQueueSizeAcrossPartitions-int-) | 50000 | Set the maximum size of the total receiver queue across partitions. |
+| [`pulsar.consumer.subscription.topics.mode`](/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#subscriptionTopicsMode-Mode-) | PersistentOnly | Set the subscription topic mode for consumers. |
+| [`pulsar.crypto.reader.factory.class.name`](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html#setCryptoKeyReader-org.apache.pulsar.client.api.CryptoKeyReader-) | | Specify the CryptoReader-Factory(`CryptoKeyReaderFactory`) classname which allows consumer to create CryptoKeyReader. |
diff --git a/site2/website-next/docs/admin-api-brokers.md b/site2/website-next/docs/admin-api-brokers.md
index accaac4f2e7..adaeb73cece 100644
--- a/site2/website-next/docs/admin-api-brokers.md
+++ b/site2/website-next/docs/admin-api-brokers.md
@@ -14,11 +14,11 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](/tools/pulsar-admin/).
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
Pulsar brokers consist of two components:
@@ -27,7 +27,7 @@ Pulsar brokers consist of two components:
[Brokers](reference-terminology.md#broker) can be managed via:
-* The `brokers` command of the [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/) tool
+* The `brokers` command of the [`pulsar-admin`](/tools/pulsar-admin/) tool
* The `/admin/v2/brokers` endpoint of the admin {@inject: rest:REST:/} API
* The `brokers` method of the `PulsarAdmin` object in the [Java API](client-libraries-java)
@@ -175,7 +175,7 @@ One way to configure a Pulsar [broker](reference-terminology.md#broker) is to su
But since all broker configuration in Pulsar is stored in ZooKeeper, configuration values can also be dynamically updated *while the broker is running*. When you update broker configuration dynamically, ZooKeeper will notify the broker of the change and the broker will then override any existing configuration values.
-* The `brokers` command for the [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/) tool has a variety of subcommands that enable you to manipulate a broker's configuration dynamically, enabling you to [update config values](#update-dynamic-configuration) and more.
+* The `brokers` command for the [`pulsar-admin`](/tools/pulsar-admin/) tool has a variety of subcommands that enable you to manipulate a broker's configuration dynamically, enabling you to [update config values](#update-dynamic-configuration) and more.
* In the Pulsar admin {@inject: rest:REST:/} API, dynamic configuration is managed through the `/admin/v2/brokers/configuration` endpoint.
### Update dynamic configuration
@@ -186,7 +186,7 @@ But since all broker configuration in Pulsar is stored in ZooKeeper, configurati
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-The [`update-dynamic-config`](https://pulsar.apache.org/tools/pulsar-admin/) subcommand will update existing configuration. It takes two arguments: the name of the parameter and the new value using the `config` and `value` flag respectively. Here's an example for the [`brokerShutdownTimeoutMs`](reference-configuration.md#broker-brokerShutdownTimeoutMs) parameter:
+The [`update-dynamic-config`](/tools/pulsar-admin/) subcommand will update existing configuration. It takes two arguments: the name of the parameter and the new value using the `config` and `value` flag respectively. Here's an example for the [`brokerShutdownTimeoutMs`](reference-configuration.md#broker-brokerShutdownTimeoutMs) parameter:
```shell
diff --git a/site2/website-next/docs/admin-api-clusters.md b/site2/website-next/docs/admin-api-clusters.md
index 418626f3091..64875cde8b5 100644
--- a/site2/website-next/docs/admin-api-clusters.md
+++ b/site2/website-next/docs/admin-api-clusters.md
@@ -14,18 +14,18 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/)
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](/tools/pulsar-admin/)
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
Pulsar clusters consist of one or more Pulsar [brokers](reference-terminology.md#broker), one or more [BookKeeper](reference-terminology.md#bookkeeper)
servers (aka [bookies](reference-terminology.md#bookie)), and a [ZooKeeper](https://zookeeper.apache.org) cluster that provides configuration and coordination management.
Clusters can be managed via:
-* The `clusters` command of the [`pulsar-admin`]([reference-pulsar-admin.md](https://pulsar.apache.org/tools/pulsar-admin/)) tool
+* The `clusters` command of the [`pulsar-admin`](/tools/pulsar-admin/) tool
* The `/admin/v2/clusters` endpoint of the admin {@inject: rest:REST:/} API
* The `clusters` method of the `PulsarAdmin` object in the [Java API](client-libraries-java)
@@ -43,7 +43,7 @@ New clusters can be provisioned using the admin interface.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-You can provision a new cluster using the [`create`](reference-pulsar-admin.md#clusters-create) subcommand. Here's an example:
+You can provision a new cluster using the [`create`](/tools/pulsar-admin/) subcommand. Here's an example:
```shell
@@ -124,7 +124,7 @@ You can fetch the [configuration](reference-configuration) for an existing clust
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`get`](reference-pulsar-admin.md#clusters-get) subcommand and specify the name of the cluster. Here's an example:
+Use the [`get`](/tools/pulsar-admin/) subcommand and specify the name of the cluster. Here's an example:
```shell
@@ -168,7 +168,7 @@ You can update the configuration for an existing cluster at any time.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`update`](reference-pulsar-admin.md#clusters-update) subcommand and specify new configuration values using flags.
+Use the [`update`](/tools/pulsar-admin/) subcommand and specify new configuration values using flags.
```shell
@@ -213,7 +213,7 @@ Clusters can be deleted from a Pulsar [instance](reference-terminology.md#instan
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`delete`](reference-pulsar-admin.md#clusters-delete) subcommand and specify the name of the cluster.
+Use the [`delete`](/tools/pulsar-admin/) subcommand and specify the name of the cluster.
```
@@ -250,7 +250,7 @@ You can fetch a list of all clusters in a Pulsar [instance](reference-terminolog
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`list`](reference-pulsar-admin.md#clusters-list) subcommand.
+Use the [`list`](/tools/pulsar-admin/) subcommand.
```shell
@@ -289,7 +289,7 @@ Peer clusters can be configured for a given cluster in a Pulsar [instance](refer
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`update-peer-clusters`](reference-pulsar-admin.md#clusters-update-peer-clusters) subcommand and specify the list of peer-cluster names.
+Use the [`update-peer-clusters`](/tools/pulsar-admin/) subcommand and specify the list of peer-cluster names.
```
diff --git a/site2/website-next/docs/admin-api-functions.md b/site2/website-next/docs/admin-api-functions.md
index 4173217a53f..f2f2cd8471a 100644
--- a/site2/website-next/docs/admin-api-functions.md
+++ b/site2/website-next/docs/admin-api-functions.md
@@ -14,11 +14,11 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/)
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](/tools/pulsar-admin/)
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
**Pulsar Functions** are lightweight compute processes that
@@ -30,7 +30,7 @@ Functions can be managed via the following methods.
Method | Description
---|---
-**Admin CLI** | The `functions` command of the [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/) tool.
+**Admin CLI** | The `functions` command of the [`pulsar-admin`](/tools/pulsar-admin/) tool.
**REST API** |The `/admin/v3/functions` endpoint of the admin {@inject: rest:REST:/} API.
**Java Admin API**| The `functions` method of the `PulsarAdmin` object in the [Java API](client-libraries-java).
@@ -48,7 +48,7 @@ You can create a Pulsar function in cluster mode (deploy it on a Pulsar cluster)
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`create`](reference-pulsar-admin.md#functions-create) subcommand.
+Use the [`create`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -106,7 +106,7 @@ You can update a Pulsar function that has been deployed to a Pulsar cluster usin
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST Admin API","value":"REST Admin API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`update`](reference-pulsar-admin.md#functions-update) subcommand.
+Use the [`update`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -159,7 +159,7 @@ You can start a stopped function instance with `instance-id` using Admin CLI, RE
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`start`](reference-pulsar-admin.md#functions-start) subcommand.
+Use the [`start`](/tools/pulsar-admin/) subcommand.
```shell
@@ -200,7 +200,7 @@ You can start all stopped function instances using Admin CLI, REST API or Java A
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="Admin CLI">
-Use the [`start`](reference-pulsar-admin.md#functions-start) subcommand.
+Use the [`start`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -242,7 +242,7 @@ You can stop a function instance with `instance-id` using Admin CLI, REST API or
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`stop`](reference-pulsar-admin.md#functions-stop) subcommand.
+Use the [`stop`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -285,7 +285,7 @@ You can stop all function instances using Admin CLI, REST API or Java Admin API.
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`stop`](reference-pulsar-admin.md#functions-stop) subcommand.
+Use the [`stop`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -327,7 +327,7 @@ Restart a function instance with `instance-id` using Admin CLI, REST API or Java
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`restart`](reference-pulsar-admin.md#functions-restart) subcommand.
+Use the [`restart`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -370,7 +370,7 @@ You can restart all function instances using Admin CLI, REST API or Java admin A
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`restart`](reference-pulsar-admin.md#functions-restart) subcommand.
+Use the [`restart`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -412,7 +412,7 @@ You can list all Pulsar functions running under a specific tenant and namespace
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`list`](reference-pulsar-admin.md#functions-list) subcommand.
+Use the [`list`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -453,7 +453,7 @@ You can delete a Pulsar function that is running on a Pulsar cluster using Admin
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`delete`](reference-pulsar-admin.md#functions-delete) subcommand.
+Use the [`delete`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -495,7 +495,7 @@ You can get information about a Pulsar function currently running in cluster mod
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`get`](reference-pulsar-admin.md#functions-get) subcommand.
+Use the [`get`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -536,7 +536,7 @@ You can get the current status of a Pulsar function instance with `instance-id`
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`status`](reference-pulsar-admin.md#functions-status) subcommand.
+Use the [`status`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -579,7 +579,7 @@ You can get the current status of a Pulsar function instance using Admin CLI, RE
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`status`](reference-pulsar-admin.md#functions-status) subcommand.
+Use the [`status`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -620,7 +620,7 @@ You can get the current stats of a Pulsar Function instance with `instance-id` u
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`stats`](reference-pulsar-admin.md#functions-stats) subcommand.
+Use the [`stats`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -663,7 +663,7 @@ You can get the current stats of a Pulsar function using Admin CLI, REST API or
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`stats`](reference-pulsar-admin.md#functions-stats) subcommand.
+Use the [`stats`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -705,7 +705,7 @@ You can trigger a specified Pulsar function with a supplied value using Admin CL
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`trigger`](reference-pulsar-admin.md#functions-trigger) subcommand.
+Use the [`trigger`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -750,7 +750,7 @@ You can put the state associated with a Pulsar function using Admin CLI, REST AP
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin API","value":"Java Admin API"}]}>
<TabItem value="Admin CLI">
-Use the [`putstate`](reference-pulsar-admin.md#functions-putstate) subcommand.
+Use the [`putstate`](/tools/pulsar-admin/) subcommand.
**Example**
@@ -795,7 +795,7 @@ You can fetch the current state associated with a Pulsar function using Admin CL
values={[{"label":"Admin CLI","value":"Admin CLI"},{"label":"REST API","value":"REST API"},{"label":"Java Admin CLI","value":"Java Admin CLI"}]}>
<TabItem value="Admin CLI">
-Use the [`querystate`](reference-pulsar-admin.md#functions-querystate) subcommand.
+Use the [`querystate`](/tools/pulsar-admin/) subcommand.
**Example**
diff --git a/site2/website-next/docs/admin-api-namespaces.md b/site2/website-next/docs/admin-api-namespaces.md
index 89b83713a99..55ddc6696b5 100644
--- a/site2/website-next/docs/admin-api-namespaces.md
+++ b/site2/website-next/docs/admin-api-namespaces.md
@@ -14,17 +14,17 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](/tools/pulsar-admin/).
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
Pulsar [namespaces](reference-terminology.md#namespace) are logical groupings of [topics](reference-terminology.md#topic).
Namespaces can be managed via:
-* The `namespaces` command of the [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/) tool
+* The `namespaces` command of the [`pulsar-admin`](/tools/pulsar-admin/) tool
* The `/admin/v2/namespaces` endpoint of the admin {@inject: rest:REST:/} API
* The `namespaces` method of the `PulsarAdmin` object in the [Java API](client-libraries-java)
@@ -40,7 +40,7 @@ You can create new namespaces under a given [tenant](reference-terminology.md#te
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`create`](reference-pulsar-admin.md#namespaces-create) subcommand and specify the namespace by name:
+Use the [`create`](/tools/pulsar-admin/) subcommand and specify the namespace by name:
```shell
@@ -81,7 +81,7 @@ You can fetch the current policies associated with a namespace at any time.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`policies`](reference-pulsar-admin.md#namespaces-policies) subcommand and specify the namespace:
+Use the [`policies`](/tools/pulsar-admin/) subcommand and specify the namespace:
```shell
@@ -143,7 +143,7 @@ You can list all namespaces within a given Pulsar [tenant](reference-terminology
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`list`](reference-pulsar-admin.md#namespaces-list) subcommand and specify the tenant:
+Use the [`list`](/tools/pulsar-admin/) subcommand and specify the tenant:
```shell
@@ -186,7 +186,7 @@ You can delete existing namespaces from a tenant.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`delete`](reference-pulsar-admin.md#namespaces-delete) subcommand and specify the namespace:
+Use the [`delete`](/tools/pulsar-admin/) subcommand and specify the namespace:
```shell
@@ -1362,7 +1362,7 @@ You can unload a namespace, or a [namespace bundle](reference-terminology.md#nam
#### pulsar-admin
-Use the [`unload`](reference-pulsar-admin.md#unload) subcommand of the [`namespaces`](reference-pulsar-admin.md#namespaces) command.
+Use the [`unload`](/tools/pulsar-admin/) subcommand of the [`namespaces`](/tools/pulsar-admin/) command.
````mdx-code-block
<Tabs
diff --git a/site2/website-next/docs/admin-api-overview.md b/site2/website-next/docs/admin-api-overview.md
index 5b245ec4f51..38d1b412ff0 100644
--- a/site2/website-next/docs/admin-api-overview.md
+++ b/site2/website-next/docs/admin-api-overview.md
@@ -24,7 +24,7 @@ You can interact with the admin interface via:
> **Important**
>
- > For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
+ > For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](/tools/pulsar-admin/).
- HTTP calls, which are made against the admin {@inject: rest:REST:/} API provided by Pulsar brokers. For some RESTful APIs, they might be redirected to the owner brokers for serving with [`307 Temporary Redirect`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/307), hence the HTTP callers should handle `307 Temporary Redirect`. If you use `curl` commands, you should specify `-L` to handle redirections.
@@ -36,7 +36,7 @@ You can interact with the admin interface via:
> **Important**
>
- > For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+ > For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
> **The REST API is the admin interface**. Both the `pulsar-admin` CLI tool and the Java client use the REST API. If you implement your own admin interface client, you should use the REST API.
@@ -136,8 +136,8 @@ Kubernetes requires a name that can be used as a DNS subdomain name as defined i
:::tip
-- If you get an error in translating Pulsar object names into Kubernetes resource labels (for example, you may have a naming collision if your Pulsar object name is too long) or want to customize the translating rules, see [customize Kubernetes runtime](https://pulsar.apache.org/docs/en/next/functions-runtime/#customize-kubernetes-runtime).
-- For how to configure Kubernetes runtime, see [here](https://pulsar.apache.org/docs/en/next/functions-runtime/#configure-kubernetes-runtime).
+- If you get an error in translating Pulsar object names into Kubernetes resource labels (for example, you may have a naming collision if your Pulsar object name is too long) or want to customize the translating rules, see [customize Kubernetes runtime](/functions-runtime.md#customize-kubernetes-runtime).
+- For how to configure Kubernetes runtime, see [here](/functions-runtime.md#configure-kubernetes-runtime).
:::
diff --git a/site2/website-next/docs/admin-api-packages.md b/site2/website-next/docs/admin-api-packages.md
index 258c99e5bef..9262cf4489c 100644
--- a/site2/website-next/docs/admin-api-packages.md
+++ b/site2/website-next/docs/admin-api-packages.md
@@ -14,11 +14,11 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](/tools/pulsar-admin/).
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
Package managers or package-management systems automatically manage packages in a consistent manner. These tools simplify the installation tasks, upgrade process, and deletion operations for users. A package is a minimal unit that a package manager deals with. In Pulsar, packages are organized at the tenant- and namespace-level to manage Pulsar Functions and Pulsar IO connectors (i.e., source and sink).
diff --git a/site2/website-next/docs/admin-api-permissions.md b/site2/website-next/docs/admin-api-permissions.md
index 8432b5b82cd..74886c7f5a0 100644
--- a/site2/website-next/docs/admin-api-permissions.md
+++ b/site2/website-next/docs/admin-api-permissions.md
@@ -14,11 +14,11 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/)
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](/tools/pulsar-admin/)
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
Pulsar allows you to grant namespace-level or topic-level permission to users.
@@ -38,7 +38,7 @@ You can grant permissions to specific roles for lists of operations such as `pro
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`grant-permission`](reference-pulsar-admin.md#grant-permission) subcommand and specify a namespace, actions using the `--actions` flag, and a role using the `--role` flag:
+Use the [`grant-permission`](/tools/pulsar-admin/) subcommand and specify a namespace, actions using the `--actions` flag, and a role using the `--role` flag:
```shell
@@ -116,7 +116,7 @@ You can see which permissions have been granted to which roles in a namespace.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`permissions`](reference-pulsar-admin#permissions) subcommand and specify a namespace:
+Use the [`permissions`](/tools/pulsar-admin/) subcommand and specify a namespace:
```shell
@@ -159,7 +159,7 @@ You can revoke permissions from specific roles, which means that those roles wil
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`revoke-permission`](reference-pulsar-admin.md#revoke-permission) subcommand and specify a namespace and a role using the `--role` flag:
+Use the [`revoke-permission`](/tools/pulsar-admin/) subcommand and specify a namespace and a role using the `--role` flag:
```shell
diff --git a/site2/website-next/docs/admin-api-tenants.md b/site2/website-next/docs/admin-api-tenants.md
index 8071b3261c6..b8bdc8be07f 100644
--- a/site2/website-next/docs/admin-api-tenants.md
+++ b/site2/website-next/docs/admin-api-tenants.md
@@ -14,11 +14,11 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/)
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](/tools/pulsar-admin/)
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
Tenants, like namespaces, can be managed using the [admin API](admin-api-overview). There are currently two configurable aspects of tenants:
@@ -37,7 +37,7 @@ You can list all of the tenants associated with an [instance](reference-terminol
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`list`](reference-pulsar-admin.md#tenants-list) subcommand.
+Use the [`list`](/tools/pulsar-admin/) subcommand.
```shell
@@ -76,7 +76,7 @@ You can create a new tenant.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`create`](reference-pulsar-admin.md#tenants-create) subcommand:
+Use the [`create`](/tools/pulsar-admin/) subcommand:
```shell
@@ -129,7 +129,7 @@ You can fetch the [configuration](reference-configuration) for an existing tenan
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`get`](reference-pulsar-admin.md#tenants-get) subcommand and specify the name of the tenant. Here's an example:
+Use the [`get`](/tools/pulsar-admin/) subcommand and specify the name of the tenant. Here's an example:
```shell
@@ -176,7 +176,7 @@ Tenants can be deleted from a Pulsar [instance](reference-terminology.md#instanc
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`delete`](reference-pulsar-admin.md#tenants-delete) subcommand and specify the name of the tenant.
+Use the [`delete`](/tools/pulsar-admin/) subcommand and specify the name of the tenant.
```shell
@@ -213,7 +213,7 @@ You can update a tenant's configuration.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"JAVA","value":"JAVA"}]}>
<TabItem value="pulsar-admin">
-Use the [`update`](reference-pulsar-admin.md#tenants-update) subcommand.
+Use the [`update`](/tools/pulsar-admin/) subcommand.
```shell
diff --git a/site2/website-next/docs/admin-api-topics.md b/site2/website-next/docs/admin-api-topics.md
index f365f780de6..2d14b9bd07b 100644
--- a/site2/website-next/docs/admin-api-topics.md
+++ b/site2/website-next/docs/admin-api-topics.md
@@ -14,11 +14,11 @@ import TabItem from '@theme/TabItem';
>
> This page only shows **some frequently used operations**.
>
-> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/)
+> - For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](/tools/pulsar-admin/)
>
> - For the latest and complete information about `REST API`, including parameters, responses, samples, and more, see {@inject: rest:REST:/} API doc.
>
-> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](https://pulsar.apache.org/api/admin/).
+> - For the latest and complete information about `Java admin API`, including classes, methods, descriptions, and more, see [Java admin API doc](/api/admin/).
Pulsar has persistent and non-persistent topics. Persistent topic is a logical endpoint for publishing and consuming messages. The topic name structure for persistent topics is:
@@ -1694,7 +1694,7 @@ You can create non-partitioned topics in the following ways.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-When you create non-partitioned topics with the [`create`](reference-pulsar-admin.md#create-3) command, you need to specify the topic name as an argument.
+When you create non-partitioned topics with the [`create`](/tools/pulsar-admin/) command, you need to specify the topic name as an argument.
```shell
@@ -1890,7 +1890,7 @@ You can create partitioned topics in the following ways.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-When you create partitioned topics with the [`create-partitioned-topic`](reference-pulsar-admin.md#create-partitioned-topic)
+When you create partitioned topics with the [`create-partitioned-topic`](/tools/pulsar-admin/)
command, you need to specify the topic name as an argument and the number of partitions using the `-p` or `--partitions` flag.
```shell
@@ -1930,7 +1930,7 @@ admin.topics().createPartitionedTopic(topicName, numPartitions);
### Create missed partitions
-When topic auto-creation is disabled, and you have a partitioned topic without any partitions, you can use the [`create-missed-partitions`](reference-pulsar-admin.md#create-missed-partitions) command to create partitions for the topic.
+When topic auto-creation is disabled, and you have a partitioned topic without any partitions, you can use the [`create-missed-partitions`](/tools/pulsar-admin/) command to create partitions for the topic.
````mdx-code-block
<Tabs
@@ -1938,7 +1938,7 @@ When topic auto-creation is disabled, and you have a partitioned topic without a
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-You can create missed partitions with the [`create-missed-partitions`](reference-pulsar-admin.md#create-missed-partitions) command and specify the topic name as an argument.
+You can create missed partitions with the [`create-missed-partitions`](/tools/pulsar-admin/) command and specify the topic name as an argument.
```shell
@@ -1981,7 +1981,7 @@ Field | Description
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-You can check the number of partitions in a partitioned topic with the [`get-partitioned-topic-metadata`](reference-pulsar-admin.md#get-partitioned-topic-metadata) subcommand.
+You can check the number of partitions in a partitioned topic with the [`get-partitioned-topic-metadata`](/tools/pulsar-admin/) subcommand.
```shell
@@ -2025,7 +2025,7 @@ Producers and consumers can find the newly created partitions automatically.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-You can update partitioned topics with the [`update-partitioned-topic`](reference-pulsar-admin.md#update-partitioned-topic) command.
+You can update partitioned topics with the [`update-partitioned-topic`](/tools/pulsar-admin/) command.
```shell
@@ -2055,7 +2055,7 @@ admin.topics().updatePartitionedTopic(topic, numPartitions);
````
### Delete
-You can delete partitioned topics with the [`delete-partitioned-topic`](reference-pulsar-admin.md#delete-partitioned-topic) command, REST API and Java.
+You can delete partitioned topics with the [`delete-partitioned-topic`](/tools/pulsar-admin/) command, REST API and Java.
````mdx-code-block
<Tabs
diff --git a/site2/website-next/docs/administration-geo.md b/site2/website-next/docs/administration-geo.md
index c4463fb1205..a7911659f82 100644
--- a/site2/website-next/docs/administration-geo.md
+++ b/site2/website-next/docs/administration-geo.md
@@ -49,7 +49,7 @@ This section guides you through the steps to configure geo-replicated clusters.
### Connect replication clusters
-To replicate data among clusters, you need to configure each cluster to connect to the other. You can use the [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/) tool to create a connection.
+To replicate data among clusters, you need to configure each cluster to connect to the other. You can use the [`pulsar-admin`](/tools/pulsar-admin/) tool to create a connection.
**Example**
@@ -70,7 +70,7 @@ $ bin/pulsar-admin clusters create \
:::tip
- - If you want to use a secure connection for a cluster, you can use the flags `--broker-url-secure` and `--url-secure`. For more information, see [pulsar-admin clusters create](https://pulsar.apache.org/tools/pulsar-admin/).
+ - If you want to use a secure connection for a cluster, you can use the flags `--broker-url-secure` and `--url-secure`. For more information, see [pulsar-admin clusters create](/tools/pulsar-admin/).
- Different clusters may have different authentications. You can use the authentication flag `--auth-plugin` and `--auth-parameters` together to set cluster authentication, which overrides `brokerClientAuthenticationPlugin` and `brokerClientAuthenticationParameters` if `authenticationEnabled` sets to `true` in `broker.conf` and `standalone.conf`. For more information, see [authentication and authorization](concepts-authentication).
:::
@@ -131,7 +131,7 @@ $ bin/pulsar-admin namespaces set-clusters my-tenant/my-namespace \
#### Enable geo-replication at topic level
-You can set geo-replication at topic level using the command `pulsar-admin topics set-replication-clusters`. For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
+You can set geo-replication at topic level using the command `pulsar-admin topics set-replication-clusters`. For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](/tools/pulsar-admin/).
```shell
@@ -182,7 +182,7 @@ You can check topic-specific statistics for geo-replication topics using one of
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"}]}>
<TabItem value="pulsar-admin">
-Use the [`pulsar-admin topics stats`](https://pulsar.apache.org/tools/pulsar-admin/) command.
+Use the [`pulsar-admin topics stats`](/tools/pulsar-admin/) command.
```shell
diff --git a/site2/website-next/docs/administration-isolation.md b/site2/website-next/docs/administration-isolation.md
index c808043c471..b5a2b96b81f 100644
--- a/site2/website-next/docs/administration-isolation.md
+++ b/site2/website-next/docs/administration-isolation.md
@@ -33,7 +33,7 @@ pulsar-admin ns-isolation-policy set options
```
-For more information about the command `pulsar-admin ns-isolation-policy set options`, see [here](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about the command `pulsar-admin ns-isolation-policy set options`, see [here](/tools/pulsar-admin/).
**Example**
@@ -50,7 +50,7 @@ bin/pulsar-admin ns-isolation-policy set \
</TabItem>
<TabItem value="REST API">
-[PUT /admin/v2/namespaces/{tenant}/{namespace}](https://pulsar.apache.org/admin-rest-api/?version=master&apiversion=v2#operation/createNamespace)
+[PUT /admin/v2/namespaces/{tenant}/{namespace}](/admin-rest-api/?version=master&apiversion=v2#operation/createNamespace)
</TabItem>
<TabItem value="Java admin API">
@@ -81,7 +81,7 @@ pulsar-admin namespaces set-bookie-affinity-group options
```
-For more information about the command `pulsar-admin namespaces set-bookie-affinity-group options`, see [here](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about the command `pulsar-admin namespaces set-bookie-affinity-group options`, see [here](/tools/pulsar-admin/).
**Example**
@@ -103,14 +103,14 @@ bin/pulsar-admin namespaces set-bookie-affinity-group public/default \
- Do not set a bookie rack name to slash (`/`) or an empty string (`""`) if you use Pulsar earlier than 2.7.5, 2.8.3, and 2.9.2. If you use Pulsar 2.7.5, 2.8.3, 2.9.2 or later versions, it falls back to `/default-rack` or `/default-region/default-rack`.
- When `RackawareEnsemblePlacementPolicy` is enabled, the rack name is not allowed to contain slash (`/`) except for the beginning and end of the rack name string. For example, rack name like `/rack0` is okay, but `/rack/0` is not allowed.
- When `RegionawareEnsemblePlacementPolicy` is enabled, the rack name can only contain one slash (`/`) except for the beginning and end of the rack name string. For example, rack name like `/region0/rack0` is okay, but `/region0rack0` and `/region0/rack/0` are not allowed.
-For the bookie rack name restrictions, see [pulsar-admin bookies set-bookie-rack](https://pulsar.apache.org/tools/pulsar-admin/).
+For the bookie rack name restrictions, see [pulsar-admin bookies set-bookie-rack](/tools/pulsar-admin/).
:::
</TabItem>
<TabItem value="REST API">
-[POST /admin/v2/namespaces/{tenant}/{namespace}/persistence/bookieAffinity](https://pulsar.apache.org/admin-rest-api/?version=master&apiversion=v2#operation/setBookieAffinityGroup)
+[POST /admin/v2/namespaces/{tenant}/{namespace}/persistence/bookieAffinity](/admin-rest-api/?version=master&apiversion=v2#operation/setBookieAffinityGroup)
</TabItem>
<TabItem value="Java admin API">
diff --git a/site2/website-next/docs/administration-pulsar-manager.md b/site2/website-next/docs/administration-pulsar-manager.md
index 545a9ad677c..5997a58afea 100644
--- a/site2/website-next/docs/administration-pulsar-manager.md
+++ b/site2/website-next/docs/administration-pulsar-manager.md
@@ -86,7 +86,7 @@ jwt.broker.secret.key=file:///path/broker-secret.key
• `jwt.broker.public.key`: configure this option if you use the PUBLIC mode.
• `jwt.broker.private.key`: configure this option if you use the PRIVATE mode.
• `jwt.broker.secret.key`: configure this option if you use the SECRET mode.
-For more information, see [Token Authentication Admin of Pulsar](https://pulsar.apache.org/docs/en/security-token-admin/).
+For more information, see [Token Authentication Admin of Pulsar](/docs/en/security-token-admin/).
Docker command to add profile and key files mount.
@@ -145,7 +145,7 @@ The request parameter in curl command:
When using binary packages for direct deployment, you can follow these steps.
-- Download and unzip the binary package, which is available on the [Pulsar Download](https://pulsar.apache.org/en/download/) page.
+- Download and unzip the binary package, which is available on the [Pulsar Download](/en/download/) page.
```bash
diff --git a/site2/website-next/docs/administration-zk-bk.md b/site2/website-next/docs/administration-zk-bk.md
index c0aec95c3e9..37dc96c0020 100644
--- a/site2/website-next/docs/administration-zk-bk.md
+++ b/site2/website-next/docs/administration-zk-bk.md
@@ -297,7 +297,7 @@ You can set persistence policies for BookKeeper at the [namespace](reference-ter
#### Pulsar-admin
-Use the [`set-persistence`](reference-pulsar-admin.md#namespaces-set-persistence) subcommand and specify a namespace as well as any policies that you want to apply. The available flags are:
+Use the [`set-persistence`](/tools/pulsar-admin/) subcommand and specify a namespace as well as any policies that you want to apply. The available flags are:
Flag | Description | Default
:----|:------------|:-------
@@ -340,7 +340,7 @@ You can see which persistence policy currently applies to a namespace.
#### Pulsar-admin
-Use the [`get-persistence`](reference-pulsar-admin.md#namespaces-get-persistence) subcommand and specify the namespace.
+Use the [`get-persistence`](/tools/pulsar-admin/) subcommand and specify the namespace.
The following is an example:
diff --git a/site2/website-next/docs/client-libraries-java.md b/site2/website-next/docs/client-libraries-java.md
index 3f0ba313b59..0c2d6ce4e89 100644
--- a/site2/website-next/docs/client-libraries-java.md
+++ b/site2/website-next/docs/client-libraries-java.md
@@ -18,7 +18,7 @@ Javadoc for the Pulsar client is divided into two domains by package as follows.
Package | Description | Maven Artifact
:-------|:------------|:--------------
-[`org.apache.pulsar.client.api`](/api/client) | [The producer and consumer API](https://pulsar.apache.org/api/client/) | [org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
+[`org.apache.pulsar.client.api`](/api/client) | [The producer and consumer API](/api/client/) | [org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
[`org.apache.pulsar.client.admin`](/api/admin) | The Java [admin API](admin-api-overview) | [org.apache.pulsar:pulsar-client-admin:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client-admin%7C@pulsar:version@%7Cjar)
`org.apache.pulsar.client.all` |Include both `pulsar-client` and `pulsar-client-admin`<br /> Both `pulsar-client` and `pulsar-client-admin` are shaded packages and they shade dependencies independently. Consequently, the applications using both `pulsar-client` and `pulsar-client-admin` have redundant shaded classes. It would be troublesome if you introduce new dependencies but forget to update shading rules. <br /> In this case, you can use `pulsar-client-all`, which shades dependencies [...]
@@ -138,7 +138,7 @@ If you create a client, you can use the `loadConf` configuration. The following
`operationTimeoutMs`|long|`operationTimeoutMs`|Operation timeout |30000
`statsIntervalSeconds`|long|Interval between each stats information<br /><br />Stats is activated with positive `statsInterval`<br /><br />Set `statsIntervalSeconds` to 1 second at least. |60
`numIoThreads`| int| The number of threads used for handling connections to brokers | 1
-`numListenerThreads`|int|The number of threads used for handling message listeners. The listener thread pool is shared across all the consumers and readers using the "listener" model to get messages. For a given consumer, the listener is always invoked from the same thread to ensure ordering. If you want multiple threads to process a single topic, you need to create a [`shared`](https://pulsar.apache.org/docs/en/next/concepts-messaging/#shared) subscription and multiple consumers for thi [...]
+`numListenerThreads`|int|The number of threads used for handling message listeners. The listener thread pool is shared across all the consumers and readers using the "listener" model to get messages. For a given consumer, the listener is always invoked from the same thread to ensure ordering. If you want multiple threads to process a single topic, you need to create a [`shared`](/concepts-messaging.md#shared) subscription and multiple consumers for this subscription. This does not ensure [...]
`useTcpNoDelay`| boolean| Whether to use TCP no-delay flag on the connection to disable Nagle algorithm |true
`useTls` |boolean |Whether to use TLS encryption on the connection| false
`tlsTrustCertsFilePath` |string |Path to the trusted TLS certificate file|None
@@ -1366,7 +1366,7 @@ TableView<String> tv = client.newTableViewBuilder(Schema.STRING)
```
-You can use the available parameters in the `loadConf` configuration or related [API](https://pulsar.apache.org/api/client/2.10.0-SNAPSHOT/org/apache/pulsar/client/api/TableViewBuilder.html) to customize your TableView.
+You can use the available parameters in the `loadConf` configuration or related [API](/api/client/2.10.0-SNAPSHOT/org/apache/pulsar/client/api/TableViewBuilder.html) to customize your TableView.
| Name | Type| Required? | <div>Description</div> | Default
|---|---|---|---|---
diff --git a/site2/website-next/docs/client-libraries-node.md b/site2/website-next/docs/client-libraries-node.md
index a13253478ab..81fed781346 100644
--- a/site2/website-next/docs/client-libraries-node.md
+++ b/site2/website-next/docs/client-libraries-node.md
@@ -476,7 +476,7 @@ The following static methods are available for the message id object:
## End-to-end encryption
-[End-to-end encryption](https://pulsar.apache.org/docs/en/next/cookbooks-encryption/#docsNav) allows applications to encrypt messages at producers and decrypt at consumers.
+[End-to-end encryption](/cookbooks-encryption.md#docsNav) allows applications to encrypt messages at producers and decrypt at consumers.
### Configuration
diff --git a/site2/website-next/docs/client-libraries-python.md b/site2/website-next/docs/client-libraries-python.md
index 4b6b4f9e41d..ee58b807f5c 100644
--- a/site2/website-next/docs/client-libraries-python.md
+++ b/site2/website-next/docs/client-libraries-python.md
@@ -538,7 +538,7 @@ consumer = client.subscribe(
## End-to-end encryption
-[End-to-end encryption](https://pulsar.apache.org/docs/en/next/cookbooks-encryption/#docsNav) allows applications to encrypt messages at producers and decrypt messages at consumers.
+[End-to-end encryption](/cookbooks-encryption.md#docsNav) allows applications to encrypt messages at producers and decrypt messages at consumers.
### Configuration
diff --git a/site2/website-next/docs/client-libraries-websocket.md b/site2/website-next/docs/client-libraries-websocket.md
index a6e60361749..2fed4bc6af8 100644
--- a/site2/website-next/docs/client-libraries-websocket.md
+++ b/site2/website-next/docs/client-libraries-websocket.md
@@ -107,11 +107,11 @@ Key | Type | Required? | Explanation
`batchingMaxMessages` | int | no | Maximum number of messages permitted in a batch (default: 1000)
`maxPendingMessages` | int | no | Set the max size of the internal-queue holding the messages (default: 1000)
`batchingMaxPublishDelay` | long | no | Time period within which the messages will be batched (default: 10ms)
-`messageRoutingMode` | string | no | Message [routing mode](https://pulsar.apache.org/api/client/index.html?org/apache/pulsar/client/api/ProducerConfiguration.MessageRoutingMode.html) for the partitioned producer: `SinglePartition`, `RoundRobinPartition`
-`compressionType` | string | no | Compression [type](https://pulsar.apache.org/api/client/index.html?org/apache/pulsar/client/api/CompressionType.html): `LZ4`, `ZLIB`
+`messageRoutingMode` | string | no | Message [routing mode](/api/client/index.html?org/apache/pulsar/client/api/ProducerConfiguration.MessageRoutingMode.html) for the partitioned producer: `SinglePartition`, `RoundRobinPartition`
+`compressionType` | string | no | Compression [type](/api/client/index.html?org/apache/pulsar/client/api/CompressionType.html): `LZ4`, `ZLIB`
`producerName` | string | no | Specify the name for the producer. Pulsar will enforce only one producer with same name can be publishing on a topic
`initialSequenceId` | long | no | Set the baseline for the sequence ids for messages published by the producer.
-`hashingScheme` | string | no | [Hashing function](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.HashingScheme.html) to use when publishing on a partitioned topic: `JavaStringHash`, `Murmur3_32Hash`
+`hashingScheme` | string | no | [Hashing function](/api/client/org/apache/pulsar/client/api/ProducerConfiguration.HashingScheme.html) to use when publishing on a partitioned topic: `JavaStringHash`, `Murmur3_32Hash`
`token` | string | no | Authentication token, this is used for the browser javascript client
@@ -182,12 +182,12 @@ ws://broker-service-url:8080/ws/v2/consumer/persistent/:tenant/:namespace/:topic
Key | Type | Required? | Explanation
:---|:-----|:----------|:-----------
`ackTimeoutMillis` | long | no | Set the timeout for unacked messages (default: 0)
-`subscriptionType` | string | no | [Subscription type](https://pulsar.apache.org/api/client/index.html?org/apache/pulsar/client/api/SubscriptionType.html): `Exclusive`, `Failover`, `Shared`, `Key_Shared`
+`subscriptionType` | string | no | [Subscription type](/api/client/index.html?org/apache/pulsar/client/api/SubscriptionType.html): `Exclusive`, `Failover`, `Shared`, `Key_Shared`
`receiverQueueSize` | int | no | Size of the consumer receive queue (default: 1000)
`consumerName` | string | no | Consumer name
-`priorityLevel` | int | no | Define a [priority](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setPriorityLevel-int-) for the consumer
-`maxRedeliverCount` | int | no | Define a [maxRedeliverCount](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#deadLetterPolicy-org.apache.pulsar.client.api.DeadLetterPolicy-) for the consumer (default: 0). Activates [Dead Letter Topic](https://github.com/apache/pulsar/wiki/PIP-22%3A-Pulsar-Dead-Letter-Topic) feature.
-`deadLetterTopic` | string | no | Define a [deadLetterTopic](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#deadLetterPolicy-org.apache.pulsar.client.api.DeadLetterPolicy-) for the consumer (default: {topic}-{subscription}-DLQ). Activates [Dead Letter Topic](https://github.com/apache/pulsar/wiki/PIP-22%3A-Pulsar-Dead-Letter-Topic) feature.
+`priorityLevel` | int | no | Define a [priority](/api/client/org/apache/pulsar/client/api/ConsumerConfiguration.html#setPriorityLevel-int-) for the consumer
+`maxRedeliverCount` | int | no | Define a [maxRedeliverCount](/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#deadLetterPolicy-org.apache.pulsar.client.api.DeadLetterPolicy-) for the consumer (default: 0). Activates [Dead Letter Topic](https://github.com/apache/pulsar/wiki/PIP-22%3A-Pulsar-Dead-Letter-Topic) feature.
+`deadLetterTopic` | string | no | Define a [deadLetterTopic](/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#deadLetterPolicy-org.apache.pulsar.client.api.DeadLetterPolicy-) for the consumer (default: {topic}-{subscription}-DLQ). Activates [Dead Letter Topic](https://github.com/apache/pulsar/wiki/PIP-22%3A-Pulsar-Dead-Letter-Topic) feature.
`pullMode` | boolean | no | Enable pull mode (default: false). See "Flow Control" below.
`negativeAckRedeliveryDelay` | int | no | When a message is negatively acknowledged, the delay time before the message is redelivered (in milliseconds). The default value is 60000.
`token` | string | no | Authentication token, this is used for the browser javascript client
diff --git a/site2/website-next/docs/client-libraries.md b/site2/website-next/docs/client-libraries.md
index 536cd0ccda8..071e33a08b2 100644
--- a/site2/website-next/docs/client-libraries.md
+++ b/site2/website-next/docs/client-libraries.md
@@ -8,17 +8,17 @@ Pulsar supports the following client libraries:
|Language|Documentation|Release note|Code repo
|---|---|---|---
-Java |- [User doc](client-libraries-java) <br /><br />- [API doc](https://pulsar.apache.org/api/client/)|[Here](https://pulsar.apache.org/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-client)
-C++ | - [User doc](client-libraries-cpp) <br /><br />- [API doc](https://pulsar.apache.org/api/cpp/)|[Here](https://pulsar.apache.org/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-client-cpp)
-Python | - [User doc](client-libraries-python) <br /><br />- [API doc](https://pulsar.apache.org/api/python/)|[Here](https://pulsar.apache.org/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-client-cpp/python)
-WebSocket| [User doc](client-libraries-websocket) | [Here](https://pulsar.apache.org/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-websocket)
+Java |- [User doc](client-libraries-java) <br /><br />- [API doc](/api/client/)|[Here](/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-client)
+C++ | - [User doc](client-libraries-cpp) <br /><br />- [API doc](/api/cpp/)|[Here](/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-client-cpp)
+Python | - [User doc](client-libraries-python) <br /><br />- [API doc](/api/python/)|[Here](/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-client-cpp/python)
+WebSocket| [User doc](client-libraries-websocket) | [Here](/release-notes/)|[Here](https://github.com/apache/pulsar/tree/master/pulsar-websocket)
Go client|[User doc](client-libraries-go.md)|[Here](https://github.com/apache/pulsar-client-go/blob/master/CHANGELOG) |[Here](https://github.com/apache/pulsar-client-go)
Node.js|[User doc](client-libraries-node)|[Here](https://github.com/apache/pulsar-client-node/releases) |[Here](https://github.com/apache/pulsar-client-node)
C# |[User doc](client-libraries-dotnet.md)| [Here](https://github.com/apache/pulsar-dotpulsar/blob/master/CHANGELOG)|[Here](https://github.com/apache/pulsar-dotpulsar)
:::note
-- The code repos of **Java, C++, Python,** and **WebSocket** clients are hosted in the [Pulsar main repo](https://github.com/apache/pulsar) and these clients are released with Pulsar, so their release notes are parts of [Pulsar release note](https://pulsar.apache.org/release-notes/).
+- The code repos of **Java, C++, Python,** and **WebSocket** clients are hosted in the [Pulsar main repo](https://github.com/apache/pulsar) and these clients are released with Pulsar, so their release notes are parts of [Pulsar release note](/release-notes/).
- The code repos of **Go, Node.js,** and **C#** clients are hosted outside of the [Pulsar main repo](https://github.com/apache/pulsar) and these clients are not released with Pulsar, so they have independent release notes.
:::
diff --git a/site2/website-next/docs/concepts-messaging.md b/site2/website-next/docs/concepts-messaging.md
index c5faba29d7d..00ed7f10d43 100644
--- a/site2/website-next/docs/concepts-messaging.md
+++ b/site2/website-next/docs/concepts-messaging.md
@@ -151,7 +151,7 @@ To enable message chunking, set the `chunkingEnabled` parameter to `true` when c
:::note
-If the consumer fails to receive all chunks of a message within a specified time period, it expires incomplete chunks. The default value is 1 minute. For more information about the `expireTimeOfIncompleteChunkedMessage` parameter, refer to [org.apache.pulsar.client.api](https://pulsar.apache.org/api/client/).
+If the consumer fails to receive all chunks of a message within a specified time period, it expires incomplete chunks. The default value is 1 minute. For more information about the `expireTimeOfIncompleteChunkedMessage` parameter, refer to [org.apache.pulsar.client.api](/api/client/).
:::
@@ -818,7 +818,7 @@ In non-persistent topics, brokers immediately deliver messages to all connected
> With non-persistent topics, message data lives only in memory, without a specific buffer - which means data *is not* buffered in memory. The received messages are immediately transmitted to all *connected consumers*. If a message broker fails or message data can otherwise not be retrieved from memory, your message data may be lost. Use non-persistent topics only if you're *certain* that your use case requires it and can sustain it.
-By default, non-persistent topics are enabled on Pulsar brokers. You can disable them in the broker's [configuration](reference-configuration.md#broker-enableNonPersistentTopics). You can manage non-persistent topics using the `pulsar-admin topics` command. For more information, see [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/).
+By default, non-persistent topics are enabled on Pulsar brokers. You can disable them in the broker's [configuration](reference-configuration.md#broker-enableNonPersistentTopics). You can manage non-persistent topics using the `pulsar-admin topics` command. For more information, see [`pulsar-admin`](/tools/pulsar-admin/).
Currently, non-persistent topics which are not partitioned are not persisted to ZooKeeper, which means if the broker owning them crashes, they do not get re-assigned to another broker because they only exist in the owner broker memory. The current workaround is to set the value of `allowAutoTopicCreation` to `true` and `allowAutoTopicCreationType` to `non-partitioned` (they are default values) in broker configuration.
diff --git a/site2/website-next/docs/concepts-multi-tenancy.md b/site2/website-next/docs/concepts-multi-tenancy.md
index 8a17e72a4c8..f40f542ecc5 100644
--- a/site2/website-next/docs/concepts-multi-tenancy.md
+++ b/site2/website-next/docs/concepts-multi-tenancy.md
@@ -28,7 +28,7 @@ To each tenant in a Pulsar instance you can assign:
Tenants and namespaces are two key concepts of Pulsar to support multi-tenancy.
* Pulsar is provisioned for specified tenants with appropriate capacity allocated to the tenant.
-* A namespace is the administrative unit nomenclature within a tenant. The configuration policies set on a namespace apply to all the topics created in that namespace. A tenant may create multiple namespaces via self-administration using the REST API and the [`pulsar-admin`](reference-pulsar-admin) CLI tool. For instance, a tenant with different applications can create a separate namespace for each application.
+* A namespace is the administrative unit nomenclature within a tenant. The configuration policies set on a namespace apply to all the topics created in that namespace. A tenant may create multiple namespaces via self-administration using the REST API and the [`pulsar-admin`](/tools/pulsar-admin/) CLI tool. For instance, a tenant with different applications can create a separate namespace for each application.
Names for topics in the same namespace will look like this:
diff --git a/site2/website-next/docs/concepts-tiered-storage.md b/site2/website-next/docs/concepts-tiered-storage.md
index f0bbde61718..30b6077eca8 100644
--- a/site2/website-next/docs/concepts-tiered-storage.md
+++ b/site2/website-next/docs/concepts-tiered-storage.md
@@ -12,6 +12,6 @@ One way to alleviate this cost is to use Tiered Storage. With tiered storage, ol
> Data written to BookKeeper is replicated to 3 physical machines by default. However, once a segment is sealed in BookKeeper it becomes immutable and can be copied to long term storage. Long term storage can achieve cost savings by using mechanisms such as [Reed-Solomon error correction](https://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_correction) to require fewer physical copies of data.
-Pulsar currently supports S3, Google Cloud Storage (GCS), and filesystem for [long term store](https://pulsar.apache.org/docs/en/cookbooks-tiered-storage/). Offloading to long term storage triggered via a Rest API or command line interface. The user passes in the amount of topic data they wish to retain on BookKeeper, and the broker will copy the backlog data to long term storage. The original data will then be deleted from BookKeeper after a configured delay (4 hours by default).
+Pulsar currently supports S3, Google Cloud Storage (GCS), and filesystem for [long term store](/docs/en/cookbooks-tiered-storage/). Offloading to long term storage triggered via a Rest API or command line interface. The user passes in the amount of topic data they wish to retain on BookKeeper, and the broker will copy the backlog data to long term storage. The original data will then be deleted from BookKeeper after a configured delay (4 hours by default).
> For a guide for setting up tiered storage, see the [Tiered storage cookbook](cookbooks-tiered-storage).
diff --git a/site2/website-next/docs/cookbooks-compaction.md b/site2/website-next/docs/cookbooks-compaction.md
index f95f64c4ebb..e4495841f2d 100644
--- a/site2/website-next/docs/cookbooks-compaction.md
+++ b/site2/website-next/docs/cookbooks-compaction.md
@@ -44,7 +44,7 @@ Configuring the compaction threshold on a namespace will apply to all topics wit
## Triggering compaction manually
-In order to run compaction on a topic, you need to use the [`topics compact`](reference-pulsar-admin.md#topics-compact) command for the [`pulsar-admin`](reference-pulsar-admin) CLI tool. Here's an example:
+In order to run compaction on a topic, you need to use the [`topics compact`](/tools/pulsar-admin/) command for the [`pulsar-admin`](/tools/pulsar-admin/) CLI tool. Here's an example:
```bash
diff --git a/site2/website-next/docs/cookbooks-deduplication.md b/site2/website-next/docs/cookbooks-deduplication.md
index a14a3c36981..21b38c48c7f 100644
--- a/site2/website-next/docs/cookbooks-deduplication.md
+++ b/site2/website-next/docs/cookbooks-deduplication.md
@@ -42,7 +42,7 @@ Even if you set the value for `brokerDeduplicationEnabled`, enabling or disablin
### Enable message deduplication
-Though message deduplication is disabled by default at the broker level, you can enable message deduplication for a specific namespace or topic using the [`pulsar-admin namespaces set-deduplication`](reference-pulsar-admin.md#namespace-set-deduplication) or the [`pulsar-admin topics set-deduplication`](reference-pulsar-admin.md#topic-set-deduplication) command. You can use the `--enable`/`-e` flag and specify the namespace/topic.
+Though message deduplication is disabled by default at the broker level, you can enable message deduplication for a specific namespace or topic using the [`pulsar-admin namespaces set-deduplication`](/tools/pulsar-admin/) or the [`pulsar-admin topics set-deduplication`](/tools/pulsar-admin/) command. You can use the `--enable`/`-e` flag and specify the namespace/topic.
The following example shows how to enable message deduplication at the namespace level.
@@ -56,7 +56,7 @@ $ bin/pulsar-admin namespaces set-deduplication \
### Disable message deduplication
-Even if you enable message deduplication at the broker level, you can disable message deduplication for a specific namespace or topic using the [`pulsar-admin namespace set-deduplication`](reference-pulsar-admin.md#namespace-set-deduplication) or the [`pulsar-admin topics set-deduplication`](reference-pulsar-admin.md#topic-set-deduplication) command. Use the `--disable`/`-d` flag and specify the namespace/topic.
+Even if you enable message deduplication at the broker level, you can disable message deduplication for a specific namespace or topic using the [`pulsar-admin namespace set-deduplication`](/tools/pulsar-admin/) or the [`pulsar-admin topics set-deduplication`](/tools/pulsar-admin/) command. Use the `--disable`/`-d` flag and specify the namespace/topic.
The following example shows how to disable message deduplication at the namespace level.
diff --git a/site2/website-next/docs/cookbooks-non-persistent.md b/site2/website-next/docs/cookbooks-non-persistent.md
index d40c4fbd0cf..888761d7d9e 100644
--- a/site2/website-next/docs/cookbooks-non-persistent.md
+++ b/site2/website-next/docs/cookbooks-non-persistent.md
@@ -54,7 +54,7 @@ If you'd like to enable *only* non-persistent topics in a broker, you can set th
## Managing with cli
-Non-persistent topics can be managed using the [`pulsar-admin non-persistent`](reference-pulsar-admin.md#non-persistent) command-line interface. With that interface you can perform actions like [create a partitioned non-persistent topic](reference-pulsar-admin.md#non-persistent-create-partitioned-topic), get [stats](reference-pulsar-admin.md#non-persistent-stats) for a non-persistent topic, [list](reference-pulsar-admin) non-persistent topics under a namespace, and more.
+Non-persistent topics can be managed using the [`pulsar-admin non-persistent`](/tools/pulsar-admin/) command-line interface. With that interface you can perform actions like [create a partitioned non-persistent topic](/tools/pulsar-admin/), get [stats](/tools/pulsar-admin/) for a non-persistent topic, [list](/tools/pulsar-admin/) non-persistent topics under a namespace, and more.
## Using with Pulsar clients
diff --git a/site2/website-next/docs/cookbooks-retention-expiry.md b/site2/website-next/docs/cookbooks-retention-expiry.md
index 86160c3f7ec..f023560e546 100644
--- a/site2/website-next/docs/cookbooks-retention-expiry.md
+++ b/site2/website-next/docs/cookbooks-retention-expiry.md
@@ -72,7 +72,7 @@ You can set a retention policy for a namespace by specifying the namespace, a si
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-You can use the [`set-retention`](reference-pulsar-admin.md#namespaces-set-retention) subcommand and specify a namespace, a size limit using the `-s`/`--size` flag, and a time limit using the `-t`/`--time` flag.
+You can use the [`set-retention`](/tools/pulsar-admin/) subcommand and specify a namespace, a size limit using the `-s`/`--size` flag, and a time limit using the `-t`/`--time` flag.
In the following example, the size limit is set to 10 GB and the time limit is set to 3 hours for each topic within the `my-tenant/my-ns` namespace.
- When the size of messages reaches 10 GB on a topic within 3 hours, the acknowledged messages will not be retained.
@@ -164,7 +164,7 @@ You can fetch the retention policy for a namespace by specifying the namespace.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`get-retention`](reference-pulsar-admin.md#namespaces) subcommand and specify the namespace.
+Use the [`get-retention`](/tools/pulsar-admin/) subcommand and specify the namespace.
##### Example
@@ -236,7 +236,7 @@ You can set a size and/or time threshold and backlog retention policy for all of
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`set-backlog-quota`](reference-pulsar-admin.md#namespaces) subcommand and specify a namespace, a size limit using the `-l`/`--limit` , `-lt`/`--limitTime` flag to limit backlog, a retention policy using the `-p`/`--policy` flag and a policy type using `-t`/`--type` (default is destination_storage).
+Use the [`set-backlog-quota`](/tools/pulsar-admin/) subcommand and specify a namespace, a size limit using the `-l`/`--limit` , `-lt`/`--limitTime` flag to limit backlog, a retention policy using the `-p`/`--policy` flag and a policy type using `-t`/`--type` (default is destination_storage).
##### Example
@@ -289,7 +289,7 @@ You can see which size threshold and backlog retention policy has been applied t
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`get-backlog-quotas`](reference-pulsar-admin.md#pulsar-admin-namespaces-get-backlog-quotas) subcommand and specify a namespace. Here's an example:
+Use the [`get-backlog-quotas`](/tools/pulsar-admin/) subcommand and specify a namespace. Here's an example:
```shell
@@ -331,7 +331,7 @@ Map<BacklogQuota.BacklogQuotaType,BacklogQuota> quotas =
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`remove-backlog-quota`](reference-pulsar-admin.md#pulsar-admin-namespaces-remove-backlog-quota) subcommand and specify a namespace, use `t`/`--type` to specify backlog type to remove(default is destination_storage). Here's an example:
+Use the [`remove-backlog-quota`](/tools/pulsar-admin/) subcommand and specify a namespace, use `t`/`--type` to specify backlog type to remove(default is destination_storage). Here's an example:
```shell
@@ -362,7 +362,7 @@ admin.namespaces().removeBacklogQuota(namespace);
#### pulsar-admin
-Use the [`clear-backlog`](reference-pulsar-admin.md#pulsar-admin-namespaces-clear-backlog) subcommand.
+Use the [`clear-backlog`](/tools/pulsar-admin/) subcommand.
##### Example
@@ -391,7 +391,7 @@ The diagram below illustrates the concept of TTL.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`set-message-ttl`](reference-pulsar-admin.md#pulsar-admin-namespaces-set-message-ttl) subcommand and specify a namespace and a TTL (in seconds) using the `-ttl`/`--messageTTL` flag.
+Use the [`set-message-ttl`](/tools/pulsar-admin/) subcommand and specify a namespace and a TTL (in seconds) using the `-ttl`/`--messageTTL` flag.
##### Example
@@ -429,7 +429,7 @@ admin.namespaces().setNamespaceMessageTTL(namespace, ttlInSeconds);
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`get-message-ttl`](reference-pulsar-admin.md#pulsar-admin-namespaces-get-message-ttl) subcommand and specify a namespace.
+Use the [`get-message-ttl`](/tools/pulsar-admin/) subcommand and specify a namespace.
##### Example
@@ -467,7 +467,7 @@ admin.namespaces().getNamespaceMessageTTL(namespace)
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`remove-message-ttl`](reference-pulsar-admin.md#pulsar-admin-namespaces-remove-message-ttl) subcommand and specify a namespace.
+Use the [`remove-message-ttl`](/tools/pulsar-admin/) subcommand and specify a namespace.
##### Example
diff --git a/site2/website-next/docs/deploy-bare-metal-multi-cluster.md b/site2/website-next/docs/deploy-bare-metal-multi-cluster.md
index cc11172191a..143d5028dbe 100644
--- a/site2/website-next/docs/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/docs/deploy-bare-metal-multi-cluster.md
@@ -65,7 +65,7 @@ The Pulsar binary package initially contains the following directories:
Directory | Contains
:---------|:--------
-`bin` | [Command-line tools](reference-cli-tools) of Pulsar, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/)
+`bin` | [Command-line tools](reference-cli-tools) of Pulsar, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](/tools/pulsar-admin/)
`conf` | Configuration files for Pulsar, including for [broker configuration](reference-configuration.md#broker), [ZooKeeper configuration](reference-configuration.md#zookeeper), and more
`examples` | A Java JAR file containing example [Pulsar Functions](functions-overview)
`lib` | The [JAR](https://en.wikipedia.org/wiki/JAR_(file_format)) files that Pulsar uses
@@ -387,7 +387,7 @@ serviceUrl=http://pulsar.us-west.example.com:8080/
Pulsar is built as a fundamentally multi-tenant system.
-If a new tenant wants to use the system, you need to create a new one. You can create a new tenant by using the [`pulsar-admin`](reference-pulsar-admin.md#tenants) CLI tool:
+If a new tenant wants to use the system, you need to create a new one. You can create a new tenant by using the [`pulsar-admin`](/tools/pulsar-admin/) CLI tool:
```shell
diff --git a/site2/website-next/docs/deploy-bare-metal.md b/site2/website-next/docs/deploy-bare-metal.md
index 49a5a125291..1c46febe158 100644
--- a/site2/website-next/docs/deploy-bare-metal.md
+++ b/site2/website-next/docs/deploy-bare-metal.md
@@ -122,13 +122,13 @@ The extracted directory contains the following subdirectories:
Directory | Contains
:---------|:--------
-`bin` |[command-line tools](reference-cli-tools) of Pulsar, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/)
+`bin` |[command-line tools](reference-cli-tools) of Pulsar, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](/tools/pulsar-admin/)
`conf` | Configuration files for Pulsar, including for [broker configuration](reference-configuration.md#broker), [ZooKeeper configuration](reference-configuration.md#zookeeper), and more
`data` | The data storage directory that ZooKeeper and BookKeeper use
`lib` | The [JAR](https://en.wikipedia.org/wiki/JAR_(file_format)) files that Pulsar uses
`logs` | Logs that the installation creates
-## [Install Builtin Connectors (optional)]( https://pulsar.apache.org/docs/en/next/standalone/#install-builtin-connectors-optional)
+## [Install Builtin Connectors (optional)](/standalone.md#install-builtin-connectors-optional)
> Since Pulsar release `2.1.0-incubating`, Pulsar provides a separate binary distribution, containing all the `builtin` connectors.
> To enable the `builtin` connectors (optional), you can follow the instructions below.
@@ -163,7 +163,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
```
-## [Install Tiered Storage Offloaders (optional)](https://pulsar.apache.org/docs/en/next/standalone/#install-tiered-storage-offloaders-optional)
+## [Install Tiered Storage Offloaders (optional)](/standalone.md#install-tiered-storage-offloaders-optional)
> Since Pulsar release `2.2.0`, Pulsar releases a separate binary distribution, containing the tiered storage offloaders.
> If you want to enable tiered storage feature, you can follow the instructions as below; otherwise you can
diff --git a/site2/website-next/docs/deploy-monitoring.md b/site2/website-next/docs/deploy-monitoring.md
index adf3587b7ae..705630c71b9 100644
--- a/site2/website-next/docs/deploy-monitoring.md
+++ b/site2/website-next/docs/deploy-monitoring.md
@@ -100,7 +100,7 @@ pulsar-admin functions-worker function-stats
```
-The aggregated functions and connectors metrics can be exposed in Prometheus formats as below. You can get [`FUNCTIONS_WORKER_ADDRESS`](http://pulsar.apache.org/docs/en/next/functions-worker/) and `WORKER_PORT` from the `functions_worker.yml` file.
+The aggregated functions and connectors metrics can be exposed in Prometheus formats as below. You can get [`FUNCTIONS_WORKER_ADDRESS`](/functions-worker.md) and `WORKER_PORT` from the `functions_worker.yml` file.
```
@@ -130,7 +130,7 @@ When you deploy Pulsar on Kubernetes with the Pulsar Helm Chart, a `pulsar-grafa
The following are some Grafana dashboards examples:
-- [pulsar-grafana](http://pulsar.apache.org/docs/en/deploy-monitoring/#grafana): a Grafana dashboard that displays metrics collected in Prometheus for Pulsar clusters running on Kubernetes.
+- [pulsar-grafana](/docs/en/deploy-monitoring/#grafana): a Grafana dashboard that displays metrics collected in Prometheus for Pulsar clusters running on Kubernetes.
- [apache-pulsar-grafana-dashboard](https://github.com/streamnative/apache-pulsar-grafana-dashboard): a collection of Grafana dashboard templates for different Pulsar components running on both Kubernetes and on-premise machines.
## Alerting rules
diff --git a/site2/website-next/docs/functions-debug.md b/site2/website-next/docs/functions-debug.md
index 61d4d056ebe..6e80b1a60d6 100644
--- a/site2/website-next/docs/functions-debug.md
+++ b/site2/website-next/docs/functions-debug.md
@@ -216,7 +216,7 @@ The message published to log topic contains several properties for better reason
## Use Functions CLI
-With [Pulsar Functions CLI](reference-pulsar-admin.md#functions), you can debug Pulsar Functions with the following subcommands:
+With [Pulsar Functions CLI](/tools/pulsar-admin/), you can debug Pulsar Functions with the following subcommands:
* `get`
* `status`
@@ -226,7 +226,7 @@ With [Pulsar Functions CLI](reference-pulsar-admin.md#functions), you can debug
:::tip
-For complete commands of **Pulsar Functions CLI**, see [here](reference-pulsar-admin.md#functions)。
+For complete commands of **Pulsar Functions CLI**, see [here](/tools/pulsar-admin/)。
:::
diff --git a/site2/website-next/docs/functions-deploy.md b/site2/website-next/docs/functions-deploy.md
index aa4b799a0af..66895225d84 100644
--- a/site2/website-next/docs/functions-deploy.md
+++ b/site2/website-next/docs/functions-deploy.md
@@ -13,13 +13,13 @@ To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
-If you want to deploy and trigger Python user-defined functions, you need to install [the pulsar python client](http://pulsar.apache.org/docs/en/client-libraries-python/) on all the machines running [functions workers](functions-worker).
+If you want to deploy and trigger Python user-defined functions, you need to install [the pulsar python client](/docs/en/client-libraries-python/) on all the machines running [functions workers](functions-worker).
## Command-line interface
-Pulsar Functions are deployed and managed using the [`pulsar-admin functions`](reference-pulsar-admin.md#functions) interface, which contains commands such as [`create`](reference-pulsar-admin.md#functions-create) for deploying functions in [cluster mode](#cluster-mode), [`trigger`](reference-pulsar-admin.md#trigger) for [triggering](#triggering-pulsar-functions) functions, [`list`](reference-pulsar-admin.md#list-2) for listing deployed functions.
+Pulsar Functions are deployed and managed using the [`pulsar-admin functions`](/tools/pulsar-admin/) interface, which contains commands such as [`create`](/tools/pulsar-admin/) for deploying functions in [cluster mode](#cluster-mode), [`trigger`](/tools/pulsar-admin/) for [triggering](#triggering-pulsar-functions) functions, [`list`](/tools/pulsar-admin/) for listing deployed functions.
-To learn more commands, refer to [`pulsar-admin functions`](reference-pulsar-admin.md#functions).
+To learn more commands, refer to [`pulsar-admin functions`](/tools/pulsar-admin/).
### Default arguments
@@ -52,7 +52,7 @@ The function has default values for the function name (`MyFunction`), tenant (`p
## Local run mode
-If you run a Pulsar Function in **local run** mode, it runs on the machine from which you enter the commands (on your laptop, an [AWS EC2](https://aws.amazon.com/ec2/) instance, and so on). The following is a [`localrun`](reference-pulsar-admin.md#localrun) command example.
+If you run a Pulsar Function in **local run** mode, it runs on the machine from which you enter the commands (on your laptop, an [AWS EC2](https://aws.amazon.com/ec2/) instance, and so on). The following is a [`localrun`](/tools/pulsar-admin/) command example.
```bash
@@ -76,7 +76,7 @@ $ bin/pulsar-admin functions localrun \
## Cluster mode
-When you run a Pulsar Function in **cluster** mode, the function code is uploaded to a Pulsar broker and runs *alongside the broker* rather than in your [local environment](#local-run-mode). You can run a function in cluster mode using the [`create`](reference-pulsar-admin.md#create-1) command.
+When you run a Pulsar Function in **cluster** mode, the function code is uploaded to a Pulsar broker and runs *alongside the broker* rather than in your [local environment](#local-run-mode). You can run a function in cluster mode using the [`create`](/tools/pulsar-admin/) command.
```bash
@@ -90,7 +90,7 @@ $ bin/pulsar-admin functions create \
### Update functions in cluster mode
-You can use the [`update`](reference-pulsar-admin.md#update-1) command to update a Pulsar Function running in cluster mode. The following command updates the function created in the [cluster mode](#cluster-mode) section.
+You can use the [`update`](/tools/pulsar-admin/) command to update a Pulsar Function running in cluster mode. The following command updates the function created in the [cluster mode](#cluster-mode) section.
```bash
@@ -106,7 +106,7 @@ $ bin/pulsar-admin functions update \
Pulsar Functions run as processes or threads, which are called **instances**. When you run a Pulsar Function, it runs as a single instance by default. With one localrun command, you can only run a single instance of a function. If you want to run multiple instances, you can use localrun command multiple times.
-When you create a function, you can specify the *parallelism* of a function (the number of instances to run). You can set the parallelism factor using the `--parallelism` flag of the [`create`](reference-pulsar-admin.md#functions-create) command.
+When you create a function, you can specify the *parallelism* of a function (the number of instances to run). You can set the parallelism factor using the `--parallelism` flag of the [`create`](r/tools/pulsar-admin/) command.
```bash
@@ -116,7 +116,7 @@ $ bin/pulsar-admin functions create \
```
-You can adjust the parallelism of an already created function using the [`update`](reference-pulsar-admin.md#update-1) interface.
+You can adjust the parallelism of an already created function using the [`update`](/tools/pulsar-admin/) interface.
```bash
@@ -199,7 +199,7 @@ When you have a ready to use package URL, you can create the function with packa
If a Pulsar Function is running in [cluster mode](#cluster-mode), you can **trigger** it at any time using the command line. Triggering a function means that you send a message with a specific value to the function and get the function output (if any) via the command line.
-> Triggering a function is to invoke a function by producing a message on one of the input topics. With the [`pulsar-admin functions trigger`](reference-pulsar-admin.md#trigger) command, you can send messages to functions without using the [`pulsar-client`](reference-cli-tools.md#pulsar-client) tool or a language-specific client library.
+> Triggering a function is to invoke a function by producing a message on one of the input topics. With the [`pulsar-admin functions trigger`](/tools/pulsar-admin/) command, you can send messages to functions without using the [`pulsar-client`](reference-cli-tools.md#pulsar-client) tool or a language-specific client library.
To learn how to trigger a function, you can start with Python function that returns a simple string based on the input.
diff --git a/site2/website-next/docs/functions-develop.md b/site2/website-next/docs/functions-develop.md
index c5a09bc6143..3766fe89170 100644
--- a/site2/website-next/docs/functions-develop.md
+++ b/site2/website-next/docs/functions-develop.md
@@ -342,7 +342,7 @@ To apply this customized SerDe to a particular Pulsar Function, you need to:
* Package the `Tweet` and `TweetSerde` classes into a JAR.
* Specify a path to the JAR and SerDe class name when deploying the function.
-The following is an example of [`create`](reference-pulsar-admin.md#create-1) operation.
+The following is an example of [`create`](/tools/pulsar-admin/) operation.
```bash
diff --git a/site2/website-next/docs/functions-overview.md b/site2/website-next/docs/functions-overview.md
index c84be36c588..25e9bd7a56e 100644
--- a/site2/website-next/docs/functions-overview.md
+++ b/site2/website-next/docs/functions-overview.md
@@ -176,7 +176,7 @@ Delivery semantics | Description
### Apply processing guarantees to a function
-You can set the processing guarantees for a Pulsar Function when you create the Function. The following [`pulsar-function create`](reference-pulsar-admin.md#create-1) command creates a function with effectively-once guarantees applied.
+You can set the processing guarantees for a Pulsar Function when you create the Function. The following [`pulsar-function create`](/tools/pulsar-admin/) command creates a function with effectively-once guarantees applied.
```bash
@@ -196,7 +196,7 @@ The available options for `--processing-guarantees` are:
> By default, Pulsar Functions provide at-least-once delivery guarantees. So if you create a function without supplying a value for the `--processingGuarantees` flag, the function provides at-least-once guarantees.
### Update the processing guarantees of a function
-You can change the processing guarantees applied to a function using the [`update`](reference-pulsar-admin.md#update-1) command. The following is an example.
+You can change the processing guarantees applied to a function using the [`update`](/tools/pulsar-admin/) command. The following is an example.
```bash
diff --git a/site2/website-next/docs/functions-package.md b/site2/website-next/docs/functions-package.md
index 79ce8b6ac2f..68b485c6803 100644
--- a/site2/website-next/docs/functions-package.md
+++ b/site2/website-next/docs/functions-package.md
@@ -494,4 +494,4 @@ If you want to start a function in cluster mode, replace `localrun` with `create
```
-For information about parameters on `--classname`, `--jar`, `--py`, `--go`, `--inputs`, run the command `./bin/pulsar-admin functions` or see [here](reference-pulsar-admin.md#functions).
\ No newline at end of file
+For information about parameters on `--classname`, `--jar`, `--py`, `--go`, `--inputs`, run the command `./bin/pulsar-admin functions` or see [here](/tools/pulsar-admin/).
\ No newline at end of file
diff --git a/site2/website-next/docs/functions-worker.md b/site2/website-next/docs/functions-worker.md
index 3bab3a5b0c2..e790196d917 100644
--- a/site2/website-next/docs/functions-worker.md
+++ b/site2/website-next/docs/functions-worker.md
@@ -337,7 +337,7 @@ Hence you need to configure your `pulsar-admin` to use the right service URL acc
In order to address this inconvenience, you can start a proxy cluster for routing the admin rest requests accordingly. Hence you will have one central entry point for your admin service.
-If you already have a proxy cluster, continue reading. If you haven't setup a proxy cluster before, you can follow the [instructions](http://pulsar.apache.org/docs/en/administration-proxy/) to
+If you already have a proxy cluster, continue reading. If you haven't setup a proxy cluster before, you can follow the [instructions](/docs/en/administration-proxy/) to
start proxies.
diff --git a/site2/website-next/docs/getting-started-helm.md b/site2/website-next/docs/getting-started-helm.md
index b72e3f5b6fe..e3f6907aa75 100644
--- a/site2/website-next/docs/getting-started-helm.md
+++ b/site2/website-next/docs/getting-started-helm.md
@@ -313,7 +313,7 @@ brokerServiceUrl=pulsar://127.0.0.1:61854/
Then you can proceed with the following steps:
-1. Download the Apache Pulsar tarball from the [downloads page](https://pulsar.apache.org/en/download/).
+1. Download the Apache Pulsar tarball from the [downloads page](/en/download/).
2. Decompress the tarball based on your download file.
diff --git a/site2/website-next/docs/getting-started-pulsar.md b/site2/website-next/docs/getting-started-pulsar.md
index 560c8c1bd7c..ae525bcab8d 100644
--- a/site2/website-next/docs/getting-started-pulsar.md
+++ b/site2/website-next/docs/getting-started-pulsar.md
@@ -18,7 +18,7 @@ There are a few major changes that you should be aware of, as they may significa
### Properties versus tenants
-Previously, Pulsar had a concept of properties. A property is essentially the exact same thing as a tenant, so the "property" terminology has been removed in version 2.0. The [`pulsar-admin properties`](reference-pulsar-admin.md#pulsar-admin) command-line interface, for example, has been replaced with the [`pulsar-admin tenants`](reference-pulsar-admin.md#pulsar-admin-tenants) interface. In some cases the properties terminology is still used but is now considered deprecated and will be r [...]
+Previously, Pulsar had a concept of properties. A property is essentially the exact same thing as a tenant, so the "property" terminology has been removed in version 2.0. The [`pulsar-admin properties`](/tools/pulsar-admin/) command-line interface, for example, has been replaced with the [`pulsar-admin tenants`](/tools/pulsar-admin/) interface. In some cases the properties terminology is still used but is now considered deprecated and will be removed entirely in a future release.
### Topic names
diff --git a/site2/website-next/docs/getting-started-standalone.md b/site2/website-next/docs/getting-started-standalone.md
index d8c67f9c1be..35ab327c945 100644
--- a/site2/website-next/docs/getting-started-standalone.md
+++ b/site2/website-next/docs/getting-started-standalone.md
@@ -63,7 +63,7 @@ The Pulsar binary package initially contains the following directories:
Directory | Contains
:---------|:--------
-`bin` | Pulsar's command-line tools, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/).
+`bin` | Pulsar's command-line tools, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](/tools/pulsar-admin/).
`conf` | Configuration files for Pulsar, including [broker configuration](reference-configuration.md#broker) and more.<br />**Note:** Pulsar standalone uses RocksDB as the local metadata store and its configuration file path [`metadataStoreConfigPath`](reference-configuration) is configurable in the `standalone.conf` file. For more information about the configurations of RocksDB, see [here](https://github.com/facebook/rocksdb/blob/main/examples/rocksdb_option_file_example.ini) and relate [...]
`examples` | A Java JAR file containing [Pulsar Functions](functions-overview) example.
`instances` | Artifacts created for [Pulsar Functions](functions-overview).
@@ -203,7 +203,7 @@ If you have started Pulsar successfully, you will see `INFO`-level log messages
:::
-You can also run the service as a background process using the `bin/pulsar-daemon start standalone` command. For more information, see [pulsar-daemon](https://pulsar.apache.org/docs/en/reference-cli-tools/#pulsar-daemon).
+You can also run the service as a background process using the `bin/pulsar-daemon start standalone` command. For more information, see [pulsar-daemon](/docs/en/reference-cli-tools/#pulsar-daemon).
>
> * By default, there is no encryption, authentication, or authorization configured. Apache Pulsar can be accessed from remote server without any authorization. Please do check [Security Overview](security-overview) document to secure your deployment.
>
@@ -262,7 +262,7 @@ Press `Ctrl+C` to stop a local standalone Pulsar.
:::tip
If the service runs as a background process using the `bin/pulsar-daemon start standalone` command, then use the `bin/pulsar-daemon stop standalone` command to stop the service.
-For more information, see [pulsar-daemon](https://pulsar.apache.org/docs/en/reference-cli-tools/#pulsar-daemon).
+For more information, see [pulsar-daemon](/docs/en/reference-cli-tools/#pulsar-daemon).
:::
diff --git a/site2/website-next/docs/io-cli.md b/site2/website-next/docs/io-cli.md
index 2a019f2aed6..afd11689022 100644
--- a/site2/website-next/docs/io-cli.md
+++ b/site2/website-next/docs/io-cli.md
@@ -8,7 +8,7 @@ sidebar_label: "CLI"
**Important**
-This page is deprecated and not updated anymore. For the latest and complete information about `Pulsar-admin`, including commands, flags, descriptions, and more, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+This page is deprecated and not updated anymore. For the latest and complete information about `Pulsar-admin`, including commands, flags, descriptions, and more, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
diff --git a/site2/website-next/docs/io-debug.md b/site2/website-next/docs/io-debug.md
index 97678e5edc7..dbde5ab82d4 100644
--- a/site2/website-next/docs/io-debug.md
+++ b/site2/website-next/docs/io-debug.md
@@ -379,7 +379,7 @@ Use the `topics stats` command to get the stats for a topic and its connected pr
:::tip
-For more information about the `topic stats` command, see [`topic stats`](http://pulsar.apache.org/docs/en/pulsar-admin/#stats-1).
+For more information about the `topic stats` command, see [`topic stats`](/docs/en/pulsar-admin/#stats-1).
:::
diff --git a/site2/website-next/docs/io-kafka-source.md b/site2/website-next/docs/io-kafka-source.md
index 69185c8d75e..a20996de7fa 100644
--- a/site2/website-next/docs/io-kafka-source.md
+++ b/site2/website-next/docs/io-kafka-source.md
@@ -212,7 +212,7 @@ This example explains how to create a Kafka source connector in an on-premises c
```
-2. Reload all [built-in connectors](https://pulsar.apache.org/docs/en/next/io-connectors/).
+2. Reload all [built-in connectors](/io-connectors.md).
```
@@ -228,7 +228,7 @@ This example explains how to create a Kafka source connector in an on-premises c
```
-4. Create a Kafka source connector on a Pulsar cluster using the [`pulsar-admin sources create`](http://pulsar.apache.org/tools/pulsar-admin/2.11.0-SNAPSHOT/#-em-create-em--14) command.
+4. Create a Kafka source connector on a Pulsar cluster using the [`pulsar-admin sources create`](/tools/pulsar-admin/2.11.0-SNAPSHOT/#-em-create-em--14) command.
```
diff --git a/site2/website-next/docs/io-overview.md b/site2/website-next/docs/io-overview.md
index 4447eea8ade..640c38a4e7a 100644
--- a/site2/website-next/docs/io-overview.md
+++ b/site2/website-next/docs/io-overview.md
@@ -157,7 +157,7 @@ For more information about the options of `pulsar-admin sinks update`, see [here
## Work with connector
-You can manage Pulsar connectors (for example, create, update, start, stop, restart, reload, delete and perform other operations on connectors) via the `Connector Admin CLI` with sources and sinks subcommands. For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+You can manage Pulsar connectors (for example, create, update, start, stop, restart, reload, delete and perform other operations on connectors) via the `Connector Admin CLI` with sources and sinks subcommands. For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
Connectors (sources and sinks) and Functions are components of instances, and they all run on Functions workers. When managing a source, sink or function via the `Connector Admin CLI` or [Functions Admin CLI](functions-cli), an instance is started on a worker. For more information, see [Functions worker](functions-worker.md#run-functions-worker-separately).
diff --git a/site2/website-next/docs/io-quickstart.md b/site2/website-next/docs/io-quickstart.md
index da32882ca52..37f8bc4a403 100644
--- a/site2/website-next/docs/io-quickstart.md
+++ b/site2/website-next/docs/io-quickstart.md
@@ -239,7 +239,7 @@ For more information, see [Cassandra sink connector](io-cassandra-sink).
### Create a Cassandra sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to create a sink connector and perform other operations on them.
Run the following command to create a Cassandra sink connector with sink type _cassandra_ and the config file _examples/cassandra-sink.yml_ created previously.
@@ -266,7 +266,7 @@ as a Pulsar Function and writes the messages produced in the topic _test_cassand
### Inspect a Cassandra sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to monitor a connector and perform other operations on it.
* Get the information of a Cassandra sink.
@@ -430,7 +430,7 @@ to monitor a connector and perform other operations on it.
### Delete a Cassandra Sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to delete a connector and perform other operations on it.
```bash
@@ -614,7 +614,7 @@ In this section, you need to configure a JDBC sink connector.
### Create a JDBC sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to create a sink connector and perform other operations on it.
This example creates a sink connector and specifies the desired information.
@@ -646,7 +646,7 @@ This sink connector runs as a Pulsar Function and writes the messages produced i
:::tip
-For more information about `pulsar-admin sinks create options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about `pulsar-admin sinks create options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
@@ -660,7 +660,7 @@ Created successfully
### Inspect a JDBC sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to monitor a connector and perform other operations on it.
* List all running JDBC sink(s).
@@ -675,7 +675,7 @@ to monitor a connector and perform other operations on it.
:::tip
- For more information about `pulsar-admin sinks list options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+ For more information about `pulsar-admin sinks list options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
@@ -702,7 +702,7 @@ to monitor a connector and perform other operations on it.
:::tip
- For more information about `pulsar-admin sinks get options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+ For more information about `pulsar-admin sinks get options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
@@ -747,7 +747,7 @@ to monitor a connector and perform other operations on it.
:::tip
- For more information about `pulsar-admin sinks status options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+ For more information about `pulsar-admin sinks status options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
@@ -780,7 +780,7 @@ to monitor a connector and perform other operations on it.
### Stop a JDBC sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to stop a connector and perform other operations on it.
```bash
@@ -794,7 +794,7 @@ $ bin/pulsar-admin sinks stop \
:::tip
-For more information about `pulsar-admin sinks stop options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about `pulsar-admin sinks stop options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
@@ -808,7 +808,7 @@ Stopped successfully
### Restart a JDBC sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to restart a connector and perform other operations on it.
```bash
@@ -822,7 +822,7 @@ $ bin/pulsar-admin sinks restart \
:::tip
-For more information about `pulsar-admin sinks restart options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about `pulsar-admin sinks restart options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
@@ -838,13 +838,13 @@ Started successfully
* Optionally, you can run a standalone sink connector using `pulsar-admin sinks localrun options`.
Note that `pulsar-admin sinks localrun options` **runs a sink connector locally**, while `pulsar-admin sinks start options` **starts a sink connector in a cluster**.
-* For more information about `pulsar-admin sinks localrun options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+* For more information about `pulsar-admin sinks localrun options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
### Update a JDBC sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to update a connector and perform other operations on it.
This example updates the parallelism of the _pulsar-postgres-jdbc-sink_ sink connector to 2.
@@ -859,7 +859,7 @@ $ bin/pulsar-admin sinks update \
:::tip
-For more information about `pulsar-admin sinks update options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about `pulsar-admin sinks update options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
@@ -912,7 +912,7 @@ The result shows that the parallelism is 2.
### Delete a JDBC sink
-You can use the [Connector Admin CLI](https://pulsar.apache.org/tools/pulsar-admin/)
+You can use the [Connector Admin CLI](/tools/pulsar-admin/)
to delete a connector and perform other operations on it.
This example deletes the _pulsar-postgres-jdbc-sink_ sink connector.
@@ -928,7 +928,7 @@ $ bin/pulsar-admin sinks delete \
:::tip
-For more information about `pulsar-admin sinks delete options`, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about `pulsar-admin sinks delete options`, see [Pulsar admin docs](/tools/pulsar-admin/).
:::
diff --git a/site2/website-next/docs/io-use.md b/site2/website-next/docs/io-use.md
index cc871f191b1..b5c6fc1d350 100644
--- a/site2/website-next/docs/io-use.md
+++ b/site2/website-next/docs/io-use.md
@@ -136,7 +136,7 @@ $ pulsar-admin sources reload
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
#### Sink
@@ -148,7 +148,7 @@ $ pulsar-admin sinks reload
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
### `available`
@@ -207,7 +207,7 @@ $ pulsar-admin sources create options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -239,7 +239,7 @@ Send a `POST` request to this endpoint: {@inject: endpoint|POST|/admin/v3/source
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`createSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#createSource-SourceConfig-java.lang.String-).
+ For more information, see [`createSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#createSource-SourceConfig-java.lang.String-).
* Create a source connector using a **remote file** with a URL from which fun-pkg can be downloaded.
@@ -272,7 +272,7 @@ Send a `POST` request to this endpoint: {@inject: endpoint|POST|/admin/v3/source
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`createSourceWithUrl`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#createSourceWithUrl-SourceConfig-java.lang.String-).
+ For more information, see [`createSourceWithUrl`](/api/admin/org/apache/pulsar/client/admin/Source.html#createSourceWithUrl-SourceConfig-java.lang.String-).
</TabItem>
@@ -298,7 +298,7 @@ $ pulsar-admin sinks create options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -330,7 +330,7 @@ Send a `POST` request to this endpoint: {@inject: endpoint|POST|/admin/v3/sinks/
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`createSink`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#createSink-SinkConfig-java.lang.String-).
+ For more information, see [`createSink`](/api/admin/org/apache/pulsar/client/admin/Sink.html#createSink-SinkConfig-java.lang.String-).
* Create a sink connector using a **remote file** with a URL from which fun-pkg can be downloaded.
@@ -363,7 +363,7 @@ Send a `POST` request to this endpoint: {@inject: endpoint|POST|/admin/v3/sinks/
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`createSinkWithUrl`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#createSinkWithUrl-SinkConfig-java.lang.String-).
+ For more information, see [`createSinkWithUrl`](/api/admin/org/apache/pulsar/client/admin/Sink.html#createSinkWithUrl-SinkConfig-java.lang.String-).
</TabItem>
@@ -393,7 +393,7 @@ $ pulsar-admin sources start options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -430,7 +430,7 @@ $ pulsar-admin sinks start options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -471,7 +471,7 @@ $ pulsar-admin sources localrun options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
@@ -497,7 +497,7 @@ $ pulsar-admin sinks localrun options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
</Tabs>
@@ -536,7 +536,7 @@ $ pulsar-admin sources get options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -623,7 +623,7 @@ Exception name | Description
`PulsarAdminException.NotFoundException` | Cluster doesn't exist
`PulsarAdminException` | Unexpected error
-For more information, see [`getSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#getSource-java.lang.String-java.lang.String-java.lang.String-).
+For more information, see [`getSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#getSource-java.lang.String-java.lang.String-java.lang.String-).
</TabItem>
@@ -649,7 +649,7 @@ $ pulsar-admin sinks get options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -729,7 +729,7 @@ Name| Description
`namespace` | Namespace name
`sink` | Sink name
-For more information, see [`getSink`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#getSink-java.lang.String-java.lang.String-java.lang.String-).
+For more information, see [`getSink`](/api/admin/org/apache/pulsar/client/admin/Sink.html#getSink-java.lang.String-java.lang.String-java.lang.String-).
</TabItem>
@@ -759,7 +759,7 @@ $ pulsar-admin sources list options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -792,7 +792,7 @@ Exception name | Description
`PulsarAdminException.NotAuthorizedException` | You don't have the admin permission
`PulsarAdminException` | Unexpected error
-For more information, see [`listSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#listSources-java.lang.String-java.lang.String-).
+For more information, see [`listSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#listSources-java.lang.String-java.lang.String-).
</TabItem>
@@ -818,7 +818,7 @@ $ pulsar-admin sinks list options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -851,7 +851,7 @@ Exception name | Description
`PulsarAdminException.NotAuthorizedException` | You don't have the admin permission
`PulsarAdminException` | Unexpected error
-For more information, see [`listSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#listSinks-java.lang.String-java.lang.String-).
+For more information, see [`listSource`](/api/admin/org/apache/pulsar/client/admin/Sink.html#listSinks-java.lang.String-java.lang.String-).
</TabItem>
@@ -881,7 +881,7 @@ $ pulsar-admin sources status options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -922,7 +922,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
`PulsarAdminException` | Unexpected error
- For more information, see [`getSourceStatus`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#getSource-java.lang.String-java.lang.String-java.lang.String-).
+ For more information, see [`getSourceStatus`](/api/admin/org/apache/pulsar/client/admin/Source.html#getSource-java.lang.String-java.lang.String-java.lang.String-).
* Gets the current status of a **specified** source connector.
@@ -951,7 +951,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
`PulsarAdminException` | Unexpected error
- For more information, see [`getSourceStatus`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#getSourceStatus-java.lang.String-java.lang.String-java.lang.String-int-).
+ For more information, see [`getSourceStatus`](/api/admin/org/apache/pulsar/client/admin/Source.html#getSourceStatus-java.lang.String-java.lang.String-java.lang.String-int-).
</TabItem>
@@ -977,7 +977,7 @@ $ pulsar-admin sinks status options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1018,7 +1018,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
`PulsarAdminException` | Unexpected error
- For more information, see [`getSinkStatus`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#getSinkStatus-java.lang.String-java.lang.String-java.lang.String-).
+ For more information, see [`getSinkStatus`](/api/admin/org/apache/pulsar/client/admin/Sink.html#getSinkStatus-java.lang.String-java.lang.String-java.lang.String-).
* Gets the current status of a **specified** source connector.
@@ -1047,7 +1047,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
`PulsarAdminException` | Unexpected error
- For more information, see [`getSinkStatusWithInstanceID`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#getSinkStatus-java.lang.String-java.lang.String-java.lang.String-int-).
+ For more information, see [`getSinkStatusWithInstanceID`](/api/admin/org/apache/pulsar/client/admin/Sink.html#getSinkStatus-java.lang.String-java.lang.String-java.lang.String-int-).
</TabItem>
@@ -1079,7 +1079,7 @@ $ pulsar-admin sources update options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1113,7 +1113,7 @@ Send a `PUT` request to this endpoint: {@inject: endpoint|PUT|/admin/v3/sources/
| `PulsarAdminException.NotFoundException` | Cluster doesn't exist
| `PulsarAdminException` | Unexpected error
- For more information, see [`updateSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#updateSource-SourceConfig-java.lang.String-).
+ For more information, see [`updateSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#updateSource-SourceConfig-java.lang.String-).
* Update a source connector using a **remote file** with a URL from which fun-pkg can be downloaded.
@@ -1148,7 +1148,7 @@ Send a `PUT` request to this endpoint: {@inject: endpoint|PUT|/admin/v3/sources/
| `PulsarAdminException.NotFoundException` | Cluster doesn't exist
| `PulsarAdminException` | Unexpected error
-For more information, see [`createSourceWithUrl`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#updateSourceWithUrl-SourceConfig-java.lang.String-).
+For more information, see [`createSourceWithUrl`](/api/admin/org/apache/pulsar/client/admin/Source.html#updateSourceWithUrl-SourceConfig-java.lang.String-).
</TabItem>
@@ -1174,7 +1174,7 @@ $ pulsar-admin sinks update options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1208,7 +1208,7 @@ Send a `PUT` request to this endpoint: {@inject: endpoint|PUT|/admin/v3/sinks/:t
| `PulsarAdminException.NotFoundException` | Cluster doesn't exist
| `PulsarAdminException` | Unexpected error
- For more information, see [`updateSink`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#updateSink-SinkConfig-java.lang.String-).
+ For more information, see [`updateSink`](/api/admin/org/apache/pulsar/client/admin/Sink.html#updateSink-SinkConfig-java.lang.String-).
* Update a sink connector using a **remote file** with a URL from which fun-pkg can be downloaded.
@@ -1243,7 +1243,7 @@ Send a `PUT` request to this endpoint: {@inject: endpoint|PUT|/admin/v3/sinks/:t
|`PulsarAdminException.NotFoundException` | Cluster doesn't exist
|`PulsarAdminException` | Unexpected error
-For more information, see [`updateSinkWithUrl`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#updateSinkWithUrl-SinkConfig-java.lang.String-).
+For more information, see [`updateSinkWithUrl`](/api/admin/org/apache/pulsar/client/admin/Sink.html#updateSinkWithUrl-SinkConfig-java.lang.String-).
</TabItem>
@@ -1275,7 +1275,7 @@ $ pulsar-admin sources stop options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1316,7 +1316,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`stopSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#stopSource-java.lang.String-java.lang.String-java.lang.String-).
+ For more information, see [`stopSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#stopSource-java.lang.String-java.lang.String-java.lang.String-).
* Stop a **specified** source connector.
@@ -1345,7 +1345,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`stopSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#stopSource-java.lang.String-java.lang.String-java.lang.String-int-).
+ For more information, see [`stopSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#stopSource-java.lang.String-java.lang.String-java.lang.String-int-).
</TabItem>
@@ -1371,7 +1371,7 @@ $ pulsar-admin sinks stop options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1412,7 +1412,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`stopSink`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#stopSink-java.lang.String-java.lang.String-java.lang.String-).
+ For more information, see [`stopSink`](/api/admin/org/apache/pulsar/client/admin/Sink.html#stopSink-java.lang.String-java.lang.String-java.lang.String-).
* Stop a **specified** sink connector.
@@ -1441,7 +1441,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`stopSink`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#stopSink-java.lang.String-java.lang.String-java.lang.String-int-).
+ For more information, see [`stopSink`](/api/admin/org/apache/pulsar/client/admin/Sink.html#stopSink-java.lang.String-java.lang.String-java.lang.String-int-).
</TabItem>
@@ -1473,7 +1473,7 @@ $ pulsar-admin sources restart options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1514,7 +1514,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`restartSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#restartSource-java.lang.String-java.lang.String-java.lang.String-).
+ For more information, see [`restartSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#restartSource-java.lang.String-java.lang.String-java.lang.String-).
* Restart a **specified** source connector.
@@ -1543,7 +1543,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`restartSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#restartSource-java.lang.String-java.lang.String-java.lang.String-int-).
+ For more information, see [`restartSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#restartSource-java.lang.String-java.lang.String-java.lang.String-int-).
</TabItem>
@@ -1569,7 +1569,7 @@ $ pulsar-admin sinks restart options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1610,7 +1610,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`restartSink`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#restartSink-java.lang.String-java.lang.String-java.lang.String-).
+ For more information, see [`restartSink`](/api/admin/org/apache/pulsar/client/admin/Sink.html#restartSink-java.lang.String-java.lang.String-java.lang.String-).
* Restart a **specified** sink connector.
@@ -1639,7 +1639,7 @@ For the latest and complete information, see [Pulsar admin docs](https://pulsar.
|---|---
| `PulsarAdminException` | Unexpected error
- For more information, see [`restartSink`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#restartSink-java.lang.String-java.lang.String-java.lang.String-int-).
+ For more information, see [`restartSink`](/api/admin/org/apache/pulsar/client/admin/Sink.html#restartSink-java.lang.String-java.lang.String-java.lang.String-int-).
</TabItem>
@@ -1671,7 +1671,7 @@ $ pulsar-admin sources delete options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1711,7 +1711,7 @@ void deleteSource(String tenant,
| `PulsarAdminException.PreconditionFailedException` | Cluster is not empty
| `PulsarAdminException` | Unexpected error
-For more information, see [`deleteSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Source.html#deleteSource-java.lang.String-java.lang.String-java.lang.String-).
+For more information, see [`deleteSource`](/api/admin/org/apache/pulsar/client/admin/Source.html#deleteSource-java.lang.String-java.lang.String-java.lang.String-).
</TabItem>
@@ -1737,7 +1737,7 @@ $ pulsar-admin sinks delete options
```
-For the latest and complete information, see [Pulsar admin docs](https://pulsar.apache.org/tools/pulsar-admin/).
+For the latest and complete information, see [Pulsar admin docs](/tools/pulsar-admin/).
</TabItem>
<TabItem value="REST API">
@@ -1777,7 +1777,7 @@ void deleteSink(String tenant,
| `PulsarAdminException.PreconditionFailedException` | Cluster is not empty
| `PulsarAdminException` | Unexpected error
-For more information, see [`deleteSource`](https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Sink.html#deleteSink-java.lang.String-java.lang.String-java.lang.String-).
+For more information, see [`deleteSource`](/api/admin/org/apache/pulsar/client/admin/Sink.html#deleteSink-java.lang.String-java.lang.String-java.lang.String-).
</TabItem>
diff --git a/site2/website-next/docs/kubernetes-helm.md b/site2/website-next/docs/kubernetes-helm.md
index d4353712d6d..6353bae71e4 100644
--- a/site2/website-next/docs/kubernetes-helm.md
+++ b/site2/website-next/docs/kubernetes-helm.md
@@ -313,7 +313,7 @@ brokerServiceUrl=pulsar://127.0.0.1:61854/
Then you can proceed with the following steps:
-1. Download the Apache Pulsar tarball from the [downloads page](https://pulsar.apache.org/en/download/).
+1. Download the Apache Pulsar tarball from the [downloads page](/en/download/).
2. Decompress the tarball based on your download file.
diff --git a/site2/website-next/docs/performance-pulsar-perf.md b/site2/website-next/docs/performance-pulsar-perf.md
index 3e6c5cdf616..2e8a510f840 100644
--- a/site2/website-next/docs/performance-pulsar-perf.md
+++ b/site2/website-next/docs/performance-pulsar-perf.md
@@ -10,7 +10,7 @@ The Pulsar Perf is a built-in performance test tool for Apache Pulsar. You can u
:::tip
-For the latest and complete information about `pulsar-perf`, including commands, flags, descriptions, and more, see [`pulsar-perf`](https://pulsar.apache.org/tools/pulsar-perf/) or [here](reference-cli-tools.md#pulsar-perf).
+For the latest and complete information about `pulsar-perf`, including commands, flags, descriptions, and more, see [`pulsar-perf`](/tools/pulsar-perf/) or [here](reference-cli-tools.md#pulsar-perf).
:::
@@ -76,7 +76,7 @@ For the latest and complete information about `pulsar-perf`, including commands,
:::tip
-For the latest and complete information about `pulsar-perf`, including commands, flags, descriptions, and more, see [`pulsar-perf`](https://pulsar.apache.org/tools/pulsar-perf/) or [here](reference-cli-tools.md#pulsar-perf).
+For the latest and complete information about `pulsar-perf`, including commands, flags, descriptions, and more, see [`pulsar-perf`](/tools/pulsar-perf/) or [here](reference-cli-tools.md#pulsar-perf).
:::
diff --git a/site2/website-next/docs/reference-cli-tools.md b/site2/website-next/docs/reference-cli-tools.md
index 221a273d97d..0e533e10662 100644
--- a/site2/website-next/docs/reference-cli-tools.md
+++ b/site2/website-next/docs/reference-cli-tools.md
@@ -17,7 +17,7 @@ All Pulsar command-line tools can be run from the `bin` directory of your [insta
> **Important**
>
-> - This page only shows **some frequently used commands**. For the latest information about `pulsar`, `pulsar-client`, and `pulsar-perf`, including commands, flags, descriptions, and more information, see [Pulsar tools](https://pulsar.apache.org/tools/).
+> - This page only shows **some frequently used commands**. For the latest information about `pulsar`, `pulsar-client`, and `pulsar-perf`, including commands, flags, descriptions, and more information, see [Pulsar tools](/tools/).
>
> - You can get help for any CLI tool, command, or subcommand using the `--help` flag, or `-h` for short. Here's an example:
>
diff --git a/site2/website-next/docs/reference-configuration.md b/site2/website-next/docs/reference-configuration.md
index b9c91325bcd..10c08983e79 100644
--- a/site2/website-next/docs/reference-configuration.md
+++ b/site2/website-next/docs/reference-configuration.md
@@ -243,7 +243,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated backlog size is greater
|maxUnackedMessagesPerConsumer| Max number of unacknowledged messages allowed to receive messages by a consumer on a shared subscription. Broker will stop sending messages to consumer once, this limit reaches until consumer starts acknowledging messages back. Using a value of 0, is disabling unackeMessage limit check and consumer can receive messages without any restriction |50000|
|maxUnackedMessagesPerSubscription| Max number of unacknowledged messages allowed per shared subscription. Broker will stop dispatching messages to all consumers of the subscription once this limit reaches until consumer starts acknowledging messages back and unack count reaches to limit/2. Using a value of 0, is disabling unackedMessage-limit check and dispatcher can dispatch messages without any restriction |200000|
|subscriptionRedeliveryTrackerEnabled| Enable subscription message redelivery tracker |true|
-|subscriptionExpirationTimeMinutes | How long to delete inactive subscriptions from last consuming. <br /><br />Setting this configuration to a value **greater than 0** deletes inactive subscriptions automatically.<br />Setting this configuration to **0** does not delete inactive subscriptions automatically. <br /><br /> Since this configuration takes effect on all topics, if there is even one topic whose subscriptions should not be deleted automatically, you need to set it to 0. <br />I [...]
+|subscriptionExpirationTimeMinutes | How long to delete inactive subscriptions from last consuming. <br /><br />Setting this configuration to a value **greater than 0** deletes inactive subscriptions automatically.<br />Setting this configuration to **0** does not delete inactive subscriptions automatically. <br /><br /> Since this configuration takes effect on all topics, if there is even one topic whose subscriptions should not be deleted automatically, you need to set it to 0. <br />I [...]
|maxConcurrentLookupRequest| Max number of concurrent lookup request broker allows to throttle heavy incoming lookup traffic |50000|
|maxConcurrentTopicLoadRequest| Max number of concurrent topic loading request broker allows to control number of zk-operations |5000|
|authenticationEnabled| Enable authentication |false|
diff --git a/site2/website-next/docs/reference-connector-admin.md b/site2/website-next/docs/reference-connector-admin.md
index ec2005c78f2..471e5214f1d 100644
--- a/site2/website-next/docs/reference-connector-admin.md
+++ b/site2/website-next/docs/reference-connector-admin.md
@@ -6,6 +6,6 @@ sidebar_label: "Connector Admin CLI"
> **Important**
>
-> For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
+> For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](/tools/pulsar-admin/).
>
diff --git a/site2/website-next/docs/reference-pulsar-admin.md b/site2/website-next/docs/reference-pulsar-admin.md
index af179707872..d5ae12bbd27 100644
--- a/site2/website-next/docs/reference-pulsar-admin.md
+++ b/site2/website-next/docs/reference-pulsar-admin.md
@@ -6,7 +6,7 @@ sidebar_label: "Pulsar Admin CLI"
> **Important**
>
-> This page is deprecated and not updated anymore. For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/)
+> This page is deprecated and not updated anymore. For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more, see [Pulsar admin doc](/tools/pulsar-admin/)
The `pulsar-admin` tool enables you to manage Pulsar installations, including clusters, brokers, namespaces, tenants, and more.
diff --git a/site2/website-next/docs/reference-rest-api-overview.md b/site2/website-next/docs/reference-rest-api-overview.md
index 4bdcf23483a..8e3d410112b 100644
--- a/site2/website-next/docs/reference-rest-api-overview.md
+++ b/site2/website-next/docs/reference-rest-api-overview.md
@@ -10,9 +10,9 @@ Pulsar provides a variety of REST APIs that enable you to interact with Pulsar t
| REST API category | Description |
| --- | --- |
-| [Admin](https://pulsar.apache.org/admin-rest-api/?version=master) | REST APIs for administrative operations.|
-| [Functions](https://pulsar.apache.org/functions-rest-api/?version=master) | REST APIs for function-specific operations.|
-| [Sources](https://pulsar.apache.org/source-rest-api/?version=master) | REST APIs for source-specific operations.|
-| [Sinks](https://pulsar.apache.org/sink-rest-api/?version=master) | REST APIs for sink-specific operations.|
-| [Packages](https://pulsar.apache.org/packages-rest-api/?version=master) | REST APIs for package-specific operations. A package can be a group of functions, sources, and sinks.|
+| [Admin](/admin-rest-api/?version=master) | REST APIs for administrative operations.|
+| [Functions](/functions-rest-api/?version=master) | REST APIs for function-specific operations.|
+| [Sources](/source-rest-api/?version=master) | REST APIs for source-specific operations.|
+| [Sinks](/sink-rest-api/?version=master) | REST APIs for sink-specific operations.|
+| [Packages](/packages-rest-api/?version=master) | REST APIs for package-specific operations. A package can be a group of functions, sources, and sinks.|
diff --git a/site2/website-next/docs/schema-manage.md b/site2/website-next/docs/schema-manage.md
index 072078dd582..1f7745abf44 100644
--- a/site2/website-next/docs/schema-manage.md
+++ b/site2/website-next/docs/schema-manage.md
@@ -159,8 +159,8 @@ To manage schemas, you can use one of the following methods.
| Method | Description |
| --- | --- |
-| **Admin CLI**<li></li> | You can use the `pulsar-admin` tool to manage Pulsar schemas, brokers, clusters, sources, sinks, topics, tenants and so on. For more information about how to use the `pulsar-admin` tool, see [here](reference-pulsar-admin). |
-| **REST API**<li></li> | Pulsar exposes schema related management API in Pulsar’s admin RESTful API. You can access the admin RESTful endpoint directly to manage schemas. For more information about how to use the Pulsar REST API, see [here](http://pulsar.apache.org/admin-rest-api/). |
+| **Admin CLI**<li></li> | You can use the `pulsar-admin` tool to manage Pulsar schemas, brokers, clusters, sources, sinks, topics, tenants and so on. For more information about how to use the `pulsar-admin` tool, see [here](/tools/pulsar-admin/). |
+| **REST API**<li></li> | Pulsar exposes schema related management API in Pulsar’s admin RESTful API. You can access the admin RESTful endpoint directly to manage schemas. For more information about how to use the Pulsar REST API, see [here](/admin-rest-api/). |
| **Java Admin API**<li></li> | Pulsar provides Java admin library. |
### Upload a schema
@@ -661,7 +661,7 @@ To set a schema compatibility check strategy at the topic level, use one of the
<TabItem value="Admin CLI">
-Use the [`pulsar-admin topicPolicies set-schema-compatibility-strategy`](https://pulsar.apache.org/tools/pulsar-admin/) command.
+Use the [`pulsar-admin topicPolicies set-schema-compatibility-strategy`](/tools/pulsar-admin/) command.
```shell
@@ -707,7 +707,7 @@ To get the topic-level schema compatibility check strategy, use one of the follo
<TabItem value="Admin CLI">
-Use the [`pulsar-admin topicPolicies get-schema-compatibility-strategy`](https://pulsar.apache.org/tools/pulsar-admin/) command.
+Use the [`pulsar-admin topicPolicies get-schema-compatibility-strategy`](/tools/pulsar-admin/) command.
```shell
@@ -757,7 +757,7 @@ To remove the topic-level schema compatibility check strategy, use one of the fo
<TabItem value="Admin CLI">
-Use the [`pulsar-admin topicPolicies remove-schema-compatibility-strategy`](https://pulsar.apache.org/tools/pulsar-admin/) command.
+Use the [`pulsar-admin topicPolicies remove-schema-compatibility-strategy`](/tools/pulsar-admin/) command.
```shell
@@ -806,7 +806,7 @@ You can set schema compatibility check strategy at namespace level using one of
<TabItem value="Admin CLI">
-Use the [`pulsar-admin namespaces set-schema-compatibility-strategy`](https://pulsar.apache.org/tools/pulsar-admin/) command.
+Use the [`pulsar-admin namespaces set-schema-compatibility-strategy`](/tools/pulsar-admin/) command.
```shell
@@ -822,7 +822,7 @@ Send a `PUT` request to this endpoint: {@inject: endpoint|PUT|/admin/v2/namespac
</TabItem>
<TabItem value="Java Admin CLI">
-Use the [`setSchemaCompatibilityStrategy`](https://pulsar.apache.org/api/admin/)method.
+Use the [`setSchemaCompatibilityStrategy`](/api/admin/)method.
```java
diff --git a/site2/website-next/docs/security-athenz.md b/site2/website-next/docs/security-athenz.md
index ba27ba43eb9..6a425290844 100644
--- a/site2/website-next/docs/security-athenz.md
+++ b/site2/website-next/docs/security-athenz.md
@@ -75,7 +75,7 @@ For more information on Pulsar client authentication using Athenz, see the follo
## Configure CLI tools for Athenz
-[Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-pulsar-admin), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
+[Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](/tools/pulsar-admin/), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
You need to add the following authentication parameters to the `conf/client.conf` config file to use Athenz with CLI tools of Pulsar:
diff --git a/site2/website-next/docs/security-authorization.md b/site2/website-next/docs/security-authorization.md
index d9d33665d06..61b44b65df8 100644
--- a/site2/website-next/docs/security-authorization.md
+++ b/site2/website-next/docs/security-authorization.md
@@ -58,7 +58,7 @@ superUserRoles=my-super-user-1,my-super-user-2,my-proxy-role
Pulsar [instance](reference-terminology.md#instance) administrators or some kind of self-service portal typically provisions a Pulsar [tenant](reference-terminology.md#tenant).
-You can manage tenants using the [`pulsar-admin`](reference-pulsar-admin) tool.
+You can manage tenants using the [`pulsar-admin`](/tools/pulsar-admin/) tool.
### Create a new tenant
diff --git a/site2/website-next/docs/security-extending.md b/site2/website-next/docs/security-extending.md
index 3d3fde6e486..4cdc9bad785 100644
--- a/site2/website-next/docs/security-extending.md
+++ b/site2/website-next/docs/security-extending.md
@@ -26,8 +26,8 @@ PulsarClient client = PulsarClient.builder()
```
You can implement 2 interfaces on the client side:
- * [`Authentication`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/Authentication.html)
- * [`AuthenticationDataProvider`](http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/AuthenticationDataProvider.html)
+ * [`Authentication`](/api/client/org/apache/pulsar/client/api/Authentication.html)
+ * [`AuthenticationDataProvider`](/api/client/org/apache/pulsar/client/api/AuthenticationDataProvider.html)
This in turn requires you to provide the client credentials in the form of `org.apache.pulsar.client.api.AuthenticationDataProvider` and also leaves the chance to return different kinds of authentication token for different types of connection or by passing a certificate chain to use for TLS.
diff --git a/site2/website-next/docs/security-jwt.md b/site2/website-next/docs/security-jwt.md
index 4160d16d0e2..9ce352b6d49 100644
--- a/site2/website-next/docs/security-jwt.md
+++ b/site2/website-next/docs/security-jwt.md
@@ -35,7 +35,7 @@ Application specifies the token when you create the client instance. An alternat
### CLI Tools
-[Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-pulsar-admin), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
+[Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](/tools/pulsar-admin/), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
You need to add the following parameters to that file to use the token authentication with CLI tools of Pulsar:
diff --git a/site2/website-next/docs/security-tls-authentication.md b/site2/website-next/docs/security-tls-authentication.md
index e6921bd4418..947de576b57 100644
--- a/site2/website-next/docs/security-tls-authentication.md
+++ b/site2/website-next/docs/security-tls-authentication.md
@@ -46,7 +46,7 @@ $ openssl req -config openssl.cnf \
:::note
-If openssl.cnf is not specified, read [Certificate authority](http://pulsar.apache.org/docs/en/security-tls-transport/#certificate-authority) to get the openssl.cnf.
+If openssl.cnf is not specified, read [Certificate authority](/docs/en/security-tls-transport/#certificate-authority) to get the openssl.cnf.
:::
@@ -122,7 +122,7 @@ When you use TLS authentication, client connects via TLS transport. You need to
### CLI tools
-[Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-pulsar-admin), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
+[Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](/tools/pulsar-admin/), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
You need to add the following parameters to that file to use TLS authentication with the CLI tools of Pulsar:
diff --git a/site2/website-next/docs/standalone.md b/site2/website-next/docs/standalone.md
index 9e5d8dc571c..a7b7f8cb69b 100644
--- a/site2/website-next/docs/standalone.md
+++ b/site2/website-next/docs/standalone.md
@@ -62,7 +62,7 @@ The Pulsar binary package initially contains the following directories:
Directory | Contains
:---------|:--------
-`bin` | Pulsar's command-line tools, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/).
+`bin` | Pulsar's command-line tools, such as [`pulsar`](reference-cli-tools.md#pulsar) and [`pulsar-admin`](/tools/pulsar-admin/).
`conf` | Configuration files for Pulsar, including [broker configuration](reference-configuration.md#broker) and more.<br />**Note:** Pulsar standalone uses RocksDB as the local metadata store and its configuration file path [`metadataStoreConfigPath`](reference-configuration) is configurable in the `standalone.conf` file. For more information about the configurations of RocksDB, see [here](https://github.com/facebook/rocksdb/blob/main/examples/rocksdb_option_file_example.ini) and relate [...]
`examples` | A Java JAR file containing [Pulsar Functions](functions-overview) example.
`instances` | Artifacts created for [Pulsar Functions](functions-overview).
@@ -202,7 +202,7 @@ If you have started Pulsar successfully, you will see `INFO`-level log messages
:::
-You can also run the service as a background process using the `bin/pulsar-daemon start standalone` command. For more information, see [pulsar-daemon](https://pulsar.apache.org/docs/en/reference-cli-tools/#pulsar-daemon).
+You can also run the service as a background process using the `bin/pulsar-daemon start standalone` command. For more information, see [pulsar-daemon](/docs/en/reference-cli-tools/#pulsar-daemon).
>
> * By default, there is no encryption, authentication, or authorization configured. Apache Pulsar can be accessed from remote server without any authorization. Please do check [Security Overview](security-overview) document to secure your deployment.
>
@@ -261,7 +261,7 @@ Press `Ctrl+C` to stop a local standalone Pulsar.
:::tip
If the service runs as a background process using the `bin/pulsar-daemon start standalone` command, then use the `bin/pulsar-daemon stop standalone` command to stop the service.
-For more information, see [pulsar-daemon](https://pulsar.apache.org/docs/en/reference-cli-tools/#pulsar-daemon).
+For more information, see [pulsar-daemon](/docs/en/reference-cli-tools/#pulsar-daemon).
:::
diff --git a/site2/website-next/docs/tiered-storage-aliyun.md b/site2/website-next/docs/tiered-storage-aliyun.md
index 48db44aebca..e24dc9b3332 100644
--- a/site2/website-next/docs/tiered-storage-aliyun.md
+++ b/site2/website-next/docs/tiered-storage-aliyun.md
@@ -18,9 +18,9 @@ Follow the steps below to install the Aliyun OSS offloader.
This example uses Pulsar 2.8.0.
-1. Download the Pulsar tarball, see [here](https://pulsar.apache.org/docs/en/standalone/#install-pulsar-using-binary-release).
+1. Download the Pulsar tarball, see [here](/docs/en/standalone/#install-pulsar-using-binary-release).
-2. Download and untar the Pulsar offloaders package, then copy the Pulsar offloaders as `offloaders` in the Pulsar directory, see [here](https://pulsar.apache.org/docs/en/standalone/#install-tiered-storage-offloaders-optional).
+2. Download and untar the Pulsar offloaders package, then copy the Pulsar offloaders as `offloaders` in the Pulsar directory, see [here](/docs/en/standalone/#install-tiered-storage-offloaders-optional).
**Output**
@@ -143,7 +143,7 @@ Automatic offloading runs when a new segment is added to a topic log. If you set
You can configure the threshold size using CLI tools, such as pulsar-admin.
-The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
+The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
#### Example
@@ -157,7 +157,7 @@ bin/pulsar-admin namespaces set-offload-threshold --size 10M my-tenant/my-namesp
:::tip
-For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-threshold-em-).
+For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-threshold-em-).
:::
@@ -191,7 +191,7 @@ For individual topics, you can trigger the Aliyun OSS offloader manually using o
:::tip
- For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-em-).
+ For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-em-).
:::
@@ -248,7 +248,7 @@ For individual topics, you can trigger the Aliyun OSS offloader manually using o
:::tip
- For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-status-em-).
+ For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-status-em-).
:::
diff --git a/site2/website-next/docs/tiered-storage-aws.md b/site2/website-next/docs/tiered-storage-aws.md
index 8f86d4c1e56..70ecc717f65 100644
--- a/site2/website-next/docs/tiered-storage-aws.md
+++ b/site2/website-next/docs/tiered-storage-aws.md
@@ -22,7 +22,7 @@ This example uses Pulsar 2.5.1.
* Download from the [Apache mirror](https://archive.apache.org/dist/pulsar/pulsar-2.5.1/apache-pulsar-2.5.1-bin.tar.gz)
- * Download from the Pulsar [downloads page](https://pulsar.apache.org/download)
+ * Download from the Pulsar [downloads page](/download)
* Use [wget](https://www.gnu.org/software/wget):
@@ -212,7 +212,7 @@ Automatic offloading runs when a new segment is added to a topic log. If you set
You can configure the threshold size using CLI tools, such as pulsar-admin.
-The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
+The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
#### Example
@@ -226,7 +226,7 @@ bin/pulsar-admin namespaces set-offload-threshold --size 10M my-tenant/my-namesp
:::tip
-For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-threshold-em-).
+For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-threshold-em-).
:::
@@ -260,7 +260,7 @@ For individual topics, you can trigger AWS S3 offloader manually using one of th
:::tip
- For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-em-).
+ For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-em-).
:::
@@ -317,7 +317,7 @@ For individual topics, you can trigger AWS S3 offloader manually using one of th
:::tip
- For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-status-em-).
+ For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-status-em-).
:::
diff --git a/site2/website-next/docs/tiered-storage-azure.md b/site2/website-next/docs/tiered-storage-azure.md
index 8a2d7b3a23d..b446346f283 100644
--- a/site2/website-next/docs/tiered-storage-azure.md
+++ b/site2/website-next/docs/tiered-storage-azure.md
@@ -22,7 +22,7 @@ This example uses Pulsar 2.6.2.
* Download from the [Apache mirror](https://archive.apache.org/dist/pulsar/pulsar-2.6.2/apache-pulsar-2.6.2-bin.tar.gz)
- * Download from the Pulsar [downloads page](https://pulsar.apache.org/download)
+ * Download from the Pulsar [downloads page](/download)
* Use [wget](https://www.gnu.org/software/wget):
@@ -150,7 +150,7 @@ Automatic offloading runs when a new segment is added to a topic log. If you set
You can configure the threshold size using CLI tools, such as pulsar-admin.
-The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
+The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
#### Example
@@ -164,7 +164,7 @@ bin/pulsar-admin namespaces set-offload-threshold --size 10M my-tenant/my-namesp
:::tip
-For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-threshold-em-).
+For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-threshold-em-).
:::
@@ -198,7 +198,7 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
:::tip
- For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-em-).
+ For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-em-).
:::
@@ -255,7 +255,7 @@ For individual topics, you can trigger Azure BlobStore offloader manually using
:::tip
- For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, and default values, see [here](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-status-em-).
+ For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, and default values, see [here](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-offload-status-em-).
:::
diff --git a/site2/website-next/docs/tiered-storage-filesystem.md b/site2/website-next/docs/tiered-storage-filesystem.md
index cbb6c4a99f3..30e693a76d8 100644
--- a/site2/website-next/docs/tiered-storage-filesystem.md
+++ b/site2/website-next/docs/tiered-storage-filesystem.md
@@ -28,7 +28,7 @@ This example uses Pulsar 2.5.1.
* Download the Pulsar tarball from the [Apache mirror](https://archive.apache.org/dist/pulsar/pulsar-2.5.1/apache-pulsar-2.5.1-bin.tar.gz)
- * Download the Pulsar tarball from the Pulsar [download page](https://pulsar.apache.org/download)
+ * Download the Pulsar tarball from the Pulsar [download page](/download)
* Use the [wget](https://www.gnu.org/software/wget) command to download the Pulsar tarball.
@@ -166,7 +166,7 @@ pulsar-admin namespaces set-offload-threshold --size 10M my-tenant/my-namespace
:::tip
-For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, default values, and shorthands, see [here](https://pulsar.apache.org/tools/pulsar-admin/).
+For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, default values, and shorthands, see [here](/tools/pulsar-admin/).
:::
@@ -200,7 +200,7 @@ To manually trigger the filesystem offloader via CLI tools, you need to specify
:::tip
- For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, default values, and shorthands, see [here](reference-pulsar-admin.md#offload).
+ For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, default values, and shorthands, see [here](/tools/pulsar-admin/).
:::
@@ -257,7 +257,7 @@ To manually trigger the filesystem offloader via CLI tools, you need to specify
:::tip
- For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, default values, and shorthands, see [here](https://pulsar.apache.org/tools/pulsar-admin/).
+ For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, default values, and shorthands, see [here](/tools/pulsar-admin/).
:::
diff --git a/site2/website-next/docs/tiered-storage-gcs.md b/site2/website-next/docs/tiered-storage-gcs.md
index c87b62c6ec8..d395713dcaf 100644
--- a/site2/website-next/docs/tiered-storage-gcs.md
+++ b/site2/website-next/docs/tiered-storage-gcs.md
@@ -22,7 +22,7 @@ This example uses Pulsar 2.5.1.
* Download from the [Apache mirror](https://archive.apache.org/dist/pulsar/pulsar-2.5.1/apache-pulsar-2.5.1-bin.tar.gz)
- * Download from the Pulsar [download page](https://pulsar.apache.org/download)
+ * Download from the Pulsar [download page](/download)
* Use [wget](https://www.gnu.org/software/wget)
@@ -202,7 +202,7 @@ Automatic offloading runs when a new segment is added to a topic log. If you set
You can configure the threshold size using CLI tools, such as pulsar-admin.
-The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](https://pulsar.apache.org/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
+The offload configurations in `broker.conf` and `standalone.conf` are used for the namespaces that do not have namespace level offload policies. Each namespace can have its own offload policy. If you want to set offload policy for each namespace, use the command [`pulsar-admin namespaces set-offload-policies options`](/tools/pulsar-admin/2.6.0-SNAPSHOT/#-em-set-offload-policies-em-) command.
#### Example
@@ -216,7 +216,7 @@ pulsar-admin namespaces set-offload-threshold --size 10M my-tenant/my-namespace
:::tip
-For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, default values, and shorthands, see [here](reference-pulsar-admin.md#set-offload-threshold).
+For more information about the `pulsar-admin namespaces set-offload-threshold options` command, including flags, descriptions, default values, and shorthands, see [here](/tools/pulsar-admin/).
:::
@@ -250,7 +250,7 @@ For individual topics, you can trigger GCS offloader manually using one of the f
:::tip
- For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, default values, and shorthands, see [here](reference-pulsar-admin.md#offload).
+ For more information about the `pulsar-admin topics offload options` command, including flags, descriptions, default values, and shorthands, see [here](/tools/pulsar-admin/).
:::
@@ -307,7 +307,7 @@ For individual topics, you can trigger GCS offloader manually using one of the f
:::tip
- For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, default values, and shorthands, see [here](reference-pulsar-admin.md#offload-status).
+ For more information about the `pulsar-admin topics offload-status options` command, including flags, descriptions, default values, and shorthands, see [here](/tools/pulsar-admin/).
:::
diff --git a/site2/website-next/docs/txn-monitor.md b/site2/website-next/docs/txn-monitor.md
index 18f06d9d3de..fe36e044fe0 100644
--- a/site2/website-next/docs/txn-monitor.md
+++ b/site2/website-next/docs/txn-monitor.md
@@ -4,6 +4,6 @@ title: How to monitor transactions?
sidebar_label: "How to monitor transactions?"
---
-You can monitor the status of the transactions in Prometheus and Grafana using the [transaction metrics](https://pulsar.apache.org/docs/en/next/reference-metrics/#pulsar-transaction).
+You can monitor the status of the transactions in Prometheus and Grafana using the [transaction metrics](/reference-metrics.md#pulsar-transaction).
-For how to configure Prometheus and Grafana, see [here](https://pulsar.apache.org/docs/en/next/deploy-monitoring).
+For how to configure Prometheus and Grafana, see [here](/deploy-monitoring.md).
diff --git a/site2/website-next/docs/txn-use.md b/site2/website-next/docs/txn-use.md
index 19b11dd38c6..a8f21b766a5 100644
--- a/site2/website-next/docs/txn-use.md
+++ b/site2/website-next/docs/txn-use.md
@@ -6,7 +6,7 @@ sidebar_label: "How to use transactions?"
## Transaction API
-The transaction feature is primarily a server-side and protocol-level feature. You can use the transaction feature via the [transaction API](https://pulsar.apache.org/api/admin/), which is available in **Pulsar 2.8.0 or later**.
+The transaction feature is primarily a server-side and protocol-level feature. You can use the transaction feature via the [transaction API](/api/admin/), which is available in **Pulsar 2.8.0 or later**.
To use the transaction API, you do not need any additional settings in the Pulsar client. **By default**, transactions is **disabled**.
diff --git a/site2/website-next/docs/txn-what.md b/site2/website-next/docs/txn-what.md
index 7c6cb78fc41..e603f37f7ef 100644
--- a/site2/website-next/docs/txn-what.md
+++ b/site2/website-next/docs/txn-what.md
@@ -4,7 +4,7 @@ title: What are transactions?
sidebar_label: "What are transactions?"
---
-Transactions strengthen the message delivery semantics of Apache Pulsar and [processing guarantees of Pulsar Functions](https://pulsar.apache.org/docs/en/next/functions-overview/#processing-guarantees). The Pulsar Transaction API supports atomic writes and acknowledgments across multiple topics.
+Transactions strengthen the message delivery semantics of Apache Pulsar and [processing guarantees of Pulsar Functions](functions-overview.md#processing-guarantees). The Pulsar Transaction API supports atomic writes and acknowledgments across multiple topics.
Transactions allow:
diff --git a/site2/website-next/docs/txn-why.md b/site2/website-next/docs/txn-why.md
index 0696b389b3a..c4f607db8bc 100644
--- a/site2/website-next/docs/txn-why.md
+++ b/site2/website-next/docs/txn-why.md
@@ -23,7 +23,7 @@ The Pulsar transactions API strengthens the message delivery semantics and the p
Avoiding data loss or duplication can be achieved by using the Pulsar idempotent producer, but it does not provide guarantees for writes across multiple partitions.
-In Pulsar, the highest level of message delivery guarantee is using an [idempotent producer](https://pulsar.apache.org/docs/en/next/concepts-messaging/#producer-idempotency) with the exactly once semantic at one single partition, that is, each message is persisted exactly once without data loss and duplication. However, there are some limitations in this solution:
+In Pulsar, the highest level of message delivery guarantee is using an [idempotent producer](concepts-messaging.md#producer-idempotency) with the exactly once semantic at one single partition, that is, each message is persisted exactly once without data loss and duplication. However, there are some limitations in this solution:
- Due to the monotonic increasing sequence ID, this solution only works on a single partition and within a single producer session (that is, for producing one message), so there is no atomicity when producing multiple messages to one or multiple partitions.