[fix][doc] Fix 404 URL issues (apache#15309)

drianpauL · Apr 26, 2022 · 7086ac4 · 7086ac4
1 parent 84b6559
commit 7086ac4
Show file tree

Hide file tree

Showing 91 changed files with 121 additions and 121 deletions.
diff --git a/site2/docs/concepts-architecture-overview.md b/site2/docs/concepts-architecture-overview.md
@@ -45,7 +45,7 @@ Clusters can replicate amongst themselves using [geo-replication](concepts-repli
 
 ## Metadata store
 
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster configuration, and coordination. The Pulsar metadata store can be deployed on a separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper metadata store](https://bookkeeper.apache.org/docs/latest/getting-started/concepts/#metadata-storage). If you want to deploy Pulsar brokers connected to an existing BookKeeper cluster, you need to deploy separate ZooKeeper clusters for Pulsar metadata store and BookKeeper metadata store respectively.
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster configuration, and coordination. The Pulsar metadata store can be deployed on a separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper metadata store. If you want to deploy Pulsar brokers connected to an existing BookKeeper cluster, you need to deploy separate ZooKeeper clusters for Pulsar metadata store and BookKeeper metadata store respectively.
 
 > Pulsar also supports more metadata backend services, including [ETCD](https://etcd.io/) and [RocksDB](http://rocksdb.org/) (for standalone Pulsar only). 
 

diff --git a/site2/docs/concepts-proxy-sni-routing.md b/site2/docs/concepts-proxy-sni-routing.md
@@ -43,7 +43,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING /proxy-key.pem
 CONFIG proxy.config.http.connect_ports STRING 4443 6651
 ```
 
-The [ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html) file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
+The `ssl_server_name` file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
 
 The following example shows mapping of the inbound SNI hostname coming from the client, and the actual broker service URL where request should be redirected. For example, if the client sends the SNI header `pulsar-broker1`, the proxy creates a TLS tunnel by redirecting request to the `pulsar-broker1:6651` service URL.
 

diff --git a/site2/docs/getting-started-standalone.md b/site2/docs/getting-started-standalone.md
@@ -1,5 +1,5 @@
 ---
-id: standalone
+id: getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
 ---

diff --git a/...2/website/versioned_docs/version-2.1.0-incubating/getting-started-standalone.md b/...2/website/versioned_docs/version-2.1.0-incubating/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.1.0-incubating-standalone
+id: version-2.1.0-incubating-getting-started-standalone
 title: Setting up a local standalone cluster
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For the purposes of local development and testing, you can run Pulsar in standalone mode on your own machine. Standalone mode includes a Pulsar broker as well as the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-clients.md b/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-clients.md
@@ -43,7 +43,7 @@ There are also [Doxygen](http://www.stack.nl/~dimitri/doxygen/)-generated API do
 
 ## Feature Matrix
 
-This matrix listing all the features among different languages in Pulsar master can be found [here](https://github.com/apache/incubator-pulsar/wiki/Client-Features-Matrix).
+This matrix listing all the features among different languages in Pulsar master can be found [here](https://github.com/apache/pulsar/wiki/PIP-108:-Pulsar-Feature-Matrix-(Client-and-Function)).
 
 ## Thirdparty Clients
 

diff --git a/...2/website/versioned_docs/version-2.1.1-incubating/getting-started-standalone.md b/...2/website/versioned_docs/version-2.1.1-incubating/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.1.1-incubating-standalone
+id: version-2.1.1-incubating-getting-started-standalone
 title: Setting up a local standalone cluster
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For the purposes of local development and testing, you can run Pulsar in standalone mode on your own machine. Standalone mode includes a Pulsar broker as well as the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.10.0/concepts-architecture-overview.md b/site2/website/versioned_docs/version-2.10.0/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using [geo-replication](concepts-repli
 
 ## Metadata store
 
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster configuration, and coordination. The Pulsar metadata store can be deployed on a separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper metadata store](https://bookkeeper.apache.org/docs/latest/getting-started/concepts/#metadata-storage). If you want to deploy Pulsar brokers connected to an existing BookKeeper cluster, you need to deploy separate ZooKeeper clusters for Pulsar metadata store and BookKeeper metadata store respectively.
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster configuration, and coordination. The Pulsar metadata store can be deployed on a separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper metadata store. If you want to deploy Pulsar brokers connected to an existing BookKeeper cluster, you need to deploy separate ZooKeeper clusters for Pulsar metadata store and BookKeeper metadata store respectively.
 
 > Pulsar also supports more metadata backend services, including [ETCD](https://etcd.io/) and [RocksDB](http://rocksdb.org/) (for standalone Pulsar only). 
 

diff --git a/site2/website/versioned_docs/version-2.10.0/concepts-proxy-sni-routing.md b/site2/website/versioned_docs/version-2.10.0/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING /proxy-key.pem
 CONFIG proxy.config.http.connect_ports STRING 4443 6651
 ```
 
-The [ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html) file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
+The `ssl_server_name` file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
 
 The following example shows mapping of the inbound SNI hostname coming from the client, and the actual broker service URL where request should be redirected. For example, if the client sends the SNI header `pulsar-broker1`, the proxy creates a TLS tunnel by redirecting request to the `pulsar-broker1:6651` service URL.
 

diff --git a/site2/website/versioned_docs/version-2.10.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.10.0/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.10.0-standalone
+id: version-2.10.0-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary [RocksDB](http://rocksdb.org/) and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.2.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.2.0/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.2.0-standalone
+id: version-2.2.0-getting-started-standalone
 title: Setting up a local standalone cluster
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For the purposes of local development and testing, you can run Pulsar in standalone mode on your own machine. Standalone mode includes a Pulsar broker as well as the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.2.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.2.1/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.2.1-standalone
+id: version-2.2.1-getting-started-standalone
 title: Setting up a local standalone cluster
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For the purposes of local development and testing, you can run Pulsar in standalone mode on your own machine. Standalone mode includes a Pulsar broker as well as the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.3.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.3.0/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.3.0-standalone
+id: version-2.3.0-getting-started-standalone
 title: Setting up a local standalone cluster
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For the purposes of local development and testing, you can run Pulsar in standalone mode on your own machine. Standalone mode includes a Pulsar broker as well as the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.3.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.3.1/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.3.1-standalone
+id: version-2.3.1-getting-started-standalone
 title: Setting up a local standalone cluster
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For the purposes of local development and testing, you can run Pulsar in standalone mode on your own machine. Standalone mode includes a Pulsar broker as well as the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.3.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.3.2/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.3.2-standalone
+id: version-2.3.2-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.4.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.4.0/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.4.0-standalone
+id: version-2.4.0-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.4.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.4.1/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.4.1-standalone
+id: version-2.4.1-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.4.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.4.2/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.4.2-standalone
+id: version-2.4.2-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.5.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.5.0/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.5.0-standalone
+id: version-2.5.0-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.5.1/concepts-architecture-overview.md b/site2/website/versioned_docs/version-2.5.1/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using [geo-replication](concepts-repli
 
 ## Metadata store
 
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster configuration, and coordination. The Pulsar metadata store can be deployed on a separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper metadata store](https://bookkeeper.apache.org/docs/latest/getting-started/concepts/#metadata-storage). If you want to deploy Pulsar brokers connected to an existing BookKeeper cluster, you need to deploy separate ZooKeeper clusters for Pulsar metadata store and BookKeeper metadata store respectively.
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster configuration, and coordination. The Pulsar metadata store can be deployed on a separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper metadata store. If you want to deploy Pulsar brokers connected to an existing BookKeeper cluster, you need to deploy separate ZooKeeper clusters for Pulsar metadata store and BookKeeper metadata store respectively.
 
 In a Pulsar instance:
 

diff --git a/...ersioned_docs/version-2.5.1/standalone.md → ...rsion-2.5.1/getting-started-standalone.md b/...ersioned_docs/version-2.5.1/standalone.md → ...rsion-2.5.1/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.5.1-standalone
+id: version-2.5.1-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.6.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.0/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.6.0-standalone
+id: version-2.6.0-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.6.1/concepts-proxy-sni-routing.md b/site2/website/versioned_docs/version-2.6.1/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING /proxy-key.pem
 CONFIG proxy.config.http.connect_ports STRING 4443 6651
 ```
 
-The [ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html) file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
+The `ssl_server_name` file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
 
 The following example shows mapping of the inbound SNI hostname coming from the client, and the actual broker service URL where request should be redirected. For example, if the client sends the SNI header `pulsar-broker1`, the proxy creates a TLS tunnel by redirecting request to the `pulsar-broker1:6651` service URL.
 

diff --git a/site2/website/versioned_docs/version-2.6.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.1/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.6.1-standalone
+id: version-2.6.1-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.

diff --git a/site2/website/versioned_docs/version-2.6.2/concepts-proxy-sni-routing.md b/site2/website/versioned_docs/version-2.6.2/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING /proxy-key.pem
 CONFIG proxy.config.http.connect_ports STRING 4443 6651
 ```
 
-The [ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html) file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
+The `ssl_server_name` file is used to configure TLS connection handling for inbound and outbound connections. The configuration is determined by the SNI values provided by the inbound connection. The file consists of a set of configuration items, and each is identified by an SNI value (`fqdn`). When an inbound TLS connection is made, the SNI value from the TLS negotiation is matched with the items specified in this file. If the values match, the values specified in that item override the default values. 
 
 The following example shows mapping of the inbound SNI hostname coming from the client, and the actual broker service URL where request should be redirected. For example, if the client sends the SNI header `pulsar-broker1`, the proxy creates a TLS tunnel by redirecting request to the `pulsar-broker1:6651` service URL.
 

diff --git a/site2/website/versioned_docs/version-2.6.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.2/getting-started-standalone.md
@@ -1,8 +1,8 @@
 ---
-id: version-2.6.2-standalone
+id: version-2.6.2-getting-started-standalone
 title: Set up a standalone Pulsar locally
 sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
 ---
 
 For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.