You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by li...@apache.org on 2022/09/22 02:35:16 UTC
[pulsar-site] branch main updated: remove old site files (#215)
This is an automated email from the ASF dual-hosted git repository.
liuyu 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 e89a8d11e3a remove old site files (#215)
e89a8d11e3a is described below
commit e89a8d11e3a5354387ada179beef68bab1c0cf7a
Author: tison <wa...@gmail.com>
AuthorDate: Thu Sep 22 10:35:11 2022 +0800
remove old site files (#215)
---
.github/workflows/ci-pulsar-website-build.yaml | 99 -
site2/website/README.md | 337 -
site2/website/__tests__/doc-links.test.js | 67 -
.../website/blog/2018-08-06-Apache-Pulsar-2-1-0.md | 88 -
.../website/blog/2019-02-20-Apache-Pulsar-2-3-0.md | 147 -
.../website/blog/2019-07-05-Apache-Pulsar-2-4-0.md | 121 -
.../website/blog/2019-12-04-Apache-Pulsar-2-4-2.md | 82 -
site2/website/blog/2019-12-18-Pulsar-summit-cfp.md | 43 -
...2019-12-20-pulsar-milestone-200-contributors.md | 26 -
...ng-the-apache-pulsar-2020-user-survey-report.md | 57 -
.../website/blog/2020-04-23-Apache-Pulsar-2-5-1.md | 97 -
.../website/blog/2020-05-19-Apache-Pulsar-2-5-2.md | 132 -
.../website/blog/2020-06-18-Apache-Pulsar-2-6-0.md | 395 -
.../website/blog/2020-08-21-Apache-Pulsar-2-6-1.md | 274 -
.../blog/2020-08-24-Pulsar-300-contributors.md | 65 -
.../blog/2020-09-01-pulsar-summit-asia-2020-cfp.md | 53 -
.../blog/2020-11-04-pulsar-summit-asia-schedule.md | 33 -
.../website/blog/2020-11-09-Apache-Pulsar-2-6-2.md | 326 -
.../website/blog/2020-12-24-Apache-Pulsar-2-7-0.md | 148 -
.../website/blog/2021-05-13-Apache-Pulsar-2-7-2.md | 40 -
.../website/blog/2021-06-12-Apache-Pulsar-2-8-0.md | 149 -
.../website/blog/2021-08-11-Apache-Pulsar-2-7-3.md | 140 -
site2/website/blog/2021-08-18-asia-cfp.md | 47 -
.../website/blog/2021-09-23-Apache-Pulsar-2-8-1.md | 148 -
site2/website/blog/2021-12-11-Log4j-CVE.md | 33 -
.../website/blog/2021-12-14-Apache-Pulsar-2-7-4.md | 150 -
.../website/blog/2022-04-08-Apache-Pulsar-2-9-2.md | 131 -
...-pulsar-community-welcomes-500th-contributor.md | 28 -
.../blog/2022-05-11-whats-new-in-pulsar-210.md | 177 -
site2/website/brodocs/actions.js | 58 -
site2/website/brodocs/brodoc.js | 214 -
site2/website/brodocs/favicon.ico | Bin 1150 -> 0 bytes
site2/website/brodocs/manifest.json | 45 -
site2/website/brodocs/markedDecorations.js | 101 -
site2/website/brodocs/pulsar-admin-manifest.json | 25 -
site2/website/brodocs/pulsar-client-manifest.json | 9 -
site2/website/brodocs/pulsar-manifest.json | 45 -
site2/website/brodocs/pulsar-perf-manifest.json | 9 -
site2/website/brodocs/scroll.js | 196 -
site2/website/brodocs/stylesheet.css | 271 -
site2/website/brodocs/tabvisibility.js | 27 -
site2/website/coding-guide.md | 79 -
site2/website/contributing.md | 348 -
site2/website/core/Footer.js | 180 -
site2/website/crowdin.yaml | 53 -
site2/website/data/connectors.js | 194 -
site2/website/data/resources.js | 1026 -
site2/website/data/team.js | 305 -
site2/website/data/users.js | 359 -
site2/website/docs/adaptors-kafka.md | 266 -
site2/website/docs/adaptors-spark.md | 80 -
site2/website/docs/adaptors-storm.md | 89 -
site2/website/docs/admin-api-brokers.md | 195 -
site2/website/docs/admin-api-clusters.md | 231 -
site2/website/docs/admin-api-functions.md | 588 -
site2/website/docs/admin-api-namespaces.md | 922 -
.../docs/admin-api-non-partitioned-topics.md | 7 -
.../docs/admin-api-non-persistent-topics.md | 7 -
site2/website/docs/admin-api-overview.md | 120 -
site2/website/docs/admin-api-packages.md | 273 -
site2/website/docs/admin-api-partitioned-topics.md | 7 -
site2/website/docs/admin-api-permissions.md | 135 -
site2/website/docs/admin-api-persistent-topics.md | 7 -
site2/website/docs/admin-api-schemas.md | 6 -
site2/website/docs/admin-api-tenants.md | 170 -
site2/website/docs/admin-api-topics.md | 1804 --
site2/website/docs/administration-geo.md | 242 -
site2/website/docs/administration-isolation.md | 92 -
site2/website/docs/administration-load-balance.md | 198 -
site2/website/docs/administration-proxy.md | 79 -
.../website/docs/administration-pulsar-manager.md | 182 -
site2/website/docs/administration-stats.md | 63 -
site2/website/docs/administration-upgrade.md | 150 -
site2/website/docs/administration-zk-bk.md | 342 -
site2/website/docs/assets/DDLC.png | Bin 194151 -> 0 bytes
site2/website/docs/assets/FileSystem-1.png | Bin 298961 -> 0 bytes
site2/website/docs/assets/FileSystem-2.png | Bin 232911 -> 0 bytes
site2/website/docs/assets/FileSystem-3.png | Bin 213823 -> 0 bytes
site2/website/docs/assets/FileSystem-8.png | Bin 216594 -> 0 bytes
site2/website/docs/assets/OverloadShedder.png | Bin 44951 -> 0 bytes
site2/website/docs/assets/ThresholdShedder.png | Bin 56518 -> 0 bytes
site2/website/docs/assets/UniformLoadShedder.png | Bin 50894 -> 0 bytes
.../docs/assets/active-active-replication.svg | 1 -
.../docs/assets/active-standby-replication.svg | 1 -
.../docs/assets/aggregation-replication.svg | 1 -
site2/website/docs/assets/backlog-quota.svg | 1 -
.../docs/assets/binary-protocol-connect.png | Bin 10230 -> 0 bytes
.../docs/assets/binary-protocol-consumer.png | Bin 32239 -> 0 bytes
.../docs/assets/binary-protocol-producer.png | Bin 33100 -> 0 bytes
.../docs/assets/binary-protocol-topic-lookup.png | Bin 29050 -> 0 bytes
site2/website/docs/assets/broker-bookie.png | Bin 136204 -> 0 bytes
site2/website/docs/assets/chunking-01.png | Bin 11881 -> 0 bytes
site2/website/docs/assets/chunking-02.png | Bin 30135 -> 0 bytes
.../docs/assets/cluster-level-failover-1.png | Bin 50187 -> 0 bytes
.../docs/assets/cluster-level-failover-2.png | Bin 62053 -> 0 bytes
.../docs/assets/cluster-level-failover-3.png | Bin 134614 -> 0 bytes
.../docs/assets/cluster-level-failover-4.png | Bin 151813 -> 0 bytes
.../docs/assets/cluster-level-failover-5.png | Bin 110855 -> 0 bytes
site2/website/docs/assets/dcos_bookie_log.png | Bin 668472 -> 0 bytes
.../docs/assets/dcos_bookkeeper_in_zookeeper.png | Bin 264657 -> 0 bytes
site2/website/docs/assets/dcos_bookkeeper_run.png | Bin 524502 -> 0 bytes
.../website/docs/assets/dcos_bookkeeper_status.png | Bin 115364 -> 0 bytes
.../docs/assets/dcos_broker_in_zookeeper.png | Bin 402876 -> 0 bytes
site2/website/docs/assets/dcos_broker_log.png | Bin 689765 -> 0 bytes
site2/website/docs/assets/dcos_broker_run.png | Bin 200575 -> 0 bytes
site2/website/docs/assets/dcos_broker_status.png | Bin 144495 -> 0 bytes
site2/website/docs/assets/dcos_command_execute.png | Bin 129195 -> 0 bytes
.../website/docs/assets/dcos_command_execute2.png | Bin 699589 -> 0 bytes
site2/website/docs/assets/dcos_consumer.png | Bin 1620672 -> 0 bytes
.../website/docs/assets/dcos_grafana_dashboard.png | Bin 102136 -> 0 bytes
.../website/docs/assets/dcos_grafana_endpoint.png | Bin 277004 -> 0 bytes
site2/website/docs/assets/dcos_metrics.png | Bin 389670 -> 0 bytes
site2/website/docs/assets/dcos_monitor_status.png | Bin 136506 -> 0 bytes
site2/website/docs/assets/dcos_producer.png | Bin 1542880 -> 0 bytes
site2/website/docs/assets/dcos_prom_endpoint.png | Bin 224700 -> 0 bytes
site2/website/docs/assets/dcos_prom_targets.png | Bin 240218 -> 0 bytes
site2/website/docs/assets/dcos_uninstall.png | Bin 115389 -> 0 bytes
.../website/docs/assets/full-mesh-replication.svg | 1 -
.../docs/assets/functions-worker-corun-proxy.png | Bin 12928 -> 0 bytes
.../website/docs/assets/functions-worker-corun.png | Bin 11286 -> 0 bytes
.../assets/functions-worker-separated-proxy.png | Bin 24788 -> 0 bytes
.../docs/assets/functions-worker-separated.png | Bin 21649 -> 0 bytes
.../website/docs/assets/geo-replication-async.svg | 1 -
site2/website/docs/assets/geo-replication-sync.svg | 1 -
site2/website/docs/assets/geo-replication.png | Bin 86141 -> 0 bytes
.../website/docs/assets/message-deduplication.png | Bin 116703 -> 0 bytes
site2/website/docs/assets/message_delay.png | Bin 30906 -> 0 bytes
site2/website/docs/assets/partitioning.png | Bin 125576 -> 0 bytes
site2/website/docs/assets/perf-produce.png | Bin 204162 -> 0 bytes
site2/website/docs/assets/pulsar-basic-setup.png | Bin 125695 -> 0 bytes
.../docs/assets/pulsar-encryption-consumer.jpg | Bin 31221 -> 0 bytes
.../docs/assets/pulsar-encryption-producer.jpg | Bin 30885 -> 0 bytes
.../docs/assets/pulsar-exclusive-subscriptions.png | Bin 59440 -> 0 bytes
.../docs/assets/pulsar-failover-subscriptions.png | Bin 64604 -> 0 bytes
.../docs/assets/pulsar-functions-overview.png | Bin 77077 -> 0 bytes
.../assets/pulsar-functions-routing-example.png | Bin 62087 -> 0 bytes
.../docs/assets/pulsar-functions-word-count.png | Bin 61459 -> 0 bytes
site2/website/docs/assets/pulsar-io.png | Bin 37316 -> 0 bytes
.../assets/pulsar-key-shared-subscriptions.png | Bin 124310 -> 0 bytes
.../assets/pulsar-reader-consumer-interfaces.png | Bin 131839 -> 0 bytes
.../docs/assets/pulsar-service-discovery.png | Bin 65898 -> 0 bytes
.../docs/assets/pulsar-shared-subscriptions.png | Bin 68922 -> 0 bytes
site2/website/docs/assets/pulsar-sni-client.png | Bin 232801 -> 0 bytes
site2/website/docs/assets/pulsar-sni-geo.png | Bin 201549 -> 0 bytes
site2/website/docs/assets/pulsar-sql-arch-1.png | Bin 167744 -> 0 bytes
site2/website/docs/assets/pulsar-sql-arch-2.png | Bin 130432 -> 0 bytes
.../docs/assets/pulsar-subscription-types.png | Bin 220423 -> 0 bytes
.../docs/assets/pulsar-system-architecture.png | Bin 309560 -> 0 bytes
.../website/docs/assets/pulsar-tiered-storage.png | Bin 70532 -> 0 bytes
site2/website/docs/assets/reader-interceptor.svg | 1 -
site2/website/docs/assets/retention-expiry.png | Bin 113741 -> 0 bytes
.../website/docs/assets/retention-storage-size.svg | 1 -
site2/website/docs/assets/retention.svg | 1 -
site2/website/docs/assets/retry-letter-topic.svg | 1 -
.../docs/assets/schema-autoupdate-consumer.png | Bin 86897 -> 0 bytes
.../docs/assets/schema-autoupdate-producer.png | Bin 116544 -> 0 bytes
site2/website/docs/assets/schema-consumer.png | Bin 171003 -> 0 bytes
site2/website/docs/assets/schema-producer.png | Bin 161680 -> 0 bytes
site2/website/docs/assets/tableview.png | Bin 53207 -> 0 bytes
site2/website/docs/assets/ttl.svg | 1 -
site2/website/docs/assets/txn-1.png | Bin 146508 -> 0 bytes
site2/website/docs/assets/txn-2.png | Bin 57117 -> 0 bytes
site2/website/docs/assets/txn-3.png | Bin 249164 -> 0 bytes
site2/website/docs/assets/txn-4.png | Bin 197983 -> 0 bytes
site2/website/docs/assets/txn-5.png | Bin 202533 -> 0 bytes
site2/website/docs/assets/txn-6.png | Bin 188856 -> 0 bytes
site2/website/docs/assets/txn-7.png | Bin 216642 -> 0 bytes
site2/website/docs/assets/txn-8.png | Bin 190633 -> 0 bytes
site2/website/docs/assets/txn-9.png | Bin 469713 -> 0 bytes
site2/website/docs/assets/zookeeper-batching.png | Bin 159664 -> 0 bytes
site2/website/docs/client-libraries-cgo.md | 546 -
site2/website/docs/client-libraries-cpp.md | 663 -
site2/website/docs/client-libraries-dotnet.md | 406 -
site2/website/docs/client-libraries-go.md | 991 -
site2/website/docs/client-libraries-java.md | 1404 -
site2/website/docs/client-libraries-node.md | 604 -
site2/website/docs/client-libraries-python.md | 577 -
site2/website/docs/client-libraries-rest.md | 122 -
site2/website/docs/client-libraries-websocket.md | 598 -
.../website/docs/concepts-architecture-overview.md | 165 -
site2/website/docs/concepts-authentication.md | 8 -
site2/website/docs/concepts-clients.md | 84 -
site2/website/docs/concepts-messaging.md | 838 -
site2/website/docs/concepts-multi-tenancy.md | 54 -
.../docs/concepts-multiple-advertised-listeners.md | 38 -
site2/website/docs/concepts-overview.md | 30 -
site2/website/docs/concepts-proxy-sni-routing.md | 150 -
site2/website/docs/concepts-replication.md | 68 -
site2/website/docs/concepts-schema-registry.md | 5 -
site2/website/docs/concepts-tiered-storage.md | 17 -
site2/website/docs/concepts-topic-compaction.md | 36 -
site2/website/docs/concepts-transactions.md | 29 -
site2/website/docs/cookbooks-bookkeepermetadata.md | 20 -
site2/website/docs/cookbooks-compaction.md | 126 -
site2/website/docs/cookbooks-deduplication.md | 124 -
site2/website/docs/cookbooks-encryption.md | 169 -
site2/website/docs/cookbooks-message-queue.md | 117 -
site2/website/docs/cookbooks-non-persistent.md | 58 -
site2/website/docs/cookbooks-partitioned.md | 6 -
site2/website/docs/cookbooks-retention-expiry.md | 392 -
site2/website/docs/cookbooks-tiered-storage.md | 310 -
site2/website/docs/deploy-aws.md | 226 -
.../docs/deploy-bare-metal-multi-cluster.md | 399 -
site2/website/docs/deploy-bare-metal.md | 477 -
site2/website/docs/deploy-docker.md | 51 -
site2/website/docs/deploy-kubernetes.md | 10 -
site2/website/docs/deploy-monitoring.md | 119 -
site2/website/docs/develop-plugin.md | 125 -
site2/website/docs/developing-binary-protocol.md | 611 -
site2/website/docs/developing-load-manager.md | 214 -
site2/website/docs/developing-tools.md | 104 -
site2/website/docs/functions-api.md | 5 -
site2/website/docs/functions-cli.md | 197 -
site2/website/docs/functions-debug.md | 465 -
site2/website/docs/functions-debugging.md | 5 -
site2/website/docs/functions-deploy.md | 229 -
site2/website/docs/functions-deploying.md | 5 -
site2/website/docs/functions-develop.md | 1394 -
site2/website/docs/functions-guarantees.md | 5 -
site2/website/docs/functions-metrics.md | 6 -
site2/website/docs/functions-overview.md | 193 -
site2/website/docs/functions-package.md | 433 -
site2/website/docs/functions-quickstart.md | 5 -
site2/website/docs/functions-runtime.md | 368 -
site2/website/docs/functions-state.md | 5 -
site2/website/docs/functions-worker.md | 347 -
site2/website/docs/getting-started-clients.md | 43 -
.../getting-started-concepts-and-architecture.md | 15 -
site2/website/docs/getting-started-docker.md | 193 -
site2/website/docs/getting-started-helm.md | 362 -
site2/website/docs/getting-started-pulsar.md | 66 -
site2/website/docs/getting-started-standalone.md | 220 -
site2/website/docs/helm-deploy.md | 378 -
site2/website/docs/helm-install.md | 37 -
site2/website/docs/helm-overview.md | 98 -
site2/website/docs/helm-prepare.md | 72 -
site2/website/docs/helm-tools.md | 42 -
site2/website/docs/helm-upgrade.md | 33 -
site2/website/docs/io-aerospike-sink.md | 25 -
site2/website/docs/io-aerospike.md | 5 -
site2/website/docs/io-canal-source.md | 202 -
site2/website/docs/io-cassandra-sink.md | 55 -
site2/website/docs/io-cassandra.md | 5 -
site2/website/docs/io-cdc-canal.md | 5 -
site2/website/docs/io-cdc-debezium.md | 480 -
site2/website/docs/io-cdc.md | 25 -
site2/website/docs/io-cli.md | 605 -
site2/website/docs/io-connectors.md | 256 -
site2/website/docs/io-debezium-source.md | 648 -
site2/website/docs/io-debug.md | 328 -
site2/website/docs/io-develop.md | 376 -
site2/website/docs/io-dynamodb-source.md | 77 -
site2/website/docs/io-dynamodb.md | 5 -
site2/website/docs/io-elasticsearch-sink.md | 217 -
site2/website/docs/io-elasticsearch.md | 5 -
site2/website/docs/io-file-source.md | 149 -
site2/website/docs/io-file.md | 5 -
site2/website/docs/io-flume-sink.md | 53 -
site2/website/docs/io-flume-source.md | 53 -
site2/website/docs/io-hbase-sink.md | 65 -
site2/website/docs/io-hbase.md | 5 -
site2/website/docs/io-hdfs.md | 5 -
site2/website/docs/io-hdfs2-sink.md | 60 -
site2/website/docs/io-hdfs3-sink.md | 55 -
site2/website/docs/io-influxdb-sink.md | 112 -
site2/website/docs/io-influxdb.md | 5 -
site2/website/docs/io-jdbc-sink.md | 173 -
site2/website/docs/io-jdbc.md | 5 -
site2/website/docs/io-kafka-sink.md | 69 -
site2/website/docs/io-kafka-source.md | 210 -
site2/website/docs/io-kafka.md | 5 -
site2/website/docs/io-kinesis-sink.md | 76 -
site2/website/docs/io-kinesis-source.md | 78 -
site2/website/docs/io-kinesis.md | 5 -
site2/website/docs/io-mongo-sink.md | 52 -
site2/website/docs/io-mongo.md | 5 -
site2/website/docs/io-netty-source.md | 206 -
site2/website/docs/io-netty.md | 5 -
site2/website/docs/io-nsq-source.md | 20 -
site2/website/docs/io-nsq.md | 5 -
site2/website/docs/io-overview.md | 135 -
site2/website/docs/io-quickstart.md | 815 -
site2/website/docs/io-rabbitmq-sink.md | 82 -
site2/website/docs/io-rabbitmq-source.md | 82 -
site2/website/docs/io-rabbitmq.md | 5 -
site2/website/docs/io-redis-sink.md | 137 -
site2/website/docs/io-redis.md | 5 -
site2/website/docs/io-solr-sink.md | 62 -
site2/website/docs/io-solr.md | 5 -
site2/website/docs/io-tcp.md | 5 -
site2/website/docs/io-twitter-source.md | 27 -
site2/website/docs/io-twitter.md | 6 -
site2/website/docs/io-use.md | 1504 --
site2/website/docs/performance-pulsar-perf.md | 231 -
site2/website/docs/reference-cli-tools.md | 891 -
site2/website/docs/reference-configuration.md | 876 -
site2/website/docs/reference-connector-admin.md | 11 -
site2/website/docs/reference-metrics.md | 669 -
site2/website/docs/reference-pulsar-admin.md | 2796 --
site2/website/docs/reference-terminology.md | 167 -
.../website/docs/schema-evolution-compatibility.md | 956 -
site2/website/docs/schema-get-started.md | 94 -
site2/website/docs/schema-manage.md | 959 -
site2/website/docs/schema-understand.md | 669 -
site2/website/docs/security-athenz.md | 92 -
site2/website/docs/security-authorization.md | 114 -
site2/website/docs/security-bouncy-castle.md | 138 -
site2/website/docs/security-encryption.md | 281 -
site2/website/docs/security-extending.md | 76 -
site2/website/docs/security-jwt.md | 263 -
site2/website/docs/security-kerberos.md | 390 -
site2/website/docs/security-oauth2.md | 263 -
site2/website/docs/security-overview.md | 36 -
site2/website/docs/security-tls-authentication.md | 187 -
site2/website/docs/security-tls-keystore.md | 304 -
site2/website/docs/security-tls-transport.md | 275 -
site2/website/docs/security-token-admin.md | 158 -
site2/website/docs/security-versioning-policy.md | 61 -
.../website/docs/sql-deployment-configurations.md | 245 -
site2/website/docs/sql-getting-started.md | 169 -
site2/website/docs/sql-overview.md | 17 -
site2/website/docs/sql-rest-api.md | 185 -
site2/website/docs/tiered-storage-aliyun.md | 215 -
site2/website/docs/tiered-storage-aws.md | 277 -
site2/website/docs/tiered-storage-azure.md | 221 -
site2/website/docs/tiered-storage-filesystem.md | 582 -
site2/website/docs/tiered-storage-gcs.md | 270 -
site2/website/docs/tiered-storage-overview.md | 55 -
site2/website/docs/transaction-api.md | 148 -
site2/website/docs/transaction-guarantee.md | 16 -
site2/website/docs/txn-how.md | 318 -
site2/website/docs/txn-monitor.md | 9 -
site2/website/docs/txn-use.md | 131 -
site2/website/docs/txn-what.md | 59 -
site2/website/docs/txn-why.md | 44 -
site2/website/docs/window-functions-context.md | 528 -
site2/website/docusaurus-version.js | 196 -
site2/website/languages.js | 185 -
site2/website/oldversions.json | 8 -
site2/website/package.json | 39 -
site2/website/pages/en/admin-rest-api.js | 21 -
site2/website/pages/en/coding-guide.js | 35 -
site2/website/pages/en/contact.js | 119 -
site2/website/pages/en/contributing.js | 35 -
site2/website/pages/en/download.js | 411 -
site2/website/pages/en/events.js | 96 -
site2/website/pages/en/functions-rest-api.js | 21 -
site2/website/pages/en/index.js | 205 -
site2/website/pages/en/packages-rest-api.js | 21 -
site2/website/pages/en/powered-by.js | 60 -
site2/website/pages/en/pulsar-admin-cli.js | 24 -
site2/website/pages/en/pulsar-cli.js | 24 -
site2/website/pages/en/pulsar-client-cli.js | 24 -
.../pages/en/pulsar-manager-release-notes.js | 35 -
site2/website/pages/en/pulsar-perf-cli.js | 24 -
site2/website/pages/en/release-notes.js | 35 -
site2/website/pages/en/resources.js | 152 -
site2/website/pages/en/sink-rest-api.js | 21 -
site2/website/pages/en/source-rest-api.js | 21 -
site2/website/pages/en/team.js | 82 -
site2/website/pages/en/versions.js | 130 -
site2/website/pulsar-adapters-release.json | 3 -
site2/website/pulsar-manager-release-notes.md | 35 -
site2/website/pulsar-manager-release.json | 4 -
site2/website/release-notes.md | 4526 ----
site2/website/releases.json | 39 -
site2/website/scripts/crowdin-cli.jar | Bin 11676600 -> 0 bytes
site2/website/scripts/fix-tab.js | 44 -
site2/website/scripts/replace.js | 233 -
site2/website/scripts/split-swagger-by-version.js | 61 -
site2/website/scripts/test-server.js | 21 -
site2/website/sidebars.json | 166 -
site2/website/siteConfig.js | 212 -
site2/website/static/api/python/2.10.0/index.html | 7 -
site2/website/static/api/python/2.10.0/pulsar.html | 6237 -----
.../api/python/2.10.0/pulsar/exceptions.html | 260 -
.../static/api/python/2.10.0/pulsar/functions.html | 259 -
.../python/2.10.0/pulsar/functions/context.html | 1384 -
.../python/2.10.0/pulsar/functions/function.html | 376 -
.../api/python/2.10.0/pulsar/functions/serde.html | 665 -
.../static/api/python/2.10.0/pulsar/schema.html | 262 -
.../python/2.10.0/pulsar/schema/definition.html | 3274 ---
.../api/python/2.10.0/pulsar/schema/schema.html | 841 -
.../python/2.10.0/pulsar/schema/schema_avro.html | 527 -
site2/website/static/api/python/2.10.0/search.js | 46 -
site2/website/static/api/python/2.10.1/index.html | 7 -
site2/website/static/api/python/2.10.1/pulsar.html | 6147 -----
.../api/python/2.10.1/pulsar/exceptions.html | 265 -
.../static/api/python/2.10.1/pulsar/functions.html | 264 -
.../python/2.10.1/pulsar/functions/context.html | 1380 -
.../python/2.10.1/pulsar/functions/function.html | 381 -
.../api/python/2.10.1/pulsar/functions/serde.html | 669 -
.../static/api/python/2.10.1/pulsar/schema.html | 267 -
.../python/2.10.1/pulsar/schema/definition.html | 3259 ---
.../api/python/2.10.1/pulsar/schema/schema.html | 863 -
.../python/2.10.1/pulsar/schema/schema_avro.html | 531 -
site2/website/static/api/python/2.10.1/search.js | 46 -
site2/website/static/api/python/2.7.0/index.html | 7 -
site2/website/static/api/python/2.7.0/pulsar.html | 5730 -----
.../static/api/python/2.7.0/pulsar/functions.html | 259 -
.../api/python/2.7.0/pulsar/functions/context.html | 1384 -
.../python/2.7.0/pulsar/functions/function.html | 376 -
.../api/python/2.7.0/pulsar/functions/serde.html | 665 -
.../static/api/python/2.7.0/pulsar/schema.html | 260 -
.../api/python/2.7.0/pulsar/schema/definition.html | 2386 --
.../api/python/2.7.0/pulsar/schema/schema.html | 957 -
site2/website/static/api/python/2.7.0/search.js | 46 -
site2/website/static/api/python/2.7.1/index.html | 7 -
site2/website/static/api/python/2.7.1/pulsar.html | 5910 -----
.../static/api/python/2.7.1/pulsar/functions.html | 259 -
.../api/python/2.7.1/pulsar/functions/context.html | 1384 -
.../python/2.7.1/pulsar/functions/function.html | 376 -
.../api/python/2.7.1/pulsar/functions/serde.html | 665 -
.../static/api/python/2.7.1/pulsar/schema.html | 260 -
.../api/python/2.7.1/pulsar/schema/definition.html | 2386 --
.../api/python/2.7.1/pulsar/schema/schema.html | 957 -
site2/website/static/api/python/2.7.1/search.js | 46 -
site2/website/static/api/python/2.7.2/index.html | 7 -
site2/website/static/api/python/2.7.2/pulsar.html | 5910 -----
.../static/api/python/2.7.2/pulsar/functions.html | 259 -
.../api/python/2.7.2/pulsar/functions/context.html | 1384 -
.../python/2.7.2/pulsar/functions/function.html | 376 -
.../api/python/2.7.2/pulsar/functions/serde.html | 665 -
.../static/api/python/2.7.2/pulsar/schema.html | 260 -
.../api/python/2.7.2/pulsar/schema/definition.html | 2635 --
.../api/python/2.7.2/pulsar/schema/schema.html | 969 -
site2/website/static/api/python/2.7.2/search.js | 46 -
site2/website/static/api/python/2.7.3/index.html | 7 -
site2/website/static/api/python/2.7.3/pulsar.html | 5910 -----
.../static/api/python/2.7.3/pulsar/functions.html | 259 -
.../api/python/2.7.3/pulsar/functions/context.html | 1384 -
.../python/2.7.3/pulsar/functions/function.html | 376 -
.../api/python/2.7.3/pulsar/functions/serde.html | 665 -
.../static/api/python/2.7.3/pulsar/schema.html | 260 -
.../api/python/2.7.3/pulsar/schema/definition.html | 2635 --
.../api/python/2.7.3/pulsar/schema/schema.html | 969 -
site2/website/static/api/python/2.7.3/search.js | 46 -
site2/website/static/api/python/2.7.4/index.html | 7 -
site2/website/static/api/python/2.7.4/pulsar.html | 5910 -----
.../static/api/python/2.7.4/pulsar/functions.html | 259 -
.../api/python/2.7.4/pulsar/functions/context.html | 1384 -
.../python/2.7.4/pulsar/functions/function.html | 376 -
.../api/python/2.7.4/pulsar/functions/serde.html | 665 -
.../static/api/python/2.7.4/pulsar/schema.html | 260 -
.../api/python/2.7.4/pulsar/schema/definition.html | 2654 --
.../api/python/2.7.4/pulsar/schema/schema.html | 969 -
site2/website/static/api/python/2.7.4/search.js | 46 -
site2/website/static/api/python/2.8.0/index.html | 7 -
site2/website/static/api/python/2.8.0/pulsar.html | 5957 -----
.../static/api/python/2.8.0/pulsar/exceptions.html | 260 -
.../static/api/python/2.8.0/pulsar/functions.html | 259 -
.../api/python/2.8.0/pulsar/functions/context.html | 1384 -
.../python/2.8.0/pulsar/functions/function.html | 376 -
.../api/python/2.8.0/pulsar/functions/serde.html | 665 -
.../static/api/python/2.8.0/pulsar/schema.html | 260 -
.../api/python/2.8.0/pulsar/schema/definition.html | 2635 --
.../api/python/2.8.0/pulsar/schema/schema.html | 969 -
site2/website/static/api/python/2.8.0/search.js | 46 -
site2/website/static/api/python/2.8.1/index.html | 7 -
site2/website/static/api/python/2.8.1/pulsar.html | 5978 -----
.../static/api/python/2.8.1/pulsar/exceptions.html | 260 -
.../static/api/python/2.8.1/pulsar/functions.html | 259 -
.../api/python/2.8.1/pulsar/functions/context.html | 1384 -
.../python/2.8.1/pulsar/functions/function.html | 376 -
.../api/python/2.8.1/pulsar/functions/serde.html | 665 -
.../static/api/python/2.8.1/pulsar/schema.html | 262 -
.../api/python/2.8.1/pulsar/schema/definition.html | 2927 ---
.../api/python/2.8.1/pulsar/schema/schema.html | 813 -
.../python/2.8.1/pulsar/schema/schema_avro.html | 488 -
site2/website/static/api/python/2.8.1/search.js | 46 -
site2/website/static/api/python/2.8.2/index.html | 7 -
site2/website/static/api/python/2.8.2/pulsar.html | 6108 -----
.../static/api/python/2.8.2/pulsar/exceptions.html | 260 -
.../static/api/python/2.8.2/pulsar/functions.html | 259 -
.../api/python/2.8.2/pulsar/functions/context.html | 1384 -
.../python/2.8.2/pulsar/functions/function.html | 376 -
.../api/python/2.8.2/pulsar/functions/serde.html | 665 -
.../static/api/python/2.8.2/pulsar/schema.html | 262 -
.../api/python/2.8.2/pulsar/schema/definition.html | 3274 ---
.../api/python/2.8.2/pulsar/schema/schema.html | 826 -
.../python/2.8.2/pulsar/schema/schema_avro.html | 527 -
site2/website/static/api/python/2.8.2/search.js | 46 -
site2/website/static/api/python/2.8.3/index.html | 7 -
site2/website/static/api/python/2.8.3/pulsar.html | 6108 -----
.../static/api/python/2.8.3/pulsar/exceptions.html | 260 -
.../static/api/python/2.8.3/pulsar/functions.html | 259 -
.../api/python/2.8.3/pulsar/functions/context.html | 1384 -
.../python/2.8.3/pulsar/functions/function.html | 376 -
.../api/python/2.8.3/pulsar/functions/serde.html | 665 -
.../static/api/python/2.8.3/pulsar/schema.html | 262 -
.../api/python/2.8.3/pulsar/schema/definition.html | 3274 ---
.../api/python/2.8.3/pulsar/schema/schema.html | 826 -
.../python/2.8.3/pulsar/schema/schema_avro.html | 527 -
site2/website/static/api/python/2.8.3/search.js | 46 -
site2/website/static/api/python/2.9.1/index.html | 7 -
site2/website/static/api/python/2.9.1/pulsar.html | 6108 -----
.../static/api/python/2.9.1/pulsar/exceptions.html | 260 -
.../static/api/python/2.9.1/pulsar/functions.html | 259 -
.../api/python/2.9.1/pulsar/functions/context.html | 1384 -
.../python/2.9.1/pulsar/functions/function.html | 376 -
.../api/python/2.9.1/pulsar/functions/serde.html | 665 -
.../static/api/python/2.9.1/pulsar/schema.html | 262 -
.../api/python/2.9.1/pulsar/schema/definition.html | 2978 ---
.../api/python/2.9.1/pulsar/schema/schema.html | 813 -
.../python/2.9.1/pulsar/schema/schema_avro.html | 488 -
site2/website/static/api/python/2.9.1/search.js | 46 -
site2/website/static/api/python/2.9.2/index.html | 7 -
site2/website/static/api/python/2.9.2/pulsar.html | 6028 -----
.../static/api/python/2.9.2/pulsar/exceptions.html | 265 -
.../static/api/python/2.9.2/pulsar/functions.html | 264 -
.../api/python/2.9.2/pulsar/functions/context.html | 1380 -
.../python/2.9.2/pulsar/functions/function.html | 381 -
.../api/python/2.9.2/pulsar/functions/serde.html | 669 -
.../static/api/python/2.9.2/pulsar/schema.html | 267 -
.../api/python/2.9.2/pulsar/schema/definition.html | 3259 ---
.../api/python/2.9.2/pulsar/schema/schema.html | 829 -
.../python/2.9.2/pulsar/schema/schema_avro.html | 531 -
site2/website/static/api/python/2.9.2/search.js | 46 -
site2/website/static/api/python/2.9.3/index.html | 7 -
site2/website/static/api/python/2.9.3/pulsar.html | 6028 -----
.../static/api/python/2.9.3/pulsar/exceptions.html | 265 -
.../static/api/python/2.9.3/pulsar/functions.html | 264 -
.../api/python/2.9.3/pulsar/functions/context.html | 1380 -
.../python/2.9.3/pulsar/functions/function.html | 381 -
.../api/python/2.9.3/pulsar/functions/serde.html | 669 -
.../static/api/python/2.9.3/pulsar/schema.html | 267 -
.../api/python/2.9.3/pulsar/schema/definition.html | 3259 ---
.../api/python/2.9.3/pulsar/schema/schema.html | 829 -
.../python/2.9.3/pulsar/schema/schema_avro.html | 531 -
site2/website/static/api/python/2.9.3/search.js | 46 -
site2/website/static/css/code-blocks-buttons.css | 46 -
site2/website/static/css/custom.css | 150 -
site2/website/static/doap.rdf | 59 -
site2/website/static/examples/openssl.cnf | 152 -
site2/website/static/img/280-1.png | Bin 194346 -> 0 bytes
site2/website/static/img/280-2.png | Bin 158780 -> 0 bytes
site2/website/static/img/apache_incubator.png | Bin 17730 -> 0 bytes
site2/website/static/img/commit-message.png | Bin 234213 -> 0 bytes
site2/website/static/img/cooperation.png | Bin 181386 -> 0 bytes
site2/website/static/img/docusaurus.svg | 1 -
site2/website/static/img/favicon/favicon.ico | Bin 1150 -> 0 bytes
site2/website/static/img/p-200.png | Bin 131947 -> 0 bytes
site2/website/static/img/pulsar-adoption.png | Bin 46300 -> 0 bytes
.../website/static/img/pulsar-summit-asia-2020.png | Bin 463865 -> 0 bytes
site2/website/static/img/pulsar-user-ban.jpg | Bin 411979 -> 0 bytes
site2/website/static/img/pulsar.ico | Bin 1150 -> 0 bytes
site2/website/static/img/pulsar.svg | 1 -
site2/website/static/js/custom.js | 247 -
site2/website/static/js/getCliByVersion.js | 48 -
site2/website/static/js/getSwaggerByVersion.js | 63 -
site2/website/static/swagger/2.10.0/swagger.json | 25683 -------------------
.../static/swagger/2.10.0/swaggerfunctions.json | 2977 ---
.../static/swagger/2.10.0/swaggerpackages.json | 1649 --
.../website/static/swagger/2.10.0/swaggersink.json | 2351 --
.../static/swagger/2.10.0/swaggersource.json | 2305 --
site2/website/static/swagger/2.3.0/swagger.json | 8143 ------
.../static/swagger/2.3.0/swaggerfunctions.json | 3431 ---
.../website/static/swagger/2.3.0/swaggersink.json | 3038 ---
.../static/swagger/2.3.0/swaggersource.json | 3038 ---
site2/website/static/swagger/2.3.1/swagger.json | 8143 ------
.../static/swagger/2.3.1/swaggerfunctions.json | 3431 ---
.../website/static/swagger/2.3.1/swaggersink.json | 3038 ---
.../static/swagger/2.3.1/swaggersource.json | 3038 ---
site2/website/static/swagger/2.3.2/swagger.json | 8143 ------
.../static/swagger/2.3.2/swaggerfunctions.json | 3431 ---
.../website/static/swagger/2.3.2/swaggersink.json | 3038 ---
.../static/swagger/2.3.2/swaggersource.json | 3038 ---
site2/website/static/swagger/2.4.0/swagger.json | 9634 -------
.../static/swagger/2.4.0/swaggerfunctions.json | 1496 --
.../website/static/swagger/2.4.0/swaggersink.json | 926 -
.../static/swagger/2.4.0/swaggersource.json | 860 -
site2/website/static/swagger/2.4.1/swagger.json | 9677 -------
.../static/swagger/2.4.1/swaggerfunctions.json | 1496 --
.../website/static/swagger/2.4.1/swaggersink.json | 935 -
.../static/swagger/2.4.1/swaggersource.json | 886 -
site2/website/static/swagger/2.4.2/swagger.json | 9949 -------
.../static/swagger/2.4.2/swaggerfunctions.json | 1496 --
.../website/static/swagger/2.4.2/swaggersink.json | 939 -
.../static/swagger/2.4.2/swaggersource.json | 886 -
site2/website/static/swagger/2.5.0/swagger.json | 10221 --------
.../static/swagger/2.5.0/swaggerfunctions.json | 1499 --
.../website/static/swagger/2.5.0/swaggersink.json | 955 -
.../static/swagger/2.5.0/swaggersource.json | 902 -
site2/website/static/swagger/2.5.1/swagger.json | 10595 --------
.../static/swagger/2.5.1/swaggerfunctions.json | 1499 --
.../website/static/swagger/2.5.1/swaggersink.json | 955 -
.../static/swagger/2.5.1/swaggersource.json | 902 -
site2/website/static/swagger/2.5.2/swagger.json | 10738 --------
.../static/swagger/2.5.2/swaggerfunctions.json | 1503 --
.../website/static/swagger/2.5.2/swaggersink.json | 955 -
.../static/swagger/2.5.2/swaggersource.json | 902 -
site2/website/static/swagger/2.6.0/swagger.json | 11850 ---------
.../static/swagger/2.6.0/swaggerfunctions.json | 1533 --
.../website/static/swagger/2.6.0/swaggersink.json | 1067 -
.../static/swagger/2.6.0/swaggersource.json | 1008 -
site2/website/static/swagger/2.6.1/swagger.json | 11972 ---------
.../static/swagger/2.6.1/swaggerfunctions.json | 1533 --
.../website/static/swagger/2.6.1/swaggersink.json | 1067 -
.../static/swagger/2.6.1/swaggersource.json | 1008 -
site2/website/static/swagger/2.6.2/swagger.json | 12356 ---------
.../static/swagger/2.6.2/swaggerfunctions.json | 1533 --
.../website/static/swagger/2.6.2/swaggersink.json | 1067 -
.../static/swagger/2.6.2/swaggersource.json | 1008 -
site2/website/static/swagger/2.7.0/swagger.json | 16910 ------------
.../static/swagger/2.7.0/swaggerfunctions.json | 1651 --
.../website/static/swagger/2.7.0/swaggersink.json | 1104 -
.../static/swagger/2.7.0/swaggersource.json | 1064 -
site2/website/static/swagger/2.7.1/swagger.json | 17804 -------------
.../static/swagger/2.7.1/swaggerfunctions.json | 1651 --
.../website/static/swagger/2.7.1/swaggersink.json | 1104 -
.../static/swagger/2.7.1/swaggersource.json | 1064 -
site2/website/static/swagger/2.7.2/swagger.json | 17827 -------------
.../static/swagger/2.7.2/swaggerfunctions.json | 1651 --
.../website/static/swagger/2.7.2/swaggersink.json | 1104 -
.../static/swagger/2.7.2/swaggersource.json | 1064 -
site2/website/static/swagger/2.7.3/swagger.json | 18689 --------------
.../static/swagger/2.7.3/swaggerfunctions.json | 1651 --
.../website/static/swagger/2.7.3/swaggersink.json | 1104 -
.../static/swagger/2.7.3/swaggersource.json | 1064 -
site2/website/static/swagger/2.7.4/swagger.json | 18814 --------------
.../static/swagger/2.7.4/swaggerfunctions.json | 1651 --
.../website/static/swagger/2.7.4/swaggersink.json | 1104 -
.../static/swagger/2.7.4/swaggersource.json | 1064 -
site2/website/static/swagger/2.8.0/swagger.json | 22103 ----------------
.../static/swagger/2.8.0/swaggerfunctions.json | 3063 ---
.../static/swagger/2.8.0/swaggerpackages.json | 1725 --
.../website/static/swagger/2.8.0/swaggersink.json | 2442 --
.../static/swagger/2.8.0/swaggersource.json | 2402 --
site2/website/static/swagger/2.8.1/swagger.json | 23378 -----------------
.../static/swagger/2.8.1/swaggerfunctions.json | 3063 ---
.../static/swagger/2.8.1/swaggerpackages.json | 1725 --
.../website/static/swagger/2.8.1/swaggersink.json | 2442 --
.../static/swagger/2.8.1/swaggersource.json | 2402 --
site2/website/static/swagger/2.8.2/swagger.json | 23411 -----------------
.../static/swagger/2.8.2/swaggerfunctions.json | 3063 ---
.../static/swagger/2.8.2/swaggerpackages.json | 1725 --
.../website/static/swagger/2.8.2/swaggersink.json | 2442 --
.../static/swagger/2.8.2/swaggersource.json | 2402 --
site2/website/static/swagger/2.8.3/swagger.json | 23429 -----------------
.../static/swagger/2.8.3/swaggerfunctions.json | 3081 ---
.../static/swagger/2.8.3/swaggerpackages.json | 1743 --
.../website/static/swagger/2.8.3/swaggersink.json | 2460 --
.../static/swagger/2.8.3/swaggersource.json | 2420 --
site2/website/static/swagger/2.9.0/swagger.json | 23734 -----------------
.../static/swagger/2.9.0/swaggerfunctions.json | 3074 ---
.../static/swagger/2.9.0/swaggerpackages.json | 1725 --
.../website/static/swagger/2.9.0/swaggersink.json | 2445 --
.../static/swagger/2.9.0/swaggersource.json | 2402 --
site2/website/static/swagger/2.9.1/swagger.json | 23738 -----------------
.../static/swagger/2.9.1/swaggerfunctions.json | 3074 ---
.../static/swagger/2.9.1/swaggerpackages.json | 1725 --
.../website/static/swagger/2.9.1/swaggersink.json | 2445 --
.../static/swagger/2.9.1/swaggersource.json | 2402 --
site2/website/static/swagger/2.9.2/swagger.json | 23947 -----------------
.../static/swagger/2.9.2/swaggerfunctions.json | 3092 ---
.../static/swagger/2.9.2/swaggerpackages.json | 1743 --
.../website/static/swagger/2.9.2/swaggersink.json | 2463 --
.../static/swagger/2.9.2/swaggersource.json | 2420 --
.../version-2.1.0-incubating/adaptors-kafka.md | 260 -
.../version-2.1.0-incubating/adaptors-spark.md | 67 -
.../version-2.1.0-incubating/adaptors-storm.md | 105 -
.../version-2.1.0-incubating/admin-api-brokers.md | 149 -
.../version-2.1.0-incubating/admin-api-clusters.md | 210 -
.../admin-api-namespaces.md | 642 -
.../admin-api-non-persistent-topics.md | 254 -
.../version-2.1.0-incubating/admin-api-overview.md | 73 -
.../admin-api-partitioned-topics.md | 333 -
.../admin-api-permissions.md | 115 -
.../admin-api-persistent-topics.md | 605 -
.../version-2.1.0-incubating/admin-api-schemas.md | 99 -
.../version-2.1.0-incubating/admin-api-tenants.md | 86 -
.../administration-dashboard.md | 51 -
.../version-2.1.0-incubating/administration-geo.md | 127 -
.../administration-load-distribution.md | 218 -
.../administration-proxy.md | 67 -
.../administration-stats.md | 64 -
.../administration-zk-bk.md | 322 -
.../client-libraries-cpp.md | 184 -
.../client-libraries-go.md | 465 -
.../client-libraries-java.md | 469 -
.../client-libraries-python.md | 99 -
.../client-libraries-websocket.md | 410 -
.../concepts-architecture-overview.md | 153 -
.../concepts-authentication.md | 9 -
.../version-2.1.0-incubating/concepts-clients.md | 80 -
.../version-2.1.0-incubating/concepts-messaging.md | 308 -
.../concepts-multi-tenancy.md | 40 -
.../version-2.1.0-incubating/concepts-overview.md | 32 -
.../concepts-replication.md | 9 -
.../concepts-schema-registry.md | 82 -
.../concepts-tiered-storage.md | 18 -
.../concepts-topic-compaction.md | 37 -
.../cookbooks-compaction.md | 132 -
.../cookbooks-deduplication.md | 122 -
.../cookbooks-encryption.md | 170 -
.../cookbooks-message-queue.md | 95 -
.../cookbooks-non-persistent.md | 59 -
.../cookbooks-partitioned.md | 78 -
.../cookbooks-retention-expiry.md | 285 -
.../cookbooks-tiered-storage.md | 136 -
.../version-2.1.0-incubating/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 409 -
.../version-2.1.0-incubating/deploy-bare-metal.md | 350 -
.../version-2.1.0-incubating/deploy-dcos.md | 183 -
.../version-2.1.0-incubating/deploy-kubernetes.md | 398 -
.../version-2.1.0-incubating/deploy-monitoring.md | 98 -
.../developing-binary-protocol.md | 553 -
.../version-2.1.0-incubating/developing-cpp.md | 101 -
.../developing-load-manager.md | 215 -
.../version-2.1.0-incubating/developing-schema.md | 58 -
.../version-2.1.0-incubating/developing-tools.md | 105 -
.../version-2.1.0-incubating/functions-api.md | 714 -
.../functions-deploying.md | 229 -
.../functions-guarantees.md | 42 -
.../version-2.1.0-incubating/functions-metrics.md | 44 -
.../version-2.1.0-incubating/functions-overview.md | 454 -
.../functions-quickstart.md | 266 -
.../version-2.1.0-incubating/functions-state.md | 119 -
.../getting-started-clients.md | 77 -
.../getting-started-concepts-and-architecture.md | 16 -
.../getting-started-docker.md | 168 -
.../getting-started-pulsar.md | 66 -
.../getting-started-standalone.md | 183 -
.../version-2.1.0-incubating/io-aerospike.md | 22 -
.../version-2.1.0-incubating/io-cassandra.md | 23 -
.../version-2.1.0-incubating/io-connectors.md | 19 -
.../version-2.1.0-incubating/io-develop.md | 195 -
.../version-2.1.0-incubating/io-kafka.md | 41 -
.../version-2.1.0-incubating/io-kinesis.md | 38 -
.../version-2.1.0-incubating/io-managing.md | 166 -
.../version-2.1.0-incubating/io-overview.md | 40 -
.../version-2.1.0-incubating/io-quickstart.md | 404 -
.../version-2.1.0-incubating/io-rabbitmq.md | 20 -
.../version-2.1.0-incubating/io-twitter.md | 25 -
.../reference-cli-tools.md | 606 -
.../reference-configuration.md | 468 -
.../reference-pulsar-admin.md | 1700 --
.../reference-terminology.md | 162 -
.../version-2.1.0-incubating/security-athenz.md | 93 -
.../security-authorization.md | 115 -
.../security-encryption.md | 170 -
.../version-2.1.0-incubating/security-extending.md | 207 -
.../version-2.1.0-incubating/security-overview.md | 40 -
.../security-tls-authentication.md | 146 -
.../security-tls-transport.md | 197 -
.../version-2.1.1-incubating/adaptors-kafka.md | 260 -
.../administration-proxy.md | 67 -
.../client-libraries-cpp.md | 184 -
.../client-libraries-python.md | 99 -
.../cookbooks-tiered-storage.md | 136 -
.../version-2.1.1-incubating/deploy-bare-metal.md | 350 -
.../version-2.1.1-incubating/functions-api.md | 708 -
.../functions-deploying.md | 229 -
.../functions-guarantees.md | 42 -
.../version-2.1.1-incubating/functions-overview.md | 454 -
.../functions-quickstart.md | 266 -
.../getting-started-clients.md | 58 -
.../getting-started-standalone.md | 198 -
.../version-2.1.1-incubating/io-managing.md | 166 -
.../version-2.1.1-incubating/io-quickstart.md | 405 -
.../reference-configuration.md | 468 -
.../reference-pulsar-admin.md | 1700 --
.../version-2.10.0/adaptors-kafka.md | 267 -
.../version-2.10.0/adaptors-spark.md | 81 -
.../version-2.10.0/adaptors-storm.md | 90 -
.../version-2.10.0/admin-api-brokers.md | 196 -
.../version-2.10.0/admin-api-clusters.md | 232 -
.../version-2.10.0/admin-api-functions.md | 589 -
.../version-2.10.0/admin-api-namespaces.md | 923 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.10.0/admin-api-overview.md | 121 -
.../version-2.10.0/admin-api-packages.md | 263 -
.../version-2.10.0/admin-api-partitioned-topics.md | 8 -
.../version-2.10.0/admin-api-permissions.md | 136 -
.../version-2.10.0/admin-api-persistent-topics.md | 8 -
.../version-2.10.0/admin-api-schemas.md | 7 -
.../version-2.10.0/admin-api-tenants.md | 171 -
.../version-2.10.0/admin-api-topics.md | 1805 --
.../version-2.10.0/administration-geo.md | 243 -
.../version-2.10.0/administration-isolation.md | 93 -
.../version-2.10.0/administration-load-balance.md | 196 -
.../version-2.10.0/administration-proxy.md | 80 -
.../administration-pulsar-manager.md | 183 -
.../version-2.10.0/administration-stats.md | 64 -
.../version-2.10.0/administration-upgrade.md | 151 -
.../version-2.10.0/administration-zk-bk.md | 343 -
.../version-2.10.0/client-libraries-cgo.md | 547 -
.../version-2.10.0/client-libraries-cpp.md | 661 -
.../version-2.10.0/client-libraries-dotnet.md | 407 -
.../version-2.10.0/client-libraries-go.md | 992 -
.../version-2.10.0/client-libraries-java.md | 1354 -
.../version-2.10.0/client-libraries-node.md | 605 -
.../version-2.10.0/client-libraries-python.md | 566 -
.../version-2.10.0/client-libraries-rest.md | 123 -
.../version-2.10.0/client-libraries-websocket.md | 599 -
.../concepts-architecture-overview.md | 166 -
.../version-2.10.0/concepts-authentication.md | 9 -
.../version-2.10.0/concepts-clients.md | 85 -
.../version-2.10.0/concepts-messaging.md | 839 -
.../version-2.10.0/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.10.0/concepts-overview.md | 31 -
.../version-2.10.0/concepts-proxy-sni-routing.md | 151 -
.../version-2.10.0/concepts-replication.md | 69 -
.../version-2.10.0/concepts-tiered-storage.md | 18 -
.../version-2.10.0/concepts-topic-compaction.md | 37 -
.../version-2.10.0/concepts-transactions.md | 30 -
.../version-2.10.0/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.10.0/cookbooks-compaction.md | 127 -
.../version-2.10.0/cookbooks-deduplication.md | 125 -
.../version-2.10.0/cookbooks-encryption.md | 170 -
.../version-2.10.0/cookbooks-message-queue.md | 118 -
.../version-2.10.0/cookbooks-non-persistent.md | 59 -
.../version-2.10.0/cookbooks-partitioned.md | 7 -
.../version-2.10.0/cookbooks-retention-expiry.md | 393 -
.../version-2.10.0/cookbooks-tiered-storage.md | 311 -
.../versioned_docs/version-2.10.0/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 399 -
.../version-2.10.0/deploy-bare-metal.md | 479 -
.../versioned_docs/version-2.10.0/deploy-docker.md | 52 -
.../version-2.10.0/deploy-kubernetes.md | 11 -
.../version-2.10.0/deploy-monitoring.md | 120 -
.../version-2.10.0/develop-plugin.md | 126 -
.../version-2.10.0/developing-binary-protocol.md | 610 -
.../version-2.10.0/developing-load-manager.md | 215 -
.../version-2.10.0/developing-tools.md | 105 -
.../versioned_docs/version-2.10.0/functions-cli.md | 198 -
.../version-2.10.0/functions-debug.md | 466 -
.../version-2.10.0/functions-deploy.md | 230 -
.../version-2.10.0/functions-develop.md | 1395 -
.../version-2.10.0/functions-metrics.md | 7 -
.../version-2.10.0/functions-overview.md | 194 -
.../version-2.10.0/functions-package.md | 431 -
.../version-2.10.0/functions-runtime.md | 369 -
.../version-2.10.0/functions-worker.md | 348 -
.../version-2.10.0/getting-started-clients.md | 44 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.10.0/getting-started-docker.md | 194 -
.../version-2.10.0/getting-started-helm.md | 363 -
.../version-2.10.0/getting-started-pulsar.md | 67 -
.../version-2.10.0/getting-started-standalone.md | 258 -
.../versioned_docs/version-2.10.0/helm-deploy.md | 379 -
.../versioned_docs/version-2.10.0/helm-install.md | 38 -
.../versioned_docs/version-2.10.0/helm-overview.md | 99 -
.../versioned_docs/version-2.10.0/helm-prepare.md | 73 -
.../versioned_docs/version-2.10.0/helm-tools.md | 43 -
.../versioned_docs/version-2.10.0/helm-upgrade.md | 34 -
.../version-2.10.0/io-aerospike-sink.md | 26 -
.../version-2.10.0/io-canal-source.md | 203 -
.../version-2.10.0/io-cassandra-sink.md | 56 -
.../version-2.10.0/io-cdc-debezium.md | 481 -
.../versioned_docs/version-2.10.0/io-cdc.md | 26 -
.../versioned_docs/version-2.10.0/io-cli.md | 606 -
.../versioned_docs/version-2.10.0/io-connectors.md | 249 -
.../version-2.10.0/io-debezium-source.md | 649 -
.../versioned_docs/version-2.10.0/io-debug.md | 329 -
.../versioned_docs/version-2.10.0/io-develop.md | 375 -
.../version-2.10.0/io-dynamodb-source.md | 78 -
.../version-2.10.0/io-elasticsearch-sink.md | 209 -
.../version-2.10.0/io-file-source.md | 150 -
.../versioned_docs/version-2.10.0/io-flume-sink.md | 54 -
.../version-2.10.0/io-flume-source.md | 54 -
.../versioned_docs/version-2.10.0/io-hbase-sink.md | 66 -
.../versioned_docs/version-2.10.0/io-hdfs2-sink.md | 61 -
.../versioned_docs/version-2.10.0/io-hdfs3-sink.md | 56 -
.../version-2.10.0/io-influxdb-sink.md | 113 -
.../versioned_docs/version-2.10.0/io-jdbc-sink.md | 148 -
.../versioned_docs/version-2.10.0/io-kafka-sink.md | 70 -
.../version-2.10.0/io-kafka-source.md | 211 -
.../version-2.10.0/io-kinesis-sink.md | 75 -
.../version-2.10.0/io-kinesis-source.md | 79 -
.../versioned_docs/version-2.10.0/io-mongo-sink.md | 53 -
.../version-2.10.0/io-netty-source.md | 207 -
.../versioned_docs/version-2.10.0/io-nsq-source.md | 21 -
.../versioned_docs/version-2.10.0/io-overview.md | 136 -
.../versioned_docs/version-2.10.0/io-quickstart.md | 816 -
.../version-2.10.0/io-rabbitmq-sink.md | 83 -
.../version-2.10.0/io-rabbitmq-source.md | 83 -
.../versioned_docs/version-2.10.0/io-redis-sink.md | 138 -
.../versioned_docs/version-2.10.0/io-solr-sink.md | 63 -
.../version-2.10.0/io-twitter-source.md | 28 -
.../versioned_docs/version-2.10.0/io-twitter.md | 7 -
.../versioned_docs/version-2.10.0/io-use.md | 1505 --
.../version-2.10.0/performance-pulsar-perf.md | 232 -
.../version-2.10.0/reference-cli-tools.md | 892 -
.../version-2.10.0/reference-configuration.md | 857 -
.../version-2.10.0/reference-connector-admin.md | 12 -
.../version-2.10.0/reference-metrics.md | 621 -
.../version-2.10.0/reference-pulsar-admin.md | 2797 --
.../version-2.10.0/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 957 -
.../version-2.10.0/schema-get-started.md | 95 -
.../versioned_docs/version-2.10.0/schema-manage.md | 960 -
.../version-2.10.0/schema-understand.md | 670 -
.../version-2.10.0/security-athenz.md | 93 -
.../version-2.10.0/security-authorization.md | 115 -
.../version-2.10.0/security-bouncy-castle.md | 139 -
.../version-2.10.0/security-encryption.md | 282 -
.../version-2.10.0/security-extending.md | 77 -
.../versioned_docs/version-2.10.0/security-jwt.md | 264 -
.../version-2.10.0/security-kerberos.md | 391 -
.../version-2.10.0/security-oauth2.md | 250 -
.../version-2.10.0/security-overview.md | 37 -
.../version-2.10.0/security-tls-authentication.md | 188 -
.../version-2.10.0/security-tls-keystore.md | 305 -
.../version-2.10.0/security-tls-transport.md | 276 -
.../version-2.10.0/security-token-admin.md | 159 -
.../version-2.10.0/security-versioning-policy.md | 62 -
.../sql-deployment-configurations.md | 246 -
.../version-2.10.0/sql-getting-started.md | 171 -
.../versioned_docs/version-2.10.0/sql-overview.md | 18 -
.../versioned_docs/version-2.10.0/sql-rest-api.md | 186 -
.../version-2.10.0/tiered-storage-aliyun.md | 218 -
.../version-2.10.0/tiered-storage-aws.md | 280 -
.../version-2.10.0/tiered-storage-azure.md | 224 -
.../version-2.10.0/tiered-storage-filesystem.md | 524 -
.../version-2.10.0/tiered-storage-gcs.md | 274 -
.../version-2.10.0/tiered-storage-overview.md | 50 -
.../version-2.10.0/transaction-api.md | 149 -
.../version-2.10.0/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.10.0/txn-how.md | 319 -
.../versioned_docs/version-2.10.0/txn-monitor.md | 10 -
.../versioned_docs/version-2.10.0/txn-use.md | 125 -
.../versioned_docs/version-2.10.0/txn-what.md | 60 -
.../versioned_docs/version-2.10.0/txn-why.md | 45 -
.../version-2.10.0/window-functions-context.md | 529 -
.../versioned_docs/version-2.2.0/adaptors-kafka.md | 262 -
.../versioned_docs/version-2.2.0/adaptors-spark.md | 67 -
.../versioned_docs/version-2.2.0/adaptors-storm.md | 105 -
.../version-2.2.0/client-libraries-cpp.md | 184 -
.../version-2.2.0/client-libraries-go.md | 463 -
.../version-2.2.0/client-libraries-python.md | 99 -
.../version-2.2.0/client-libraries-websocket.md | 410 -
.../version-2.2.0/cookbooks-tiered-storage.md | 219 -
.../versioned_docs/version-2.2.0/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 413 -
.../version-2.2.0/deploy-bare-metal.md | 393 -
.../versioned_docs/version-2.2.0/deploy-dcos.md | 183 -
.../version-2.2.0/developing-binary-protocol.md | 553 -
.../versioned_docs/version-2.2.0/developing-cpp.md | 101 -
.../version-2.2.0/developing-load-manager.md | 215 -
.../version-2.2.0/developing-schema.md | 58 -
.../versioned_docs/version-2.2.0/functions-api.md | 721 -
.../version-2.2.0/functions-deploying.md | 229 -
.../version-2.2.0/functions-guarantees.md | 42 -
.../version-2.2.0/functions-overview.md | 454 -
.../version-2.2.0/functions-quickstart.md | 266 -
.../version-2.2.0/getting-started-clients.md | 58 -
.../version-2.2.0/getting-started-standalone.md | 244 -
.../versioned_docs/version-2.2.0/io-managing.md | 166 -
.../versioned_docs/version-2.2.0/io-overview.md | 40 -
.../versioned_docs/version-2.2.0/io-quickstart.md | 404 -
.../version-2.2.0/reference-configuration.md | 468 -
.../version-2.2.0/reference-pulsar-admin.md | 1860 --
.../version-2.2.0/security-extending.md | 207 -
.../version-2.2.0/security-tls-transport.md | 212 -
.../version-2.2.0/sql-deployment-configurations.md | 151 -
.../version-2.2.0/sql-getting-started.md | 170 -
.../versioned_docs/version-2.2.0/sql-overview.md | 25 -
.../version-2.2.1/admin-api-persistent-topics.md | 623 -
.../version-2.2.1/client-libraries-go.md | 463 -
.../version-2.2.1/client-libraries-java.md | 468 -
.../version-2.2.1/client-libraries-websocket.md | 444 -
.../version-2.2.1/concepts-clients.md | 80 -
.../version-2.2.1/concepts-overview.md | 32 -
.../version-2.2.1/deploy-bare-metal.md | 420 -
.../version-2.2.1/functions-overview.md | 454 -
.../version-2.2.1/getting-started-docker.md | 168 -
.../version-2.2.1/getting-started-standalone.md | 244 -
.../website/versioned_docs/version-2.2.1/io-cdc.md | 147 -
.../versioned_docs/version-2.2.1/io-connectors.md | 21 -
.../versioned_docs/version-2.2.1/io-managing.md | 166 -
.../versioned_docs/version-2.2.1/io-overview.md | 41 -
.../versioned_docs/version-2.2.1/io-quickstart.md | 405 -
.../versioned_docs/version-2.2.1/io-rabbitmq.md | 20 -
.../website/versioned_docs/version-2.2.1/io-tcp.md | 20 -
.../version-2.2.1/reference-configuration.md | 479 -
.../version-2.2.1/reference-pulsar-admin.md | 1860 --
.../version-2.2.1/security-tls-authentication.md | 146 -
.../version-2.2.1/security-tls-transport.md | 229 -
.../version-2.2.1/security-token-admin.md | 167 -
.../version-2.2.1/security-token-client.md | 126 -
.../versioned_docs/version-2.3.0/adaptors-kafka.md | 264 -
.../versioned_docs/version-2.3.0/adaptors-storm.md | 91 -
.../version-2.3.0/admin-api-namespaces.md | 643 -
.../version-2.3.0/admin-api-partitioned-topics.md | 357 -
.../version-2.3.0/administration-proxy.md | 104 -
.../version-2.3.0/administration-zk-bk.md | 324 -
.../version-2.3.0/client-libraries-cpp.md | 182 -
.../version-2.3.0/client-libraries-go.md | 463 -
.../version-2.3.0/client-libraries-python.md | 243 -
.../version-2.3.0/concepts-messaging.md | 327 -
.../version-2.3.0/concepts-overview.md | 32 -
.../version-2.3.0/concepts-schema-registry.md | 84 -
.../version-2.3.0/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.3.0/cookbooks-retention-expiry.md | 285 -
.../version-2.3.0/deploy-bare-metal.md | 426 -
.../version-2.3.0/deploy-monitoring.md | 98 -
.../version-2.3.0/functions-deploying.md | 229 -
.../version-2.3.0/functions-quickstart.md | 337 -
.../version-2.3.0/getting-started-standalone.md | 250 -
.../versioned_docs/version-2.3.0/io-cdc-canal.md | 175 -
.../version-2.3.0/io-cdc-debezium.md | 182 -
.../website/versioned_docs/version-2.3.0/io-cdc.md | 17 -
.../versioned_docs/version-2.3.0/io-connectors.md | 22 -
.../versioned_docs/version-2.3.0/io-hbase.md | 28 -
.../versioned_docs/version-2.3.0/io-kafka.md | 45 -
.../versioned_docs/version-2.3.0/io-netty.md | 21 -
.../versioned_docs/version-2.3.0/io-quickstart.md | 393 -
.../version-2.3.0/reference-cli-tools.md | 615 -
.../version-2.3.0/reference-configuration.md | 481 -
.../version-2.3.0/reference-pulsar-admin.md | 2306 --
.../version-2.3.0/reference-terminology.md | 162 -
.../version-2.3.0/security-authorization.md | 100 -
.../version-2.3.0/security-tls-transport.md | 229 -
.../versioned_docs/version-2.3.0/sql-overview.md | 25 -
.../version-2.3.0/window-functions-context.md | 529 -
.../versioned_docs/version-2.3.1/adaptors-kafka.md | 264 -
.../admin-api-non-persistent-topics.md | 254 -
.../version-2.3.1/administration-dashboard.md | 61 -
.../version-2.3.1/administration-load-balance.md | 215 -
.../version-2.3.1/client-libraries-cpp.md | 182 -
.../version-2.3.1/client-libraries-go.md | 473 -
.../version-2.3.1/client-libraries-java.md | 475 -
.../version-2.3.1/client-libraries-python.md | 253 -
.../version-2.3.1/concepts-messaging.md | 327 -
.../version-2.3.1/concepts-overview.md | 32 -
.../version-2.3.1/concepts-schema-registry.md | 84 -
.../deploy-bare-metal-multi-cluster.md | 425 -
.../version-2.3.1/deploy-bare-metal.md | 435 -
.../version-2.3.1/functions-overview.md | 455 -
.../version-2.3.1/getting-started-docker.md | 163 -
.../version-2.3.1/getting-started-standalone.md | 235 -
.../version-2.3.1/io-cdc-debezium.md | 182 -
.../versioned_docs/version-2.3.1/io-connectors.md | 29 -
.../versioned_docs/version-2.3.1/io-develop.md | 195 -
.../version-2.3.1/io-elasticsearch.md | 22 -
.../versioned_docs/version-2.3.1/io-file.md | 28 -
.../versioned_docs/version-2.3.1/io-hdfs.md | 27 -
.../versioned_docs/version-2.3.1/io-influxdb.md | 26 -
.../versioned_docs/version-2.3.1/io-mongo.md | 21 -
.../versioned_docs/version-2.3.1/io-quickstart.md | 393 -
.../versioned_docs/version-2.3.1/io-rabbitmq.md | 55 -
.../versioned_docs/version-2.3.1/io-solr.md | 22 -
.../version-2.3.1/reference-cli-tools.md | 717 -
.../version-2.3.1/reference-configuration.md | 484 -
.../version-2.3.1/reference-pulsar-admin.md | 2340 --
.../version-2.3.1/reference-terminology.md | 167 -
.../version-2.3.1/security-tls-transport.md | 229 -
.../version-2.3.1/security-token-admin.md | 168 -
.../version-2.3.1/sql-getting-started.md | 170 -
.../version-2.3.1/window-functions-context.md | 529 -
.../versioned_docs/version-2.3.2/adaptors-spark.md | 77 -
.../version-2.3.2/admin-api-namespaces.md | 759 -
.../version-2.3.2/admin-api-schemas.md | 99 -
.../version-2.3.2/administration-geo.md | 129 -
.../version-2.3.2/concepts-clients.md | 80 -
.../version-2.3.2/concepts-messaging.md | 382 -
.../version-2.3.2/concepts-schema-registry.md | 84 -
.../version-2.3.2/deploy-bare-metal.md | 437 -
.../version-2.3.2/functions-guarantees.md | 42 -
.../version-2.3.2/functions-worker.md | 241 -
.../version-2.3.2/getting-started-clients.md | 57 -
.../version-2.3.2/getting-started-docker.md | 169 -
.../version-2.3.2/getting-started-standalone.md | 221 -
.../version-2.3.2/io-cdc-debezium.md | 182 -
.../versioned_docs/version-2.3.2/io-connectors.md | 30 -
.../versioned_docs/version-2.3.2/io-quickstart.md | 393 -
.../versioned_docs/version-2.3.2/io-redis.md | 28 -
.../version-2.3.2/reference-cli-tools.md | 717 -
.../version-2.3.2/reference-configuration.md | 490 -
.../version-2.3.2/reference-pulsar-admin.md | 2651 --
.../version-2.3.2/security-kerberos.md | 284 -
.../version-2.3.2/security-overview.md | 42 -
.../version-2.3.2/security-tls-transport.md | 229 -
.../version-2.3.2/window-functions-context.md | 529 -
.../versioned_docs/version-2.4.0/adaptors-kafka.md | 263 -
.../version-2.4.0/admin-api-overview.md | 93 -
.../version-2.4.0/administration-geo.md | 158 -
.../version-2.4.0/administration-zk-bk.md | 330 -
.../version-2.4.0/client-libraries-go.md | 541 -
.../version-2.4.0/client-libraries-java.md | 662 -
.../version-2.4.0/client-libraries-python.md | 287 -
.../version-2.4.0/concepts-messaging.md | 395 -
.../version-2.4.0/concepts-schema-registry.md | 120 -
.../version-2.4.0/concepts-tiered-storage.md | 18 -
.../version-2.4.0/cookbooks-compaction.md | 132 -
.../version-2.4.0/cookbooks-tiered-storage.md | 235 -
.../version-2.4.0/deploy-bare-metal.md | 439 -
.../version-2.4.0/developing-binary-protocol.md | 553 -
.../versioned_docs/version-2.4.0/developing-cpp.md | 101 -
.../versioned_docs/version-2.4.0/functions-api.md | 738 -
.../version-2.4.0/functions-debugging.md | 452 -
.../version-2.4.0/functions-overview.md | 515 -
.../version-2.4.0/functions-quickstart.md | 390 -
.../version-2.4.0/functions-runtime.md | 142 -
.../version-2.4.0/functions-state.md | 177 -
.../version-2.4.0/functions-worker.md | 247 -
.../version-2.4.0/getting-started-standalone.md | 221 -
.../versioned_docs/version-2.4.0/io-cdc-canal.md | 175 -
.../version-2.4.0/io-cdc-debezium.md | 304 -
.../versioned_docs/version-2.4.0/io-managing.md | 166 -
.../versioned_docs/version-2.4.0/io-quickstart.md | 750 -
.../version-2.4.0/reference-cli-tools.md | 721 -
.../version-2.4.0/reference-configuration.md | 511 -
.../version-2.4.0/reference-metrics.md | 277 -
.../version-2.4.0/reference-pulsar-admin.md | 2651 --
.../versioned_docs/version-2.4.0/security-jwt.md | 241 -
.../version-2.4.0/security-kerberos.md | 395 -
.../version-2.4.0/security-overview.md | 38 -
.../version-2.4.0/security-tls-authentication.md | 158 -
.../version-2.4.0/security-tls-transport.md | 229 -
.../version-2.4.0/security-token-admin.md | 168 -
.../version-2.4.0/sql-getting-started.md | 170 -
.../version-2.4.0/window-functions-context.md | 529 -
.../version-2.4.1/admin-api-functions.md | 546 -
.../admin-api-non-persistent-topics.md | 264 -
.../version-2.4.1/admin-api-overview.md | 89 -
.../version-2.4.1/admin-api-partitioned-topics.md | 377 -
.../version-2.4.1/administration-dashboard.md | 60 -
.../version-2.4.1/administration-geo.md | 158 -
.../version-2.4.1/administration-upgrade.md | 153 -
.../version-2.4.1/client-libraries-java.md | 704 -
.../version-2.4.1/client-libraries-python.md | 287 -
.../version-2.4.1/concepts-messaging.md | 416 -
.../version-2.4.1/concepts-schema-registry.md | 120 -
.../version-2.4.1/concepts-tiered-storage.md | 18 -
.../version-2.4.1/cookbooks-compaction.md | 127 -
.../version-2.4.1/develop-bare-metal.md | 439 -
.../versioned_docs/version-2.4.1/functions-cli.md | 196 -
.../version-2.4.1/functions-debug.md | 448 -
.../version-2.4.1/functions-deploy.md | 211 -
.../version-2.4.1/functions-develop.md | 962 -
.../version-2.4.1/functions-overview.md | 190 -
.../version-2.4.1/functions-runtime.md | 145 -
.../version-2.4.1/functions-worker.md | 248 -
.../version-2.4.1/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.4.1/io-cdc-canal.md | 175 -
.../version-2.4.1/io-cdc-debezium.md | 304 -
.../versioned_docs/version-2.4.1/io-connectors.md | 31 -
.../versioned_docs/version-2.4.1/io-debug.md | 329 -
.../versioned_docs/version-2.4.1/io-develop.md | 195 -
.../versioned_docs/version-2.4.1/io-jdbc.md | 24 -
.../versioned_docs/version-2.4.1/io-managing.md | 166 -
.../versioned_docs/version-2.4.1/io-netty.md | 148 -
.../versioned_docs/version-2.4.1/io-quickstart.md | 750 -
.../website/versioned_docs/version-2.4.1/io-use.md | 1505 --
.../version-2.4.1/reference-configuration.md | 511 -
.../version-2.4.1/reference-connector-admin.md | 605 -
.../version-2.4.1/reference-metrics.md | 277 -
.../version-2.4.1/reference-pulsar-admin.md | 2174 --
.../schema-evolution-compatibility.md | 784 -
.../version-2.4.1/schema-get-started.md | 91 -
.../versioned_docs/version-2.4.1/schema-manage.md | 786 -
.../version-2.4.1/schema-understand.md | 576 -
.../version-2.4.1/security-athenz.md | 93 -
.../version-2.4.1/security-authorization.md | 100 -
.../version-2.4.1/security-kerberos.md | 391 -
.../version-2.4.1/security-overview.md | 38 -
.../version-2.4.1/security-tls-authentication.md | 156 -
.../version-2.4.1/security-tls-transport.md | 231 -
.../version-2.4.1/security-token-client.md | 123 -
.../version-2.4.1/window-functions-context.md | 529 -
.../version-2.4.2/admin-api-functions.md | 546 -
.../admin-api-non-persistent-topics.md | 264 -
.../version-2.4.2/admin-api-overview.md | 89 -
.../version-2.4.2/admin-api-partitioned-topics.md | 377 -
.../version-2.4.2/administration-dashboard.md | 60 -
.../version-2.4.2/administration-geo.md | 157 -
.../version-2.4.2/administration-upgrade.md | 153 -
.../version-2.4.2/client-libraries-java.md | 704 -
.../version-2.4.2/client-libraries-python.md | 287 -
.../version-2.4.2/concepts-messaging.md | 416 -
.../version-2.4.2/concepts-schema-registry.md | 118 -
.../version-2.4.2/concepts-tiered-storage.md | 18 -
.../version-2.4.2/cookbooks-compaction.md | 127 -
.../version-2.4.2/develop-bare-metal.md | 439 -
.../versioned_docs/version-2.4.2/functions-cli.md | 196 -
.../version-2.4.2/functions-debug.md | 448 -
.../version-2.4.2/functions-deploy.md | 211 -
.../version-2.4.2/functions-develop.md | 960 -
.../version-2.4.2/functions-overview.md | 190 -
.../version-2.4.2/functions-runtime.md | 145 -
.../version-2.4.2/functions-worker.md | 248 -
.../version-2.4.2/getting-started-standalone.md | 228 -
.../versioned_docs/version-2.4.2/io-cdc-canal.md | 175 -
.../version-2.4.2/io-cdc-debezium.md | 305 -
.../versioned_docs/version-2.4.2/io-connectors.md | 31 -
.../versioned_docs/version-2.4.2/io-debug.md | 329 -
.../versioned_docs/version-2.4.2/io-develop.md | 195 -
.../versioned_docs/version-2.4.2/io-jdbc.md | 24 -
.../versioned_docs/version-2.4.2/io-managing.md | 166 -
.../versioned_docs/version-2.4.2/io-netty.md | 148 -
.../versioned_docs/version-2.4.2/io-quickstart.md | 750 -
.../website/versioned_docs/version-2.4.2/io-use.md | 1505 --
.../version-2.4.2/reference-configuration.md | 511 -
.../version-2.4.2/reference-connector-admin.md | 606 -
.../version-2.4.2/reference-metrics.md | 277 -
.../version-2.4.2/reference-pulsar-admin.md | 2174 --
.../schema-evolution-compatibility.md | 784 -
.../version-2.4.2/schema-get-started.md | 91 -
.../versioned_docs/version-2.4.2/schema-manage.md | 786 -
.../version-2.4.2/schema-understand.md | 576 -
.../version-2.4.2/security-athenz.md | 93 -
.../version-2.4.2/security-authorization.md | 100 -
.../version-2.4.2/security-kerberos.md | 391 -
.../version-2.4.2/security-overview.md | 38 -
.../version-2.4.2/security-tls-authentication.md | 156 -
.../version-2.4.2/security-tls-transport.md | 231 -
.../version-2.4.2/security-token-client.md | 123 -
.../version-2.4.2/window-functions-context.md | 529 -
.../versioned_docs/version-2.5.0/adaptors-kafka.md | 264 -
.../admin-api-non-partitioned-topics.md | 104 -
.../version-2.5.0/admin-api-partitioned-topics.md | 376 -
.../version-2.5.0/admin-api-persistent-topics.md | 661 -
.../version-2.5.0/admin-api-schemas.md | 7 -
.../version-2.5.0/administration-dashboard.md | 63 -
.../version-2.5.0/administration-geo.md | 196 -
.../version-2.5.0/administration-load-balance.md | 182 -
.../version-2.5.0/administration-proxy.md | 105 -
.../version-2.5.0/administration-pulsar-manager.md | 183 -
.../version-2.5.0/administration-stats.md | 64 -
.../version-2.5.0/administration-upgrade.md | 151 -
.../version-2.5.0/administration-zk-bk.md | 322 -
.../version-2.5.0/client-libraries-cpp.md | 210 -
.../version-2.5.0/client-libraries-go.md | 538 -
.../version-2.5.0/client-libraries-java.md | 820 -
.../version-2.5.0/client-libraries-node.md | 402 -
.../version-2.5.0/client-libraries-python.md | 280 -
.../version-2.5.0/concepts-clients.md | 82 -
.../version-2.5.0/concepts-messaging.md | 450 -
.../version-2.5.0/concepts-overview.md | 31 -
.../version-2.5.0/concepts-schema-registry.md | 106 -
.../version-2.5.0/concepts-tiered-storage.md | 18 -
.../version-2.5.0/cookbooks-deduplication.md | 121 -
.../version-2.5.0/cookbooks-retention-expiry.md | 291 -
.../version-2.5.0/cookbooks-tiered-storage.md | 294 -
.../versioned_docs/version-2.5.0/deploy-aws.md | 224 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.5.0/deploy-bare-metal.md | 454 -
.../versioned_docs/version-2.5.0/deploy-dcos.md | 183 -
.../version-2.5.0/deploy-kubernetes.md | 12 -
.../version-2.5.0/deploy-monitoring.md | 90 -
.../versioned_docs/version-2.5.0/functions-cli.md | 198 -
.../version-2.5.0/functions-debug.md | 455 -
.../version-2.5.0/functions-develop.md | 1046 -
.../version-2.5.0/functions-metrics.md | 7 -
.../version-2.5.0/functions-overview.md | 202 -
.../version-2.5.0/functions-runtime.md | 179 -
.../version-2.5.0/functions-worker.md | 247 -
.../version-2.5.0/getting-started-clients.md | 59 -
.../version-2.5.0/getting-started-docker.md | 159 -
.../version-2.5.0/getting-started-helm.md | 334 -
.../version-2.5.0/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.5.0/helm-deploy.md | 388 -
.../versioned_docs/version-2.5.0/helm-install.md | 40 -
.../versioned_docs/version-2.5.0/helm-overview.md | 111 -
.../versioned_docs/version-2.5.0/helm-prepare.md | 78 -
.../versioned_docs/version-2.5.0/helm-tools.md | 43 -
.../versioned_docs/version-2.5.0/helm-upgrade.md | 35 -
.../version-2.5.0/io-aerospike-sink.md | 26 -
.../version-2.5.0/io-canal-source.md | 203 -
.../version-2.5.0/io-cassandra-sink.md | 54 -
.../version-2.5.0/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.5.0/io-cdc.md | 26 -
.../website/versioned_docs/version-2.5.0/io-cli.md | 601 -
.../versioned_docs/version-2.5.0/io-connectors.md | 189 -
.../version-2.5.0/io-debezium-source.md | 350 -
.../versioned_docs/version-2.5.0/io-develop.md | 240 -
.../version-2.5.0/io-elasticsearch-sink.md | 50 -
.../versioned_docs/version-2.5.0/io-file-source.md | 138 -
.../versioned_docs/version-2.5.0/io-flume-sink.md | 52 -
.../version-2.5.0/io-flume-source.md | 52 -
.../versioned_docs/version-2.5.0/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.5.0/io-hdfs2-sink.md | 54 -
.../versioned_docs/version-2.5.0/io-hdfs3-sink.md | 54 -
.../version-2.5.0/io-influxdb-sink.md | 61 -
.../versioned_docs/version-2.5.0/io-jdbc-sink.md | 57 -
.../versioned_docs/version-2.5.0/io-kafka-sink.md | 69 -
.../version-2.5.0/io-kafka-source.md | 171 -
.../version-2.5.0/io-kinesis-sink.md | 73 -
.../version-2.5.0/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.5.0/io-mongo-sink.md | 51 -
.../version-2.5.0/io-netty-source.md | 205 -
.../versioned_docs/version-2.5.0/io-overview.md | 136 -
.../versioned_docs/version-2.5.0/io-quickstart.md | 828 -
.../version-2.5.0/io-rabbitmq-sink.md | 81 -
.../version-2.5.0/io-rabbitmq-source.md | 78 -
.../versioned_docs/version-2.5.0/io-redis-sink.md | 70 -
.../versioned_docs/version-2.5.0/io-solr-sink.md | 61 -
.../version-2.5.0/io-twitter-source.md | 28 -
.../versioned_docs/version-2.5.0/io-twitter.md | 7 -
.../website/versioned_docs/version-2.5.0/io-use.md | 1506 --
.../version-2.5.0/reference-cli-tools.md | 760 -
.../version-2.5.0/reference-configuration.md | 501 -
.../version-2.5.0/reference-connector-admin.md | 11 -
.../version-2.5.0/reference-metrics.md | 276 -
.../version-2.5.0/reference-pulsar-admin.md | 2314 --
.../schema-evolution-compatibility.md | 953 -
.../version-2.5.0/schema-get-started.md | 91 -
.../versioned_docs/version-2.5.0/schema-manage.md | 809 -
.../version-2.5.0/schema-understand.md | 592 -
.../version-2.5.0/security-encryption.md | 176 -
.../version-2.5.0/security-extending.md | 194 -
.../version-2.5.0/security-overview.md | 31 -
.../version-2.5.0/security-tls-authentication.md | 175 -
.../version-2.5.0/security-tls-transport.md | 244 -
.../version-2.5.0/security-token-admin.md | 159 -
.../version-2.5.0/sql-deployment-configurations.md | 156 -
.../version-2.5.0/sql-getting-started.md | 171 -
.../versioned_docs/version-2.5.0/sql-overview.md | 18 -
.../versioned_docs/version-2.5.0/sql-rest-api.md | 186 -
.../version-2.5.0/window-functions-context.md | 529 -
.../versioned_docs/version-2.5.1/adaptors-kafka.md | 265 -
.../admin-api-non-partitioned-topics.md | 160 -
.../version-2.5.1/admin-api-partitioned-topics.md | 377 -
.../version-2.5.1/admin-api-persistent-topics.md | 673 -
.../version-2.5.1/administration-geo.md | 196 -
.../version-2.5.1/client-libraries-cgo.md | 545 -
.../version-2.5.1/client-libraries-cpp.md | 253 -
.../version-2.5.1/client-libraries-go.md | 661 -
.../version-2.5.1/client-libraries-java.md | 822 -
.../version-2.5.1/client-libraries-node.md | 404 -
.../version-2.5.1/client-libraries-python.md | 295 -
.../concepts-architecture-overview.md | 162 -
.../version-2.5.1/concepts-authentication.md | 9 -
.../version-2.5.1/concepts-clients.md | 85 -
.../version-2.5.1/concepts-messaging.md | 469 -
.../version-2.5.1/concepts-multi-tenancy.md | 55 -
.../version-2.5.1/concepts-overview.md | 31 -
.../version-2.5.1/concepts-replication.md | 9 -
.../version-2.5.1/concepts-tiered-storage.md | 18 -
.../version-2.5.1/concepts-topic-compaction.md | 37 -
.../version-2.5.1/cookbooks-compaction.md | 127 -
.../version-2.5.1/cookbooks-partitioned.md | 93 -
.../version-2.5.1/deploy-bare-metal.md | 452 -
.../version-2.5.1/deploy-monitoring.md | 90 -
.../version-2.5.1/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.5.1/functions-cli.md | 198 -
.../version-2.5.1/functions-debug.md | 461 -
.../version-2.5.1/functions-develop.md | 1046 -
.../version-2.5.1/functions-overview.md | 194 -
.../version-2.5.1/functions-runtime.md | 189 -
.../version-2.5.1/getting-started-clients.md | 32 -
.../version-2.5.1/getting-started-standalone.md | 230 -
.../website/versioned_docs/version-2.5.1/io-cli.md | 601 -
.../versioned_docs/version-2.5.1/io-connectors.md | 197 -
.../version-2.5.1/io-debezium-source.md | 478 -
.../versioned_docs/version-2.5.1/io-debug.md | 329 -
.../versioned_docs/version-2.5.1/io-develop.md | 240 -
.../version-2.5.1/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.5.1/io-hbase-sink.md | 64 -
.../version-2.5.1/io-influxdb-sink.md | 106 -
.../version-2.5.1/io-kafka-source.md | 171 -
.../versioned_docs/version-2.5.1/io-quickstart.md | 828 -
.../version-2.5.1/io-rabbitmq-source.md | 78 -
.../version-2.5.1/kubernetes-helm.md | 363 -
.../versioned_docs/version-2.5.1/pulsar-2.0.md | 67 -
.../version-2.5.1/reference-cli-tools.md | 760 -
.../version-2.5.1/reference-configuration.md | 520 -
.../version-2.5.1/reference-metrics.md | 277 -
.../version-2.5.1/reference-pulsar-admin.md | 2503 --
.../schema-evolution-compatibility.md | 957 -
.../version-2.5.1/schema-get-started.md | 95 -
.../versioned_docs/version-2.5.1/schema-manage.md | 858 -
.../version-2.5.1/schema-understand.md | 591 -
.../version-2.5.1/security-bouncy-castle.md | 122 -
.../versioned_docs/version-2.5.1/security-jwt.md | 249 -
.../version-2.5.1/security-tls-authentication.md | 177 -
.../version-2.5.1/security-tls-transport.md | 246 -
.../version-2.5.1/standalone-docker.md | 159 -
.../version-2.5.1/window-functions-context.md | 529 -
.../versioned_docs/version-2.5.2/adaptors-kafka.md | 265 -
.../admin-api-non-partitioned-topics.md | 160 -
.../version-2.5.2/admin-api-partitioned-topics.md | 377 -
.../version-2.5.2/admin-api-persistent-topics.md | 673 -
.../version-2.5.2/administration-geo.md | 196 -
.../version-2.5.2/client-libraries-cgo.md | 545 -
.../version-2.5.2/client-libraries-cpp.md | 253 -
.../version-2.5.2/client-libraries-go.md | 661 -
.../version-2.5.2/client-libraries-java.md | 822 -
.../version-2.5.2/client-libraries-node.md | 404 -
.../version-2.5.2/client-libraries-python.md | 295 -
.../version-2.5.2/concepts-messaging.md | 469 -
.../version-2.5.2/concepts-overview.md | 31 -
.../version-2.5.2/cookbooks-compaction.md | 127 -
.../version-2.5.2/cookbooks-partitioned.md | 93 -
.../version-2.5.2/deploy-bare-metal.md | 452 -
.../version-2.5.2/deploy-monitoring.md | 90 -
.../version-2.5.2/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.5.2/functions-cli.md | 198 -
.../version-2.5.2/functions-debug.md | 461 -
.../version-2.5.2/functions-develop.md | 1046 -
.../version-2.5.2/functions-overview.md | 194 -
.../version-2.5.2/functions-runtime.md | 189 -
.../version-2.5.2/getting-started-clients.md | 32 -
.../website/versioned_docs/version-2.5.2/io-cli.md | 601 -
.../versioned_docs/version-2.5.2/io-connectors.md | 197 -
.../version-2.5.2/io-debezium-source.md | 478 -
.../versioned_docs/version-2.5.2/io-debug.md | 329 -
.../versioned_docs/version-2.5.2/io-develop.md | 240 -
.../version-2.5.2/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.5.2/io-hbase-sink.md | 63 -
.../version-2.5.2/io-influxdb-sink.md | 106 -
.../version-2.5.2/io-kafka-source.md | 171 -
.../versioned_docs/version-2.5.2/io-quickstart.md | 828 -
.../version-2.5.2/io-rabbitmq-source.md | 78 -
.../version-2.5.2/reference-cli-tools.md | 760 -
.../version-2.5.2/reference-configuration.md | 521 -
.../version-2.5.2/reference-metrics.md | 277 -
.../version-2.5.2/reference-pulsar-admin.md | 2503 --
.../version-2.5.2/schema-get-started.md | 95 -
.../version-2.5.2/schema-understand.md | 591 -
.../version-2.5.2/security-bouncy-castle.md | 122 -
.../versioned_docs/version-2.5.2/security-jwt.md | 249 -
.../version-2.5.2/security-tls-authentication.md | 177 -
.../version-2.5.2/security-tls-transport.md | 246 -
.../version-2.5.2/window-functions-context.md | 529 -
.../versioned_docs/version-2.6.0/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.6.0/adaptors-spark.md | 73 -
.../versioned_docs/version-2.6.0/adaptors-storm.md | 90 -
.../version-2.6.0/admin-api-brokers.md | 149 -
.../version-2.6.0/admin-api-clusters.md | 210 -
.../version-2.6.0/admin-api-functions.md | 546 -
.../version-2.6.0/admin-api-namespaces.md | 759 -
.../admin-api-non-partitioned-topics.md | 160 -
.../admin-api-non-persistent-topics.md | 264 -
.../version-2.6.0/admin-api-overview.md | 89 -
.../version-2.6.0/admin-api-partitioned-topics.md | 377 -
.../version-2.6.0/admin-api-permissions.md | 115 -
.../version-2.6.0/admin-api-persistent-topics.md | 697 -
.../version-2.6.0/admin-api-schemas.md | 7 -
.../version-2.6.0/admin-api-tenants.md | 86 -
.../version-2.6.0/administration-dashboard.md | 63 -
.../version-2.6.0/administration-geo.md | 196 -
.../version-2.6.0/administration-load-balance.md | 182 -
.../version-2.6.0/administration-proxy.md | 106 -
.../version-2.6.0/administration-pulsar-manager.md | 183 -
.../version-2.6.0/administration-stats.md | 64 -
.../version-2.6.0/administration-upgrade.md | 151 -
.../version-2.6.0/administration-zk-bk.md | 350 -
.../version-2.6.0/client-libraries-cgo.md | 545 -
.../version-2.6.0/client-libraries-cpp.md | 253 -
.../version-2.6.0/client-libraries-dotnet.md | 385 -
.../version-2.6.0/client-libraries-go.md | 662 -
.../version-2.6.0/client-libraries-java.md | 854 -
.../version-2.6.0/client-libraries-node.md | 404 -
.../version-2.6.0/client-libraries-python.md | 295 -
.../version-2.6.0/client-libraries-websocket.md | 444 -
.../concepts-architecture-overview.md | 153 -
.../version-2.6.0/concepts-authentication.md | 9 -
.../version-2.6.0/concepts-clients.md | 88 -
.../version-2.6.0/concepts-messaging.md | 499 -
.../version-2.6.0/concepts-multi-tenancy.md | 40 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.6.0/concepts-overview.md | 31 -
.../version-2.6.0/concepts-replication.md | 9 -
.../version-2.6.0/concepts-tiered-storage.md | 18 -
.../version-2.6.0/concepts-topic-compaction.md | 37 -
.../version-2.6.0/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.6.0/cookbooks-compaction.md | 127 -
.../version-2.6.0/cookbooks-deduplication.md | 121 -
.../version-2.6.0/cookbooks-encryption.md | 170 -
.../version-2.6.0/cookbooks-message-queue.md | 95 -
.../version-2.6.0/cookbooks-non-persistent.md | 59 -
.../version-2.6.0/cookbooks-partitioned.md | 93 -
.../version-2.6.0/cookbooks-retention-expiry.md | 301 -
.../version-2.6.0/cookbooks-tiered-storage.md | 297 -
.../versioned_docs/version-2.6.0/deploy-aws.md | 224 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.6.0/deploy-bare-metal.md | 452 -
.../versioned_docs/version-2.6.0/deploy-dcos.md | 183 -
.../version-2.6.0/deploy-kubernetes.md | 11 -
.../version-2.6.0/deploy-monitoring.md | 90 -
.../versioned_docs/version-2.6.0/develop-schema.md | 58 -
.../version-2.6.0/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.6.0/developing-cpp.md | 101 -
.../version-2.6.0/developing-load-manager.md | 215 -
.../version-2.6.0/developing-tools.md | 105 -
.../versioned_docs/version-2.6.0/functions-cli.md | 198 -
.../version-2.6.0/functions-debug.md | 461 -
.../version-2.6.0/functions-deploy.md | 211 -
.../version-2.6.0/functions-develop.md | 1048 -
.../version-2.6.0/functions-metrics.md | 7 -
.../version-2.6.0/functions-overview.md | 194 -
.../version-2.6.0/functions-runtime.md | 186 -
.../version-2.6.0/functions-worker.md | 282 -
.../version-2.6.0/getting-started-clients.md | 33 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.6.0/getting-started-docker.md | 159 -
.../version-2.6.0/getting-started-helm.md | 341 -
.../version-2.6.0/getting-started-pulsar.md | 67 -
.../version-2.6.0/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.6.0/helm-deploy.md | 379 -
.../versioned_docs/version-2.6.0/helm-install.md | 41 -
.../versioned_docs/version-2.6.0/helm-overview.md | 101 -
.../versioned_docs/version-2.6.0/helm-prepare.md | 85 -
.../versioned_docs/version-2.6.0/helm-tools.md | 43 -
.../versioned_docs/version-2.6.0/helm-upgrade.md | 34 -
.../version-2.6.0/io-aerospike-sink.md | 26 -
.../version-2.6.0/io-canal-source.md | 203 -
.../version-2.6.0/io-cassandra-sink.md | 54 -
.../version-2.6.0/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.6.0/io-cdc.md | 26 -
.../website/versioned_docs/version-2.6.0/io-cli.md | 601 -
.../versioned_docs/version-2.6.0/io-connectors.md | 226 -
.../version-2.6.0/io-debezium-source.md | 496 -
.../versioned_docs/version-2.6.0/io-debug.md | 329 -
.../versioned_docs/version-2.6.0/io-develop.md | 240 -
.../version-2.6.0/io-dynamodb-source.md | 76 -
.../version-2.6.0/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.6.0/io-file-source.md | 138 -
.../versioned_docs/version-2.6.0/io-flume-sink.md | 52 -
.../version-2.6.0/io-flume-source.md | 52 -
.../versioned_docs/version-2.6.0/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.6.0/io-hdfs2-sink.md | 54 -
.../versioned_docs/version-2.6.0/io-hdfs3-sink.md | 54 -
.../version-2.6.0/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.6.0/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.6.0/io-kafka-sink.md | 69 -
.../version-2.6.0/io-kafka-source.md | 171 -
.../version-2.6.0/io-kinesis-sink.md | 73 -
.../version-2.6.0/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.6.0/io-mongo-sink.md | 51 -
.../version-2.6.0/io-netty-source.md | 205 -
.../versioned_docs/version-2.6.0/io-overview.md | 136 -
.../versioned_docs/version-2.6.0/io-quickstart.md | 817 -
.../version-2.6.0/io-rabbitmq-sink.md | 81 -
.../version-2.6.0/io-rabbitmq-source.md | 78 -
.../versioned_docs/version-2.6.0/io-redis-sink.md | 70 -
.../versioned_docs/version-2.6.0/io-solr-sink.md | 61 -
.../version-2.6.0/io-twitter-source.md | 28 -
.../versioned_docs/version-2.6.0/io-twitter.md | 7 -
.../website/versioned_docs/version-2.6.0/io-use.md | 1505 --
.../version-2.6.0/performance-pulsar-perf.md | 188 -
.../version-2.6.0/reference-cli-tools.md | 777 -
.../version-2.6.0/reference-configuration.md | 552 -
.../version-2.6.0/reference-connector-admin.md | 11 -
.../version-2.6.0/reference-metrics.md | 449 -
.../version-2.6.0/reference-pulsar-admin.md | 2546 --
.../version-2.6.0/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.6.0/schema-get-started.md | 95 -
.../versioned_docs/version-2.6.0/schema-manage.md | 809 -
.../version-2.6.0/schema-understand.md | 591 -
.../version-2.6.0/security-athenz.md | 93 -
.../version-2.6.0/security-authorization.md | 100 -
.../version-2.6.0/security-bouncy-castle.md | 122 -
.../version-2.6.0/security-encryption.md | 180 -
.../version-2.6.0/security-extending.md | 194 -
.../versioned_docs/version-2.6.0/security-jwt.md | 264 -
.../version-2.6.0/security-kerberos.md | 391 -
.../version-2.6.0/security-overview.md | 31 -
.../version-2.6.0/security-tls-authentication.md | 186 -
.../version-2.6.0/security-tls-keystore.md | 287 -
.../version-2.6.0/security-tls-transport.md | 257 -
.../version-2.6.0/security-token-admin.md | 159 -
.../version-2.6.0/sql-deployment-configurations.md | 159 -
.../version-2.6.0/sql-getting-started.md | 171 -
.../versioned_docs/version-2.6.0/sql-overview.md | 18 -
.../versioned_docs/version-2.6.0/sql-rest-api.md | 186 -
.../version-2.6.0/window-functions-context.md | 529 -
.../versioned_docs/version-2.6.1/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.6.1/adaptors-spark.md | 72 -
.../versioned_docs/version-2.6.1/adaptors-storm.md | 90 -
.../version-2.6.1/admin-api-brokers.md | 149 -
.../version-2.6.1/admin-api-clusters.md | 210 -
.../version-2.6.1/admin-api-functions.md | 546 -
.../version-2.6.1/admin-api-namespaces.md | 766 -
.../admin-api-non-partitioned-topics.md | 160 -
.../admin-api-non-persistent-topics.md | 264 -
.../version-2.6.1/admin-api-overview.md | 89 -
.../version-2.6.1/admin-api-partitioned-topics.md | 377 -
.../version-2.6.1/admin-api-permissions.md | 115 -
.../version-2.6.1/admin-api-persistent-topics.md | 697 -
.../version-2.6.1/admin-api-tenants.md | 86 -
.../version-2.6.1/administration-dashboard.md | 63 -
.../version-2.6.1/administration-geo.md | 196 -
.../version-2.6.1/administration-load-balance.md | 182 -
.../version-2.6.1/administration-proxy.md | 106 -
.../version-2.6.1/administration-pulsar-manager.md | 183 -
.../version-2.6.1/administration-stats.md | 64 -
.../version-2.6.1/administration-upgrade.md | 151 -
.../version-2.6.1/administration-zk-bk.md | 350 -
.../version-2.6.1/client-libraries-cgo.md | 545 -
.../version-2.6.1/client-libraries-cpp.md | 253 -
.../version-2.6.1/client-libraries-dotnet.md | 385 -
.../version-2.6.1/client-libraries-go.md | 681 -
.../version-2.6.1/client-libraries-java.md | 864 -
.../version-2.6.1/client-libraries-node.md | 404 -
.../version-2.6.1/client-libraries-python.md | 268 -
.../version-2.6.1/client-libraries-websocket.md | 444 -
.../concepts-architecture-overview.md | 153 -
.../version-2.6.1/concepts-authentication.md | 9 -
.../version-2.6.1/concepts-clients.md | 88 -
.../version-2.6.1/concepts-messaging.md | 518 -
.../version-2.6.1/concepts-multi-tenancy.md | 40 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.6.1/concepts-overview.md | 31 -
.../version-2.6.1/concepts-proxy-sni-routing.md | 121 -
.../version-2.6.1/concepts-replication.md | 9 -
.../version-2.6.1/concepts-tiered-storage.md | 18 -
.../version-2.6.1/concepts-topic-compaction.md | 37 -
.../version-2.6.1/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.6.1/cookbooks-compaction.md | 127 -
.../version-2.6.1/cookbooks-deduplication.md | 119 -
.../version-2.6.1/cookbooks-encryption.md | 170 -
.../version-2.6.1/cookbooks-message-queue.md | 95 -
.../version-2.6.1/cookbooks-non-persistent.md | 59 -
.../version-2.6.1/cookbooks-partitioned.md | 93 -
.../version-2.6.1/cookbooks-retention-expiry.md | 337 -
.../version-2.6.1/cookbooks-tiered-storage.md | 295 -
.../versioned_docs/version-2.6.1/deploy-aws.md | 224 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.6.1/deploy-bare-metal.md | 452 -
.../versioned_docs/version-2.6.1/deploy-dcos.md | 183 -
.../version-2.6.1/deploy-kubernetes.md | 11 -
.../version-2.6.1/deploy-monitoring.md | 90 -
.../versioned_docs/version-2.6.1/develop-schema.md | 58 -
.../version-2.6.1/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.6.1/developing-cpp.md | 101 -
.../version-2.6.1/developing-load-manager.md | 215 -
.../version-2.6.1/developing-tools.md | 105 -
.../versioned_docs/version-2.6.1/functions-cli.md | 198 -
.../version-2.6.1/functions-debug.md | 461 -
.../version-2.6.1/functions-deploy.md | 211 -
.../version-2.6.1/functions-develop.md | 986 -
.../version-2.6.1/functions-overview.md | 194 -
.../version-2.6.1/functions-runtime.md | 189 -
.../version-2.6.1/functions-worker.md | 302 -
.../version-2.6.1/getting-started-clients.md | 33 -
.../version-2.6.1/getting-started-docker.md | 159 -
.../version-2.6.1/getting-started-helm.md | 346 -
.../version-2.6.1/getting-started-pulsar.md | 67 -
.../version-2.6.1/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.6.1/helm-deploy.md | 378 -
.../versioned_docs/version-2.6.1/helm-install.md | 41 -
.../versioned_docs/version-2.6.1/helm-overview.md | 101 -
.../versioned_docs/version-2.6.1/helm-prepare.md | 85 -
.../versioned_docs/version-2.6.1/helm-tools.md | 43 -
.../versioned_docs/version-2.6.1/helm-upgrade.md | 34 -
.../version-2.6.1/io-aerospike-sink.md | 26 -
.../version-2.6.1/io-canal-source.md | 203 -
.../version-2.6.1/io-cassandra-sink.md | 54 -
.../version-2.6.1/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.6.1/io-cdc.md | 26 -
.../website/versioned_docs/version-2.6.1/io-cli.md | 601 -
.../versioned_docs/version-2.6.1/io-connectors.md | 226 -
.../version-2.6.1/io-debezium-source.md | 496 -
.../versioned_docs/version-2.6.1/io-debug.md | 329 -
.../versioned_docs/version-2.6.1/io-develop.md | 240 -
.../version-2.6.1/io-dynamodb-source.md | 76 -
.../version-2.6.1/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.6.1/io-file-source.md | 138 -
.../versioned_docs/version-2.6.1/io-flume-sink.md | 52 -
.../version-2.6.1/io-flume-source.md | 52 -
.../versioned_docs/version-2.6.1/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.6.1/io-hdfs2-sink.md | 56 -
.../versioned_docs/version-2.6.1/io-hdfs3-sink.md | 54 -
.../version-2.6.1/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.6.1/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.6.1/io-kafka-sink.md | 69 -
.../version-2.6.1/io-kafka-source.md | 171 -
.../version-2.6.1/io-kinesis-sink.md | 73 -
.../version-2.6.1/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.6.1/io-mongo-sink.md | 51 -
.../version-2.6.1/io-netty-source.md | 205 -
.../versioned_docs/version-2.6.1/io-overview.md | 136 -
.../versioned_docs/version-2.6.1/io-quickstart.md | 813 -
.../version-2.6.1/io-rabbitmq-sink.md | 81 -
.../version-2.6.1/io-rabbitmq-source.md | 78 -
.../versioned_docs/version-2.6.1/io-redis-sink.md | 70 -
.../versioned_docs/version-2.6.1/io-solr-sink.md | 61 -
.../version-2.6.1/io-twitter-source.md | 28 -
.../website/versioned_docs/version-2.6.1/io-use.md | 1505 --
.../version-2.6.1/performance-pulsar-perf.md | 192 -
.../version-2.6.1/reference-cli-tools.md | 783 -
.../version-2.6.1/reference-configuration.md | 551 -
.../version-2.6.1/reference-connector-admin.md | 11 -
.../version-2.6.1/reference-metrics.md | 449 -
.../version-2.6.1/reference-pulsar-admin.md | 2546 --
.../version-2.6.1/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.6.1/schema-get-started.md | 91 -
.../versioned_docs/version-2.6.1/schema-manage.md | 809 -
.../version-2.6.1/schema-understand.md | 591 -
.../version-2.6.1/security-athenz.md | 93 -
.../version-2.6.1/security-authorization.md | 100 -
.../version-2.6.1/security-bouncy-castle.md | 123 -
.../version-2.6.1/security-encryption.md | 180 -
.../version-2.6.1/security-extending.md | 194 -
.../versioned_docs/version-2.6.1/security-jwt.md | 264 -
.../version-2.6.1/security-kerberos.md | 391 -
.../version-2.6.1/security-oauth2.md | 189 -
.../version-2.6.1/security-overview.md | 35 -
.../version-2.6.1/security-tls-authentication.md | 186 -
.../version-2.6.1/security-tls-keystore.md | 287 -
.../version-2.6.1/security-tls-transport.md | 257 -
.../version-2.6.1/security-token-admin.md | 159 -
.../version-2.6.1/sql-deployment-configurations.md | 159 -
.../version-2.6.1/sql-getting-started.md | 171 -
.../versioned_docs/version-2.6.1/sql-overview.md | 18 -
.../versioned_docs/version-2.6.1/sql-rest-api.md | 186 -
.../version-2.6.1/window-functions-context.md | 529 -
.../versioned_docs/version-2.6.2/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.6.2/adaptors-spark.md | 74 -
.../versioned_docs/version-2.6.2/adaptors-storm.md | 90 -
.../version-2.6.2/admin-api-brokers.md | 149 -
.../version-2.6.2/admin-api-clusters.md | 210 -
.../version-2.6.2/admin-api-functions.md | 546 -
.../version-2.6.2/admin-api-namespaces.md | 793 -
.../admin-api-non-partitioned-topics.md | 160 -
.../admin-api-non-persistent-topics.md | 264 -
.../version-2.6.2/admin-api-overview.md | 89 -
.../version-2.6.2/admin-api-partitioned-topics.md | 377 -
.../version-2.6.2/admin-api-permissions.md | 115 -
.../version-2.6.2/admin-api-persistent-topics.md | 697 -
.../version-2.6.2/admin-api-tenants.md | 86 -
.../version-2.6.2/administration-dashboard.md | 63 -
.../version-2.6.2/administration-geo.md | 196 -
.../version-2.6.2/administration-load-balance.md | 182 -
.../version-2.6.2/administration-proxy.md | 106 -
.../version-2.6.2/administration-pulsar-manager.md | 183 -
.../version-2.6.2/administration-stats.md | 64 -
.../version-2.6.2/administration-upgrade.md | 151 -
.../version-2.6.2/administration-zk-bk.md | 350 -
.../version-2.6.2/client-libraries-cgo.md | 545 -
.../version-2.6.2/client-libraries-cpp.md | 253 -
.../version-2.6.2/client-libraries-dotnet.md | 385 -
.../version-2.6.2/client-libraries-go.md | 681 -
.../version-2.6.2/client-libraries-java.md | 864 -
.../version-2.6.2/client-libraries-node.md | 404 -
.../version-2.6.2/client-libraries-python.md | 268 -
.../version-2.6.2/client-libraries-websocket.md | 444 -
.../concepts-architecture-overview.md | 153 -
.../version-2.6.2/concepts-authentication.md | 9 -
.../version-2.6.2/concepts-clients.md | 88 -
.../version-2.6.2/concepts-messaging.md | 518 -
.../version-2.6.2/concepts-multi-tenancy.md | 40 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.6.2/concepts-overview.md | 31 -
.../version-2.6.2/concepts-proxy-sni-routing.md | 121 -
.../version-2.6.2/concepts-replication.md | 9 -
.../version-2.6.2/concepts-tiered-storage.md | 18 -
.../version-2.6.2/concepts-topic-compaction.md | 37 -
.../version-2.6.2/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.6.2/cookbooks-compaction.md | 127 -
.../version-2.6.2/cookbooks-deduplication.md | 119 -
.../version-2.6.2/cookbooks-encryption.md | 170 -
.../version-2.6.2/cookbooks-message-queue.md | 95 -
.../version-2.6.2/cookbooks-non-persistent.md | 59 -
.../version-2.6.2/cookbooks-partitioned.md | 93 -
.../version-2.6.2/cookbooks-retention-expiry.md | 323 -
.../version-2.6.2/cookbooks-tiered-storage.md | 295 -
.../versioned_docs/version-2.6.2/deploy-aws.md | 224 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.6.2/deploy-bare-metal.md | 452 -
.../versioned_docs/version-2.6.2/deploy-dcos.md | 183 -
.../version-2.6.2/deploy-kubernetes.md | 11 -
.../version-2.6.2/deploy-monitoring.md | 90 -
.../version-2.6.2/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.6.2/developing-cpp.md | 101 -
.../version-2.6.2/developing-load-manager.md | 215 -
.../version-2.6.2/developing-tools.md | 105 -
.../versioned_docs/version-2.6.2/functions-cli.md | 198 -
.../version-2.6.2/functions-debug.md | 461 -
.../version-2.6.2/functions-deploy.md | 211 -
.../version-2.6.2/functions-develop.md | 986 -
.../version-2.6.2/functions-overview.md | 194 -
.../version-2.6.2/functions-runtime.md | 189 -
.../version-2.6.2/functions-worker.md | 302 -
.../version-2.6.2/getting-started-clients.md | 33 -
.../version-2.6.2/getting-started-docker.md | 159 -
.../version-2.6.2/getting-started-helm.md | 346 -
.../version-2.6.2/getting-started-pulsar.md | 67 -
.../version-2.6.2/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.6.2/helm-deploy.md | 378 -
.../versioned_docs/version-2.6.2/helm-install.md | 41 -
.../versioned_docs/version-2.6.2/helm-overview.md | 101 -
.../versioned_docs/version-2.6.2/helm-prepare.md | 85 -
.../versioned_docs/version-2.6.2/helm-tools.md | 43 -
.../versioned_docs/version-2.6.2/helm-upgrade.md | 34 -
.../version-2.6.2/io-aerospike-sink.md | 26 -
.../version-2.6.2/io-canal-source.md | 203 -
.../version-2.6.2/io-cassandra-sink.md | 54 -
.../version-2.6.2/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.6.2/io-cdc.md | 26 -
.../website/versioned_docs/version-2.6.2/io-cli.md | 601 -
.../versioned_docs/version-2.6.2/io-connectors.md | 226 -
.../version-2.6.2/io-debezium-source.md | 496 -
.../versioned_docs/version-2.6.2/io-debug.md | 329 -
.../versioned_docs/version-2.6.2/io-develop.md | 240 -
.../version-2.6.2/io-dynamodb-source.md | 76 -
.../version-2.6.2/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.6.2/io-file-source.md | 138 -
.../versioned_docs/version-2.6.2/io-flume-sink.md | 52 -
.../version-2.6.2/io-flume-source.md | 52 -
.../versioned_docs/version-2.6.2/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.6.2/io-hdfs2-sink.md | 56 -
.../versioned_docs/version-2.6.2/io-hdfs3-sink.md | 54 -
.../version-2.6.2/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.6.2/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.6.2/io-kafka-sink.md | 69 -
.../version-2.6.2/io-kafka-source.md | 171 -
.../version-2.6.2/io-kinesis-sink.md | 73 -
.../version-2.6.2/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.6.2/io-mongo-sink.md | 51 -
.../version-2.6.2/io-netty-source.md | 205 -
.../versioned_docs/version-2.6.2/io-overview.md | 136 -
.../versioned_docs/version-2.6.2/io-quickstart.md | 813 -
.../version-2.6.2/io-rabbitmq-sink.md | 81 -
.../version-2.6.2/io-rabbitmq-source.md | 78 -
.../versioned_docs/version-2.6.2/io-redis-sink.md | 70 -
.../versioned_docs/version-2.6.2/io-solr-sink.md | 61 -
.../version-2.6.2/io-twitter-source.md | 28 -
.../website/versioned_docs/version-2.6.2/io-use.md | 1505 --
.../version-2.6.2/performance-pulsar-perf.md | 195 -
.../version-2.6.2/reference-cli-tools.md | 787 -
.../version-2.6.2/reference-configuration.md | 552 -
.../version-2.6.2/reference-connector-admin.md | 11 -
.../version-2.6.2/reference-metrics.md | 449 -
.../version-2.6.2/reference-pulsar-admin.md | 2555 --
.../version-2.6.2/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.6.2/schema-get-started.md | 91 -
.../versioned_docs/version-2.6.2/schema-manage.md | 809 -
.../version-2.6.2/schema-understand.md | 591 -
.../version-2.6.2/security-athenz.md | 93 -
.../version-2.6.2/security-authorization.md | 100 -
.../version-2.6.2/security-bouncy-castle.md | 122 -
.../version-2.6.2/security-encryption.md | 180 -
.../version-2.6.2/security-extending.md | 194 -
.../versioned_docs/version-2.6.2/security-jwt.md | 264 -
.../version-2.6.2/security-kerberos.md | 391 -
.../version-2.6.2/security-oauth2.md | 189 -
.../version-2.6.2/security-overview.md | 35 -
.../version-2.6.2/security-tls-authentication.md | 186 -
.../version-2.6.2/security-tls-keystore.md | 287 -
.../version-2.6.2/security-tls-transport.md | 257 -
.../version-2.6.2/security-token-admin.md | 159 -
.../version-2.6.2/sql-deployment-configurations.md | 159 -
.../version-2.6.2/sql-getting-started.md | 171 -
.../versioned_docs/version-2.6.2/sql-overview.md | 18 -
.../versioned_docs/version-2.6.2/sql-rest-api.md | 186 -
.../version-2.6.2/window-functions-context.md | 529 -
.../versioned_docs/version-2.6.3/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.6.3/adaptors-spark.md | 72 -
.../versioned_docs/version-2.6.3/adaptors-storm.md | 89 -
.../version-2.6.3/admin-api-brokers.md | 149 -
.../version-2.6.3/admin-api-clusters.md | 210 -
.../version-2.6.3/admin-api-functions.md | 546 -
.../version-2.6.3/admin-api-namespaces.md | 793 -
.../admin-api-non-partitioned-topics.md | 160 -
.../admin-api-non-persistent-topics.md | 264 -
.../version-2.6.3/admin-api-overview.md | 89 -
.../version-2.6.3/admin-api-partitioned-topics.md | 377 -
.../version-2.6.3/admin-api-permissions.md | 115 -
.../version-2.6.3/admin-api-persistent-topics.md | 697 -
.../version-2.6.3/admin-api-tenants.md | 86 -
.../version-2.6.3/administration-dashboard.md | 63 -
.../version-2.6.3/administration-geo.md | 196 -
.../version-2.6.3/administration-load-balance.md | 182 -
.../version-2.6.3/administration-proxy.md | 106 -
.../version-2.6.3/administration-pulsar-manager.md | 183 -
.../version-2.6.3/administration-stats.md | 64 -
.../version-2.6.3/administration-upgrade.md | 151 -
.../version-2.6.3/administration-zk-bk.md | 374 -
.../version-2.6.3/client-libraries-cgo.md | 545 -
.../version-2.6.3/client-libraries-cpp.md | 253 -
.../version-2.6.3/client-libraries-dotnet.md | 385 -
.../version-2.6.3/client-libraries-go.md | 681 -
.../version-2.6.3/client-libraries-java.md | 864 -
.../version-2.6.3/client-libraries-node.md | 404 -
.../version-2.6.3/client-libraries-python.md | 268 -
.../version-2.6.3/client-libraries-websocket.md | 444 -
.../concepts-architecture-overview.md | 153 -
.../version-2.6.3/concepts-authentication.md | 9 -
.../version-2.6.3/concepts-clients.md | 88 -
.../version-2.6.3/concepts-messaging.md | 518 -
.../version-2.6.3/concepts-multi-tenancy.md | 40 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.6.3/concepts-overview.md | 31 -
.../version-2.6.3/concepts-proxy-sni-routing.md | 121 -
.../version-2.6.3/concepts-replication.md | 9 -
.../version-2.6.3/concepts-tiered-storage.md | 18 -
.../version-2.6.3/concepts-topic-compaction.md | 37 -
.../version-2.6.3/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.6.3/cookbooks-compaction.md | 127 -
.../version-2.6.3/cookbooks-deduplication.md | 119 -
.../version-2.6.3/cookbooks-encryption.md | 170 -
.../version-2.6.3/cookbooks-message-queue.md | 95 -
.../version-2.6.3/cookbooks-non-persistent.md | 59 -
.../version-2.6.3/cookbooks-partitioned.md | 93 -
.../version-2.6.3/cookbooks-retention-expiry.md | 323 -
.../version-2.6.3/cookbooks-tiered-storage.md | 295 -
.../versioned_docs/version-2.6.3/deploy-aws.md | 224 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.6.3/deploy-bare-metal.md | 452 -
.../versioned_docs/version-2.6.3/deploy-dcos.md | 183 -
.../version-2.6.3/deploy-kubernetes.md | 11 -
.../version-2.6.3/deploy-monitoring.md | 90 -
.../versioned_docs/version-2.6.3/develop-schema.md | 58 -
.../version-2.6.3/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.6.3/developing-cpp.md | 101 -
.../version-2.6.3/developing-load-manager.md | 215 -
.../version-2.6.3/developing-tools.md | 105 -
.../versioned_docs/version-2.6.3/functions-cli.md | 198 -
.../version-2.6.3/functions-debug.md | 461 -
.../version-2.6.3/functions-deploy.md | 211 -
.../version-2.6.3/functions-develop.md | 986 -
.../version-2.6.3/functions-overview.md | 194 -
.../version-2.6.3/functions-runtime.md | 189 -
.../version-2.6.3/functions-worker.md | 302 -
.../version-2.6.3/getting-started-clients.md | 33 -
.../version-2.6.3/getting-started-docker.md | 159 -
.../version-2.6.3/getting-started-helm.md | 346 -
.../version-2.6.3/getting-started-pulsar.md | 67 -
.../version-2.6.3/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.6.3/helm-deploy.md | 378 -
.../versioned_docs/version-2.6.3/helm-install.md | 41 -
.../versioned_docs/version-2.6.3/helm-overview.md | 101 -
.../versioned_docs/version-2.6.3/helm-prepare.md | 85 -
.../versioned_docs/version-2.6.3/helm-tools.md | 43 -
.../versioned_docs/version-2.6.3/helm-upgrade.md | 34 -
.../version-2.6.3/io-aerospike-sink.md | 26 -
.../version-2.6.3/io-canal-source.md | 203 -
.../version-2.6.3/io-cassandra-sink.md | 54 -
.../version-2.6.3/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.6.3/io-cdc.md | 26 -
.../website/versioned_docs/version-2.6.3/io-cli.md | 601 -
.../versioned_docs/version-2.6.3/io-connectors.md | 226 -
.../version-2.6.3/io-debezium-source.md | 496 -
.../versioned_docs/version-2.6.3/io-debug.md | 329 -
.../versioned_docs/version-2.6.3/io-develop.md | 240 -
.../version-2.6.3/io-dynamodb-source.md | 76 -
.../version-2.6.3/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.6.3/io-file-source.md | 138 -
.../versioned_docs/version-2.6.3/io-flume-sink.md | 52 -
.../version-2.6.3/io-flume-source.md | 52 -
.../versioned_docs/version-2.6.3/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.6.3/io-hdfs2-sink.md | 56 -
.../versioned_docs/version-2.6.3/io-hdfs3-sink.md | 54 -
.../version-2.6.3/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.6.3/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.6.3/io-kafka-sink.md | 69 -
.../version-2.6.3/io-kafka-source.md | 171 -
.../version-2.6.3/io-kinesis-sink.md | 73 -
.../version-2.6.3/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.6.3/io-mongo-sink.md | 51 -
.../version-2.6.3/io-netty-source.md | 205 -
.../versioned_docs/version-2.6.3/io-overview.md | 136 -
.../versioned_docs/version-2.6.3/io-quickstart.md | 813 -
.../version-2.6.3/io-rabbitmq-sink.md | 81 -
.../version-2.6.3/io-rabbitmq-source.md | 78 -
.../versioned_docs/version-2.6.3/io-redis-sink.md | 70 -
.../versioned_docs/version-2.6.3/io-solr-sink.md | 61 -
.../version-2.6.3/io-twitter-source.md | 28 -
.../website/versioned_docs/version-2.6.3/io-use.md | 1505 --
.../version-2.6.3/performance-pulsar-perf.md | 195 -
.../version-2.6.3/reference-cli-tools.md | 787 -
.../version-2.6.3/reference-configuration.md | 548 -
.../version-2.6.3/reference-connector-admin.md | 11 -
.../version-2.6.3/reference-metrics.md | 449 -
.../version-2.6.3/reference-pulsar-admin.md | 2555 --
.../version-2.6.3/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.6.3/schema-get-started.md | 91 -
.../versioned_docs/version-2.6.3/schema-manage.md | 809 -
.../version-2.6.3/schema-understand.md | 591 -
.../version-2.6.3/security-athenz.md | 93 -
.../version-2.6.3/security-authorization.md | 100 -
.../version-2.6.3/security-bouncy-castle.md | 122 -
.../version-2.6.3/security-encryption.md | 180 -
.../version-2.6.3/security-extending.md | 194 -
.../versioned_docs/version-2.6.3/security-jwt.md | 264 -
.../version-2.6.3/security-kerberos.md | 391 -
.../version-2.6.3/security-oauth2.md | 189 -
.../version-2.6.3/security-overview.md | 35 -
.../version-2.6.3/security-tls-authentication.md | 186 -
.../version-2.6.3/security-tls-keystore.md | 287 -
.../version-2.6.3/security-tls-transport.md | 257 -
.../version-2.6.3/security-token-admin.md | 159 -
.../version-2.6.3/sql-deployment-configurations.md | 159 -
.../version-2.6.3/sql-getting-started.md | 171 -
.../versioned_docs/version-2.6.3/sql-overview.md | 18 -
.../versioned_docs/version-2.6.3/sql-rest-api.md | 186 -
.../version-2.6.3/window-functions-context.md | 529 -
.../versioned_docs/version-2.6.4/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.6.4/adaptors-spark.md | 72 -
.../versioned_docs/version-2.6.4/adaptors-storm.md | 89 -
.../version-2.6.4/admin-api-brokers.md | 149 -
.../version-2.6.4/admin-api-clusters.md | 210 -
.../version-2.6.4/admin-api-functions.md | 546 -
.../version-2.6.4/admin-api-namespaces.md | 766 -
.../admin-api-non-partitioned-topics.md | 160 -
.../admin-api-non-persistent-topics.md | 264 -
.../version-2.6.4/admin-api-overview.md | 89 -
.../version-2.6.4/admin-api-partitioned-topics.md | 377 -
.../version-2.6.4/admin-api-permissions.md | 115 -
.../version-2.6.4/admin-api-persistent-topics.md | 697 -
.../version-2.6.4/admin-api-schemas.md | 7 -
.../version-2.6.4/admin-api-tenants.md | 86 -
.../version-2.6.4/administration-dashboard.md | 63 -
.../version-2.6.4/administration-geo.md | 158 -
.../version-2.6.4/administration-load-balance.md | 182 -
.../version-2.6.4/administration-proxy.md | 106 -
.../version-2.6.4/administration-pulsar-manager.md | 183 -
.../version-2.6.4/administration-stats.md | 64 -
.../version-2.6.4/administration-upgrade.md | 151 -
.../version-2.6.4/administration-zk-bk.md | 350 -
.../version-2.6.4/client-libraries-cgo.md | 545 -
.../version-2.6.4/client-libraries-cpp.md | 253 -
.../version-2.6.4/client-libraries-dotnet.md | 430 -
.../version-2.6.4/client-libraries-go.md | 681 -
.../version-2.6.4/client-libraries-java.md | 865 -
.../version-2.6.4/client-libraries-node.md | 404 -
.../version-2.6.4/client-libraries-python.md | 268 -
.../version-2.6.4/client-libraries-websocket.md | 444 -
.../concepts-architecture-overview.md | 153 -
.../version-2.6.4/concepts-authentication.md | 9 -
.../version-2.6.4/concepts-clients.md | 88 -
.../version-2.6.4/concepts-messaging.md | 516 -
.../version-2.6.4/concepts-multi-tenancy.md | 40 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.6.4/concepts-overview.md | 31 -
.../version-2.6.4/concepts-proxy-sni-routing.md | 121 -
.../version-2.6.4/concepts-replication.md | 9 -
.../version-2.6.4/concepts-tiered-storage.md | 18 -
.../version-2.6.4/concepts-topic-compaction.md | 37 -
.../version-2.6.4/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.6.4/cookbooks-compaction.md | 127 -
.../version-2.6.4/cookbooks-deduplication.md | 119 -
.../version-2.6.4/cookbooks-encryption.md | 170 -
.../version-2.6.4/cookbooks-message-queue.md | 95 -
.../version-2.6.4/cookbooks-non-persistent.md | 59 -
.../version-2.6.4/cookbooks-partitioned.md | 93 -
.../version-2.6.4/cookbooks-retention-expiry.md | 323 -
.../version-2.6.4/cookbooks-tiered-storage.md | 295 -
.../versioned_docs/version-2.6.4/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.6.4/deploy-bare-metal.md | 459 -
.../versioned_docs/version-2.6.4/deploy-dcos.md | 183 -
.../version-2.6.4/deploy-kubernetes.md | 11 -
.../version-2.6.4/deploy-monitoring.md | 90 -
.../versioned_docs/version-2.6.4/develop-schema.md | 58 -
.../version-2.6.4/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.6.4/developing-cpp.md | 101 -
.../version-2.6.4/developing-load-manager.md | 215 -
.../version-2.6.4/developing-tools.md | 105 -
.../versioned_docs/version-2.6.4/functions-cli.md | 198 -
.../version-2.6.4/functions-debug.md | 461 -
.../version-2.6.4/functions-deploy.md | 211 -
.../version-2.6.4/functions-develop.md | 984 -
.../version-2.6.4/functions-overview.md | 194 -
.../version-2.6.4/functions-runtime.md | 189 -
.../version-2.6.4/functions-worker.md | 297 -
.../version-2.6.4/getting-started-clients.md | 33 -
.../version-2.6.4/getting-started-docker.md | 159 -
.../version-2.6.4/getting-started-helm.md | 350 -
.../version-2.6.4/getting-started-pulsar.md | 67 -
.../version-2.6.4/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.6.4/helm-deploy.md | 376 -
.../versioned_docs/version-2.6.4/helm-install.md | 41 -
.../versioned_docs/version-2.6.4/helm-overview.md | 101 -
.../versioned_docs/version-2.6.4/helm-prepare.md | 85 -
.../versioned_docs/version-2.6.4/helm-tools.md | 43 -
.../versioned_docs/version-2.6.4/helm-upgrade.md | 34 -
.../version-2.6.4/io-aerospike-sink.md | 26 -
.../version-2.6.4/io-canal-source.md | 203 -
.../version-2.6.4/io-cassandra-sink.md | 54 -
.../version-2.6.4/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.6.4/io-cdc.md | 26 -
.../website/versioned_docs/version-2.6.4/io-cli.md | 601 -
.../versioned_docs/version-2.6.4/io-connectors.md | 226 -
.../version-2.6.4/io-debezium-source.md | 496 -
.../versioned_docs/version-2.6.4/io-debug.md | 329 -
.../versioned_docs/version-2.6.4/io-develop.md | 240 -
.../version-2.6.4/io-dynamodb-source.md | 76 -
.../version-2.6.4/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.6.4/io-file-source.md | 138 -
.../versioned_docs/version-2.6.4/io-flume-sink.md | 52 -
.../version-2.6.4/io-flume-source.md | 52 -
.../versioned_docs/version-2.6.4/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.6.4/io-hdfs2-sink.md | 56 -
.../versioned_docs/version-2.6.4/io-hdfs3-sink.md | 54 -
.../version-2.6.4/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.6.4/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.6.4/io-kafka-sink.md | 69 -
.../version-2.6.4/io-kafka-source.md | 171 -
.../version-2.6.4/io-kinesis-sink.md | 73 -
.../version-2.6.4/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.6.4/io-mongo-sink.md | 51 -
.../version-2.6.4/io-netty-source.md | 205 -
.../versioned_docs/version-2.6.4/io-overview.md | 136 -
.../versioned_docs/version-2.6.4/io-quickstart.md | 813 -
.../version-2.6.4/io-rabbitmq-sink.md | 81 -
.../version-2.6.4/io-rabbitmq-source.md | 78 -
.../versioned_docs/version-2.6.4/io-redis-sink.md | 70 -
.../versioned_docs/version-2.6.4/io-solr-sink.md | 61 -
.../version-2.6.4/io-twitter-source.md | 28 -
.../website/versioned_docs/version-2.6.4/io-use.md | 1505 --
.../version-2.6.4/performance-pulsar-perf.md | 195 -
.../version-2.6.4/reference-cli-tools.md | 787 -
.../version-2.6.4/reference-configuration.md | 549 -
.../version-2.6.4/reference-connector-admin.md | 11 -
.../version-2.6.4/reference-metrics.md | 449 -
.../version-2.6.4/reference-pulsar-admin.md | 2522 --
.../version-2.6.4/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.6.4/schema-get-started.md | 91 -
.../versioned_docs/version-2.6.4/schema-manage.md | 809 -
.../version-2.6.4/schema-understand.md | 591 -
.../version-2.6.4/security-athenz.md | 93 -
.../version-2.6.4/security-authorization.md | 100 -
.../version-2.6.4/security-bouncy-castle.md | 122 -
.../version-2.6.4/security-encryption.md | 180 -
.../version-2.6.4/security-extending.md | 194 -
.../versioned_docs/version-2.6.4/security-jwt.md | 248 -
.../version-2.6.4/security-kerberos.md | 391 -
.../version-2.6.4/security-oauth2.md | 154 -
.../version-2.6.4/security-overview.md | 35 -
.../version-2.6.4/security-tls-authentication.md | 186 -
.../version-2.6.4/security-tls-keystore.md | 287 -
.../version-2.6.4/security-tls-transport.md | 257 -
.../version-2.6.4/security-token-admin.md | 159 -
.../version-2.6.4/sql-deployment-configurations.md | 159 -
.../version-2.6.4/sql-getting-started.md | 171 -
.../versioned_docs/version-2.6.4/sql-overview.md | 18 -
.../versioned_docs/version-2.6.4/sql-rest-api.md | 186 -
.../version-2.6.4/tiered-storage-azure.md | 224 -
.../version-2.6.4/window-functions-context.md | 529 -
.../versioned_docs/version-2.7.0/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.7.0/adaptors-spark.md | 72 -
.../versioned_docs/version-2.7.0/adaptors-storm.md | 90 -
.../version-2.7.0/admin-api-brokers.md | 158 -
.../version-2.7.0/admin-api-clusters.md | 222 -
.../version-2.7.0/admin-api-functions.md | 579 -
.../version-2.7.0/admin-api-namespaces.md | 914 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.7.0/admin-api-overview.md | 122 -
.../version-2.7.0/admin-api-partitioned-topics.md | 8 -
.../version-2.7.0/admin-api-permissions.md | 121 -
.../version-2.7.0/admin-api-persistent-topics.md | 8 -
.../version-2.7.0/admin-api-schemas.md | 7 -
.../version-2.7.0/admin-api-tenants.md | 157 -
.../version-2.7.0/admin-api-topics.md | 1472 --
.../version-2.7.0/administration-dashboard.md | 63 -
.../version-2.7.0/administration-geo.md | 196 -
.../version-2.7.0/administration-load-balance.md | 182 -
.../version-2.7.0/administration-proxy.md | 76 -
.../version-2.7.0/administration-pulsar-manager.md | 183 -
.../version-2.7.0/administration-stats.md | 64 -
.../version-2.7.0/administration-upgrade.md | 151 -
.../version-2.7.0/administration-zk-bk.md | 351 -
.../version-2.7.0/client-libraries-cgo.md | 545 -
.../version-2.7.0/client-libraries-cpp.md | 253 -
.../version-2.7.0/client-libraries-dotnet.md | 385 -
.../version-2.7.0/client-libraries-go.md | 681 -
.../version-2.7.0/client-libraries-java.md | 898 -
.../version-2.7.0/client-libraries-node.md | 431 -
.../version-2.7.0/client-libraries-python.md | 295 -
.../version-2.7.0/client-libraries-websocket.md | 448 -
.../concepts-architecture-overview.md | 156 -
.../version-2.7.0/concepts-authentication.md | 9 -
.../version-2.7.0/concepts-clients.md | 85 -
.../version-2.7.0/concepts-messaging.md | 571 -
.../version-2.7.0/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.7.0/concepts-overview.md | 31 -
.../version-2.7.0/concepts-proxy-sni-routing.md | 121 -
.../version-2.7.0/concepts-replication.md | 9 -
.../version-2.7.0/concepts-tiered-storage.md | 18 -
.../version-2.7.0/concepts-topic-compaction.md | 37 -
.../version-2.7.0/concepts-transactions.md | 30 -
.../version-2.7.0/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.7.0/cookbooks-compaction.md | 127 -
.../version-2.7.0/cookbooks-deduplication.md | 125 -
.../version-2.7.0/cookbooks-encryption.md | 170 -
.../version-2.7.0/cookbooks-message-queue.md | 118 -
.../version-2.7.0/cookbooks-non-persistent.md | 59 -
.../version-2.7.0/cookbooks-partitioned.md | 7 -
.../version-2.7.0/cookbooks-retention-expiry.md | 350 -
.../version-2.7.0/cookbooks-tiered-storage.md | 297 -
.../versioned_docs/version-2.7.0/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.7.0/deploy-bare-metal.md | 463 -
.../versioned_docs/version-2.7.0/deploy-dcos.md | 183 -
.../versioned_docs/version-2.7.0/deploy-docker.md | 52 -
.../version-2.7.0/deploy-kubernetes.md | 11 -
.../version-2.7.0/deploy-monitoring.md | 95 -
.../versioned_docs/version-2.7.0/develop-schema.md | 58 -
.../version-2.7.0/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.7.0/developing-cpp.md | 101 -
.../version-2.7.0/developing-load-manager.md | 215 -
.../version-2.7.0/developing-tools.md | 105 -
.../versioned_docs/version-2.7.0/functions-cli.md | 198 -
.../version-2.7.0/functions-debug.md | 461 -
.../version-2.7.0/functions-deploy.md | 211 -
.../version-2.7.0/functions-develop.md | 1084 -
.../version-2.7.0/functions-metrics.md | 7 -
.../version-2.7.0/functions-overview.md | 194 -
.../version-2.7.0/functions-package.md | 431 -
.../version-2.7.0/functions-runtime.md | 320 -
.../version-2.7.0/functions-worker.md | 325 -
.../version-2.7.0/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.7.0/getting-started-docker.md | 159 -
.../version-2.7.0/getting-started-helm.md | 363 -
.../version-2.7.0/getting-started-pulsar.md | 67 -
.../version-2.7.0/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.7.0/helm-deploy.md | 379 -
.../versioned_docs/version-2.7.0/helm-install.md | 41 -
.../versioned_docs/version-2.7.0/helm-overview.md | 100 -
.../versioned_docs/version-2.7.0/helm-prepare.md | 85 -
.../versioned_docs/version-2.7.0/helm-tools.md | 43 -
.../versioned_docs/version-2.7.0/helm-upgrade.md | 34 -
.../version-2.7.0/io-aerospike-sink.md | 26 -
.../version-2.7.0/io-canal-source.md | 203 -
.../version-2.7.0/io-cassandra-sink.md | 54 -
.../version-2.7.0/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.7.0/io-cdc.md | 26 -
.../website/versioned_docs/version-2.7.0/io-cli.md | 606 -
.../versioned_docs/version-2.7.0/io-connectors.md | 232 -
.../version-2.7.0/io-debezium-source.md | 510 -
.../versioned_docs/version-2.7.0/io-debug.md | 329 -
.../versioned_docs/version-2.7.0/io-develop.md | 240 -
.../version-2.7.0/io-dynamodb-source.md | 76 -
.../version-2.7.0/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.7.0/io-file-source.md | 138 -
.../versioned_docs/version-2.7.0/io-flume-sink.md | 52 -
.../version-2.7.0/io-flume-source.md | 52 -
.../versioned_docs/version-2.7.0/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.7.0/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.7.0/io-hdfs3-sink.md | 54 -
.../version-2.7.0/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.7.0/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.7.0/io-kafka-sink.md | 69 -
.../version-2.7.0/io-kafka-source.md | 171 -
.../version-2.7.0/io-kinesis-sink.md | 73 -
.../version-2.7.0/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.7.0/io-mongo-sink.md | 51 -
.../version-2.7.0/io-netty-source.md | 205 -
.../versioned_docs/version-2.7.0/io-nsq-source.md | 21 -
.../versioned_docs/version-2.7.0/io-overview.md | 136 -
.../versioned_docs/version-2.7.0/io-quickstart.md | 816 -
.../version-2.7.0/io-rabbitmq-sink.md | 81 -
.../version-2.7.0/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.7.0/io-redis-sink.md | 70 -
.../versioned_docs/version-2.7.0/io-solr-sink.md | 61 -
.../version-2.7.0/io-twitter-source.md | 28 -
.../versioned_docs/version-2.7.0/io-twitter.md | 7 -
.../website/versioned_docs/version-2.7.0/io-use.md | 1505 --
.../version-2.7.0/performance-pulsar-perf.md | 195 -
.../version-2.7.0/reference-cli-tools.md | 792 -
.../version-2.7.0/reference-configuration.md | 778 -
.../version-2.7.0/reference-connector-admin.md | 11 -
.../version-2.7.0/reference-metrics.md | 436 -
.../version-2.7.0/reference-pulsar-admin.md | 2959 ---
.../version-2.7.0/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.7.0/schema-get-started.md | 95 -
.../versioned_docs/version-2.7.0/schema-manage.md | 809 -
.../version-2.7.0/schema-understand.md | 599 -
.../version-2.7.0/security-athenz.md | 93 -
.../version-2.7.0/security-authorization.md | 101 -
.../version-2.7.0/security-bouncy-castle.md | 139 -
.../version-2.7.0/security-encryption.md | 180 -
.../version-2.7.0/security-extending.md | 196 -
.../versioned_docs/version-2.7.0/security-jwt.md | 264 -
.../version-2.7.0/security-kerberos.md | 391 -
.../version-2.7.0/security-oauth2.md | 207 -
.../version-2.7.0/security-overview.md | 35 -
.../version-2.7.0/security-tls-authentication.md | 186 -
.../version-2.7.0/security-tls-keystore.md | 287 -
.../version-2.7.0/security-tls-transport.md | 261 -
.../version-2.7.0/security-token-admin.md | 159 -
.../version-2.7.0/sql-deployment-configurations.md | 169 -
.../version-2.7.0/sql-getting-started.md | 171 -
.../versioned_docs/version-2.7.0/sql-overview.md | 18 -
.../versioned_docs/version-2.7.0/sql-rest-api.md | 186 -
.../version-2.7.0/tiered-storage-aws.md | 280 -
.../version-2.7.0/tiered-storage-azure.md | 224 -
.../version-2.7.0/tiered-storage-filesystem.md | 524 -
.../version-2.7.0/tiered-storage-gcs.md | 274 -
.../version-2.7.0/tiered-storage-overview.md | 48 -
.../version-2.7.0/transaction-api.md | 151 -
.../version-2.7.0/transaction-guarantee.md | 17 -
.../version-2.7.0/window-functions-context.md | 529 -
.../versioned_docs/version-2.7.1/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.7.1/adaptors-spark.md | 73 -
.../versioned_docs/version-2.7.1/adaptors-storm.md | 89 -
.../version-2.7.1/admin-api-brokers.md | 158 -
.../version-2.7.1/admin-api-clusters.md | 222 -
.../version-2.7.1/admin-api-functions.md | 579 -
.../version-2.7.1/admin-api-namespaces.md | 937 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.7.1/admin-api-overview.md | 115 -
.../version-2.7.1/admin-api-partitioned-topics.md | 8 -
.../version-2.7.1/admin-api-permissions.md | 121 -
.../version-2.7.1/admin-api-persistent-topics.md | 8 -
.../version-2.7.1/admin-api-schemas.md | 7 -
.../version-2.7.1/admin-api-tenants.md | 157 -
.../version-2.7.1/admin-api-topics.md | 1472 --
.../version-2.7.1/administration-dashboard.md | 63 -
.../version-2.7.1/administration-geo.md | 196 -
.../version-2.7.1/administration-isolation.md | 79 -
.../version-2.7.1/administration-load-balance.md | 182 -
.../version-2.7.1/administration-proxy.md | 76 -
.../version-2.7.1/administration-pulsar-manager.md | 183 -
.../version-2.7.1/administration-stats.md | 64 -
.../version-2.7.1/administration-upgrade.md | 151 -
.../version-2.7.1/administration-zk-bk.md | 351 -
.../version-2.7.1/client-libraries-cgo.md | 545 -
.../version-2.7.1/client-libraries-cpp.md | 253 -
.../version-2.7.1/client-libraries-dotnet.md | 385 -
.../version-2.7.1/client-libraries-go.md | 681 -
.../version-2.7.1/client-libraries-java.md | 898 -
.../version-2.7.1/client-libraries-node.md | 431 -
.../version-2.7.1/client-libraries-python.md | 395 -
.../version-2.7.1/client-libraries-websocket.md | 448 -
.../concepts-architecture-overview.md | 156 -
.../version-2.7.1/concepts-authentication.md | 9 -
.../version-2.7.1/concepts-clients.md | 85 -
.../version-2.7.1/concepts-messaging.md | 571 -
.../version-2.7.1/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.7.1/concepts-overview.md | 31 -
.../version-2.7.1/concepts-proxy-sni-routing.md | 121 -
.../version-2.7.1/concepts-replication.md | 9 -
.../version-2.7.1/concepts-tiered-storage.md | 18 -
.../version-2.7.1/concepts-topic-compaction.md | 37 -
.../version-2.7.1/concepts-transactions.md | 30 -
.../version-2.7.1/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.7.1/cookbooks-compaction.md | 127 -
.../version-2.7.1/cookbooks-deduplication.md | 125 -
.../version-2.7.1/cookbooks-encryption.md | 170 -
.../version-2.7.1/cookbooks-message-queue.md | 117 -
.../version-2.7.1/cookbooks-non-persistent.md | 59 -
.../version-2.7.1/cookbooks-partitioned.md | 7 -
.../version-2.7.1/cookbooks-retention-expiry.md | 349 -
.../version-2.7.1/cookbooks-tiered-storage.md | 297 -
.../versioned_docs/version-2.7.1/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.7.1/deploy-bare-metal.md | 463 -
.../versioned_docs/version-2.7.1/deploy-dcos.md | 183 -
.../versioned_docs/version-2.7.1/deploy-docker.md | 52 -
.../version-2.7.1/deploy-kubernetes.md | 11 -
.../version-2.7.1/deploy-monitoring.md | 107 -
.../versioned_docs/version-2.7.1/develop-schema.md | 58 -
.../version-2.7.1/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.7.1/developing-cpp.md | 101 -
.../version-2.7.1/developing-load-manager.md | 215 -
.../version-2.7.1/developing-tools.md | 105 -
.../versioned_docs/version-2.7.1/functions-cli.md | 198 -
.../version-2.7.1/functions-debug.md | 461 -
.../version-2.7.1/functions-deploy.md | 211 -
.../version-2.7.1/functions-develop.md | 1136 -
.../version-2.7.1/functions-metrics.md | 7 -
.../version-2.7.1/functions-overview.md | 194 -
.../version-2.7.1/functions-package.md | 431 -
.../version-2.7.1/functions-runtime.md | 325 -
.../version-2.7.1/functions-worker.md | 325 -
.../version-2.7.1/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.7.1/getting-started-docker.md | 159 -
.../version-2.7.1/getting-started-helm.md | 363 -
.../version-2.7.1/getting-started-pulsar.md | 67 -
.../version-2.7.1/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.7.1/helm-deploy.md | 379 -
.../versioned_docs/version-2.7.1/helm-install.md | 41 -
.../versioned_docs/version-2.7.1/helm-overview.md | 100 -
.../versioned_docs/version-2.7.1/helm-prepare.md | 85 -
.../versioned_docs/version-2.7.1/helm-tools.md | 43 -
.../versioned_docs/version-2.7.1/helm-upgrade.md | 34 -
.../version-2.7.1/io-aerospike-sink.md | 26 -
.../version-2.7.1/io-canal-source.md | 203 -
.../version-2.7.1/io-cassandra-sink.md | 54 -
.../version-2.7.1/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.7.1/io-cdc.md | 26 -
.../website/versioned_docs/version-2.7.1/io-cli.md | 606 -
.../versioned_docs/version-2.7.1/io-connectors.md | 232 -
.../version-2.7.1/io-debezium-source.md | 510 -
.../versioned_docs/version-2.7.1/io-debug.md | 329 -
.../versioned_docs/version-2.7.1/io-develop.md | 240 -
.../version-2.7.1/io-dynamodb-source.md | 76 -
.../version-2.7.1/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.7.1/io-file-source.md | 138 -
.../versioned_docs/version-2.7.1/io-flume-sink.md | 52 -
.../version-2.7.1/io-flume-source.md | 52 -
.../versioned_docs/version-2.7.1/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.7.1/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.7.1/io-hdfs3-sink.md | 54 -
.../version-2.7.1/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.7.1/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.7.1/io-kafka-sink.md | 69 -
.../version-2.7.1/io-kafka-source.md | 171 -
.../version-2.7.1/io-kinesis-sink.md | 73 -
.../version-2.7.1/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.7.1/io-mongo-sink.md | 51 -
.../version-2.7.1/io-netty-source.md | 205 -
.../versioned_docs/version-2.7.1/io-nsq-source.md | 21 -
.../versioned_docs/version-2.7.1/io-overview.md | 136 -
.../versioned_docs/version-2.7.1/io-quickstart.md | 816 -
.../version-2.7.1/io-rabbitmq-sink.md | 81 -
.../version-2.7.1/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.7.1/io-redis-sink.md | 70 -
.../versioned_docs/version-2.7.1/io-solr-sink.md | 61 -
.../version-2.7.1/io-twitter-source.md | 28 -
.../versioned_docs/version-2.7.1/io-twitter.md | 7 -
.../website/versioned_docs/version-2.7.1/io-use.md | 1505 --
.../version-2.7.1/performance-pulsar-perf.md | 197 -
.../version-2.7.1/reference-cli-tools.md | 794 -
.../version-2.7.1/reference-configuration.md | 781 -
.../version-2.7.1/reference-connector-admin.md | 11 -
.../version-2.7.1/reference-metrics.md | 463 -
.../version-2.7.1/reference-pulsar-admin.md | 3018 ---
.../version-2.7.1/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.7.1/schema-get-started.md | 95 -
.../versioned_docs/version-2.7.1/schema-manage.md | 809 -
.../version-2.7.1/schema-understand.md | 599 -
.../version-2.7.1/security-athenz.md | 93 -
.../version-2.7.1/security-authorization.md | 101 -
.../version-2.7.1/security-bouncy-castle.md | 139 -
.../version-2.7.1/security-encryption.md | 180 -
.../version-2.7.1/security-extending.md | 196 -
.../versioned_docs/version-2.7.1/security-jwt.md | 264 -
.../version-2.7.1/security-kerberos.md | 391 -
.../version-2.7.1/security-oauth2.md | 207 -
.../version-2.7.1/security-overview.md | 35 -
.../version-2.7.1/security-tls-authentication.md | 186 -
.../version-2.7.1/security-tls-keystore.md | 287 -
.../version-2.7.1/security-tls-transport.md | 261 -
.../version-2.7.1/security-token-admin.md | 159 -
.../version-2.7.1/sql-deployment-configurations.md | 169 -
.../version-2.7.1/sql-getting-started.md | 171 -
.../versioned_docs/version-2.7.1/sql-overview.md | 18 -
.../versioned_docs/version-2.7.1/sql-rest-api.md | 186 -
.../version-2.7.1/tiered-storage-aws.md | 280 -
.../version-2.7.1/tiered-storage-azure.md | 224 -
.../version-2.7.1/tiered-storage-filesystem.md | 523 -
.../version-2.7.1/tiered-storage-gcs.md | 274 -
.../version-2.7.1/tiered-storage-overview.md | 48 -
.../version-2.7.1/transaction-api.md | 151 -
.../version-2.7.1/transaction-guarantee.md | 17 -
.../version-2.7.1/window-functions-context.md | 529 -
.../versioned_docs/version-2.7.2/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.7.2/adaptors-spark.md | 73 -
.../versioned_docs/version-2.7.2/adaptors-storm.md | 89 -
.../version-2.7.2/admin-api-brokers.md | 158 -
.../version-2.7.2/admin-api-clusters.md | 222 -
.../version-2.7.2/admin-api-functions.md | 579 -
.../version-2.7.2/admin-api-namespaces.md | 937 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.7.2/admin-api-overview.md | 115 -
.../version-2.7.2/admin-api-partitioned-topics.md | 8 -
.../version-2.7.2/admin-api-permissions.md | 121 -
.../version-2.7.2/admin-api-persistent-topics.md | 8 -
.../version-2.7.2/admin-api-schemas.md | 7 -
.../version-2.7.2/admin-api-tenants.md | 157 -
.../version-2.7.2/admin-api-topics.md | 1472 --
.../version-2.7.2/administration-dashboard.md | 63 -
.../version-2.7.2/administration-geo.md | 197 -
.../version-2.7.2/administration-isolation.md | 79 -
.../version-2.7.2/administration-load-balance.md | 182 -
.../version-2.7.2/administration-proxy.md | 76 -
.../version-2.7.2/administration-pulsar-manager.md | 183 -
.../version-2.7.2/administration-stats.md | 64 -
.../version-2.7.2/administration-upgrade.md | 151 -
.../version-2.7.2/administration-zk-bk.md | 351 -
.../version-2.7.2/client-libraries-cgo.md | 545 -
.../version-2.7.2/client-libraries-cpp.md | 253 -
.../version-2.7.2/client-libraries-dotnet.md | 385 -
.../version-2.7.2/client-libraries-go.md | 681 -
.../version-2.7.2/client-libraries-java.md | 898 -
.../version-2.7.2/client-libraries-node.md | 589 -
.../version-2.7.2/client-libraries-python.md | 395 -
.../version-2.7.2/client-libraries-websocket.md | 448 -
.../concepts-architecture-overview.md | 156 -
.../version-2.7.2/concepts-authentication.md | 9 -
.../version-2.7.2/concepts-clients.md | 85 -
.../version-2.7.2/concepts-messaging.md | 571 -
.../version-2.7.2/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.7.2/concepts-overview.md | 31 -
.../version-2.7.2/concepts-proxy-sni-routing.md | 121 -
.../version-2.7.2/concepts-replication.md | 9 -
.../version-2.7.2/concepts-tiered-storage.md | 18 -
.../version-2.7.2/concepts-topic-compaction.md | 37 -
.../version-2.7.2/concepts-transactions.md | 30 -
.../version-2.7.2/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.7.2/cookbooks-compaction.md | 127 -
.../version-2.7.2/cookbooks-deduplication.md | 125 -
.../version-2.7.2/cookbooks-encryption.md | 170 -
.../version-2.7.2/cookbooks-message-queue.md | 117 -
.../version-2.7.2/cookbooks-non-persistent.md | 59 -
.../version-2.7.2/cookbooks-partitioned.md | 7 -
.../version-2.7.2/cookbooks-retention-expiry.md | 349 -
.../version-2.7.2/cookbooks-tiered-storage.md | 297 -
.../versioned_docs/version-2.7.2/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 431 -
.../version-2.7.2/deploy-bare-metal.md | 467 -
.../versioned_docs/version-2.7.2/deploy-dcos.md | 183 -
.../versioned_docs/version-2.7.2/deploy-docker.md | 52 -
.../version-2.7.2/deploy-kubernetes.md | 11 -
.../version-2.7.2/deploy-monitoring.md | 108 -
.../version-2.7.2/develop-binary-protocol.md | 556 -
.../versioned_docs/version-2.7.2/develop-cpp.md | 101 -
.../version-2.7.2/develop-load-manager.md | 215 -
.../versioned_docs/version-2.7.2/develop-schema.md | 58 -
.../versioned_docs/version-2.7.2/develop-tools.md | 105 -
.../version-2.7.2/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.7.2/developing-cpp.md | 101 -
.../version-2.7.2/developing-load-manager.md | 215 -
.../version-2.7.2/developing-tools.md | 105 -
.../versioned_docs/version-2.7.2/functions-cli.md | 198 -
.../version-2.7.2/functions-debug.md | 461 -
.../version-2.7.2/functions-deploy.md | 211 -
.../version-2.7.2/functions-develop.md | 1318 -
.../version-2.7.2/functions-metrics.md | 7 -
.../version-2.7.2/functions-overview.md | 194 -
.../version-2.7.2/functions-package.md | 431 -
.../version-2.7.2/functions-runtime.md | 325 -
.../version-2.7.2/functions-worker.md | 325 -
.../version-2.7.2/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.7.2/getting-started-docker.md | 159 -
.../version-2.7.2/getting-started-helm.md | 363 -
.../version-2.7.2/getting-started-pulsar.md | 67 -
.../version-2.7.2/getting-started-standalone.md | 230 -
.../versioned_docs/version-2.7.2/helm-deploy.md | 379 -
.../versioned_docs/version-2.7.2/helm-install.md | 41 -
.../versioned_docs/version-2.7.2/helm-overview.md | 100 -
.../versioned_docs/version-2.7.2/helm-prepare.md | 85 -
.../versioned_docs/version-2.7.2/helm-tools.md | 43 -
.../versioned_docs/version-2.7.2/helm-upgrade.md | 34 -
.../version-2.7.2/io-aerospike-sink.md | 26 -
.../version-2.7.2/io-canal-source.md | 203 -
.../version-2.7.2/io-cassandra-sink.md | 54 -
.../version-2.7.2/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.7.2/io-cdc.md | 26 -
.../website/versioned_docs/version-2.7.2/io-cli.md | 608 -
.../versioned_docs/version-2.7.2/io-connectors.md | 232 -
.../version-2.7.2/io-debezium-source.md | 510 -
.../versioned_docs/version-2.7.2/io-debug.md | 329 -
.../versioned_docs/version-2.7.2/io-develop.md | 240 -
.../version-2.7.2/io-dynamodb-source.md | 76 -
.../version-2.7.2/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.7.2/io-file-source.md | 138 -
.../versioned_docs/version-2.7.2/io-flume-sink.md | 52 -
.../version-2.7.2/io-flume-source.md | 52 -
.../versioned_docs/version-2.7.2/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.7.2/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.7.2/io-hdfs3-sink.md | 54 -
.../version-2.7.2/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.7.2/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.7.2/io-kafka-sink.md | 69 -
.../version-2.7.2/io-kafka-source.md | 171 -
.../version-2.7.2/io-kinesis-sink.md | 73 -
.../version-2.7.2/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.7.2/io-mongo-sink.md | 51 -
.../version-2.7.2/io-netty-source.md | 205 -
.../versioned_docs/version-2.7.2/io-nsq-source.md | 21 -
.../versioned_docs/version-2.7.2/io-overview.md | 136 -
.../versioned_docs/version-2.7.2/io-quickstart.md | 816 -
.../version-2.7.2/io-rabbitmq-sink.md | 81 -
.../version-2.7.2/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.7.2/io-redis-sink.md | 70 -
.../versioned_docs/version-2.7.2/io-solr-sink.md | 61 -
.../version-2.7.2/io-twitter-source.md | 28 -
.../versioned_docs/version-2.7.2/io-twitter.md | 7 -
.../website/versioned_docs/version-2.7.2/io-use.md | 1505 --
.../version-2.7.2/performance-pulsar-perf.md | 197 -
.../version-2.7.2/reference-cli-tools.md | 794 -
.../version-2.7.2/reference-configuration.md | 781 -
.../version-2.7.2/reference-connector-admin.md | 11 -
.../version-2.7.2/reference-metrics.md | 463 -
.../version-2.7.2/reference-pulsar-admin.md | 3018 ---
.../version-2.7.2/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.7.2/schema-get-started.md | 95 -
.../versioned_docs/version-2.7.2/schema-manage.md | 809 -
.../version-2.7.2/schema-understand.md | 599 -
.../version-2.7.2/security-athenz.md | 93 -
.../version-2.7.2/security-authorization.md | 101 -
.../version-2.7.2/security-bouncy-castle.md | 139 -
.../version-2.7.2/security-encryption.md | 185 -
.../version-2.7.2/security-extending.md | 196 -
.../versioned_docs/version-2.7.2/security-jwt.md | 264 -
.../version-2.7.2/security-kerberos.md | 391 -
.../version-2.7.2/security-oauth2.md | 207 -
.../version-2.7.2/security-overview.md | 35 -
.../version-2.7.2/security-tls-authentication.md | 186 -
.../version-2.7.2/security-tls-keystore.md | 287 -
.../version-2.7.2/security-tls-transport.md | 261 -
.../version-2.7.2/security-token-admin.md | 159 -
.../version-2.7.2/sql-deployment-configurations.md | 169 -
.../version-2.7.2/sql-getting-started.md | 171 -
.../versioned_docs/version-2.7.2/sql-overview.md | 18 -
.../versioned_docs/version-2.7.2/sql-rest-api.md | 186 -
.../version-2.7.2/tiered-storage-aws.md | 280 -
.../version-2.7.2/tiered-storage-azure.md | 224 -
.../version-2.7.2/tiered-storage-filesystem.md | 524 -
.../version-2.7.2/tiered-storage-gcs.md | 273 -
.../version-2.7.2/tiered-storage-overview.md | 48 -
.../version-2.7.2/transaction-api.md | 151 -
.../version-2.7.2/transaction-guarantee.md | 17 -
.../version-2.7.2/window-functions-context.md | 529 -
.../versioned_docs/version-2.7.3/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.7.3/adaptors-spark.md | 73 -
.../versioned_docs/version-2.7.3/adaptors-storm.md | 89 -
.../version-2.7.3/admin-api-brokers.md | 158 -
.../version-2.7.3/admin-api-clusters.md | 222 -
.../version-2.7.3/admin-api-functions.md | 579 -
.../version-2.7.3/admin-api-namespaces.md | 937 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.7.3/admin-api-overview.md | 115 -
.../version-2.7.3/admin-api-partitioned-topics.md | 8 -
.../version-2.7.3/admin-api-permissions.md | 121 -
.../version-2.7.3/admin-api-persistent-topics.md | 8 -
.../version-2.7.3/admin-api-schemas.md | 7 -
.../version-2.7.3/admin-api-tenants.md | 157 -
.../version-2.7.3/admin-api-topics.md | 1472 --
.../version-2.7.3/administration-dashboard.md | 63 -
.../version-2.7.3/administration-geo.md | 197 -
.../version-2.7.3/administration-isolation.md | 79 -
.../version-2.7.3/administration-load-balance.md | 182 -
.../version-2.7.3/administration-proxy.md | 76 -
.../version-2.7.3/administration-pulsar-manager.md | 183 -
.../version-2.7.3/administration-stats.md | 64 -
.../version-2.7.3/administration-upgrade.md | 151 -
.../version-2.7.3/administration-zk-bk.md | 351 -
.../version-2.7.3/client-libraries-cgo.md | 545 -
.../version-2.7.3/client-libraries-cpp.md | 253 -
.../version-2.7.3/client-libraries-dotnet.md | 385 -
.../version-2.7.3/client-libraries-go.md | 681 -
.../version-2.7.3/client-libraries-java.md | 898 -
.../version-2.7.3/client-libraries-node.md | 589 -
.../version-2.7.3/client-libraries-python.md | 395 -
.../version-2.7.3/client-libraries-websocket.md | 448 -
.../concepts-architecture-overview.md | 156 -
.../version-2.7.3/concepts-authentication.md | 9 -
.../version-2.7.3/concepts-clients.md | 85 -
.../version-2.7.3/concepts-messaging.md | 571 -
.../version-2.7.3/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.7.3/concepts-overview.md | 31 -
.../version-2.7.3/concepts-proxy-sni-routing.md | 121 -
.../version-2.7.3/concepts-replication.md | 9 -
.../version-2.7.3/concepts-tiered-storage.md | 18 -
.../version-2.7.3/concepts-topic-compaction.md | 37 -
.../version-2.7.3/concepts-transactions.md | 30 -
.../version-2.7.3/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.7.3/cookbooks-compaction.md | 127 -
.../version-2.7.3/cookbooks-deduplication.md | 125 -
.../version-2.7.3/cookbooks-encryption.md | 170 -
.../version-2.7.3/cookbooks-message-queue.md | 117 -
.../version-2.7.3/cookbooks-non-persistent.md | 59 -
.../version-2.7.3/cookbooks-partitioned.md | 7 -
.../version-2.7.3/cookbooks-retention-expiry.md | 349 -
.../version-2.7.3/cookbooks-tiered-storage.md | 297 -
.../versioned_docs/version-2.7.3/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.7.3/deploy-bare-metal.md | 461 -
.../versioned_docs/version-2.7.3/deploy-dcos.md | 183 -
.../versioned_docs/version-2.7.3/deploy-docker.md | 52 -
.../version-2.7.3/deploy-kubernetes.md | 11 -
.../version-2.7.3/deploy-monitoring.md | 107 -
.../version-2.7.3/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.7.3/developing-cpp.md | 101 -
.../version-2.7.3/developing-load-manager.md | 215 -
.../version-2.7.3/developing-tools.md | 105 -
.../versioned_docs/version-2.7.3/functions-cli.md | 198 -
.../version-2.7.3/functions-debug.md | 461 -
.../version-2.7.3/functions-deploy.md | 211 -
.../version-2.7.3/functions-develop.md | 1318 -
.../version-2.7.3/functions-metrics.md | 7 -
.../version-2.7.3/functions-overview.md | 194 -
.../version-2.7.3/functions-package.md | 431 -
.../version-2.7.3/functions-runtime.md | 325 -
.../version-2.7.3/functions-worker.md | 325 -
.../version-2.7.3/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.7.3/getting-started-docker.md | 159 -
.../version-2.7.3/getting-started-helm.md | 363 -
.../version-2.7.3/getting-started-pulsar.md | 67 -
.../version-2.7.3/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.7.3/helm-deploy.md | 379 -
.../versioned_docs/version-2.7.3/helm-install.md | 41 -
.../versioned_docs/version-2.7.3/helm-overview.md | 100 -
.../versioned_docs/version-2.7.3/helm-prepare.md | 85 -
.../versioned_docs/version-2.7.3/helm-tools.md | 43 -
.../versioned_docs/version-2.7.3/helm-upgrade.md | 34 -
.../version-2.7.3/io-aerospike-sink.md | 26 -
.../version-2.7.3/io-canal-source.md | 203 -
.../version-2.7.3/io-cassandra-sink.md | 54 -
.../version-2.7.3/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.7.3/io-cdc.md | 26 -
.../website/versioned_docs/version-2.7.3/io-cli.md | 606 -
.../versioned_docs/version-2.7.3/io-connectors.md | 232 -
.../version-2.7.3/io-debezium-source.md | 510 -
.../versioned_docs/version-2.7.3/io-debug.md | 329 -
.../versioned_docs/version-2.7.3/io-develop.md | 240 -
.../version-2.7.3/io-dynamodb-source.md | 76 -
.../version-2.7.3/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.7.3/io-file-source.md | 138 -
.../versioned_docs/version-2.7.3/io-flume-sink.md | 52 -
.../version-2.7.3/io-flume-source.md | 52 -
.../versioned_docs/version-2.7.3/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.7.3/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.7.3/io-hdfs3-sink.md | 54 -
.../version-2.7.3/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.7.3/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.7.3/io-kafka-sink.md | 69 -
.../version-2.7.3/io-kafka-source.md | 171 -
.../version-2.7.3/io-kinesis-sink.md | 73 -
.../version-2.7.3/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.7.3/io-mongo-sink.md | 51 -
.../version-2.7.3/io-netty-source.md | 205 -
.../versioned_docs/version-2.7.3/io-nsq-source.md | 21 -
.../versioned_docs/version-2.7.3/io-overview.md | 136 -
.../versioned_docs/version-2.7.3/io-quickstart.md | 816 -
.../version-2.7.3/io-rabbitmq-sink.md | 81 -
.../version-2.7.3/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.7.3/io-redis-sink.md | 70 -
.../versioned_docs/version-2.7.3/io-solr-sink.md | 61 -
.../version-2.7.3/io-twitter-source.md | 28 -
.../versioned_docs/version-2.7.3/io-twitter.md | 7 -
.../website/versioned_docs/version-2.7.3/io-use.md | 1505 --
.../version-2.7.3/performance-pulsar-perf.md | 197 -
.../version-2.7.3/reference-cli-tools.md | 794 -
.../version-2.7.3/reference-configuration.md | 781 -
.../version-2.7.3/reference-connector-admin.md | 11 -
.../version-2.7.3/reference-metrics.md | 483 -
.../version-2.7.3/reference-pulsar-admin.md | 3017 ---
.../version-2.7.3/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.7.3/schema-get-started.md | 95 -
.../versioned_docs/version-2.7.3/schema-manage.md | 809 -
.../version-2.7.3/schema-understand.md | 599 -
.../version-2.7.3/security-athenz.md | 93 -
.../version-2.7.3/security-authorization.md | 101 -
.../version-2.7.3/security-bouncy-castle.md | 139 -
.../version-2.7.3/security-encryption.md | 185 -
.../version-2.7.3/security-extending.md | 196 -
.../versioned_docs/version-2.7.3/security-jwt.md | 264 -
.../version-2.7.3/security-kerberos.md | 391 -
.../version-2.7.3/security-oauth2.md | 207 -
.../version-2.7.3/security-overview.md | 35 -
.../version-2.7.3/security-tls-authentication.md | 186 -
.../version-2.7.3/security-tls-keystore.md | 287 -
.../version-2.7.3/security-tls-transport.md | 261 -
.../version-2.7.3/security-token-admin.md | 159 -
.../version-2.7.3/sql-deployment-configurations.md | 168 -
.../version-2.7.3/sql-getting-started.md | 171 -
.../versioned_docs/version-2.7.3/sql-overview.md | 18 -
.../versioned_docs/version-2.7.3/sql-rest-api.md | 186 -
.../version-2.7.3/tiered-storage-aws.md | 280 -
.../version-2.7.3/tiered-storage-azure.md | 224 -
.../version-2.7.3/tiered-storage-filesystem.md | 524 -
.../version-2.7.3/tiered-storage-gcs.md | 274 -
.../version-2.7.3/tiered-storage-overview.md | 48 -
.../version-2.7.3/transaction-api.md | 151 -
.../version-2.7.3/transaction-guarantee.md | 17 -
.../version-2.7.3/window-functions-context.md | 529 -
.../versioned_docs/version-2.7.4/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.7.4/adaptors-spark.md | 73 -
.../versioned_docs/version-2.7.4/adaptors-storm.md | 89 -
.../version-2.7.4/admin-api-brokers.md | 158 -
.../version-2.7.4/admin-api-clusters.md | 222 -
.../version-2.7.4/admin-api-functions.md | 579 -
.../version-2.7.4/admin-api-namespaces.md | 937 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.7.4/admin-api-overview.md | 115 -
.../version-2.7.4/admin-api-partitioned-topics.md | 8 -
.../version-2.7.4/admin-api-permissions.md | 121 -
.../version-2.7.4/admin-api-persistent-topics.md | 8 -
.../version-2.7.4/admin-api-schemas.md | 7 -
.../version-2.7.4/admin-api-tenants.md | 157 -
.../version-2.7.4/admin-api-topics.md | 1472 --
.../version-2.7.4/administration-dashboard.md | 63 -
.../version-2.7.4/administration-geo.md | 197 -
.../version-2.7.4/administration-isolation.md | 79 -
.../version-2.7.4/administration-load-balance.md | 182 -
.../version-2.7.4/administration-proxy.md | 76 -
.../version-2.7.4/administration-pulsar-manager.md | 183 -
.../version-2.7.4/administration-stats.md | 64 -
.../version-2.7.4/administration-upgrade.md | 151 -
.../version-2.7.4/administration-zk-bk.md | 351 -
.../version-2.7.4/client-libraries-cgo.md | 545 -
.../version-2.7.4/client-libraries-cpp.md | 253 -
.../version-2.7.4/client-libraries-dotnet.md | 385 -
.../version-2.7.4/client-libraries-go.md | 681 -
.../version-2.7.4/client-libraries-java.md | 898 -
.../version-2.7.4/client-libraries-node.md | 589 -
.../version-2.7.4/client-libraries-python.md | 395 -
.../version-2.7.4/client-libraries-websocket.md | 448 -
.../concepts-architecture-overview.md | 156 -
.../version-2.7.4/concepts-authentication.md | 9 -
.../version-2.7.4/concepts-clients.md | 85 -
.../version-2.7.4/concepts-messaging.md | 571 -
.../version-2.7.4/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.7.4/concepts-overview.md | 31 -
.../version-2.7.4/concepts-proxy-sni-routing.md | 121 -
.../version-2.7.4/concepts-replication.md | 9 -
.../version-2.7.4/concepts-tiered-storage.md | 18 -
.../version-2.7.4/concepts-topic-compaction.md | 37 -
.../version-2.7.4/concepts-transactions.md | 30 -
.../version-2.7.4/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.7.4/cookbooks-compaction.md | 127 -
.../version-2.7.4/cookbooks-deduplication.md | 125 -
.../version-2.7.4/cookbooks-encryption.md | 170 -
.../version-2.7.4/cookbooks-message-queue.md | 117 -
.../version-2.7.4/cookbooks-non-persistent.md | 59 -
.../version-2.7.4/cookbooks-partitioned.md | 7 -
.../version-2.7.4/cookbooks-retention-expiry.md | 349 -
.../version-2.7.4/cookbooks-tiered-storage.md | 297 -
.../versioned_docs/version-2.7.4/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 426 -
.../version-2.7.4/deploy-bare-metal.md | 461 -
.../versioned_docs/version-2.7.4/deploy-dcos.md | 183 -
.../versioned_docs/version-2.7.4/deploy-docker.md | 52 -
.../version-2.7.4/deploy-kubernetes.md | 11 -
.../version-2.7.4/deploy-monitoring.md | 107 -
.../version-2.7.4/developing-binary-protocol.md | 556 -
.../versioned_docs/version-2.7.4/developing-cpp.md | 101 -
.../version-2.7.4/developing-load-manager.md | 215 -
.../version-2.7.4/developing-tools.md | 105 -
.../versioned_docs/version-2.7.4/functions-cli.md | 198 -
.../version-2.7.4/functions-debug.md | 461 -
.../version-2.7.4/functions-deploy.md | 211 -
.../version-2.7.4/functions-develop.md | 1318 -
.../version-2.7.4/functions-metrics.md | 7 -
.../version-2.7.4/functions-overview.md | 194 -
.../version-2.7.4/functions-package.md | 431 -
.../version-2.7.4/functions-runtime.md | 325 -
.../version-2.7.4/functions-worker.md | 325 -
.../version-2.7.4/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.7.4/getting-started-docker.md | 159 -
.../version-2.7.4/getting-started-helm.md | 363 -
.../version-2.7.4/getting-started-pulsar.md | 67 -
.../version-2.7.4/getting-started-standalone.md | 226 -
.../versioned_docs/version-2.7.4/helm-deploy.md | 379 -
.../versioned_docs/version-2.7.4/helm-install.md | 41 -
.../versioned_docs/version-2.7.4/helm-overview.md | 100 -
.../versioned_docs/version-2.7.4/helm-prepare.md | 85 -
.../versioned_docs/version-2.7.4/helm-tools.md | 43 -
.../versioned_docs/version-2.7.4/helm-upgrade.md | 34 -
.../version-2.7.4/io-aerospike-sink.md | 26 -
.../version-2.7.4/io-canal-source.md | 203 -
.../version-2.7.4/io-cassandra-sink.md | 54 -
.../version-2.7.4/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.7.4/io-cdc.md | 26 -
.../website/versioned_docs/version-2.7.4/io-cli.md | 606 -
.../versioned_docs/version-2.7.4/io-connectors.md | 232 -
.../version-2.7.4/io-debezium-source.md | 510 -
.../versioned_docs/version-2.7.4/io-debug.md | 329 -
.../versioned_docs/version-2.7.4/io-develop.md | 240 -
.../version-2.7.4/io-dynamodb-source.md | 76 -
.../version-2.7.4/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.7.4/io-file-source.md | 138 -
.../versioned_docs/version-2.7.4/io-flume-sink.md | 52 -
.../version-2.7.4/io-flume-source.md | 52 -
.../versioned_docs/version-2.7.4/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.7.4/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.7.4/io-hdfs3-sink.md | 54 -
.../version-2.7.4/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.7.4/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.7.4/io-kafka-sink.md | 69 -
.../version-2.7.4/io-kafka-source.md | 171 -
.../version-2.7.4/io-kinesis-sink.md | 73 -
.../version-2.7.4/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.7.4/io-mongo-sink.md | 51 -
.../version-2.7.4/io-netty-source.md | 205 -
.../versioned_docs/version-2.7.4/io-nsq-source.md | 21 -
.../versioned_docs/version-2.7.4/io-overview.md | 136 -
.../versioned_docs/version-2.7.4/io-quickstart.md | 816 -
.../version-2.7.4/io-rabbitmq-sink.md | 81 -
.../version-2.7.4/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.7.4/io-redis-sink.md | 70 -
.../versioned_docs/version-2.7.4/io-solr-sink.md | 61 -
.../version-2.7.4/io-twitter-source.md | 28 -
.../versioned_docs/version-2.7.4/io-twitter.md | 7 -
.../website/versioned_docs/version-2.7.4/io-use.md | 1505 --
.../version-2.7.4/performance-pulsar-perf.md | 197 -
.../version-2.7.4/reference-cli-tools.md | 794 -
.../version-2.7.4/reference-configuration.md | 781 -
.../version-2.7.4/reference-connector-admin.md | 11 -
.../version-2.7.4/reference-metrics.md | 483 -
.../version-2.7.4/reference-pulsar-admin.md | 3017 ---
.../version-2.7.4/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.7.4/schema-get-started.md | 95 -
.../versioned_docs/version-2.7.4/schema-manage.md | 809 -
.../version-2.7.4/schema-understand.md | 599 -
.../version-2.7.4/security-athenz.md | 93 -
.../version-2.7.4/security-authorization.md | 101 -
.../version-2.7.4/security-bouncy-castle.md | 139 -
.../version-2.7.4/security-encryption.md | 185 -
.../version-2.7.4/security-extending.md | 196 -
.../versioned_docs/version-2.7.4/security-jwt.md | 264 -
.../version-2.7.4/security-kerberos.md | 391 -
.../version-2.7.4/security-oauth2.md | 207 -
.../version-2.7.4/security-overview.md | 35 -
.../version-2.7.4/security-tls-authentication.md | 186 -
.../version-2.7.4/security-tls-keystore.md | 302 -
.../version-2.7.4/security-tls-transport.md | 261 -
.../version-2.7.4/security-token-admin.md | 159 -
.../version-2.7.4/sql-deployment-configurations.md | 169 -
.../version-2.7.4/sql-getting-started.md | 171 -
.../versioned_docs/version-2.7.4/sql-overview.md | 18 -
.../versioned_docs/version-2.7.4/sql-rest-api.md | 186 -
.../version-2.7.4/tiered-storage-aws.md | 280 -
.../version-2.7.4/tiered-storage-azure.md | 224 -
.../version-2.7.4/tiered-storage-filesystem.md | 522 -
.../version-2.7.4/tiered-storage-gcs.md | 274 -
.../version-2.7.4/tiered-storage-overview.md | 48 -
.../version-2.7.4/transaction-api.md | 151 -
.../version-2.7.4/transaction-guarantee.md | 17 -
.../version-2.7.4/window-functions-context.md | 529 -
.../versioned_docs/version-2.8.0/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.8.0/adaptors-spark.md | 81 -
.../versioned_docs/version-2.8.0/adaptors-storm.md | 90 -
.../version-2.8.0/admin-api-brokers.md | 186 -
.../version-2.8.0/admin-api-clusters.md | 222 -
.../version-2.8.0/admin-api-functions.md | 579 -
.../version-2.8.0/admin-api-namespaces.md | 937 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.8.0/admin-api-overview.md | 110 -
.../version-2.8.0/admin-api-packages.md | 241 -
.../version-2.8.0/admin-api-partitioned-topics.md | 8 -
.../version-2.8.0/admin-api-permissions.md | 121 -
.../version-2.8.0/admin-api-persistent-topics.md | 8 -
.../version-2.8.0/admin-api-schemas.md | 7 -
.../version-2.8.0/admin-api-tenants.md | 157 -
.../version-2.8.0/admin-api-topics.md | 1505 --
.../version-2.8.0/administration-dashboard.md | 63 -
.../version-2.8.0/administration-geo.md | 197 -
.../version-2.8.0/administration-isolation.md | 85 -
.../version-2.8.0/administration-load-balance.md | 182 -
.../version-2.8.0/administration-proxy.md | 76 -
.../version-2.8.0/administration-pulsar-manager.md | 183 -
.../version-2.8.0/administration-stats.md | 64 -
.../version-2.8.0/administration-upgrade.md | 151 -
.../version-2.8.0/administration-zk-bk.md | 351 -
.../version-2.8.0/client-libraries-cgo.md | 545 -
.../version-2.8.0/client-libraries-cpp.md | 353 -
.../version-2.8.0/client-libraries-dotnet.md | 385 -
.../version-2.8.0/client-libraries-go.md | 829 -
.../version-2.8.0/client-libraries-java.md | 904 -
.../version-2.8.0/client-libraries-node.md | 598 -
.../version-2.8.0/client-libraries-python.md | 410 -
.../version-2.8.0/client-libraries-websocket.md | 556 -
.../concepts-architecture-overview.md | 162 -
.../version-2.8.0/concepts-authentication.md | 9 -
.../version-2.8.0/concepts-clients.md | 85 -
.../version-2.8.0/concepts-messaging.md | 605 -
.../version-2.8.0/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.8.0/concepts-overview.md | 31 -
.../version-2.8.0/concepts-proxy-sni-routing.md | 151 -
.../version-2.8.0/concepts-replication.md | 9 -
.../version-2.8.0/concepts-tiered-storage.md | 18 -
.../version-2.8.0/concepts-topic-compaction.md | 37 -
.../version-2.8.0/concepts-transactions.md | 30 -
.../version-2.8.0/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.8.0/cookbooks-compaction.md | 127 -
.../version-2.8.0/cookbooks-deduplication.md | 125 -
.../version-2.8.0/cookbooks-encryption.md | 170 -
.../version-2.8.0/cookbooks-message-queue.md | 118 -
.../version-2.8.0/cookbooks-non-persistent.md | 59 -
.../version-2.8.0/cookbooks-partitioned.md | 7 -
.../version-2.8.0/cookbooks-retention-expiry.md | 350 -
.../version-2.8.0/cookbooks-tiered-storage.md | 307 -
.../versioned_docs/version-2.8.0/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 431 -
.../version-2.8.0/deploy-bare-metal.md | 461 -
.../versioned_docs/version-2.8.0/deploy-dcos.md | 183 -
.../versioned_docs/version-2.8.0/deploy-docker.md | 52 -
.../version-2.8.0/deploy-kubernetes.md | 11 -
.../version-2.8.0/deploy-monitoring.md | 128 -
.../version-2.8.0/developing-binary-protocol.md | 579 -
.../version-2.8.0/developing-load-manager.md | 215 -
.../version-2.8.0/developing-tools.md | 105 -
.../versioned_docs/version-2.8.0/functions-cli.md | 198 -
.../version-2.8.0/functions-debug.md | 461 -
.../version-2.8.0/functions-deploy.md | 211 -
.../version-2.8.0/functions-develop.md | 1332 -
.../version-2.8.0/functions-metrics.md | 7 -
.../version-2.8.0/functions-overview.md | 194 -
.../version-2.8.0/functions-package.md | 431 -
.../version-2.8.0/functions-runtime.md | 362 -
.../version-2.8.0/functions-worker.md | 331 -
.../version-2.8.0/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.8.0/getting-started-docker.md | 159 -
.../version-2.8.0/getting-started-helm.md | 363 -
.../version-2.8.0/getting-started-pulsar.md | 67 -
.../version-2.8.0/getting-started-standalone.md | 230 -
.../versioned_docs/version-2.8.0/helm-deploy.md | 379 -
.../versioned_docs/version-2.8.0/helm-install.md | 41 -
.../versioned_docs/version-2.8.0/helm-overview.md | 100 -
.../versioned_docs/version-2.8.0/helm-prepare.md | 85 -
.../versioned_docs/version-2.8.0/helm-tools.md | 43 -
.../versioned_docs/version-2.8.0/helm-upgrade.md | 34 -
.../version-2.8.0/io-aerospike-sink.md | 26 -
.../version-2.8.0/io-canal-source.md | 203 -
.../version-2.8.0/io-cassandra-sink.md | 54 -
.../version-2.8.0/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.8.0/io-cdc.md | 26 -
.../website/versioned_docs/version-2.8.0/io-cli.md | 606 -
.../versioned_docs/version-2.8.0/io-connectors.md | 232 -
.../version-2.8.0/io-debezium-source.md | 510 -
.../versioned_docs/version-2.8.0/io-debug.md | 329 -
.../versioned_docs/version-2.8.0/io-develop.md | 375 -
.../version-2.8.0/io-dynamodb-source.md | 76 -
.../version-2.8.0/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.8.0/io-file-source.md | 138 -
.../versioned_docs/version-2.8.0/io-flume-sink.md | 52 -
.../version-2.8.0/io-flume-source.md | 52 -
.../versioned_docs/version-2.8.0/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.8.0/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.8.0/io-hdfs3-sink.md | 54 -
.../version-2.8.0/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.8.0/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.8.0/io-kafka-sink.md | 69 -
.../version-2.8.0/io-kafka-source.md | 199 -
.../version-2.8.0/io-kinesis-sink.md | 73 -
.../version-2.8.0/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.8.0/io-mongo-sink.md | 51 -
.../version-2.8.0/io-netty-source.md | 205 -
.../versioned_docs/version-2.8.0/io-nsq-source.md | 21 -
.../versioned_docs/version-2.8.0/io-overview.md | 136 -
.../versioned_docs/version-2.8.0/io-quickstart.md | 816 -
.../version-2.8.0/io-rabbitmq-sink.md | 81 -
.../version-2.8.0/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.8.0/io-redis-sink.md | 70 -
.../versioned_docs/version-2.8.0/io-solr-sink.md | 61 -
.../version-2.8.0/io-twitter-source.md | 28 -
.../versioned_docs/version-2.8.0/io-twitter.md | 7 -
.../website/versioned_docs/version-2.8.0/io-use.md | 1505 --
.../version-2.8.0/performance-pulsar-perf.md | 205 -
.../version-2.8.0/reference-cli-tools.md | 812 -
.../version-2.8.0/reference-configuration.md | 789 -
.../version-2.8.0/reference-connector-admin.md | 11 -
.../version-2.8.0/reference-metrics.md | 556 -
.../version-2.8.0/reference-pulsar-admin.md | 2750 --
.../version-2.8.0/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.8.0/schema-get-started.md | 95 -
.../versioned_docs/version-2.8.0/schema-manage.md | 809 -
.../version-2.8.0/schema-understand.md | 651 -
.../version-2.8.0/security-athenz.md | 93 -
.../version-2.8.0/security-authorization.md | 101 -
.../version-2.8.0/security-bouncy-castle.md | 139 -
.../version-2.8.0/security-encryption.md | 185 -
.../version-2.8.0/security-extending.md | 196 -
.../versioned_docs/version-2.8.0/security-jwt.md | 264 -
.../version-2.8.0/security-kerberos.md | 391 -
.../version-2.8.0/security-oauth2.md | 207 -
.../version-2.8.0/security-overview.md | 35 -
.../version-2.8.0/security-tls-authentication.md | 188 -
.../version-2.8.0/security-tls-keystore.md | 287 -
.../version-2.8.0/security-tls-transport.md | 262 -
.../version-2.8.0/security-token-admin.md | 159 -
.../version-2.8.0/sql-deployment-configurations.md | 169 -
.../version-2.8.0/sql-getting-started.md | 171 -
.../versioned_docs/version-2.8.0/sql-overview.md | 18 -
.../versioned_docs/version-2.8.0/sql-rest-api.md | 186 -
.../version-2.8.0/tiered-storage-aliyun.md | 218 -
.../version-2.8.0/tiered-storage-aws.md | 280 -
.../version-2.8.0/tiered-storage-azure.md | 224 -
.../version-2.8.0/tiered-storage-filesystem.md | 524 -
.../version-2.8.0/tiered-storage-gcs.md | 274 -
.../version-2.8.0/tiered-storage-overview.md | 48 -
.../version-2.8.0/transaction-api.md | 149 -
.../version-2.8.0/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.8.0/txn-how.md | 319 -
.../versioned_docs/version-2.8.0/txn-monitor.md | 10 -
.../versioned_docs/version-2.8.0/txn-use.md | 125 -
.../versioned_docs/version-2.8.0/txn-what.md | 60 -
.../versioned_docs/version-2.8.0/txn-why.md | 45 -
.../version-2.8.0/window-functions-context.md | 529 -
.../versioned_docs/version-2.8.1/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.8.1/adaptors-spark.md | 81 -
.../versioned_docs/version-2.8.1/adaptors-storm.md | 90 -
.../version-2.8.1/admin-api-brokers.md | 186 -
.../version-2.8.1/admin-api-clusters.md | 222 -
.../version-2.8.1/admin-api-functions.md | 579 -
.../version-2.8.1/admin-api-namespaces.md | 937 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.8.1/admin-api-overview.md | 110 -
.../version-2.8.1/admin-api-packages.md | 241 -
.../version-2.8.1/admin-api-partitioned-topics.md | 8 -
.../version-2.8.1/admin-api-permissions.md | 121 -
.../version-2.8.1/admin-api-persistent-topics.md | 8 -
.../version-2.8.1/admin-api-schemas.md | 7 -
.../version-2.8.1/admin-api-tenants.md | 157 -
.../version-2.8.1/admin-api-topics.md | 1506 --
.../version-2.8.1/administration-dashboard.md | 63 -
.../version-2.8.1/administration-geo.md | 197 -
.../version-2.8.1/administration-isolation.md | 85 -
.../version-2.8.1/administration-load-balance.md | 182 -
.../version-2.8.1/administration-proxy.md | 76 -
.../version-2.8.1/administration-pulsar-manager.md | 183 -
.../version-2.8.1/administration-stats.md | 64 -
.../version-2.8.1/administration-upgrade.md | 151 -
.../version-2.8.1/administration-zk-bk.md | 351 -
.../version-2.8.1/client-libraries-cgo.md | 545 -
.../version-2.8.1/client-libraries-cpp.md | 618 -
.../version-2.8.1/client-libraries-dotnet.md | 385 -
.../version-2.8.1/client-libraries-go.md | 829 -
.../version-2.8.1/client-libraries-java.md | 907 -
.../version-2.8.1/client-libraries-node.md | 598 -
.../version-2.8.1/client-libraries-python.md | 410 -
.../version-2.8.1/client-libraries-websocket.md | 556 -
.../concepts-architecture-overview.md | 162 -
.../version-2.8.1/concepts-authentication.md | 9 -
.../version-2.8.1/concepts-clients.md | 85 -
.../version-2.8.1/concepts-messaging.md | 605 -
.../version-2.8.1/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.8.1/concepts-overview.md | 31 -
.../version-2.8.1/concepts-proxy-sni-routing.md | 151 -
.../version-2.8.1/concepts-replication.md | 9 -
.../version-2.8.1/concepts-tiered-storage.md | 18 -
.../version-2.8.1/concepts-topic-compaction.md | 37 -
.../version-2.8.1/concepts-transactions.md | 30 -
.../version-2.8.1/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.8.1/cookbooks-compaction.md | 127 -
.../version-2.8.1/cookbooks-deduplication.md | 125 -
.../version-2.8.1/cookbooks-encryption.md | 170 -
.../version-2.8.1/cookbooks-message-queue.md | 118 -
.../version-2.8.1/cookbooks-non-persistent.md | 59 -
.../version-2.8.1/cookbooks-partitioned.md | 7 -
.../version-2.8.1/cookbooks-retention-expiry.md | 350 -
.../version-2.8.1/cookbooks-tiered-storage.md | 307 -
.../versioned_docs/version-2.8.1/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 431 -
.../version-2.8.1/deploy-bare-metal.md | 461 -
.../versioned_docs/version-2.8.1/deploy-dcos.md | 183 -
.../versioned_docs/version-2.8.1/deploy-docker.md | 52 -
.../version-2.8.1/deploy-kubernetes.md | 11 -
.../version-2.8.1/deploy-monitoring.md | 128 -
.../version-2.8.1/developing-binary-protocol.md | 580 -
.../version-2.8.1/developing-load-manager.md | 215 -
.../version-2.8.1/developing-tools.md | 105 -
.../versioned_docs/version-2.8.1/functions-cli.md | 198 -
.../version-2.8.1/functions-debug.md | 461 -
.../version-2.8.1/functions-deploy.md | 230 -
.../version-2.8.1/functions-develop.md | 1332 -
.../version-2.8.1/functions-metrics.md | 7 -
.../version-2.8.1/functions-overview.md | 194 -
.../version-2.8.1/functions-package.md | 431 -
.../version-2.8.1/functions-runtime.md | 362 -
.../version-2.8.1/functions-worker.md | 332 -
.../version-2.8.1/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.8.1/getting-started-docker.md | 159 -
.../version-2.8.1/getting-started-helm.md | 363 -
.../version-2.8.1/getting-started-pulsar.md | 67 -
.../version-2.8.1/getting-started-standalone.md | 230 -
.../versioned_docs/version-2.8.1/helm-deploy.md | 379 -
.../versioned_docs/version-2.8.1/helm-install.md | 41 -
.../versioned_docs/version-2.8.1/helm-overview.md | 100 -
.../versioned_docs/version-2.8.1/helm-prepare.md | 85 -
.../versioned_docs/version-2.8.1/helm-tools.md | 43 -
.../versioned_docs/version-2.8.1/helm-upgrade.md | 34 -
.../version-2.8.1/io-aerospike-sink.md | 26 -
.../version-2.8.1/io-canal-source.md | 203 -
.../version-2.8.1/io-cassandra-sink.md | 54 -
.../version-2.8.1/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.8.1/io-cdc.md | 26 -
.../website/versioned_docs/version-2.8.1/io-cli.md | 606 -
.../versioned_docs/version-2.8.1/io-connectors.md | 232 -
.../version-2.8.1/io-debezium-source.md | 510 -
.../versioned_docs/version-2.8.1/io-debug.md | 329 -
.../versioned_docs/version-2.8.1/io-develop.md | 375 -
.../version-2.8.1/io-dynamodb-source.md | 76 -
.../version-2.8.1/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.8.1/io-file-source.md | 138 -
.../versioned_docs/version-2.8.1/io-flume-sink.md | 52 -
.../version-2.8.1/io-flume-source.md | 52 -
.../versioned_docs/version-2.8.1/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.8.1/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.8.1/io-hdfs3-sink.md | 54 -
.../version-2.8.1/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.8.1/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.8.1/io-kafka-sink.md | 69 -
.../version-2.8.1/io-kafka-source.md | 199 -
.../version-2.8.1/io-kinesis-sink.md | 73 -
.../version-2.8.1/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.8.1/io-mongo-sink.md | 51 -
.../version-2.8.1/io-netty-source.md | 205 -
.../versioned_docs/version-2.8.1/io-nsq-source.md | 21 -
.../versioned_docs/version-2.8.1/io-overview.md | 136 -
.../versioned_docs/version-2.8.1/io-quickstart.md | 816 -
.../version-2.8.1/io-rabbitmq-sink.md | 81 -
.../version-2.8.1/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.8.1/io-redis-sink.md | 70 -
.../versioned_docs/version-2.8.1/io-solr-sink.md | 61 -
.../version-2.8.1/io-twitter-source.md | 28 -
.../versioned_docs/version-2.8.1/io-twitter.md | 7 -
.../website/versioned_docs/version-2.8.1/io-use.md | 1505 --
.../version-2.8.1/performance-pulsar-perf.md | 205 -
.../version-2.8.1/reference-cli-tools.md | 812 -
.../version-2.8.1/reference-configuration.md | 790 -
.../version-2.8.1/reference-connector-admin.md | 11 -
.../version-2.8.1/reference-metrics.md | 559 -
.../version-2.8.1/reference-pulsar-admin.md | 2753 --
.../version-2.8.1/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.8.1/schema-get-started.md | 95 -
.../versioned_docs/version-2.8.1/schema-manage.md | 809 -
.../version-2.8.1/schema-understand.md | 651 -
.../version-2.8.1/security-athenz.md | 93 -
.../version-2.8.1/security-authorization.md | 115 -
.../version-2.8.1/security-bouncy-castle.md | 139 -
.../version-2.8.1/security-encryption.md | 185 -
.../version-2.8.1/security-extending.md | 196 -
.../versioned_docs/version-2.8.1/security-jwt.md | 264 -
.../version-2.8.1/security-kerberos.md | 391 -
.../version-2.8.1/security-oauth2.md | 207 -
.../version-2.8.1/security-overview.md | 35 -
.../version-2.8.1/security-tls-authentication.md | 188 -
.../version-2.8.1/security-tls-keystore.md | 287 -
.../version-2.8.1/security-tls-transport.md | 262 -
.../version-2.8.1/security-token-admin.md | 159 -
.../version-2.8.1/sql-deployment-configurations.md | 169 -
.../version-2.8.1/sql-getting-started.md | 171 -
.../versioned_docs/version-2.8.1/sql-overview.md | 18 -
.../versioned_docs/version-2.8.1/sql-rest-api.md | 186 -
.../version-2.8.1/tiered-storage-aliyun.md | 218 -
.../version-2.8.1/tiered-storage-aws.md | 280 -
.../version-2.8.1/tiered-storage-azure.md | 224 -
.../version-2.8.1/tiered-storage-filesystem.md | 524 -
.../version-2.8.1/tiered-storage-gcs.md | 274 -
.../version-2.8.1/tiered-storage-overview.md | 48 -
.../version-2.8.1/transaction-api.md | 149 -
.../version-2.8.1/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.8.1/txn-how.md | 319 -
.../versioned_docs/version-2.8.1/txn-monitor.md | 10 -
.../versioned_docs/version-2.8.1/txn-use.md | 125 -
.../versioned_docs/version-2.8.1/txn-what.md | 60 -
.../versioned_docs/version-2.8.1/txn-why.md | 45 -
.../version-2.8.1/window-functions-context.md | 529 -
.../versioned_docs/version-2.8.2/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.8.2/adaptors-spark.md | 81 -
.../versioned_docs/version-2.8.2/adaptors-storm.md | 90 -
.../version-2.8.2/admin-api-brokers.md | 196 -
.../version-2.8.2/admin-api-clusters.md | 232 -
.../version-2.8.2/admin-api-functions.md | 589 -
.../version-2.8.2/admin-api-namespaces.md | 947 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.8.2/admin-api-overview.md | 121 -
.../version-2.8.2/admin-api-packages.md | 251 -
.../version-2.8.2/admin-api-partitioned-topics.md | 8 -
.../version-2.8.2/admin-api-permissions.md | 136 -
.../version-2.8.2/admin-api-persistent-topics.md | 8 -
.../version-2.8.2/admin-api-schemas.md | 7 -
.../version-2.8.2/admin-api-tenants.md | 167 -
.../version-2.8.2/admin-api-topics.md | 1515 --
.../version-2.8.2/administration-dashboard.md | 63 -
.../version-2.8.2/administration-geo.md | 197 -
.../version-2.8.2/administration-isolation.md | 85 -
.../version-2.8.2/administration-load-balance.md | 182 -
.../version-2.8.2/administration-proxy.md | 76 -
.../version-2.8.2/administration-pulsar-manager.md | 183 -
.../version-2.8.2/administration-stats.md | 64 -
.../version-2.8.2/administration-upgrade.md | 151 -
.../version-2.8.2/administration-zk-bk.md | 351 -
.../version-2.8.2/client-libraries-cgo.md | 545 -
.../version-2.8.2/client-libraries-cpp.md | 353 -
.../version-2.8.2/client-libraries-dotnet.md | 385 -
.../version-2.8.2/client-libraries-go.md | 829 -
.../version-2.8.2/client-libraries-java.md | 907 -
.../version-2.8.2/client-libraries-node.md | 598 -
.../version-2.8.2/client-libraries-python.md | 410 -
.../version-2.8.2/client-libraries-websocket.md | 592 -
.../concepts-architecture-overview.md | 162 -
.../version-2.8.2/concepts-authentication.md | 9 -
.../version-2.8.2/concepts-clients.md | 85 -
.../version-2.8.2/concepts-messaging.md | 605 -
.../version-2.8.2/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.8.2/concepts-overview.md | 31 -
.../version-2.8.2/concepts-proxy-sni-routing.md | 151 -
.../version-2.8.2/concepts-replication.md | 9 -
.../version-2.8.2/concepts-tiered-storage.md | 18 -
.../version-2.8.2/concepts-topic-compaction.md | 37 -
.../version-2.8.2/concepts-transactions.md | 30 -
.../version-2.8.2/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.8.2/cookbooks-compaction.md | 127 -
.../version-2.8.2/cookbooks-deduplication.md | 125 -
.../version-2.8.2/cookbooks-encryption.md | 170 -
.../version-2.8.2/cookbooks-message-queue.md | 118 -
.../version-2.8.2/cookbooks-non-persistent.md | 59 -
.../version-2.8.2/cookbooks-partitioned.md | 7 -
.../version-2.8.2/cookbooks-retention-expiry.md | 350 -
.../version-2.8.2/cookbooks-tiered-storage.md | 307 -
.../versioned_docs/version-2.8.2/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 431 -
.../version-2.8.2/deploy-bare-metal.md | 461 -
.../versioned_docs/version-2.8.2/deploy-dcos.md | 183 -
.../versioned_docs/version-2.8.2/deploy-docker.md | 52 -
.../version-2.8.2/deploy-kubernetes.md | 11 -
.../version-2.8.2/deploy-monitoring.md | 128 -
.../version-2.8.2/developing-binary-protocol.md | 580 -
.../version-2.8.2/developing-load-manager.md | 215 -
.../version-2.8.2/developing-tools.md | 105 -
.../versioned_docs/version-2.8.2/functions-cli.md | 198 -
.../version-2.8.2/functions-debug.md | 461 -
.../version-2.8.2/functions-deploy.md | 230 -
.../version-2.8.2/functions-develop.md | 1332 -
.../version-2.8.2/functions-metrics.md | 7 -
.../version-2.8.2/functions-overview.md | 194 -
.../version-2.8.2/functions-package.md | 431 -
.../version-2.8.2/functions-runtime.md | 362 -
.../version-2.8.2/functions-worker.md | 332 -
.../version-2.8.2/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.8.2/getting-started-docker.md | 159 -
.../version-2.8.2/getting-started-helm.md | 363 -
.../version-2.8.2/getting-started-pulsar.md | 67 -
.../version-2.8.2/getting-started-standalone.md | 230 -
.../versioned_docs/version-2.8.2/helm-deploy.md | 379 -
.../versioned_docs/version-2.8.2/helm-install.md | 41 -
.../versioned_docs/version-2.8.2/helm-overview.md | 100 -
.../versioned_docs/version-2.8.2/helm-prepare.md | 85 -
.../versioned_docs/version-2.8.2/helm-tools.md | 43 -
.../versioned_docs/version-2.8.2/helm-upgrade.md | 34 -
.../version-2.8.2/io-aerospike-sink.md | 26 -
.../version-2.8.2/io-canal-source.md | 203 -
.../version-2.8.2/io-cassandra-sink.md | 54 -
.../version-2.8.2/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.8.2/io-cdc.md | 26 -
.../website/versioned_docs/version-2.8.2/io-cli.md | 606 -
.../versioned_docs/version-2.8.2/io-connectors.md | 232 -
.../version-2.8.2/io-debezium-source.md | 510 -
.../versioned_docs/version-2.8.2/io-debug.md | 329 -
.../versioned_docs/version-2.8.2/io-develop.md | 375 -
.../version-2.8.2/io-dynamodb-source.md | 76 -
.../version-2.8.2/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.8.2/io-file-source.md | 138 -
.../versioned_docs/version-2.8.2/io-flume-sink.md | 52 -
.../version-2.8.2/io-flume-source.md | 52 -
.../versioned_docs/version-2.8.2/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.8.2/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.8.2/io-hdfs3-sink.md | 54 -
.../version-2.8.2/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.8.2/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.8.2/io-kafka-sink.md | 69 -
.../version-2.8.2/io-kafka-source.md | 199 -
.../version-2.8.2/io-kinesis-sink.md | 73 -
.../version-2.8.2/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.8.2/io-mongo-sink.md | 51 -
.../version-2.8.2/io-netty-source.md | 205 -
.../versioned_docs/version-2.8.2/io-nsq-source.md | 21 -
.../versioned_docs/version-2.8.2/io-overview.md | 136 -
.../versioned_docs/version-2.8.2/io-quickstart.md | 816 -
.../version-2.8.2/io-rabbitmq-sink.md | 81 -
.../version-2.8.2/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.8.2/io-redis-sink.md | 70 -
.../versioned_docs/version-2.8.2/io-solr-sink.md | 61 -
.../version-2.8.2/io-twitter-source.md | 28 -
.../versioned_docs/version-2.8.2/io-twitter.md | 7 -
.../website/versioned_docs/version-2.8.2/io-use.md | 1505 --
.../version-2.8.2/performance-pulsar-perf.md | 205 -
.../version-2.8.2/reference-cli-tools.md | 812 -
.../version-2.8.2/reference-configuration.md | 793 -
.../version-2.8.2/reference-connector-admin.md | 11 -
.../version-2.8.2/reference-metrics.md | 568 -
.../version-2.8.2/reference-pulsar-admin.md | 2752 --
.../version-2.8.2/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 957 -
.../version-2.8.2/schema-get-started.md | 95 -
.../versioned_docs/version-2.8.2/schema-manage.md | 858 -
.../version-2.8.2/schema-understand.md | 651 -
.../version-2.8.2/security-athenz.md | 93 -
.../version-2.8.2/security-authorization.md | 115 -
.../version-2.8.2/security-bouncy-castle.md | 139 -
.../version-2.8.2/security-encryption.md | 280 -
.../version-2.8.2/security-extending.md | 196 -
.../versioned_docs/version-2.8.2/security-jwt.md | 264 -
.../version-2.8.2/security-kerberos.md | 391 -
.../version-2.8.2/security-oauth2.md | 207 -
.../version-2.8.2/security-overview.md | 35 -
.../version-2.8.2/security-tls-authentication.md | 188 -
.../version-2.8.2/security-tls-keystore.md | 302 -
.../version-2.8.2/security-tls-transport.md | 262 -
.../version-2.8.2/security-token-admin.md | 159 -
.../version-2.8.2/sql-deployment-configurations.md | 168 -
.../version-2.8.2/sql-getting-started.md | 171 -
.../versioned_docs/version-2.8.2/sql-overview.md | 18 -
.../versioned_docs/version-2.8.2/sql-rest-api.md | 186 -
.../version-2.8.2/tiered-storage-aliyun.md | 218 -
.../version-2.8.2/tiered-storage-aws.md | 280 -
.../version-2.8.2/tiered-storage-azure.md | 224 -
.../version-2.8.2/tiered-storage-filesystem.md | 524 -
.../version-2.8.2/tiered-storage-gcs.md | 274 -
.../version-2.8.2/tiered-storage-overview.md | 49 -
.../version-2.8.2/transaction-api.md | 149 -
.../version-2.8.2/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.8.2/txn-how.md | 319 -
.../versioned_docs/version-2.8.2/txn-monitor.md | 10 -
.../versioned_docs/version-2.8.2/txn-use.md | 125 -
.../versioned_docs/version-2.8.2/txn-what.md | 60 -
.../versioned_docs/version-2.8.2/txn-why.md | 45 -
.../version-2.8.2/window-functions-context.md | 529 -
.../versioned_docs/version-2.8.3/adaptors-kafka.md | 265 -
.../versioned_docs/version-2.8.3/adaptors-spark.md | 81 -
.../versioned_docs/version-2.8.3/adaptors-storm.md | 90 -
.../version-2.8.3/admin-api-brokers.md | 196 -
.../version-2.8.3/admin-api-clusters.md | 232 -
.../version-2.8.3/admin-api-functions.md | 589 -
.../version-2.8.3/admin-api-namespaces.md | 947 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.8.3/admin-api-overview.md | 121 -
.../version-2.8.3/admin-api-packages.md | 251 -
.../version-2.8.3/admin-api-partitioned-topics.md | 8 -
.../version-2.8.3/admin-api-permissions.md | 136 -
.../version-2.8.3/admin-api-persistent-topics.md | 8 -
.../version-2.8.3/admin-api-schemas.md | 7 -
.../version-2.8.3/admin-api-tenants.md | 167 -
.../version-2.8.3/admin-api-topics.md | 1515 --
.../version-2.8.3/administration-dashboard.md | 63 -
.../version-2.8.3/administration-geo.md | 197 -
.../version-2.8.3/administration-isolation.md | 85 -
.../version-2.8.3/administration-load-balance.md | 182 -
.../version-2.8.3/administration-proxy.md | 76 -
.../version-2.8.3/administration-pulsar-manager.md | 183 -
.../version-2.8.3/administration-stats.md | 64 -
.../version-2.8.3/administration-upgrade.md | 151 -
.../version-2.8.3/administration-zk-bk.md | 351 -
.../version-2.8.3/client-libraries-cgo.md | 545 -
.../version-2.8.3/client-libraries-cpp.md | 353 -
.../version-2.8.3/client-libraries-dotnet.md | 385 -
.../version-2.8.3/client-libraries-go.md | 829 -
.../version-2.8.3/client-libraries-java.md | 907 -
.../version-2.8.3/client-libraries-node.md | 598 -
.../version-2.8.3/client-libraries-python.md | 410 -
.../version-2.8.3/client-libraries-websocket.md | 592 -
.../concepts-architecture-overview.md | 162 -
.../version-2.8.3/concepts-authentication.md | 9 -
.../version-2.8.3/concepts-clients.md | 85 -
.../version-2.8.3/concepts-messaging.md | 605 -
.../version-2.8.3/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.8.3/concepts-overview.md | 31 -
.../version-2.8.3/concepts-proxy-sni-routing.md | 151 -
.../version-2.8.3/concepts-replication.md | 9 -
.../version-2.8.3/concepts-tiered-storage.md | 18 -
.../version-2.8.3/concepts-topic-compaction.md | 37 -
.../version-2.8.3/concepts-transactions.md | 30 -
.../version-2.8.3/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.8.3/cookbooks-compaction.md | 127 -
.../version-2.8.3/cookbooks-deduplication.md | 125 -
.../version-2.8.3/cookbooks-encryption.md | 170 -
.../version-2.8.3/cookbooks-message-queue.md | 118 -
.../version-2.8.3/cookbooks-non-persistent.md | 59 -
.../version-2.8.3/cookbooks-partitioned.md | 7 -
.../version-2.8.3/cookbooks-retention-expiry.md | 350 -
.../version-2.8.3/cookbooks-tiered-storage.md | 307 -
.../versioned_docs/version-2.8.3/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 431 -
.../version-2.8.3/deploy-bare-metal.md | 461 -
.../versioned_docs/version-2.8.3/deploy-dcos.md | 183 -
.../versioned_docs/version-2.8.3/deploy-docker.md | 52 -
.../version-2.8.3/deploy-kubernetes.md | 11 -
.../version-2.8.3/deploy-monitoring.md | 128 -
.../version-2.8.3/developing-binary-protocol.md | 580 -
.../version-2.8.3/developing-load-manager.md | 215 -
.../version-2.8.3/developing-tools.md | 105 -
.../versioned_docs/version-2.8.3/functions-cli.md | 198 -
.../version-2.8.3/functions-debug.md | 461 -
.../version-2.8.3/functions-deploy.md | 230 -
.../version-2.8.3/functions-develop.md | 1332 -
.../version-2.8.3/functions-metrics.md | 7 -
.../version-2.8.3/functions-overview.md | 194 -
.../version-2.8.3/functions-package.md | 431 -
.../version-2.8.3/functions-runtime.md | 362 -
.../version-2.8.3/functions-worker.md | 332 -
.../version-2.8.3/getting-started-clients.md | 35 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.8.3/getting-started-docker.md | 159 -
.../version-2.8.3/getting-started-helm.md | 363 -
.../version-2.8.3/getting-started-pulsar.md | 67 -
.../version-2.8.3/getting-started-standalone.md | 230 -
.../versioned_docs/version-2.8.3/helm-deploy.md | 379 -
.../versioned_docs/version-2.8.3/helm-install.md | 41 -
.../versioned_docs/version-2.8.3/helm-overview.md | 100 -
.../versioned_docs/version-2.8.3/helm-prepare.md | 85 -
.../versioned_docs/version-2.8.3/helm-tools.md | 43 -
.../versioned_docs/version-2.8.3/helm-upgrade.md | 34 -
.../version-2.8.3/io-aerospike-sink.md | 26 -
.../version-2.8.3/io-canal-source.md | 203 -
.../version-2.8.3/io-cassandra-sink.md | 54 -
.../version-2.8.3/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.8.3/io-cdc.md | 26 -
.../website/versioned_docs/version-2.8.3/io-cli.md | 606 -
.../versioned_docs/version-2.8.3/io-connectors.md | 232 -
.../version-2.8.3/io-debezium-source.md | 510 -
.../versioned_docs/version-2.8.3/io-debug.md | 329 -
.../versioned_docs/version-2.8.3/io-develop.md | 375 -
.../version-2.8.3/io-dynamodb-source.md | 76 -
.../version-2.8.3/io-elasticsearch-sink.md | 138 -
.../versioned_docs/version-2.8.3/io-file-source.md | 138 -
.../versioned_docs/version-2.8.3/io-flume-sink.md | 52 -
.../version-2.8.3/io-flume-source.md | 52 -
.../versioned_docs/version-2.8.3/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.8.3/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.8.3/io-hdfs3-sink.md | 54 -
.../version-2.8.3/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.8.3/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.8.3/io-kafka-sink.md | 69 -
.../version-2.8.3/io-kafka-source.md | 199 -
.../version-2.8.3/io-kinesis-sink.md | 73 -
.../version-2.8.3/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.8.3/io-mongo-sink.md | 51 -
.../version-2.8.3/io-netty-source.md | 205 -
.../versioned_docs/version-2.8.3/io-nsq-source.md | 21 -
.../versioned_docs/version-2.8.3/io-overview.md | 136 -
.../versioned_docs/version-2.8.3/io-quickstart.md | 816 -
.../version-2.8.3/io-rabbitmq-sink.md | 81 -
.../version-2.8.3/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.8.3/io-redis-sink.md | 70 -
.../versioned_docs/version-2.8.3/io-solr-sink.md | 61 -
.../version-2.8.3/io-twitter-source.md | 28 -
.../versioned_docs/version-2.8.3/io-twitter.md | 7 -
.../website/versioned_docs/version-2.8.3/io-use.md | 1505 --
.../version-2.8.3/performance-pulsar-perf.md | 205 -
.../version-2.8.3/reference-cli-tools.md | 812 -
.../version-2.8.3/reference-configuration.md | 793 -
.../version-2.8.3/reference-connector-admin.md | 11 -
.../version-2.8.3/reference-metrics.md | 568 -
.../version-2.8.3/reference-pulsar-admin.md | 2752 --
.../version-2.8.3/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 957 -
.../version-2.8.3/schema-get-started.md | 95 -
.../versioned_docs/version-2.8.3/schema-manage.md | 858 -
.../version-2.8.3/schema-understand.md | 651 -
.../version-2.8.3/security-athenz.md | 93 -
.../version-2.8.3/security-authorization.md | 101 -
.../version-2.8.3/security-bouncy-castle.md | 139 -
.../version-2.8.3/security-encryption.md | 285 -
.../version-2.8.3/security-extending.md | 196 -
.../versioned_docs/version-2.8.3/security-jwt.md | 264 -
.../version-2.8.3/security-kerberos.md | 391 -
.../version-2.8.3/security-oauth2.md | 207 -
.../version-2.8.3/security-overview.md | 35 -
.../version-2.8.3/security-tls-authentication.md | 188 -
.../version-2.8.3/security-tls-keystore.md | 302 -
.../version-2.8.3/security-tls-transport.md | 262 -
.../version-2.8.3/security-token-admin.md | 159 -
.../version-2.8.3/sql-deployment-configurations.md | 168 -
.../version-2.8.3/sql-getting-started.md | 171 -
.../versioned_docs/version-2.8.3/sql-overview.md | 18 -
.../versioned_docs/version-2.8.3/sql-rest-api.md | 186 -
.../version-2.8.3/tiered-storage-aliyun.md | 218 -
.../version-2.8.3/tiered-storage-aws.md | 280 -
.../version-2.8.3/tiered-storage-azure.md | 224 -
.../version-2.8.3/tiered-storage-filesystem.md | 524 -
.../version-2.8.3/tiered-storage-gcs.md | 274 -
.../version-2.8.3/tiered-storage-overview.md | 49 -
.../version-2.8.3/transaction-api.md | 149 -
.../version-2.8.3/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.8.3/txn-how.md | 319 -
.../versioned_docs/version-2.8.3/txn-monitor.md | 10 -
.../versioned_docs/version-2.8.3/txn-use.md | 125 -
.../versioned_docs/version-2.8.3/txn-what.md | 60 -
.../versioned_docs/version-2.8.3/txn-why.md | 45 -
.../version-2.8.3/window-functions-context.md | 529 -
.../versioned_docs/version-2.9.0/adaptors-kafka.md | 267 -
.../versioned_docs/version-2.9.0/adaptors-spark.md | 81 -
.../versioned_docs/version-2.9.0/adaptors-storm.md | 90 -
.../version-2.9.0/admin-api-brokers.md | 196 -
.../version-2.9.0/admin-api-clusters.md | 232 -
.../version-2.9.0/admin-api-functions.md | 589 -
.../version-2.9.0/admin-api-namespaces.md | 923 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.9.0/admin-api-overview.md | 121 -
.../version-2.9.0/admin-api-packages.md | 251 -
.../version-2.9.0/admin-api-partitioned-topics.md | 8 -
.../version-2.9.0/admin-api-permissions.md | 131 -
.../version-2.9.0/admin-api-persistent-topics.md | 8 -
.../version-2.9.0/admin-api-schemas.md | 7 -
.../version-2.9.0/admin-api-tenants.md | 167 -
.../version-2.9.0/admin-api-topics.md | 1701 --
.../version-2.9.0/administration-dashboard.md | 63 -
.../version-2.9.0/administration-geo.md | 196 -
.../version-2.9.0/administration-isolation.md | 85 -
.../version-2.9.0/administration-load-balance.md | 176 -
.../version-2.9.0/administration-proxy.md | 76 -
.../version-2.9.0/administration-pulsar-manager.md | 183 -
.../version-2.9.0/administration-stats.md | 64 -
.../version-2.9.0/administration-upgrade.md | 151 -
.../version-2.9.0/administration-zk-bk.md | 351 -
.../version-2.9.0/client-libraries-cgo.md | 545 -
.../version-2.9.0/client-libraries-cpp.md | 617 -
.../version-2.9.0/client-libraries-dotnet.md | 385 -
.../version-2.9.0/client-libraries-go.md | 829 -
.../version-2.9.0/client-libraries-java.md | 912 -
.../version-2.9.0/client-libraries-node.md | 598 -
.../version-2.9.0/client-libraries-python.md | 429 -
.../version-2.9.0/client-libraries-websocket.md | 599 -
.../concepts-architecture-overview.md | 162 -
.../version-2.9.0/concepts-authentication.md | 9 -
.../version-2.9.0/concepts-clients.md | 85 -
.../version-2.9.0/concepts-messaging.md | 609 -
.../version-2.9.0/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.9.0/concepts-overview.md | 31 -
.../version-2.9.0/concepts-proxy-sni-routing.md | 151 -
.../version-2.9.0/concepts-replication.md | 9 -
.../version-2.9.0/concepts-tiered-storage.md | 18 -
.../version-2.9.0/concepts-topic-compaction.md | 37 -
.../version-2.9.0/concepts-transactions.md | 30 -
.../version-2.9.0/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.9.0/cookbooks-compaction.md | 127 -
.../version-2.9.0/cookbooks-deduplication.md | 125 -
.../version-2.9.0/cookbooks-encryption.md | 170 -
.../version-2.9.0/cookbooks-message-queue.md | 118 -
.../version-2.9.0/cookbooks-non-persistent.md | 59 -
.../version-2.9.0/cookbooks-partitioned.md | 7 -
.../version-2.9.0/cookbooks-retention-expiry.md | 371 -
.../version-2.9.0/cookbooks-tiered-storage.md | 311 -
.../versioned_docs/version-2.9.0/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 399 -
.../version-2.9.0/deploy-bare-metal.md | 474 -
.../versioned_docs/version-2.9.0/deploy-dcos.md | 182 -
.../versioned_docs/version-2.9.0/deploy-docker.md | 52 -
.../version-2.9.0/deploy-kubernetes.md | 11 -
.../version-2.9.0/deploy-monitoring.md | 128 -
.../version-2.9.0/developing-binary-protocol.md | 580 -
.../version-2.9.0/developing-load-manager.md | 215 -
.../version-2.9.0/developing-tools.md | 106 -
.../versioned_docs/version-2.9.0/functions-cli.md | 198 -
.../version-2.9.0/functions-debug.md | 466 -
.../version-2.9.0/functions-deploy.md | 230 -
.../version-2.9.0/functions-develop.md | 1332 -
.../version-2.9.0/functions-metrics.md | 7 -
.../version-2.9.0/functions-overview.md | 194 -
.../version-2.9.0/functions-package.md | 431 -
.../version-2.9.0/functions-runtime.md | 366 -
.../version-2.9.0/functions-worker.md | 331 -
.../version-2.9.0/getting-started-clients.md | 36 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.9.0/getting-started-docker.md | 193 -
.../version-2.9.0/getting-started-helm.md | 363 -
.../version-2.9.0/getting-started-pulsar.md | 67 -
.../version-2.9.0/getting-started-standalone.md | 220 -
.../versioned_docs/version-2.9.0/helm-deploy.md | 379 -
.../versioned_docs/version-2.9.0/helm-install.md | 38 -
.../versioned_docs/version-2.9.0/helm-overview.md | 99 -
.../versioned_docs/version-2.9.0/helm-prepare.md | 73 -
.../versioned_docs/version-2.9.0/helm-tools.md | 43 -
.../versioned_docs/version-2.9.0/helm-upgrade.md | 34 -
.../version-2.9.0/io-aerospike-sink.md | 26 -
.../version-2.9.0/io-canal-source.md | 203 -
.../version-2.9.0/io-cassandra-sink.md | 54 -
.../version-2.9.0/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.9.0/io-cdc.md | 26 -
.../website/versioned_docs/version-2.9.0/io-cli.md | 606 -
.../versioned_docs/version-2.9.0/io-connectors.md | 249 -
.../version-2.9.0/io-debezium-source.md | 647 -
.../versioned_docs/version-2.9.0/io-debug.md | 329 -
.../versioned_docs/version-2.9.0/io-develop.md | 375 -
.../version-2.9.0/io-dynamodb-source.md | 76 -
.../version-2.9.0/io-elasticsearch-sink.md | 207 -
.../versioned_docs/version-2.9.0/io-file-source.md | 138 -
.../versioned_docs/version-2.9.0/io-flume-sink.md | 52 -
.../version-2.9.0/io-flume-source.md | 52 -
.../versioned_docs/version-2.9.0/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.9.0/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.9.0/io-hdfs3-sink.md | 54 -
.../version-2.9.0/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.9.0/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.9.0/io-kafka-sink.md | 69 -
.../version-2.9.0/io-kafka-source.md | 199 -
.../version-2.9.0/io-kinesis-sink.md | 73 -
.../version-2.9.0/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.9.0/io-mongo-sink.md | 51 -
.../version-2.9.0/io-netty-source.md | 205 -
.../versioned_docs/version-2.9.0/io-nsq-source.md | 21 -
.../versioned_docs/version-2.9.0/io-overview.md | 136 -
.../versioned_docs/version-2.9.0/io-quickstart.md | 816 -
.../version-2.9.0/io-rabbitmq-sink.md | 81 -
.../version-2.9.0/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.9.0/io-redis-sink.md | 136 -
.../versioned_docs/version-2.9.0/io-solr-sink.md | 61 -
.../version-2.9.0/io-twitter-source.md | 28 -
.../versioned_docs/version-2.9.0/io-twitter.md | 7 -
.../website/versioned_docs/version-2.9.0/io-use.md | 1505 --
.../version-2.9.0/performance-pulsar-perf.md | 207 -
.../version-2.9.0/reference-cli-tools.md | 801 -
.../version-2.9.0/reference-configuration.md | 775 -
.../version-2.9.0/reference-connector-admin.md | 12 -
.../version-2.9.0/reference-metrics.md | 560 -
.../version-2.9.0/reference-pulsar-admin.md | 2703 --
.../version-2.9.0/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.9.0/schema-get-started.md | 95 -
.../versioned_docs/version-2.9.0/schema-manage.md | 809 -
.../version-2.9.0/schema-understand.md | 670 -
.../version-2.9.0/security-athenz.md | 93 -
.../version-2.9.0/security-authorization.md | 115 -
.../version-2.9.0/security-bouncy-castle.md | 139 -
.../version-2.9.0/security-encryption.md | 185 -
.../version-2.9.0/security-extending.md | 196 -
.../versioned_docs/version-2.9.0/security-jwt.md | 264 -
.../version-2.9.0/security-kerberos.md | 391 -
.../version-2.9.0/security-oauth2.md | 207 -
.../version-2.9.0/security-overview.md | 35 -
.../version-2.9.0/security-tls-authentication.md | 188 -
.../version-2.9.0/security-tls-keystore.md | 300 -
.../version-2.9.0/security-tls-transport.md | 262 -
.../version-2.9.0/security-token-admin.md | 159 -
.../version-2.9.0/sql-deployment-configurations.md | 169 -
.../version-2.9.0/sql-getting-started.md | 171 -
.../versioned_docs/version-2.9.0/sql-overview.md | 18 -
.../versioned_docs/version-2.9.0/sql-rest-api.md | 186 -
.../version-2.9.0/tiered-storage-aliyun.md | 218 -
.../version-2.9.0/tiered-storage-aws.md | 280 -
.../version-2.9.0/tiered-storage-azure.md | 224 -
.../version-2.9.0/tiered-storage-filesystem.md | 269 -
.../version-2.9.0/tiered-storage-gcs.md | 274 -
.../version-2.9.0/tiered-storage-overview.md | 50 -
.../version-2.9.0/transaction-api.md | 149 -
.../version-2.9.0/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.9.0/txn-how.md | 319 -
.../versioned_docs/version-2.9.0/txn-monitor.md | 10 -
.../versioned_docs/version-2.9.0/txn-use.md | 125 -
.../versioned_docs/version-2.9.0/txn-what.md | 60 -
.../versioned_docs/version-2.9.0/txn-why.md | 45 -
.../version-2.9.0/window-functions-context.md | 529 -
.../versioned_docs/version-2.9.1/adaptors-kafka.md | 267 -
.../versioned_docs/version-2.9.1/adaptors-spark.md | 81 -
.../versioned_docs/version-2.9.1/adaptors-storm.md | 90 -
.../version-2.9.1/admin-api-brokers.md | 196 -
.../version-2.9.1/admin-api-clusters.md | 232 -
.../version-2.9.1/admin-api-functions.md | 589 -
.../version-2.9.1/admin-api-namespaces.md | 923 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.9.1/admin-api-overview.md | 121 -
.../version-2.9.1/admin-api-packages.md | 251 -
.../version-2.9.1/admin-api-partitioned-topics.md | 8 -
.../version-2.9.1/admin-api-permissions.md | 131 -
.../version-2.9.1/admin-api-persistent-topics.md | 8 -
.../version-2.9.1/admin-api-schemas.md | 7 -
.../version-2.9.1/admin-api-tenants.md | 167 -
.../version-2.9.1/admin-api-topics.md | 1701 --
.../version-2.9.1/administration-dashboard.md | 63 -
.../version-2.9.1/administration-geo.md | 220 -
.../version-2.9.1/administration-isolation.md | 85 -
.../version-2.9.1/administration-load-balance.md | 176 -
.../version-2.9.1/administration-proxy.md | 76 -
.../version-2.9.1/administration-pulsar-manager.md | 183 -
.../version-2.9.1/administration-stats.md | 64 -
.../version-2.9.1/administration-upgrade.md | 151 -
.../version-2.9.1/administration-zk-bk.md | 351 -
.../version-2.9.1/client-libraries-cgo.md | 545 -
.../version-2.9.1/client-libraries-cpp.md | 617 -
.../version-2.9.1/client-libraries-dotnet.md | 385 -
.../version-2.9.1/client-libraries-go.md | 829 -
.../version-2.9.1/client-libraries-java.md | 912 -
.../version-2.9.1/client-libraries-node.md | 598 -
.../version-2.9.1/client-libraries-python.md | 429 -
.../version-2.9.1/client-libraries-websocket.md | 597 -
.../concepts-architecture-overview.md | 162 -
.../version-2.9.1/concepts-authentication.md | 9 -
.../version-2.9.1/concepts-clients.md | 85 -
.../version-2.9.1/concepts-messaging.md | 609 -
.../version-2.9.1/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.9.1/concepts-overview.md | 31 -
.../version-2.9.1/concepts-proxy-sni-routing.md | 151 -
.../version-2.9.1/concepts-replication.md | 9 -
.../version-2.9.1/concepts-tiered-storage.md | 18 -
.../version-2.9.1/concepts-topic-compaction.md | 37 -
.../version-2.9.1/concepts-transactions.md | 30 -
.../version-2.9.1/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.9.1/cookbooks-compaction.md | 127 -
.../version-2.9.1/cookbooks-deduplication.md | 125 -
.../version-2.9.1/cookbooks-encryption.md | 170 -
.../version-2.9.1/cookbooks-message-queue.md | 118 -
.../version-2.9.1/cookbooks-non-persistent.md | 59 -
.../version-2.9.1/cookbooks-partitioned.md | 7 -
.../version-2.9.1/cookbooks-retention-expiry.md | 371 -
.../version-2.9.1/cookbooks-tiered-storage.md | 311 -
.../versioned_docs/version-2.9.1/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 399 -
.../version-2.9.1/deploy-bare-metal.md | 474 -
.../versioned_docs/version-2.9.1/deploy-dcos.md | 182 -
.../versioned_docs/version-2.9.1/deploy-docker.md | 52 -
.../version-2.9.1/deploy-kubernetes.md | 11 -
.../version-2.9.1/deploy-monitoring.md | 128 -
.../version-2.9.1/developing-binary-protocol.md | 580 -
.../version-2.9.1/developing-load-manager.md | 215 -
.../version-2.9.1/developing-tools.md | 106 -
.../versioned_docs/version-2.9.1/functions-cli.md | 198 -
.../version-2.9.1/functions-debug.md | 466 -
.../version-2.9.1/functions-deploy.md | 230 -
.../version-2.9.1/functions-develop.md | 1332 -
.../version-2.9.1/functions-metrics.md | 7 -
.../version-2.9.1/functions-overview.md | 194 -
.../version-2.9.1/functions-package.md | 431 -
.../version-2.9.1/functions-runtime.md | 366 -
.../version-2.9.1/functions-worker.md | 331 -
.../version-2.9.1/getting-started-clients.md | 36 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.9.1/getting-started-docker.md | 193 -
.../version-2.9.1/getting-started-helm.md | 363 -
.../version-2.9.1/getting-started-pulsar.md | 67 -
.../version-2.9.1/getting-started-standalone.md | 220 -
.../versioned_docs/version-2.9.1/helm-deploy.md | 379 -
.../versioned_docs/version-2.9.1/helm-install.md | 38 -
.../versioned_docs/version-2.9.1/helm-overview.md | 99 -
.../versioned_docs/version-2.9.1/helm-prepare.md | 73 -
.../versioned_docs/version-2.9.1/helm-tools.md | 43 -
.../versioned_docs/version-2.9.1/helm-upgrade.md | 34 -
.../version-2.9.1/io-aerospike-sink.md | 26 -
.../version-2.9.1/io-canal-source.md | 203 -
.../version-2.9.1/io-cassandra-sink.md | 54 -
.../version-2.9.1/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.9.1/io-cdc.md | 26 -
.../website/versioned_docs/version-2.9.1/io-cli.md | 606 -
.../versioned_docs/version-2.9.1/io-connectors.md | 249 -
.../version-2.9.1/io-debezium-source.md | 647 -
.../versioned_docs/version-2.9.1/io-debug.md | 329 -
.../versioned_docs/version-2.9.1/io-develop.md | 375 -
.../version-2.9.1/io-dynamodb-source.md | 76 -
.../version-2.9.1/io-elasticsearch-sink.md | 207 -
.../versioned_docs/version-2.9.1/io-file-source.md | 138 -
.../versioned_docs/version-2.9.1/io-flume-sink.md | 52 -
.../version-2.9.1/io-flume-source.md | 52 -
.../versioned_docs/version-2.9.1/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.9.1/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.9.1/io-hdfs3-sink.md | 54 -
.../version-2.9.1/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.9.1/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.9.1/io-kafka-sink.md | 69 -
.../version-2.9.1/io-kafka-source.md | 199 -
.../version-2.9.1/io-kinesis-sink.md | 73 -
.../version-2.9.1/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.9.1/io-mongo-sink.md | 51 -
.../version-2.9.1/io-netty-source.md | 205 -
.../versioned_docs/version-2.9.1/io-nsq-source.md | 21 -
.../versioned_docs/version-2.9.1/io-overview.md | 136 -
.../versioned_docs/version-2.9.1/io-quickstart.md | 816 -
.../version-2.9.1/io-rabbitmq-sink.md | 81 -
.../version-2.9.1/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.9.1/io-redis-sink.md | 136 -
.../versioned_docs/version-2.9.1/io-solr-sink.md | 61 -
.../version-2.9.1/io-twitter-source.md | 28 -
.../versioned_docs/version-2.9.1/io-twitter.md | 7 -
.../website/versioned_docs/version-2.9.1/io-use.md | 1505 --
.../version-2.9.1/performance-pulsar-perf.md | 207 -
.../version-2.9.1/reference-cli-tools.md | 801 -
.../version-2.9.1/reference-configuration.md | 775 -
.../version-2.9.1/reference-connector-admin.md | 12 -
.../version-2.9.1/reference-metrics.md | 560 -
.../version-2.9.1/reference-pulsar-admin.md | 2703 --
.../version-2.9.1/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.9.1/schema-get-started.md | 95 -
.../versioned_docs/version-2.9.1/schema-manage.md | 809 -
.../version-2.9.1/schema-understand.md | 670 -
.../version-2.9.1/security-athenz.md | 93 -
.../version-2.9.1/security-authorization.md | 115 -
.../version-2.9.1/security-bouncy-castle.md | 139 -
.../version-2.9.1/security-encryption.md | 185 -
.../version-2.9.1/security-extending.md | 196 -
.../versioned_docs/version-2.9.1/security-jwt.md | 264 -
.../version-2.9.1/security-kerberos.md | 391 -
.../version-2.9.1/security-oauth2.md | 207 -
.../version-2.9.1/security-overview.md | 35 -
.../version-2.9.1/security-tls-authentication.md | 188 -
.../version-2.9.1/security-tls-keystore.md | 300 -
.../version-2.9.1/security-tls-transport.md | 262 -
.../version-2.9.1/security-token-admin.md | 159 -
.../version-2.9.1/sql-deployment-configurations.md | 169 -
.../version-2.9.1/sql-getting-started.md | 171 -
.../versioned_docs/version-2.9.1/sql-overview.md | 18 -
.../versioned_docs/version-2.9.1/sql-rest-api.md | 186 -
.../version-2.9.1/tiered-storage-aliyun.md | 218 -
.../version-2.9.1/tiered-storage-aws.md | 280 -
.../version-2.9.1/tiered-storage-azure.md | 224 -
.../version-2.9.1/tiered-storage-filesystem.md | 269 -
.../version-2.9.1/tiered-storage-gcs.md | 274 -
.../version-2.9.1/tiered-storage-overview.md | 50 -
.../version-2.9.1/transaction-api.md | 149 -
.../version-2.9.1/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.9.1/txn-how.md | 319 -
.../versioned_docs/version-2.9.1/txn-monitor.md | 10 -
.../versioned_docs/version-2.9.1/txn-use.md | 125 -
.../versioned_docs/version-2.9.1/txn-what.md | 60 -
.../versioned_docs/version-2.9.1/txn-why.md | 45 -
.../version-2.9.1/window-functions-context.md | 529 -
.../versioned_docs/version-2.9.2/adaptors-kafka.md | 267 -
.../versioned_docs/version-2.9.2/adaptors-spark.md | 81 -
.../versioned_docs/version-2.9.2/adaptors-storm.md | 90 -
.../version-2.9.2/admin-api-brokers.md | 196 -
.../version-2.9.2/admin-api-clusters.md | 232 -
.../version-2.9.2/admin-api-functions.md | 589 -
.../version-2.9.2/admin-api-namespaces.md | 923 -
.../admin-api-non-partitioned-topics.md | 8 -
.../admin-api-non-persistent-topics.md | 8 -
.../version-2.9.2/admin-api-overview.md | 121 -
.../version-2.9.2/admin-api-packages.md | 251 -
.../version-2.9.2/admin-api-partitioned-topics.md | 8 -
.../version-2.9.2/admin-api-permissions.md | 131 -
.../version-2.9.2/admin-api-persistent-topics.md | 8 -
.../version-2.9.2/admin-api-schemas.md | 7 -
.../version-2.9.2/admin-api-tenants.md | 167 -
.../version-2.9.2/admin-api-topics.md | 1701 --
.../version-2.9.2/administration-dashboard.md | 63 -
.../version-2.9.2/administration-geo.md | 220 -
.../version-2.9.2/administration-isolation.md | 85 -
.../version-2.9.2/administration-load-balance.md | 176 -
.../version-2.9.2/administration-proxy.md | 76 -
.../version-2.9.2/administration-pulsar-manager.md | 183 -
.../version-2.9.2/administration-stats.md | 64 -
.../version-2.9.2/administration-upgrade.md | 151 -
.../version-2.9.2/administration-zk-bk.md | 351 -
.../version-2.9.2/client-libraries-cgo.md | 545 -
.../version-2.9.2/client-libraries-cpp.md | 617 -
.../version-2.9.2/client-libraries-dotnet.md | 385 -
.../version-2.9.2/client-libraries-go.md | 829 -
.../version-2.9.2/client-libraries-java.md | 912 -
.../version-2.9.2/client-libraries-node.md | 598 -
.../version-2.9.2/client-libraries-python.md | 429 -
.../version-2.9.2/client-libraries-websocket.md | 597 -
.../concepts-architecture-overview.md | 162 -
.../version-2.9.2/concepts-authentication.md | 9 -
.../version-2.9.2/concepts-clients.md | 85 -
.../version-2.9.2/concepts-messaging.md | 609 -
.../version-2.9.2/concepts-multi-tenancy.md | 55 -
.../concepts-multiple-advertised-listeners.md | 39 -
.../version-2.9.2/concepts-overview.md | 31 -
.../version-2.9.2/concepts-proxy-sni-routing.md | 151 -
.../version-2.9.2/concepts-replication.md | 9 -
.../version-2.9.2/concepts-tiered-storage.md | 18 -
.../version-2.9.2/concepts-topic-compaction.md | 37 -
.../version-2.9.2/concepts-transactions.md | 30 -
.../version-2.9.2/cookbooks-bookkeepermetadata.md | 21 -
.../version-2.9.2/cookbooks-compaction.md | 127 -
.../version-2.9.2/cookbooks-deduplication.md | 125 -
.../version-2.9.2/cookbooks-encryption.md | 170 -
.../version-2.9.2/cookbooks-message-queue.md | 118 -
.../version-2.9.2/cookbooks-non-persistent.md | 59 -
.../version-2.9.2/cookbooks-partitioned.md | 7 -
.../version-2.9.2/cookbooks-retention-expiry.md | 371 -
.../version-2.9.2/cookbooks-tiered-storage.md | 311 -
.../versioned_docs/version-2.9.2/deploy-aws.md | 227 -
.../deploy-bare-metal-multi-cluster.md | 399 -
.../version-2.9.2/deploy-bare-metal.md | 474 -
.../versioned_docs/version-2.9.2/deploy-dcos.md | 182 -
.../versioned_docs/version-2.9.2/deploy-docker.md | 52 -
.../version-2.9.2/deploy-kubernetes.md | 11 -
.../version-2.9.2/deploy-monitoring.md | 128 -
.../version-2.9.2/developing-binary-protocol.md | 580 -
.../version-2.9.2/developing-load-manager.md | 215 -
.../version-2.9.2/developing-tools.md | 106 -
.../versioned_docs/version-2.9.2/functions-cli.md | 198 -
.../version-2.9.2/functions-debug.md | 466 -
.../version-2.9.2/functions-deploy.md | 230 -
.../version-2.9.2/functions-develop.md | 1332 -
.../version-2.9.2/functions-metrics.md | 7 -
.../version-2.9.2/functions-overview.md | 194 -
.../version-2.9.2/functions-package.md | 431 -
.../version-2.9.2/functions-runtime.md | 366 -
.../version-2.9.2/functions-worker.md | 331 -
.../version-2.9.2/getting-started-clients.md | 36 -
.../getting-started-concepts-and-architecture.md | 16 -
.../version-2.9.2/getting-started-docker.md | 193 -
.../version-2.9.2/getting-started-helm.md | 363 -
.../version-2.9.2/getting-started-pulsar.md | 67 -
.../version-2.9.2/getting-started-standalone.md | 220 -
.../versioned_docs/version-2.9.2/helm-deploy.md | 379 -
.../versioned_docs/version-2.9.2/helm-install.md | 38 -
.../versioned_docs/version-2.9.2/helm-overview.md | 99 -
.../versioned_docs/version-2.9.2/helm-prepare.md | 73 -
.../versioned_docs/version-2.9.2/helm-tools.md | 43 -
.../versioned_docs/version-2.9.2/helm-upgrade.md | 34 -
.../version-2.9.2/io-aerospike-sink.md | 26 -
.../version-2.9.2/io-canal-source.md | 203 -
.../version-2.9.2/io-cassandra-sink.md | 54 -
.../version-2.9.2/io-cdc-debezium.md | 475 -
.../website/versioned_docs/version-2.9.2/io-cdc.md | 26 -
.../website/versioned_docs/version-2.9.2/io-cli.md | 606 -
.../versioned_docs/version-2.9.2/io-connectors.md | 249 -
.../version-2.9.2/io-debezium-source.md | 647 -
.../versioned_docs/version-2.9.2/io-debug.md | 329 -
.../versioned_docs/version-2.9.2/io-develop.md | 375 -
.../version-2.9.2/io-dynamodb-source.md | 76 -
.../version-2.9.2/io-elasticsearch-sink.md | 207 -
.../versioned_docs/version-2.9.2/io-file-source.md | 138 -
.../versioned_docs/version-2.9.2/io-flume-sink.md | 52 -
.../version-2.9.2/io-flume-source.md | 52 -
.../versioned_docs/version-2.9.2/io-hbase-sink.md | 64 -
.../versioned_docs/version-2.9.2/io-hdfs2-sink.md | 59 -
.../versioned_docs/version-2.9.2/io-hdfs3-sink.md | 54 -
.../version-2.9.2/io-influxdb-sink.md | 106 -
.../versioned_docs/version-2.9.2/io-jdbc-sink.md | 140 -
.../versioned_docs/version-2.9.2/io-kafka-sink.md | 69 -
.../version-2.9.2/io-kafka-source.md | 211 -
.../version-2.9.2/io-kinesis-sink.md | 73 -
.../version-2.9.2/io-kinesis-source.md | 77 -
.../versioned_docs/version-2.9.2/io-mongo-sink.md | 51 -
.../version-2.9.2/io-netty-source.md | 205 -
.../versioned_docs/version-2.9.2/io-nsq-source.md | 21 -
.../versioned_docs/version-2.9.2/io-overview.md | 136 -
.../versioned_docs/version-2.9.2/io-quickstart.md | 816 -
.../version-2.9.2/io-rabbitmq-sink.md | 81 -
.../version-2.9.2/io-rabbitmq-source.md | 81 -
.../versioned_docs/version-2.9.2/io-redis-sink.md | 136 -
.../versioned_docs/version-2.9.2/io-solr-sink.md | 61 -
.../version-2.9.2/io-twitter-source.md | 28 -
.../versioned_docs/version-2.9.2/io-twitter.md | 7 -
.../website/versioned_docs/version-2.9.2/io-use.md | 1505 --
.../version-2.9.2/performance-pulsar-perf.md | 207 -
.../version-2.9.2/reference-cli-tools.md | 801 -
.../version-2.9.2/reference-configuration.md | 775 -
.../version-2.9.2/reference-connector-admin.md | 12 -
.../version-2.9.2/reference-metrics.md | 560 -
.../version-2.9.2/reference-pulsar-admin.md | 2703 --
.../version-2.9.2/reference-terminology.md | 168 -
.../schema-evolution-compatibility.md | 953 -
.../version-2.9.2/schema-get-started.md | 95 -
.../versioned_docs/version-2.9.2/schema-manage.md | 809 -
.../version-2.9.2/schema-understand.md | 670 -
.../version-2.9.2/security-athenz.md | 93 -
.../version-2.9.2/security-authorization.md | 115 -
.../version-2.9.2/security-bouncy-castle.md | 139 -
.../version-2.9.2/security-encryption.md | 185 -
.../version-2.9.2/security-extending.md | 196 -
.../versioned_docs/version-2.9.2/security-jwt.md | 264 -
.../version-2.9.2/security-kerberos.md | 391 -
.../version-2.9.2/security-oauth2.md | 207 -
.../version-2.9.2/security-overview.md | 35 -
.../version-2.9.2/security-tls-authentication.md | 188 -
.../version-2.9.2/security-tls-keystore.md | 300 -
.../version-2.9.2/security-tls-transport.md | 262 -
.../version-2.9.2/security-token-admin.md | 159 -
.../version-2.9.2/sql-deployment-configurations.md | 169 -
.../version-2.9.2/sql-getting-started.md | 171 -
.../versioned_docs/version-2.9.2/sql-overview.md | 18 -
.../versioned_docs/version-2.9.2/sql-rest-api.md | 186 -
.../version-2.9.2/tiered-storage-aliyun.md | 218 -
.../version-2.9.2/tiered-storage-aws.md | 280 -
.../version-2.9.2/tiered-storage-azure.md | 224 -
.../version-2.9.2/tiered-storage-filesystem.md | 269 -
.../version-2.9.2/tiered-storage-gcs.md | 274 -
.../version-2.9.2/tiered-storage-overview.md | 50 -
.../version-2.9.2/transaction-api.md | 149 -
.../version-2.9.2/transaction-guarantee.md | 17 -
.../versioned_docs/version-2.9.2/txn-how.md | 319 -
.../versioned_docs/version-2.9.2/txn-monitor.md | 10 -
.../versioned_docs/version-2.9.2/txn-use.md | 125 -
.../versioned_docs/version-2.9.2/txn-what.md | 60 -
.../versioned_docs/version-2.9.2/txn-why.md | 45 -
.../version-2.9.2/window-functions-context.md | 529 -
.../version-2.1.0-incubating-sidebars.json | 115 -
.../version-2.1.1-incubating-sidebars.json | 115 -
.../version-2.10.0-sidebars.json | 169 -
.../versioned_sidebars/version-2.2.0-sidebars.json | 120 -
.../versioned_sidebars/version-2.2.1-sidebars.json | 120 -
.../versioned_sidebars/version-2.3.0-sidebars.json | 125 -
.../versioned_sidebars/version-2.3.1-sidebars.json | 125 -
.../versioned_sidebars/version-2.3.2-sidebars.json | 127 -
.../versioned_sidebars/version-2.4.0-sidebars.json | 130 -
.../versioned_sidebars/version-2.4.1-sidebars.json | 143 -
.../versioned_sidebars/version-2.4.2-sidebars.json | 143 -
.../versioned_sidebars/version-2.5.0-sidebars.json | 146 -
.../versioned_sidebars/version-2.5.1-sidebars.json | 147 -
.../versioned_sidebars/version-2.5.2-sidebars.json | 147 -
.../versioned_sidebars/version-2.6.0-sidebars.json | 153 -
.../versioned_sidebars/version-2.6.1-sidebars.json | 155 -
.../versioned_sidebars/version-2.6.2-sidebars.json | 155 -
.../versioned_sidebars/version-2.6.3-sidebars.json | 155 -
.../versioned_sidebars/version-2.6.4-sidebars.json | 154 -
.../versioned_sidebars/version-2.7.0-sidebars.json | 162 -
.../versioned_sidebars/version-2.7.1-sidebars.json | 162 -
.../versioned_sidebars/version-2.7.2-sidebars.json | 162 -
.../versioned_sidebars/version-2.7.3-sidebars.json | 162 -
.../versioned_sidebars/version-2.7.4-sidebars.json | 162 -
.../versioned_sidebars/version-2.8.0-sidebars.json | 165 -
.../versioned_sidebars/version-2.8.1-sidebars.json | 165 -
.../versioned_sidebars/version-2.8.2-sidebars.json | 165 -
.../versioned_sidebars/version-2.8.3-sidebars.json | 165 -
.../versioned_sidebars/version-2.9.0-sidebars.json | 165 -
.../versioned_sidebars/version-2.9.1-sidebars.json | 165 -
.../versioned_sidebars/version-2.9.2-sidebars.json | 165 -
site2/website/versions.json | 33 -
4108 files changed, 1702455 deletions(-)
diff --git a/.github/workflows/ci-pulsar-website-build.yaml b/.github/workflows/ci-pulsar-website-build.yaml
deleted file mode 100644
index 89d87764b85..00000000000
--- a/.github/workflows/ci-pulsar-website-build.yaml
+++ /dev/null
@@ -1,99 +0,0 @@
-#
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements. See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership. The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License. You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied. See the License for the
-# specific language governing permissions and limitations
-# under the License.
-#
-
-name: CI - Pulsar Website build
-on:
- push:
- branches: [main]
-
-
-env:
- MAVEN_OPTS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.http.retryHandler.class=standard -Dmaven.wagon.http.retryHandler.count=3
-
-jobs:
- build-website:
- if: ${{ github.repository == 'apache/pulsar-site' }}
- name: Build and publish pulsar website
- runs-on: ubuntu-latest
- timeout-minutes: 180
- steps:
- - name: checkout
- uses: actions/checkout@v2
-
- - name: Tune Runner VM
- uses: ./.github/actions/tune-runner-vm
-
- - name: Cache local Maven repository
- uses: actions/cache@v2
- with:
- path: |
- ~/.m2/repository/*/*/*
- !~/.m2/repository/org/apache/pulsar
- key: ${{ runner.os }}-m2-dependencies-website-${{ hashFiles('**/pom.xml') }}
- restore-keys: |
- ${{ runner.os }}-m2-dependencies-all-${{ hashFiles('**/pom.xml') }}
- ${{ runner.os }}-m2-dependencies-core-modules-${{ hashFiles('**/pom.xml') }}
- ${{ runner.os }}-m2-dependencies-core-modules-
-
- - name: Set up JDK 17
- uses: actions/setup-java@v2
- with:
- distribution: 'temurin'
- java-version: 17
-
- - name: Clean disk
- run: |
- sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc
- sudo apt clean
- docker rmi $(docker images -q) -f
- df -h
-
- - name: Clone Pulsar
- env:
- GH_TOKEN: ${{ secrets.PULSARBOT_TOKEN }}
- CROWDIN_DOCUSAURUS_API_KEY: ${{ secrets.PULSAR_CROWDIN_DOCUSAURUS_API_KEY }}
- run: |
- cd ../
- git clone -b master --depth 1 https://github.com/apache/pulsar.git
- rm -rf pulsar/.git
- rm -rf pulsar/site2
- mv pulsar/* pulsar-site/
-
- - name: Run install by skip tests
- run: mvn -q -B -ntp install -Pcore-modules,-main -DskipTests -DskipSourceReleaseAssembly=true -Dspotbugs.skip=true -Dlicense.skip=true
-
- - name: Generate swagger json file
- run: mvn -B -ntp -pl pulsar-broker install -DskipTests -Pswagger
-
- - name: Publish
- env:
- GH_TOKEN: ${{ secrets.PULSARBOT_TOKEN }}
- CROWDIN_DOCUSAURUS_API_KEY: ${{ secrets.PULSAR_CROWDIN_DOCUSAURUS_API_KEY }}
- run: |
- export CROWDIN_DOCUSAURUS_PROJECT_ID=apache-pulsar
- echo "Copying swagger json file ..."
- mkdir -p site2/website/static/swagger/master/
- cp pulsar-broker/target/docs/swagger*.json site2/website/static/swagger/master
- echo "Copied swagger json file."
- echo "Building Website"
- # Build the new website
- site2/tools/docker-build-site.sh
-
- # # Script was initially made for travis
- bash -e site2/tools/publish-website.sh
diff --git a/site2/website/README.md b/site2/website/README.md
deleted file mode 100644
index a99d2db967c..00000000000
--- a/site2/website/README.md
+++ /dev/null
@@ -1,337 +0,0 @@
-# Pulsar website and documentation
-
-Pulsar website is comprised of two parts: website pages (including blog posts) and documentation.
-
-You can run the website locally to test your updates. The documentation is written in English, and we also encourage contributions in different languages.
-
-
-## Website
-
-Pulsar website framework adopts [Docusaurus](https://docusaurus.io/). Website pages are non-versioned. They are placed in the `/site2/website` directory. Ensure that you have installed the latest version of [Node](https://nodejs.org/en/download/) and [Yarn](https://yarnpkg.com/en/docs/install) before running the site locally.
-
-> You have to be on Node >= 8.x and Yarn >= 1.5.
-
-### Run the site locally
-
-To run the site locally, enter the following commands.
-
-```bash
-git clone https://github.com/apache/pulsar.git
-cd pulsar/site2/website
-yarn install
-yarn start
-```
-> Notes
->
-> 1. If you have installed `yarn`, you can skip the `yarn install` command.
-> 2. After you enter the `yarn start` command, you will be navigated to a local address, for example, `http://localhost:3000`. Click `Docs` to see documentation for the latest release of Pulsar.
-> 3. The `http://localhost:3000/en/versions` path shows the documentation for all versions. To view your local changes, click `Documentation` in **Latest Version**, or enter `http://localhost:3000/docs/en/next/standalone` in a browser.
-
-### Tests
-
-To run tests locally, enter the following commands
-```bash
-cd pulsar/site2/website
-yarn test
-```
-
-### Check
-
-Before submitting a pull request, run the following command to make sure no broken links exist.
-
-```
-cd pulsar/site2/website
-yarn build
-```
-
-If warning messages are shown as below, it means broken links exist.
-
-```
-[WARN] unresolved links in file 'version-2.4.1/getting-started-standalone.md' > [ 'security-overview.md' ]
-
-[WARN] unresolved links in file 'version-2.4.0/io-managing.md' > [ 'functions-overview.md' ]
-```
-
-Fix the broken links manually and then send a pull request.
-
-Besides, you can use an automatic checker tool to crawl through the Pulsar website and identify dead links, for example, [Dr. Link Checker](https://www.drlinkcheck.com/).
-
-## Documentation
-
-This is the **Pulsar Document Development Life Cycle** (DDLC). It is essential for developing a document to enhance the precision and understandability for users. In general, documentation contributors involve themselves in the following phases.
-
-
-
-Pulsar documents are written in English. Documentation related pages are placed in the `/site2/docs` directory. All documentation pages are versioned. For more details, refer to [versioning](#versioning).
-
-### Contribute to documentation
-
-We welcome contributions to help improve Pulsar documentation. The documents are written in [Markdown](http://daringfireball.net/projects/markdown/syntax) and follow [Google Developer Documentation Style Guide](https://developers.google.com/style/). If you are not familiar with the writing styles, we are happy to guide you along the way.
-
-For workflow on how to contribute to Pulsar, refer to [contribution](http://pulsar.apache.org/en/contributing/) guidelines.
-
-To learn more about Pulsar documents, read the following instructions.
-
-### Layout
-
-The markdown files placed in the `docs` directory adopt a flat structure.
-
-```
-├── docs
-│ ├── adaptors-kafka.md
-│ ├── adaptors-spark.md
-│ ├── adaptors-storm.md
-│ ├── admin-api-brokers.md
-│ ├── admin-api-clusters.md
-│ ├── admin-api-namespaces.md
-│ ├── admin-api-overview.md
-│ ├── admin-api-permissions.md
-│ ├── admin-api-topics.md
-│ ├── admin-api-tenants.md
-│ ├── administration-dashboard.md
-│ ├── administration-geo.md
-│ ├── administration-load-distribution.md
-│ ├── administration-proxy.md
-...
-```
-
-All the files are named in the following convention:
-
-```
-<category>-<page-name>.md
-```
-
-`<category>` is the category within the sidebar that this file belongs to, while `<page-name>` is the string to name the file within this category.
-
-### Markdown Headers
-
-All the documents are usual Markdown files. However you need to add some Docusaurus-specific fields in Markdown headers in order to link them correctly to the [Sidebar](#sidebar) and [Navigation Bar](#navigation).
-
-`id`: A unique document ID. If this field is not specified, the document ID defaults to its file name (without the extension).
-
-`title`: The title of the document. If this field is not specified, the document title defaults to its id.
-
-`hide_title`: Whether to hide the title at the top of the doc.
-
-`sidebar_label`: The text shown in the document sidebar for this document. If this field is not specified, the document `sidebar_label` defaults to its title.
-
-For example:
-
-```bash
----
-id: io-overview
-title: Pulsar IO Overview
-sidebar_label: Overview
----
-```
-
-### Link to another document
-
-To link to other documentation files, you can use relative URLs, which will be automatically converted to the corresponding HTML links when they are rendered.
-
-Example:
-
-```md
-[This links to another document](other-document.md)
-```
-
-The markdown file will be automatically converted into a link to /docs/other-document.html (or the appropriately translated/versioned link) once it is rendered.
-
-This helps when you want to navigate through docs on GitHub since the links there are functional links to other documents (still on GitHub), and the documents have the correct HTML links when they are rendered.
-
-### Link to javadoc of Pulsar class
-
-We have a [remarkable plugin](https://github.com/jonschlinkert/remarkable) to generate links to the javadoc for Pulsar classes.
-You can write them in the following syntax:
-
-```shell
-{@inject: javadoc:<Display Name>:<Relative-Path-To-Javadoc-Html-File>}
-```
-
-For example, the following line generates a hyperlink to the javadoc of `PulsarAdmin` class.
-
-```shell
-{@inject: javadoc:PulsarAdmin:/admin/org/apache/pulsar/client/admin/PulsarAdmin.html}
-```
-
-### Link to files in Pulsar GitHub repository
-
-We use the same [remarkable plugin](https://github.com/jonschlinkert/remarkable) to generate links to files in Pulsar GitHub repository.
-
-You can write it using similar syntax:
-
-```shell
-{@inject: github:<Display Text>:<Relative-Path-To-Files>}
-```
-
-For example, the following line generates a hyperlink to the dashboard Dockerfile.
-
-```
-{@inject: github:`Dockerfile`:/dashboard/Dockerfile}
-```
-
-For more details about markdown features, read [here](https://docusaurus.io/docs/en/doc-markdown).
-
-### Sidebar
-
-All the sidebars are defined in a `sidebars.json` file in the `website` directory. The documentation sidebar is named `docs` in the JSON structure.
-
-When you want to add a page to sidebar, you can add the document `id` you used in the document header to the existing sidebar/category. In the example below,
-`docs` is the name of the sidebar, "Getting started" is a category within the sidebar, and "pulsar-2.0" is the `id` of a document.
-
-```bash
-{
- "docs": {
- "Getting started": [
- "pulsar-2.0",
- "standalone",
- "standalone-docker",
- "client-libraries",
- "concepts-architecture"
- ],
- ...
- }
-}
-```
-
-### Navigation
-
-To add links to the top navigation bar, you can add entries to the `headerLinks` of `siteConfig.js` under `website` directory.
-
-To learn different types of links you can add to the top navigation bar, refer to [Navigation and Sidebars](https://docusaurus.io/docs/en/navigation).
-
-### Versioning
-
-Documentation versioning with Docusaurus becomes simpler. When done with a new release, just simply run the following command.
-
-```shell
-yarn run version ${version}
-```
-
-This preserves all markdown files in the `docs` directory and make them available as documentation for version `${version}`.
-Versioned documents are placed into `website/versioned_docs/version-${version}`, where `${version}` is the version number
-you supplied in the command above.
-
-Versioned sidebars are also copied into `website/versioned_sidebars` and are named as `version-${version}-sidebars.json`.
-
-If you want to change the documentation for a previous version, you can access files for that respective version.
-
-For more details about versioning, refer to [Versioning](https://docusaurus.io/docs/en/versioning).
-
-## C++ client API doc
-
-You can use the C++ client API to connect to a Pulsar cluster and handles data. [Pulsar C++ client API doc](https://pulsar.apache.org/api/cpp/https://pulsar.apache.org/api/cpp/) provides extensive implementation details and usage conventions for the C++ client.
-
-If you want to modify the C++ client API doc, follow the steps below.
-
-**Prerequisite**
-
-- [Doxygen](http://www.doxygen.nl/)
-
- Pulsar uses [Doxygen](http://www.doxygen.nl/) to generate the C++ client API doc. Before submitting doc changes, you need to preview the docs using Doxygen.
-
- 1. Install Doxygen.
-
- Go to the directory `pulsar/pulsar-client-cpp` and run the command `brew install doxygen` (MacOS).
-
- 2. Create a folder for the generated HTML files.
-
- Go to the directory `pulsar` and run the command `mkdir -p ../target/doxygen`.
-
-- [clang-format](https://www.electronjs.org/docs/development/clang-format#:~:text=clang%2Dformat%20is%20a%20tool,style%20issues%20during%20code%20reviews)
-
- Long code lines might cause C++ API tests to fail. Consequently, before submitting doc changes, you can break long lines of code automatically using `clang-format`.
-
- To install clang-format, go to the directory `pulsar` and run the command `brew install clang-format` (MacOS).
-
-**Step**
-
-1. Modify your desired code file.
-
- All C++ API code files are stored at [here](https://github.com/apache/pulsar/tree/master/pulsar-client-cpp/include/pulsar).
-
- > #### Tip
- >
- > - Each class has its corresponding `h` file. For example, if you want to update the [ProducerConfiguration class](https://pulsar.apache.org/api/cpp/classpulsar_1_1_producer_configuration.html), you need to modify the file [ProducerConfiguration.h](https://github.com/apache/pulsar/blob/master/pulsar-client-cpp/include/pulsar/ProducerConfiguration.h).
- >
- > - If you want to update descriptions for member functions, you can take [Pulsar Java API doc](https://github.com/apache/pulsar/tree/master/pulsar-client-api/src/main/java/org/apache/pulsar/client/api) as references.
-
-2. Format the code file.
-
- Go to the directory `pulsar/pulsar-client-cpp` and run the command `clang-format -i include/pulsar/<your-file-name>`.
-
- Check your file to make sure that the long lines are broken into short lines.
-
-3. Preview the code changes.
-
- Go to the directory `pulsar/pulsar-client-cpp` and run the command `doxygen`.
-
- All HTML files are stored at the folder `pulsar/target/doxygen/html`. Check your file to make sure that all changes take effect.
-
-4. Submit your doc PR.
-
- [Here](https://github.com/apache/pulsar/pull/9822) is an example.
-
-## Translation and localization
-
-Docusaurus makes it easy to use translation functionality using [Crowdin](https://crowdin.com/).
-All the markdown files are written in English. These markdown files are uploaded to Crowdin for translation by users within a community. Top-level pages are also written in English.
-The strings that are needed to be translated are wrapped in a `<translate>` tag.
-
-[Pulsar Website Build](https://builds.apache.org/job/pulsar-website-build/) pulls down and uploads translation for all the Pulsar website documentation files automatically. Once it pulls down translation from Crowdin, it will build the translation into the website.
-
-### Contribute translation
-
-Translation is stored and managed in the [Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar).
-To contribute translation, you can simply create a Crowdin account, join the project and make contributions.
-Crowdin provides very good documentation for translators. You can read [Crowdin Knowledge Base](https://support.crowdin.com/crowdin-intro/) before contributing.
-
-Translation you contribute is licensed under [Apache License V2](https://www.apache.org/licenses/LICENSE-2.0).
-Pulsar Committers will review translation. If your translation is not reviewed or approved by any committer, feel free to reach out via [slack channel](https://apache-pulsar.herokuapp.com/) or [mailing lists](https://pulsar.apache.org/contact/).
-
-### Download translated docs
-
-When you find display issues on the translated pages, you can download the translated docs from Crowdin, and follow the instructions below to debug and fix issues.
-
-1. Install Java (optional)
-If you have installed Java, skip this step. If you have not installed [Java](https://java.com/en/), install the latest version.
-If you are using Mac OS, you can use the following command to install Java:
-
-```
-brew cask install java
-```
-
-2. Install Crowdin CLI
-
-To download the translated markdown files, you need to install [Crowdin CLI](https://support.crowdin.com/cli-tool/#installation).
-
-3. Set environment variables
-
-You need to set the following environment variables:
-
-```
-export CROWDIN_DOCUSAURUS_PROJECT_ID="apache-pulsar"
-export CROWDIN_DOCUSAURUS_API_KEY=<crowdin-pulsar-api-key>
-```
-
-You can find the API Key of Pulsar Crowdin project [here](https://crowdin.com/project/apache-pulsar/settings#api). Only PMC members and
-committers are able to retrieve the API key. If the API key is invalid, regenerate.
-
-4. Download the translated docs
-
-Now you are ready to download the translated docs from Crowdin.
-
-```
-$ cd ${PULSAR_HOME}/site2/website
-# download all translated docs
-$ yarn crowdin-download
-# download the translated docs for `zh-CN`
-$ yarn crowdin-download -l zh-CN
-```
-
-The translated docs are downloaded to the `site2/website/translated_docs` directory.
-
-### Check issues, fix and verify
-
-After downloading the translated documents, you can open the target markdown file, check issues and fix them.
-To verify if you have fixed the issues correctly, [run the site locally](#run-the-site-locally).
diff --git a/site2/website/__tests__/doc-links.test.js b/site2/website/__tests__/doc-links.test.js
deleted file mode 100644
index 2f76ff4b764..00000000000
--- a/site2/website/__tests__/doc-links.test.js
+++ /dev/null
@@ -1,67 +0,0 @@
-const CWD = process.cwd();
-
-const path = require('path');
-const fs = require('fs');
-
-const docsDir = path.join(CWD, '../', 'docs');
-
-
-test('markdown doc links', async () => {
- const docsDir = path.join(CWD, '../', 'docs');
- const pages = new Set();
-
- // collect all doc pages
- fs.readdirSync(docsDir).forEach(file => {
- if (file.endsWith('.md')) {
- pages.add(file);
- }
- });
-
- const mdBrokenLinks = []
- pages.forEach(page => {
- const pageFile = path.join(docsDir, page)
- const mdLinks = getPageMDLinks(pageFile);
-
- const brokenLinks = []
- new Set(mdLinks).forEach(link => {
- if (!pages.has(link)) {
- brokenLinks.push(link);
- }
- })
-
- if (brokenLinks.length > 0) {
- mdBrokenLinks.push({page: page, brokenLinks: brokenLinks})
- }
- })
-
- // did we find some broken links?
- if (mdBrokenLinks.length > 0) {
- const brokenLinksJson = JSON.stringify(mdBrokenLinks, null, 2);
- const errorMessage = `Found the following broken links in docs pages:\n${brokenLinksJson}`
- console.log(errorMessage);
- expect(mdBrokenLinks.length).toBe(0)
- }
-})
-
-
-function getPageMDLinks(file) {
- if (!fs.existsSync(file)) {
- return [];
- }
- const content = fs.readFileSync(file, 'utf8');
-
- const mdLinks = [];
- // find any inline-style links to markdown files
- const linkRegex = /(?:\]\()(?:\.\/)?([^'")\]\s>]+\.md)/g;
- let linkMatch = linkRegex.exec(content);
- while (linkMatch !== null) {
- const link = linkMatch[1]
- // we are only checking links to other docs in this test
- if (!link.startsWith('http')) {
- mdLinks.push(linkMatch[1]);
- }
- linkMatch = linkRegex.exec(content);
- }
-
- return mdLinks;
-}
diff --git a/site2/website/blog/2018-08-06-Apache-Pulsar-2-1-0.md b/site2/website/blog/2018-08-06-Apache-Pulsar-2-1-0.md
deleted file mode 100644
index 2fd84446351..00000000000
--- a/site2/website/blog/2018-08-06-Apache-Pulsar-2-1-0.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-author: Sijie Guo
-authorURL: https://twitter.com/sijieg
-title: Apache Pulsar 2.1.0-incubating
----
-
-We are glad to present the new 2.1.0-incubating release of Pulsar.
-This release is the culmination of 2 months of work that have
-brought multiple new features and improvements to Pulsar.
-
-In Pulsar 2.1 you'll see:
-
-- [Pulsar IO](/docs/io-overview) connector framework and a list of [builtin connectors](/docs/io-connectors)
-- [PIP-17](https://github.com/apache/incubator-pulsar/wiki/PIP-17:-Tiered-storage-for-Pulsar-topics): [Tiered Storage](/docs/concepts-tiered-storage)
-- Pulsar [Stateful Functions](/docs/functions-state)
-- [Go Client](/docs/client-libraries-go)
-- [Avro](https://github.com/apache/incubator-pulsar/blob/v2.1.0-incubating/pulsar-client-schema/src/main/java/org/apache/pulsar/client/impl/schema/AvroSchema.java)
- and [Protobuf](https://github.com/apache/incubator-pulsar/blob/v2.1.0-incubating/pulsar-client-schema/src/main/java/org/apache/pulsar/client/impl/schema/ProtobufSchema.java) Schemas
-
-For details information please check the detailed [release notes](/release-notes/#2.1.0-incubating) and [2.1.0 documentation](/versions).
-
-<!--truncate-->
-
-We'll provide a brief summary of these features in the section below.
-
-## Pulsar IO
-
-Since Pulsar 2.0, we introduced a serverless inspired lightweight computing framework [Pulsar Functions](/docs/functions-overview),
-providing the easiest possible way to implement application-specific in-stream processing logic of any complexity. A lot of developers
-love Pulsar Functions because they require minimal boilerplate and are easy to reason about.
-
-In Pulsar 2.1, we continued following this "simplicity first" principle on developing Pulsar. We developed this IO (input/output) connector
-framework on top of Pulsar Functions, to simplify getting data in and out of Apache Pulsar. You don't need to write any single line of code.
-All you need is prepare a configuration file of the system your want to connect to, and use Pulsar admin
-CLI to submit a connector to Pulsar. Pulsar will take care of all the other stuffs, such as fault-tolerance, rebalancing and etc.
-
-There are 6 built-in connectors released in 2.1 release. They are:
-
-- [Aerospike Connector](/docs/io-aerospike/)
-- [Cassandra Connector](/docs/io-cassandra/)
-- [Kafka Connector](/docs/io-kafka/)
-- [Kinesis Connector](/docs/io-kinesis/)
-- [RabbitMQ Connector](/docs/io-rabbitmq/)
-- [Twitter Firehose Connector](/docs/io-twitter/)
-
-You can follow [the tutorial](/docs/io-quickstart) to try out Pulsar IO on connecting Pulsar with [Apache Cassandra](http://cassandra.apache.org/).
-
-More connectors will be coming in future releases. If you are interested in contributing a connector to Pulsar, checkout the guide on [Developing Connectors](/docs/io-develop).
-It is as simple as writing a Pulsar function.
-
-## Tiered Storage
-
-One of the advantages of Apache Pulsar is [its segment storage](https://streaml.io/blog/pulsar-segment-based-architecture) using
-[Apache BookKeeper](https://bookkeeper.apache.org/). You can store a topic backlog as large as you want.
-When the cluster starts to run out of space, you just add another storage node, and the system will automatically
-pickup the new storage nodes and start using them without rebalancing partitions. However, this can start to get expensive after a while.
-
-Pulsar mitigates this cost/size trade-off by providing Tiered Storage. Tiered Storage turns your Pulsar topics into real *infinite* streams,
-by offloading older segments into a long term storage, such as AWS S3, GCS and HDFS, which is designed for storing cold data. To the end user,
-there is no perceivable difference between consuming streams whose data is stored in BookKeeper or in long term storage. All the underlying
-offloading mechanisms and metadata management are transparent to applications.
-
-Currently [S3](https://aws.amazon.com/s3/) is supported in 2.1. More offloaders (such as Google GCS, Azure Blobstore, and HDFS) are coming
-in future releases.
-
-If you are interested in this feature, you can checkout more details [here](/docs/cookbooks-tiered-storage).
-
-## Stateful Function
-
-The greatest challenge that stream processing engines face is managing *state*. So does Pulsar Functions. As the goal for Pulsar Functions
-is to simplify developing stream native processing logic, we also want to provide an easier way for Pulsar Functions to manage their state.
-We introduced a set of [State API](/docs/functions-state/#api) for Pulsar Functions to store their state. It integrates with the table service
-in Apache BookKeeper for storing the state.
-
-It is released as a developer preview feature in Pulsar Functions Java SDK. We would like to collect feedback to improve it in future releases.
-
-## Schemas
-
-Pulsar 2.0 introduces native support for schemas in Pulsar. It means you can declare how message data looks and have Pulsar enforce that
-producers can only publish valid data on the topics. In 2.0, Pulsar only supports `String`, `bytes` and `JSON` schemas. We introduced the
-support for [Avro](https://avro.apache.org/) and [Protobuf](https://developers.google.com/protocol-buffers/) in this release.
-
-## Clients
-
-We have introduced a new [Go](/docs/client-libraries-go) client in 2.1 release. The Pulsar Go client library is based on the
-[C++](/docs/client-libraries-cpp/) client library.
-
-Follow [the instructions](/docs/client-libraries-go/#installing-go-package) to try it out in your Go applications!
diff --git a/site2/website/blog/2019-02-20-Apache-Pulsar-2-3-0.md b/site2/website/blog/2019-02-20-Apache-Pulsar-2-3-0.md
deleted file mode 100644
index 74ba27ef43a..00000000000
--- a/site2/website/blog/2019-02-20-Apache-Pulsar-2-3-0.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-author: Matteo Merli
-authorURL: https://twitter.com/merlimat
-title: Apache Pulsar 2.3.0
----
-
-The Apache Pulsar PMC is happy to announce the release of Pulsar 2.3.0. This
-is the result of huge effort from the community, with over 480 commits and
-a long list of new features, general improvements and bug fixes.
-
-These improvements have been across the board in all of Pulsar components,
-from new messaging features, to improved usability for Pulsar Functions
-and Pulsar IO.
-
-Check out the official <b>[release notes](/release-notes/#2.3.0)</b> for a
-detailed list of the changes, with links to the relevant pull-requests,
-discussions and documentation.
-
-Regarding new features introduced, I just want to highlight here a tiny
-subset of them:
-
-<!--truncate-->
-
-### Pulsar functions in Kubernetes
-
-It's now possible to use Kubernetes as the scheduler for Pulsar Functions.
-
-When a Pulsar cluster is configured to use Kubernetes, submitting a
-function, using CLI tools or REST API, will cause the function instances
-to be submitted as Kubernetes pods rather than running as processes
-or threads within the Pulsar functions worker.
-
-With this runtime manager, it's possible to set quota on CPU/Mem and
-have Kubernetes assign the required resources and enforce isolation
-between different instances and functions.
-
-### New Pulsar IO connectors:
-
-A new batch of connectors was added, including MongoDB, Elastic Search,
-HBase and local files source and sink.
-
-We introduce support for doing
-[Change-Data-Capture](https://en.wikipedia.org/wiki/Change_data_capture)
-with [Debezium](https://debezium.io/). This allows to record all
-the update from a database into a Pulsar topic and use it for replication,
-streaming jobs, cache updating, etc..
-
-With Pulsar IO, Debezium will run as a regular Pulsar IO source,
-completely managed by Pulsar. Users can easily submit a Debezium
-builtin connector to a Pulsar cluster and start feeding data
-from a long list of supported databases like MySQL, MongoDB,
-PostgreSQL, Oracle and SQL Server.
-
-Check out the [Debezium connector](/docs/io-cdc) documentation for how
-to get started in capturing database changes.
-
-### Token Authentication
-
-Token Authentication provides a very simple and secure method of authentication for Pulsar.
-This is based on [JSON Web Tokens](https://jwt.io/).
-
-With tokens authentication, a client only needs to provide a single credential, or "token", in the
-form of an opaque string provided by either the system administrator or some automated service.
-
-The Java code for a client using token authentication will look like:
-
-```java
-PulsarClient client = PulsarClient.builder()
- .serviceUrl("pulsar://broker.example.com:6650/")
- .authentication(
- AuthenticationFactory.token("eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJKb2UifQ.ipevRNuRP6HflG8cFKnmUPtypruRC4fb1DWtoLL62SY")
- .build();
-```
-
-See [Client Authentication using tokens](/docs/security-token-client) for a complete walk through
-and instructions on how to set it up and manage it.
-
-
-### Schema support in Python client library
-
-This feature adds a Python idiomatic way to declare the schema
-of a producer or consumer and integrates directly with the Pulsar
-schema registry.
-
-```python
-import pulsar
-from pulsar.schema import *
-
-class Example(Record):
- a = String()
- b = Integer()
- c = Boolean()
-
-producer = client.create_producer(
- topic='my-topic',
- schema=AvroSchema(Example) )
-
-producer.send(Example(a='Hello', b=1))
-```
-
-The above example will make the producer `Example` schema to be
-validated by broker when we try to publish on `my-topic`. If the
-topic has a schema that is incompatible, the producer creation will
-fail.
-
-Currently, the Python schema support Avro and JSON, in addition to
-regular types like `str` and `bytes`.
-
-The complete documentation is available at [Python schema](/docs/client-libraries-python/#schema).
-
-### Function state API in Python
-
-From 2.3.0, Python function can access the state in as similar
-way as Java functions, through the context object.
-
-```python
-import pulsar
-
-# The classic ExclamationFunction that appends an
-# exclamation at the end of the input
-class WordCountFunction(pulsar.Function):
- def process(self, input, context):
- for word in input.split():
- context.incr_counter(word, 1)
- return input + "!"
-```
-
-Available methods for state management in the context object are:
-
-```python
-def incr_counter(self, key, amount):
- """incr the counter of a given key in the managed state"""
-
-def get_counter(self, key):
- """get the counter of a given key in the managed state"""
-
-def put_state(self, key, value):
- """update the value of a given key in the managed state"""
-
-def get_state(self, key):
- """get the value of a given key in the managed state"""
-```
-
-## Conclusion
-
-Please [download](/download) Pulsar 2.3.0 and report feedback, issues or any comment into our mailing lists,
-slack channel or Github page. ([Contact page](/contact))
diff --git a/site2/website/blog/2019-07-05-Apache-Pulsar-2-4-0.md b/site2/website/blog/2019-07-05-Apache-Pulsar-2-4-0.md
deleted file mode 100644
index b0e8c1044fb..00000000000
--- a/site2/website/blog/2019-07-05-Apache-Pulsar-2-4-0.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-author: Penghui Li
-authorURL: https://twitter.com/lipenghui6
-title: Apache Pulsar 2.4.0
----
-
-We are glad to publish Apache Pulsar 2.4.0. This is the result of a huge
-effort from the community, with over 460 commits and a long list of new features,
-general improvements and bug fixes.
-
-Check out the <b>[release notes](/release-notes/#2.4.0)</b> for a detailed list of
-the changes, with links to the relevant pull requests, discussions and documentation.
-
-Regarding new features introduced, I just want to highlight here a tiny subset of them:
-
-<!--truncate-->
-
-### Delayed message delivery
-
-It's now possible to send a delayed message by Pulsar producer, and a delayed message will be
-available after a delay time.
-
-The Java code for a client using delayed messages delivery looks as follows:
-
-```java
-producer.newMessage().value("delayed message").deliverAfter(10, TimeUnit.SECONDS).send()
-```
-
-> Note:
->
-> 1. Messages are only delayed on shared subscriptions, other subscriptions will deliver immediately.
-> 2. Delayed messages are sent individually even if you enable message batching on producer.
-
-### Go Functions
-
-Before 2.4.0 release, Java and Python are supported to write Pulsar Functions. Now, you can
-use Go to write Pulsar Functions, the following is an example of
-a Pulsar Function written in Go.
-
-```go
-import (
- "fmt"
- "context"
-
- "github.com/apache/pulsar/pulsar-function-go/pf"
-)
-
-func HandleRequest(ctx context.Context, in []byte) error {
- fmt.Println(string(in) + "!")
- return nil
-}
-
-func main() {
- pf.Start(HandleRequest)
-}
-```
-
-### Key_Shared subscription
-
-A new subscription mode `Key_shared` is introduced in 2.4.0. In `Key_shared` subscription mode,
-one partition could have several consumers to consume messages in parallelism and ensure messages
-with the same key are distributed to a consumer in order.
-Here is [architecture](http://pulsar.apache.org/docs/en/concepts-messaging/#key_shared)
-for Key_Shared.
-
-The following is an example to use `Key_shared` subscription:
-
-```java
-client.newConsumer()
- .topic("topic")
- .subscriptionType(SubscriptionType.Key_Shared)
- .subscriptionName("sub-1")
- .subscribe();
-```
-
-### Schema versioning
-
-Before 2.4.0 release, Avro schema used one schema for both writer schema and reader schema.
-Multiple schemas version is supported now.
-
-With multiple schemas, a producer can send messages with different schema versions and a consumer
-can read messages with different schemas.
-
-In 2.4.0 release, `FORWARD_TRANSITIVE`, `BACKWARD_TRANSITIVE` and `FULL_TRANSITIVE` compatibility
-strategies are added to check the compatibility with all existing schema version.
-
-### Replicated subscription
-
-In 2.4.0 release, a mechanism is added to keep subscription state in sync, within a sub-second timeframe,
-in the context of a topic that is being asynchronously replicated across multiple geographical
-regions. Here is [architecture](https://github.com/apache/pulsar/wiki/PIP-33%3A-Replicated-subscriptions)
-for replicated subscription.
-
-The following is an example to use replicated subscription:
-
-```java
-Consumer<String> consumer = client.newConsumer(Schema.STRING)
- .topic("my-topic")
- .subscriptionName("my-subscription")
- .replicateSubscriptionState(true)
- .subscribe();
-```
-
-### New IO connectors
-
-A new batch of connectors is added, including Flume, Redis sink, Solr sink, RabbitMQ sink.
-The following lists builtin [connectors](http://pulsar.apache.org/docs/en/io-connectors/)
-that Pulsar supports.
-
-### Security
-
-In 2.4.0 release, Kerberos is supported in Apache Pulsar broker and client.
-To enable Kerberos authentication, refer to the [document](http://pulsar.apache.org/docs/en/security-kerberos/).
-
-Also added role based Pulsar Function authentication and authorization.
-
-## Conclusion
-
-If you want to download Pulsar 2.4.0, click [here](/download). You can send any questions or suggestions
-to our mailing lists, contribute to Pulsar on [GitHub](https://github.com/apache/pulsar) or join
-the Apache Pulsar community on [Slack](https://apache-pulsar.herokuapp.com/).
\ No newline at end of file
diff --git a/site2/website/blog/2019-12-04-Apache-Pulsar-2-4-2.md b/site2/website/blog/2019-12-04-Apache-Pulsar-2-4-2.md
deleted file mode 100644
index 51e7cd6d07f..00000000000
--- a/site2/website/blog/2019-12-04-Apache-Pulsar-2-4-2.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-author: Xiaolong Ran
-authorURL: https://twitter.com/wolf4j1
-title: Apache Pulsar 2.4.2
----
-
-We are proud to publish Apache Pulsar 2.4.2. Thank the great efforts from Apache Pulsar community with over 110 commits, covering improvements and bug fixes.
-
-For detailed changes related to 2.4.2 release, refer to <b>[release notes](/release-notes/#2.4.2)</b>.
-
-I will highlight some improvements and bug fixes in this blog.
-
-<!--truncate-->
-
-## Use classLoaders to load Java functions
-In Pulsar 2.4.2, windowed functions can work well whether Java Functions instances use shaded JAR or classLoaders, and functionClassLoader is set correctly when the `--output-serde-classname` option is enabled.
-
-Before Pulsar 2.4.2, Java Functions instances are started with a shaded JAR, and different classLoaders are used to load the internal Pulsar code, user code, and the interfaces that the two interacts with each other. This change results in two issues:
-- The windowed functions do not work well if Java Functions instances use classLoaders.
-- When using the `--output-serde-classname` option, functionClassLoader is not set correctly.
-
-## Start Broker with Functions worker
-In Pulsar 2.4.2, we can start Broker with Functions worker when broker client is enabled with TLS. Before Pulsar 2.4.2, when we run Functions worker with the broker, it checks whether TLS is enabled in the `function_worker.yml` file. If TLS is enabled, it uses TLS port. However, when TLS is enabled on Functions worker, it checks the `broker.conf`. Since Functions worker runs with the broker, it makes sense to check the `broker.conf` as the single source of truth about whether or not to u [...]
-
-## Add error code and error message when a key does not exist
-In Pulsar Functions, BookKeeper is supported to store the state of Functions. When users attempt to fetch a key that does not exist from function state, an NPE(NullPointerException) error occurs. In Pulsar 2.4.2, we add error code and error message for the case when a key does not exist.
-
-## Deduplication
-Deduplication removes messages based on the the largest sequence ID that pre-persisted. If an error is persisted to BookKeeper, a retry attempt is “deduplicated” with no message ever getting persisted. In version 2.4.2, we fix the issue from the following two aspects:
-- Double check the pending messages and return error to the producer when the duplication status is uncertain. For example, when a message is still pending.
-- Sync back the lastPushed map with the lastStored map after failures.
-
-## Consume data from the earliest location
-In Pulsar 2.4.2, we add `--subs-position` for Pulsar Sinks, so users can consume data from the latest and earliest locations. Before 2.4.2 release, data in topics is consumed from the latest location in Pulsar Sinks by default, and users can not consume the earliest data in sink topic.
-
-## Close previous dispatcher when the subscription type changes
-
-In Pulsar 2.4.2, when the type of a subscription changes, a new dispatcher is created, and the old dispatcher is closed, thus avoiding memory leaks. Before 2.4.2, when the subscription type of a topic changes, a new dispatcher is created and the old one is discarded, yet not closed, which causes memory leaks. If the cursor is not durable, the subscription is closed and removed from the topic when all consumers are removed. The dispatcher should be closed at this time. Otherwise, RateLimi [...]
-
-## Select an active consumer based on the subscription order
-In Pulsar 2.4.2, the active consumer is selected based on the subscription order. The first consumer in the consumer list is selected as an active consumer without sorting. Before 2.4.2, the active consumer is selected based on the priority level and consumer name. In this case, the active consumer joins and leaves, and no consumer is actually elected as "active" or consumes messages.
-
-## Remove failed stale producer from the connection
-In Pulsar 2.4.2, failed producer is removed correctly from the connection. Before Pulsar 2.4.2, broker cannot clean up the old failed producer correctly from the connection. When broker tries to clean up `producer-future` in the failed producer, it removes the newly created `producer-future` rather than the old failed producer, and the following error occurs in broker.
-
-```text
-17:22:00.700 [pulsar-io-21-26] WARN org.apache.pulsar.broker.service.ServerCnx - [/1.1.1.1:1111][453] Producer with id persistent://prop/cluster/ns/topic is already present on the connection
-```
-
-## Add new APIs for schema
-In Pulsar 2.4.2, we add the following APIs for schema:
-- `getAllVersions`: return the list of schema versions for a given topic.
-- `testCompatibility`: be able to test the compatibility for a schema without registering it.
-- `getVersionBySchema`: provide a schema definition and provide the schema version for it.
-
-## Expose `getLastMessageId()` method in consumerImpl
-In Pulsar 2.4.2, we expose `getLastMessageId()` method in consumerImpl. It benefits users when they want to know the lag messages, or only consume messages before the current time.
-
-## Add new `send()` interface in C++/Go
-In Pulsar 2.4.2, we add new `send()` interface in C++/Go, so the `MessageID` will be returned to users. The logic is consistent with that in Java. In Java client, the `MessageId send(byte[] message)` returns `MessageId` for users.
-
-## Consumer background tasks are cancelled after subscription failures
-In Pulsar 2.4.2, we ensure that consumer background tasks are cancelled after subscription failures. Before 2.4.2, some background consumer tasks are started in the ConsumerImpl constructor though these tasks are not cancelled if the consumer creation fails, leaving active references to these objects.
-
-## Delete topics attached with regex consumers
-In Pulsar 2.4.2, we can delete topics attached with a regex consumer. The followings are detailed methods.
-- Add a flag in CommandSubscribe so that a regex consumer will never trigger the creation of a topic.
-- Subscribe to a non-existing topic. When a specific error occurs, the consumer is interpreted as a permanent failure and thus stopping retrying.
-
-Before 2.4.2, it's not possible to delete topics when there is a regex consumer attached to them. The reason is that the regex consumer will immediately reconnect and re-create the topic.
-
-## Reference
-
-Download Pulsar 2.4.2 [here](https://pulsar.apache.org/en/download/).
-
-If you have any questions or suggestions, contact us with mailing lists or slack.
-- [users@pulsar.apache.org](mailto:users@pulsar.apache.org)
-- [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-- Pulsar slack channel: https://apache-pulsar.slack.com/
-- You can self-register at https://apache-pulsar.herokuapp.com/
-
-Looking forward to your contributions to [Pulsar](https://github.com/apache/pulsar).
\ No newline at end of file
diff --git a/site2/website/blog/2019-12-18-Pulsar-summit-cfp.md b/site2/website/blog/2019-12-18-Pulsar-summit-cfp.md
deleted file mode 100644
index a7f9033b240..00000000000
--- a/site2/website/blog/2019-12-18-Pulsar-summit-cfp.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-author: Jennifer Huang
-authorURL: https://twitter.com/Jennife06125739
-title: Pulsar Summit San Francisco 2020 CFP is now open
-
----
-
-Pulsar Summit is an annual conference dedicated to Apache Pulsar community, bringing together an international audience of CTOs/CIOs, developers, data architects, data scientists, Apache Pulsar committers/contributors, and the messaging and streaming community, to share experiences, exchange ideas and knowledge about Pulsar and its growing community, and receive hands-on training sessions led by Pulsar experts.
-
-We are excited to announce that the first Pulsar Summit will be held in San Francisco in April, 2020. Talk submissions, pre-registration, and sponsorship opportunities are now open for the conference!
-
-## Speak at Pulsar Summit
-Presentations and lightning talks are accepted for speaking proposals. Suggested topics cover Pulsar use cases, operations, technology deep dive, and ecosystem. Submissions are open until **January 31, 2020**.
-
-If you are unsure about your proposal, or want some feedback or advice in general, please do not hesitate to reach out to [sf-2020@pulsar-summit.org](mailto:sf-2020@pulsar-summit.org). We are happy to help out! Further details are available on the [CFP website](https://pulsar-summit.org/call-for-presentations/).
-
-## Dates to remember
-- CFP opens: December 15, 2019
-- CFP closes: January 31, 2020 - 23:59 PST
-- CFP notification: February 21, 2020
-- Schedule announcement: February 24, 2020
-
-## Speaker benefits
-When your speaking proposal is approved, you will enjoy the following benefits:
-
-- Full conference pass.
-- Exclusive swag only available to speakers.
-- Expand your network and raise your profile in the Pulsar community.
-- A professionally produced video of your presentation.
-- Your name, title, company, and bio will be featured on the Pulsar Summit San Francisco 2020 website.
-- Your session will be added to the Pulsar Summit YouTube Channel and promoted on Twitter and LinkedIn.
-
-## Pre-registration
-If you are interested in attending Pulsar Summit San Francisco 2020, we’d like to hear from you with your [pre-registration](https://pulsar-summit.org/pre-registration/). Your ideas are very important to us, and we will prepare the content accordingly.
-
-After you submit the pre-registration form, you will be added to the waitlist of Pulsar Summit San Francisco 2020. Once the registration is open, you will be notified with an email.
-
-## Sponsor Pulsar Summit
-Pulsar Summit is a community run conference and your support is needed. Sponsoring this event will provide a great opportunity for your organization to further engage with the Apache Pulsar community. [Contact us](mailto:partners@pulsar-summit.org) to learn more.
-
-Help us make #PulsarSummit 2020 a big success by spreading the word and submitting your proposal! Follow us on Twitter ([@pulsarsummit](https://twitter.com/PulsarSummit)) to receive the latest updates of the conference!
-
-Hope to see you at Pulsar Summit San Francisco 2020!
diff --git a/site2/website/blog/2019-12-20-pulsar-milestone-200-contributors.md b/site2/website/blog/2019-12-20-pulsar-milestone-200-contributors.md
deleted file mode 100644
index 7e5b06397d0..00000000000
--- a/site2/website/blog/2019-12-20-pulsar-milestone-200-contributors.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-author: Yu Liu
-authorURL: https://twitter.com/Anonymitaet1
-title: Pulsar milestone celebration—200 contributors!
-
----
-
-Dear Apache Pulsar enthusiast,
-
-As we know, when assessing the health of an open-source community, it is tempting to focus on various quantitative metrics, for example, activity, size (contributors), demographics, diversity, and so on, among which the number of contributors is a key metric for measuring the health and popularity of a project and a way to inform the trends.
-
-And today, we are very proud to see that **Apache Pulsar has attracted its 200th contributor!** It is an important milestone for our community growth.
-
-Over the years, there’s been an upward trend that more organizations embracing real-time data and stream processing, and Pulsar is the key component of that shift. As an open-source distributed pub-sub messaging system originally created at Yahoo! and graduated as a Top-Level Project (TLP) in September 2018, Pulsar has launched 79 releases, attracted 4100+ commits from 200 contributors, and received 4.6k+ stars, 1.2k+ forks, and 1.3k+ Slack users up to now.
-
-
-
-This achievement is worth celebrating, and at the same time, we would like to **express sincere gratitude to you** for making what Pulsar is today and shape what Pulsar will be tomorrow.
-
-Pulsar aims to empower the next generation of event streaming systems by delivering a unified solution that connects, stores and processes real-time event streams. Going forward, we will be continuously dedicated to making Pulsar as a highly flexible, scalable and reliable product and creating a welcoming and sustainable community where Pulsar and you can thrive together.
-
-
-
-P.S. want to be a Pulsar contributor?
-
-Get started today by [reading contribution guidelines](http://pulsar.apache.org/en/contributing/) and [submitting a PR](https://github.com/apache/pulsar), any contribution on codes, docs or other is highly appreciated. Thank you.
diff --git a/site2/website/blog/2020-03-17-announcing-the-apache-pulsar-2020-user-survey-report.md b/site2/website/blog/2020-03-17-announcing-the-apache-pulsar-2020-user-survey-report.md
deleted file mode 100644
index 35f2e5e8184..00000000000
--- a/site2/website/blog/2020-03-17-announcing-the-apache-pulsar-2020-user-survey-report.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-author: Sijie Guo
-authorURL: https://twitter.com/sijieg
-title: "Announcing: The Apache Pulsar 2020 User Survey Report"
----
-
-For the first time ever, the Apache Pulsar PMC team is publishing a user survey report.
-**The 2020 Apache Pulsar User Survey Report** reveals Pulsar’s accelerating rate of global
-adoption, details how organizations are leveraging Pulsar to build real-time streaming
-applications, and highlights key features on Pulsar’s product roadmap.
-
-
-
-Pulsar adoption has largely been driven by the market’s increased demand for real-time,
-data-enabled technologies. While companies have tried to leverage monolithic messaging
-systems to build-out real-time offerings, they’ve hit major roadblocks. Ultimately, these
-technologies are not equipped to provide the scale or reliability that mission-critical
-applications require.
-
-As a result, companies have sought-out Apache Pulsar for its cloud-native, distributed
-messaging and streaming platform capabilities. From asynchronous applications to core
-business applications to ETL, companies are increasingly leveraging Pulsar to develop
-real-time applications.
-
-Pulsar has received global adoption from major technology companies such as Verizon Media,
-Narvar, Overstock, Nutanix, Yahoo! JAPAN, Tencent, OVHCloud, and Clever Cloud, who rely on
-its ability to deliver on performance, scalability, and resiliency. As the Pulsar project
-and community garner increasing attention, we’re excited to share the **2020 Apache Pulsar User Survey Report**.
-
-
-
-In the 2020 Apache Pulsar User Survey Report, we hear from 165 users and learn how their
-companies are leveraging Pulsar’s cloud-native, multi-layer design architecture, built-in
-multi-tenancy, and multi-cluster replication, to build scalable real-time offerings. This
-report details insights and use cases on how organizations are deploying Pulsar today.
-
-The report also reveals Pulsar’s top-used features, its most popular applications, and how
-it is delivering scalable, reliable, real-time streaming solutions for organizations. In
-this quotation from Qiang Fei, Tech Lead for Tencent, we see how
-[one organization is leveraging Pulsar to improve their offering](https://streamnative.io/whitepaper/case-studay-apache-pulsar-tencent-billing/):
-
-> Pulsar provides us with a highly consistent and highly reliable distributed message queue that
-> fits well in our financial use cases. Multi-tenant and storage separation architecture design
-> greatly reduces our operational and maintenance overhead. We have used Pulsar on a very large
-> scale in our organization and we are impressed that Pulsar is able to provide high consistency
-> while supporting high concurrent client connections.
->
-> - Qiang Fei, Tech Lead at Tencent
-
-From its built-in multi-tenancy, which reduces architectural complexity and enables organizations
-to scale, to its multi-datacenter replication, which allows Pulsar to handle data center failures,
-we see how Pulsar has evolved into a robust and differentiated messaging and streaming platform.
-The report also reveals some of the community-driven features on Pulsar’s product roadmap for 2020
-and beyond. To find out more, [download the report today](https://streamnative.io/whitepaper/oss-apache-pulsar-user-survey-report-2020/).
-
-Join us for the first-ever Apache Pulsar Summit on August 26, 2020, in San Francisco, CA.
-More details on the Summit to come!
diff --git a/site2/website/blog/2020-04-23-Apache-Pulsar-2-5-1.md b/site2/website/blog/2020-04-23-Apache-Pulsar-2-5-1.md
deleted file mode 100644
index 1e90e9bda09..00000000000
--- a/site2/website/blog/2020-04-23-Apache-Pulsar-2-5-1.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-author: Guangning E
-authorURL: https://twitter.com/tuteng3
-title: Apache Pulsar 2.5.1
----
-
-We are proud to publish Apache Pulsar 2.5.1. This is the result of a huge effort from the community, with over 130 commits and a long list of new features, general improvements and bug fixes.
-
-For detailed changes related to 2.5.1 release, refer to the <b>[release notes](/release-notes/#2.5.1)</b> and the <b>[PR list for Pulsar 2.5.1](https://github.com/apache/pulsar/pulls?q=is:pr%20label:release/2.5.1%20is:closed)</b>.
-
-The following justs highlights a tiny subset of new features.
-
-<!--truncate-->
-
-## Refresh authentication credentials
-
-In Pulsar 2.5.1, two more methods are introduced in the single `AuthenticationState` interface credentials holder. This helps enhance the Pulsar authentication framework to support credentials that expire over time and need to be refreshed by forcing clients to re-authenticate.
-
-Existing authentication plugins are unaffected. If a new plugin wants to support expiration, it just overrides the `isExpired()` method. The Pulsar broker ensures to periodically check the expiration status for the AuthenticationState of every `ServerCnx` object. You can also use the `authenticationRefreshCheckSeconds` setting to control the frequency of the expiration check.
-
-## Upgrade Avro to 1.9.1
-
-The library used to handle logical datetime values has been changed from Joda-Time to JSR-310. For keeping forward compatibility, Pulsar java client uses Joda-Time conversion for logical datetime. To use JSR-310 conversion, you can enable it in the schema definition.
-
-```java
-AvroSchema.of(SchemaDefinition.builder()
-.withJSR310ConversionEnabled(true)
-.build()
-```
-> #### Note
->
-> By default, Avro 1.9.1 enables the JSR310 datetimes, which might introduce some regression problems if users use source codes generated by Avro compiler 1.8.x and the source codes contain datetimes fields. It is recommended to use Avro 1.9.x compiler to recompile.
-And, Avro may remove the Joda time support in the future. This may also be deleted in Pulsar in the future.
-## Support unloading all partitions of a partitioned topic
-Before Pulsar 2.5.1, Pulsar supports unloading a non-partitioned topic or a partition of a partitioned topic. If there is a partitioned topic with too many partitions, users need to get all partitions and unload them one by one. In Pulsar 2.5.1, we support unloading all partitions of a partitioned topic.
-## Supports evenly distributing topics count when splitting bundle
-In Pulsar 2.5.1, we introduce an option(`-balance-topic-count`) for bundle split. When setting this option to true, the given bundle is split into two parts and each part has the same amount of topics. In addition, we bring in a new Load Manager implementation named `org.apache.pulsar.broker.loadbalance.impl.BalanceTopicCountModularLoadManager`. The new Load Manager implementation splits the bundle with balance topics count.
-You can enable this feature in the broker.conf:
-```
-defaultNamespaceBundleSplitAlgorithm=topic_count_equally_divide
-```
-If you use the Pulsar Admin to split a bundle, you can use following command to split bundle based on topics count:
-```
-bin/pulsar-admin namespaces split-bundle -b 0x00000000_0xffffffff --split-algorithm-name topic_count_equally_divide public/default
-```
-## Support KeyValue schema for Pulsar SQL
-Before Pulsar 2.5.1, Pulsar SQL cannot read the keyValue schema data. In Pulsar 2.5.1, we add the prefix `key.` for the key field name, add the prefix `value.` for the value field name. Therefore, Pulsar SQL can read the keyValue schema data.
-## Update Netty version to `4.1.45.Final`
-Netty 4.1.43 has a bug, which prevents it from using Linux native Epoll transport. This makes Pulsar brokers fail over to NioEventLoopGroup even when running on Linux. The bug is fixed in Netty `4.1.45.Final` .
-## Improve Key_Shared subscription message dispatching performance
-In Pulsar 2.5.1, to improve Key_Shared subscription message dispatching performance, we make the following operations for saving CPU usage which can improve non-batched message dispatch performance:
-- Reduce making hash for the message key.
-- Reduce the number of finding consumers for message keys..
-## Add Joda time logical type conversion
-In Pulsar 2.5.1, Avro is upgraded to 1.9.x and the default time conversion is changed to JSR-310. For forwarding compatibility, we add the Joda time conversion in Pulsar 2.5.1 and enable it by default
-## Support deleting inactive topic when subscriptions caught up
-Before Pulsar 2.5.1, Pulsar supported deleting inactive topics that have no active producers or subscriptions. In Pulsar 2.5.1, we expose inactive topic delete mode in `broker.conf` to delete inactive topics that have no active producers or consumers but all subscriptions of the topic are caught up. You can enable this feature in the broker.conf:
-```
-brokerDeleteInactiveTopicsMode=delete_when_subscriptions_caught_up
-```
-## Introduce maxMessagePublishBufferSizeInMB configuration to avoid broker OOM
-Before Pulsar 2.5.1, if a broker has a smaller direct memory (e.g. 2G) and runs pulsar-perf to write messages, the broker becomes unstable. Because the broker reads messages from the channel automatically and the ByteBuf cannot be released until the entry is written to Bookie successfully or the timeout expires.
-In Pulsar 2.5.1, we introduce the `maxMessagePublishBufferSizeInMB` configuration to avoid broker OOM (Out of Memory). If the processing message size exceeds this value, the broker stops reading data from the connection. When the available size is greater than half of the maxMessagePublishBufferSizeInMB, the broker starts automatically reading data from the connection. You can set up the publish buffer size in broker.conf:
-```
-# Max memory size for broker handling messages sending from producers.
-# If the processing message size exceed this value, broker will stop read data
-# from the connection. The processing messages means messages are sends to broker
-# but broker have not send response to client, usually waiting to write to bookies.
-# It's shared across all the topics running in the same broker.
-# Use -1 to disable the memory limitation. Default is 1/2 of direct memory.
-maxMessagePublishBufferSizeInMB=
-```
-## Support BouncyCastle FIPS provider
-In Pulsar 2.5.1, Pulsar supports BC-FIPS (BouncyCastle FIPS) provider. Before Pulsar 2.5.1, Pulsar only supported BouncyCastle (BC) provider, and BC JARs are tied strongly into both the broker and the client code. Users fail to change from the BC provider to the BC-FIPS provider. This feature splits the BC dependency out into a separate module. Therefore, users can freely switch between the BC provider and the BC-FIPS provider.
-## Allow tenant Admin to manage subscription permission
-In previous releases, we have added support to grant subscriber-permission to manage subscription based APIs. However, grant-subscription-permission API requires super-user access and it creates too much dependency on system-admin when many tenants want to grant subscription permission.
-In Pulsar 2.5.1, through the Restful API or the Pulsar Admin, we allow each tenant Admin to manage subscription permission in order to reduce administrative efforts for super users.
-## Allow to enable/disable delayed delivery for messages on namespace
-In Pulsar 2.5.1, we add the `set-delayed-delivery` and `set-delayed-delivery-time` policies for the namespace. Therefore, Pulsar 2.5.1 allows to enable or disable delayed delayed delivery for messages on namespace.
-## Support offloader at namespace level
-In previous releases, the offload operation only had the cluster-level configuration. Users cannot set the offload configuration at the namespace level. In Pulsar 2.5.1, we support using the Pulsar Admin to set the offloader at the namespace level.
-## Disallow sub auto creation by Admin when disabling topic auto creation
-In previous releases, when Auto topic creation is disabled in KoP, non-partitioned topics are created with Flink Pulsar Source. To fix this bug, in Pulsar 2.5.1, we change the admin code to disable sub auto creation by the Admin when Auto topic creation is disabled.
-## Support Python 3.8 for Pulsar client
-In pulsar 2.5.1, we add `3.8 cp38-cp38` to support Python 3.8 for the Pulsar client. Therefore, users can install the Pulsar client on Python 3.8 .
-## Provide another `libpulsarwithdeps.a` in Debian/RPM cpp client library
-Pulsar 2.5.1 mainly provides 2 additional pulsar c++ client libraries in Debian/RPM:
-- pulsarSharedNossl (libpulsarnossl.so): it is similar to pulsarShared(libpulsar.so), and has no SSL statically linked.
-- pulsarStaticWithDeps(libpulsarwithdeps.a): it is similar to pulsarStatic(libpulsar.a), and is archived in the dependencies libraries of `libboost_regex`, `libboost_system`, `libcurl`, `libprotobuf`, `libzstd` and `libz` statically.
-## Reference
-To download Apache Pulsar 2.5.1, click [here](https://pulsar.apache.org/en/download/).
-If you have any questions or suggestions, contact us with mailing lists or slack.
-- [users@pulsar.apache.org](mailto:users@pulsar.apache.org)
-- [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-- Pulsar slack channel: https://apache-pulsar.slack.com/
-- Self-registration at https://apache-pulsar.herokuapp.com/
-Looking forward to your contributions to [Pulsar](https://github.com/apache/pulsar).
\ No newline at end of file
diff --git a/site2/website/blog/2020-05-19-Apache-Pulsar-2-5-2.md b/site2/website/blog/2020-05-19-Apache-Pulsar-2-5-2.md
deleted file mode 100644
index 1e2f9a0dcd2..00000000000
--- a/site2/website/blog/2020-05-19-Apache-Pulsar-2-5-2.md
+++ /dev/null
@@ -1,132 +0,0 @@
----
-author: Jia Zhai
-authorURL: https://twitter.com/Jia_Zhai
-title: Apache Pulsar 2.5.2
----
-
-We are proud to publish Apache Pulsar 2.5.2. This is the result of a huge effort from the community, with over 56 commits, general improvements and bug fixes.
-
-For detailed changes related to 2.5.2 release, refer to the <b>[release notes](/release-notes/#2.5.2)</b> and the <b>[PR list for Pulsar 2.5.2](https://github.com/apache/pulsar/pulls?q=is:pr%20label:release/2.5.2%20is:closed)</b>.
-
-The following highlights some improved features and fixed bugs in this release.
-
-<!--truncate-->
-
-## Implement AutoTopicCreation by namespace level override
-
-Introduce a new namespace policy `autoTopicCreationOverride`, which enables an override of broker `autoTopicCreation` settings on the namespace level. You can disable `autoTopicCreation` for the broker while allowing it on a specific namespace.
-
-## Add customized deletionLag and threshold for offloading policies per namespace
-
-Support configuring `deletionLag` and threshold in the offloading policy on the namespace level to remove data from the offloaded tiered storage.
-
-## Invalidate managed ledgers ZooKeeper cache instead of reloading on watcher triggered
-
-The ZooKeeper children cache is reloaded for z-nodes when topics are frequently created or deleted. This creates additional load on the ZooKeeper and the broker, slows down brokers and makes them less stable. In this release, `ZooKeeperManagedLedgerCache` is introduced to invalidate instead of reloading the ZooKeeper cache, when topics are created or deleted. This helps reduce pressures on the ZooKeeper.
-
-## Respect retention policy when there is no traffic
-
-In previous releases, retention is checked when the ledger rollover happens. So if the traffic is stopped, the ledgers are not cleaned up even if all the messages are already acknowledged. In Pulsar 2.5.2, `retentionCheckIntervalInSeconds` is introduced to check if consumed ledgers need to be trimmed between intervals. If the value is set to 0 or a negative number, the system does not check the consumed ledgers.
-
-## Bump Netty version to 4.1.48.Final
-
-The ZlibDecoders in Netty 4.1.x (before 4.1.46) allow for unbounded memory allocation while decoding a ZlibEncoded byte stream. An attacker could send a large ZlibEncoded byte stream to the Netty server, forcing the server to allocate all of its free memory to a single decoder. The bug is fixed in Netty `4.1.48.Final` .
-
-## Increase timeout for loading topics
-
-Loading replicated topics is quite an expensive operation and involves global ZooKeeper lookups and the start of many sub-processes. In Pulsar 2.5.2, we increase the timeout for loading topics which have many replicated clusters to 60 seconds.
-
-## Fix incorrect cursor state for cursor without consumers
-
-If consumers of a subscription are closed, the cursor is set to inactive. But the cursor is set to active during `PulsarStats.updateStats()` when the backlog size is less than `backloggedCursorThresholdEntries`. In Pulsar 2.5.2, we move the `checkBackloggedCursors()` from `ManagedLedger` to `Topic` and check the consumer list to fix this bug.
-
-## Change non-durable cursor to active to improve performance
-
-In non-durable subscription mode, the cursor is not active, which leads to the written entries not being put into cache. This would degrade the reading performance. In Pulsar 2.5.2, we set the `NonDurableCursorImpl` to active and remove three override methods `setActive()`, `isActive()`, `setInactive()` to improve the reading performance.
-
-## Add keystore configurations to TLS
-
-In Pulsar 2.5.2, we add keystore configurations to the TLS to allow users to define their own CA certificates while the internal communication uses an internal CA certificate. This change keeps the original TLS settings untouched, and adds new configurations in needed paths.
-
-## Close producer when the topic does not exists
-
-In previous releases, when we create a producer for a non-existent topic, the `ProducerImpl` object is hanging in the dump. This leads to OOM in micro-service which by mistake tries to produce consistently to a non-existent topic. In Pulsar 2.5.2, we fix the bug in the following two aspects:
-
-- Fix the exception handle for a non-existent topic.
-- Change state to `Close` when the producer gets the `TopicDoesNotExists` exception.
-
-## Fix `topicPublishRateLimiter` not effective after restarting broker
-
-In previous releases, when a publishing rate is configured on the namespace, it can limit the publishing rate. But when the broker is restarted, the limit expires. In Pulsar 2.5.2, this bug is fixed.
-
-## Expose pulsar_out_bytes_total and pulsar_out_messages_total for namespace/subscription/consumer
-
-Add pulsar_out_bytes_total and pulsar_out_messages_total for the namespace, subscription, and consumer. This helps to avoid missing the rate to be computed in Prometheus or missing change of rates within the scraping interval.
-
-## Fix `ttlDurationDefaultInSeconds` policy
-
-The TTL for namespaces should be retrieved from the broker configuration if it is not configured at namespace policies. In previous releases, the code only returns the value stored in namespace policies directly without judging if the TTL is configured or not. In Pulsar 2.5.2, we add a condition to test if TTL is configured at namespace policies. If not, the broker retrieves value stored in broker configuration and returns it as the output.
-
-## Fix long field parse in GenricJsonRecord
-
-For messages sent in JSON schema, the long field is decoded as int if its value is smaller than `Integer.MAX_VALUE`. Otherwise, the long field is decoded as a string. Pulsar 2.5.2 introduces a field type check in GenericJsonRecord to fix this bug.
-
-## Fix the leak of cursor reset if message encode fails in Avro schema
-
-If the Avro encode for a message fails after a few bytes are written, the cursor in the stream is not reset. The following `flush()`, which normally resets the cursor, is skipped if there is an exception. In Pulsar 2.5.2, we introduced a `flush()` in the finally block to fix this bug.
-
-## Update topic partitions automatically
-
-In Pulsar 2.5.2, the C++ client supports previously-created producers and consumers to automatically update partitions when the partitions for a topic are updated.
-
-- Add a `boost::asio::deadline_timer` to `PartitionedConsumerImpl` and `PartitionedProducerImpl` to register a lookup task to detect partition changes periodically.
-- Add an unsigned int configuration parameter to indicate the period of detecting partition changes.
-- Unlock the `mutex_` in `PartitionedConsumerImpl::receive` after `state_` were checked.
-
-## Fix default message ID in sent callback
-
-In previous releases, the `MessageId` in the callback is always the default value (`-1, -1, -1, -1`). In Pulsar 2.5.2, we remove the useless field `messageId` of `BatchMessageContainer::MessageContainer` and add the `const MessageId&` argument to `batchMessageCallBack`. Therefore, we can get the correct message ID in the callback if the message is sent successfully.
-
-## Fix message ID error if messages are sent to partitioned topics
-
-If messages are sent to a partitioned topic, the `partition` field of the message ID is always set to -1 because the `SendReceipt` command only contains the ledger ID and the entry ID. In Pulsar 2.5.2, we fix this bug by adding a `partition` field to `ProducerImpl` and setting the `partition` field of the message ID with it in the `ackReceived` method.
-
-## Support Async mode for Pulsar Functions
-
-In previous releases, Pulsar Functions does not support the Async mode, such as the user passed in a Function in the following format:
-
-```
-Function<I, CompletableFuture<O>>
-```
-
-This kind of function is useful if the Pulsar Functions use RPCs to call external systems. Therefore, in Pulsar 2.5.2, we introduce Async mode support for Pulsar Functions.
-
-
-## Fix localrunner netty dependency issue
-
-In Pulsar 2.5.2, we add a Log4j2 configuration file for pulsar-functions-local-runner to log to console by default. This helps troubleshoot the problem that Netty libraries are missing and the class is not found, when pulling in pulsar-functions-local-runner as a dependency and attempting to run Pulsar Functions locally.
-
-## Fix SerDe validation of Pulsar Functions update
-
-In previous releases, the `outputSchemaType` field is improperly used to validate parameters for Pulsar Function updates. In fact, the `outputSerdeClassName` parameter should be used. In Pulsar 2.5.2, we fix this bug.
-
-## Avoid pre-fetching too much data when offloading data to HDFS
-
-If too much data is pre-fetched when data is offloaded to HDFS, it may cause severe OOM. In Pulsar 2.5.2, the `managedLedgerOffloadPrefetchRounds` is introduced, which is used to set the maximum pre-fetch rounds for ledger reading for offloading data.
-
-## JDBC sink handles null fields in schema
-
-JDBC sink does not handle `null` fields. The schema registered in Pulsar allows for it and the table schema in MySQL has a column of the same name. When messages are sent to the JDBC sink without that field, an exception is thrown. In Pulsar 2.5.2, the JDBC sink uses the `setColumnNull` method to properly reflect the null field value in the database row.
-
-## Reference
-
-To download Apache Pulsar 2.5.2, click [here](https://pulsar.apache.org/en/download/).
-
-If you have any questions or suggestions, contact us with mailing lists or slack.
-
-- [users@pulsar.apache.org](mailto:users@pulsar.apache.org)
-- [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-- Pulsar slack channel: https://apache-pulsar.slack.com/
-- Self-registration at https://apache-pulsar.herokuapp.com/
-
-Looking forward to your contributions to [Pulsar](https://github.com/apache/pulsar).
diff --git a/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md b/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
deleted file mode 100644
index b7be9f6674a..00000000000
--- a/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
+++ /dev/null
@@ -1,395 +0,0 @@
----
-author: Penghui Li
-authorURL: https://twitter.com/lipenghui6
-title: Apache Pulsar 2.6.0
----
-We are very glad to see the Apache Pulsar community has successfully released the wonderful 2.6.0 version after accumulated hard work. It is a great milestone for this fast-growing project and the whole Pulsar community. This is the result of a huge effort from the community, with over 450 commits and a long list of new features, improvements, and bug fixes.
-
-Here is a selection of some of the most interesting and major features added to Pulsar 2.6.0.
-
-<!--truncate-->
-
-## Core Pulsar
-
-### [PIP-37] Large message size support
-
-This PIP adds support for producing and consuming large size messages by splitting the large message into multiple chunks. This is a very powerful feature for sending and consuming very large messages.
-
-Currently, this feature only works for the non-shared subscription and it has client-side changes. You need to upgrade the Pulsar client version to 2.6.0. You can enable the message trunk at the producer side as below.
-
-```java
-client.newProducer()
- .topic("my-topic")
- .enableChunking(true)
- .create();
-```
-
-For more information about PIP-37, see [here](https://github.com/apache/pulsar/wiki/PIP-37:-Large-message-size-handling-in-Pulsar). <br> For more information about implementation details, see [PR-4440](https://github.com/apache/pulsar/pull/4400).
-
-### [PIP-39] Namespace change events (system topic)
-
-This PIP introduces the system topic to store namespace change events. Previously, Pulsar only allowed you to set the namespace policy, all topics under the namespace followed the namespace policy. Many users want to set the policy for topics. The main reason for not using the same way as namespace level policy is to avoid introducing more workload on the ZooKeeper.
-
-The original intention of the system topic is to be able to store topic policy in a topic rather than ZooKeeper. So this is the first step to achieve topic level policy. And we can easily add support for the topic level policy with this feature.
-
-For more information about PIP-39, see [here](https://github.com/apache/pulsar/wiki/PIP-39%3A-Namespace-Change-Events).<br> For more information about implementation details, see [PR-4955](https://github.com/apache/pulsar/pull/4955).
-
-### [PIP-45] Pluggable metadata interface
-
-We have been advancing to enable Pulsar to use other metastore services rather than ZooKeeper. This PIP converts `ManagedLedger` to use the `MetadataStore` interface. This facilitates the metadata server plug-in process. Through the `MetadataStore` interface, it is easy to add other metadata servers into Pulsar such as [etcd](https://github.com/etcd-io/etcd).
-
-For more information about PIP-45, see [here](https://github.com/apache/pulsar/wiki/PIP-45%3A-Pluggable-metadata-interface). <br> For more information about implementation details, see [PR-5358](https://github.com/apache/pulsar/pull/5358).
-
-### [PIP-54] Support acknowledgment at the batch index level
-
-Previously, the broker only tracked the acknowledged state in the batch message level. If a subset of the batch messages was acknowledged, the consumer could still get the acknowledged message of that batch message while the batch message redelivery happened.
-
-This PIP adds support for acknowledging the local batch index of a batch. This feature is not enabled by default. You can enable it in the `broker.conf` as below.
-
-```
-acknowledgmentAtBatchIndexLevelEnabled=true
-```
-
-For more information about PIP-54, see [here](https://github.com/apache/pulsar/wiki/PIP-54:-Support-acknowledgment-at-batch-index-level). <br> For more information about implementation details, see [PR-6052](https://github.com/apache/pulsar/pull/6052).
-
-### [PIP-58] Support consumers setting custom message retry delay
-
-For many online business systems, various exceptions usually occur in business logic processing, so the message needs to be re-consumed, but users hope that this delay time can be controlled flexibly. Previously, processing methods were usually to send messages to special retry topics, because production can specify any delay, so consumers subscribe to the business topic and retry topic at the same time. Now you can set a retry delay for each message as below.
-
-```java
-Consumer<byte[]> consumer = pulsarClient.newConsumer(Schema.BYTES)
- .enableRetry(true)
- .receiverQueueSize(100)
- .deadLetterPolicy(DeadLetterPolicy.builder()
- .maxRedeliverCount(maxRedeliveryCount)
- .retryLetterTopic("persistent://my-property/my-ns/my-subscription-custom-Retry")
- .build())
- .subscribe();
-
-consumer.reconsumeLater(message, 10, TimeUnit.SECONDS);
-```
-
-For more information about PIP-58, see [here](https://github.com/apache/pulsar/wiki/PIP-58-%3A-Support-Consumers--Set-Custom-Retry-Delay). <br> For more information about implementation details, see [PR-6449](https://github.com/apache/pulsar/pull/6449).
-
-### [PIP-60] Support SNI routing to support various proxy servers
-
-Previously, Pulsar did not provide support to use other proxies, such as Apache Traffic Server (ATS), HAProxy, Nginx, and Envoy, which are more scalable and secured. Most of these proxy servers support SNI routing which can route traffic to a destination without having to terminate the SSL connection. This PIP adds SNI routing and makes changes to the Pulsar client.
-
-For more information about PIP-60, see [here](https://github.com/apache/pulsar/wiki/PIP-60:-Support-Proxy-server-with-SNI-routing). <br> For more information about implementation details, see [PR-6566](https://github.com/apache/pulsar/pull/6566).
-
-### [PIP-61] Advertise multiple addresses
-
-This PIP allows the broker to expose multiple advertised listeners and to support the separation of internal and external network traffic. You can specify multiple advertised listeners in `broker.conf` as below.
-
-```
-advertisedListeners=internal:pulsar://192.168.1.11:6660,external:pulsar://110.95.234.50:6650
-```
-
-From the client side, you can specify the listener name for the client as below.
-
-```java
-PulsarClient.builder()
- .serviceUrl(url)
- .listenerName("internal")
- .build();
-```
-
-For more information about PIP-61, see [here](https://github.com/apache/pulsar/wiki/PIP-61%3A-Advertised-multiple-addresses). <br> For more information about implementation details, see [PR-6903](https://github.com/apache/pulsar/pull/6903).
-
-### [PIP-65] Adapt Pulsar IO sources to support `BatchSources`
-
-This PIP introduces `BatchSource` as a new interface for writing batch-based connectors. It also introduces `BatchSourceTriggerer` as an interface to trigger the data collection of a `BatchSource`. It then provides system implementation in `BatchSourceExecutor`.
-
-For more information about PIP-65, see [here](https://github.com/apache/pulsar/wiki/PIP-65%3A-Adapting-Pulsar-IO-Sources-to-support-Batch-Sources). <br> For more information about implementation details, see [PR-7090](https://github.com/apache/pulsar/pull/7090).
-
-### [Load balancer] Add `ThresholdShedder` strategy for the load balancer
-
-The `ThresholdShedder` strategy is more flexible than `LoadSheddingStrategy` for Pulsar. The `ThresholdShedder` calculates the average resource usage of the brokers, and individual broker resource usage compares with the average value. If it is greater than the average value plus threshold, the overload shedder is triggered. You can enable it in `broker.conf` as below.
-
-```
-loadBalancerLoadSheddingStrategy=org.apache.pulsar.broker.loadbalance.impl.ThresholdShedder
-```
-
-You can customize more parameters for the `ThresholdShedder` if needed as below.
-
-```
-# The broker resource usage threshold.
-# When the broker resource usage is greater than the pulsar cluster average resource usage,
-# the threshold shedder will be triggered to offload bundles from the broker.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerBrokerThresholdShedderPercentage=10
-
-# When calculating new resource usage, the history usage accounts for.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerHistoryResourcePercentage=0.9
-
-# The BandWithIn usage weight when calculating new resource usage.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerBandwithInResourceWeight=1.0
-
-# The BandWithOut usage weight when calculating new resource usage.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerBandwithOutResourceWeight=1.0
-
-# The CPU usage weight when calculating new resource usage.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerCPUResourceWeight=1.0
-
-# The heap memory usage weight when calculating new resource usage.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerMemoryResourceWeight=1.0
-
-# The direct memory usage weight when calculating new resource usage.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerDirectMemoryResourceWeight=1.0
-
-# Bundle unload minimum throughput threshold (MB), avoiding bundle unload frequently.
-# It only takes effect in ThresholdShedder strategy.
-loadBalancerBundleUnloadMinThroughputThreshold=10
-```
-
-For more information about implementation details, see [PR-6772](https://github.com/apache/pulsar/pull/6772).
-
-### [Key Shared] Add consistent hashing in the Key_Shared distribution
-
-Previously, the implementation of the Key_Shared subscription used a mechanism to divide their hash space across the available consumers. This was based on dividing the currently assigned hash ranges when a new consumer joined or left. Pulsar 2.6.0 introduces a new consistent hash distribution for the Key_Shared subscription. You can enable the consistent hash distribution in `broker.conf` and the auto split approach is still selected by default.
-
-```
-# On KeyShared subscriptions, with default AUTO_SPLIT mode, use splitting ranges or
-# consistent hashing to reassign keys to new consumers
-subscriptionKeySharedUseConsistentHashing=false
-
-# On KeyShared subscriptions, number of points in the consistent-hashing ring.
-# The higher the number, the more equal the assignment of keys to consumers
-subscriptionKeySharedConsistentHashingReplicaPoints=100
-```
-
-We plan to use consistent hash distribution by default in the subsequent versions.
-For more information about implementation details, see [PR-6791](https://github.com/apache/pulsar/pull/6791).
-
-### [Key Shared] Fix ordering issue in KeyShared dispatcher when adding consumers
-
-This is a great fix for the Key_Shared subscription. Previously, ordering was broken in a KeyShared dispatcher if a new consumer c2 came in and an existing consumer c1 went out. This was because messages with keys previously assigned to c1 may route to c2, which might break the message ordering dispatch guarantee in the Key_Shared subscription. This PR introduces new consumers joining in a "paused" state until the previous messages are acknowledged to ensure the messages are dispatched o [...]
-
-If you still want the relaxed ordering, you can set up at the consumer side as below.
-
-```java
-pulsarClient.newConsumer()
- .keySharedPolicy(KeySharedPolicy.autoSplitHashRange().setAllowOutOfOrderDelivery(true))
- .subscribe();
-```
-
-For more information about implementation details, see [PR-7106](https://github.com/apache/pulsar/pull/7106) and [PR-7108](https://github.com/apache/pulsar/pull/7108).
-
-### [Key Shared] Add support for key hash range reading
-
-This PR supports sticky key hash range reader. A broker only dispatches messages whose hash of the message key contains by a specified key hash range. Besides, multiple key hash ranges can be specified on a reader.
-
-```java
-pulsarClient.newReader()
- .topic(topic)
- .startMessageId(MessageId.earliest)
- .keyHashRange(Range.of(0, 10000), Range.of(20001, 30000))
- .create();
-```
-
-For more information about implementation details, see [PR-5928](https://github.com/apache/pulsar/pull/5928).
-
-### Use pure-java Air-Compressor instead of JNI based libraries
-
-Previously, JNI based libraries were used to perform data compression. While these libraries do have an overhead in terms of size and affect the JNI overhead which is typically measurable when compressing many small payloads. This PR replaces compression libraries for LZ4, ZStd, and Snappy with [AirCompressor](https://github.com/airlift/aircompressor), which is a pure Java compression library used by Presto.
-
-For more information about implementation details, see [PR-5390](https://github.com/apache/pulsar/pull/5390).
-
-### Support multiple Pulsar clusters using the same BookKeeper cluster
-
-This PR allows multiple pulsar clusters to use the specified BookKeeper cluster by pointing BookKeeper client to the ZooKeeper connection string of BookKeeper cluster. This PR adds a configuration (`bookkeeperMetadataServiceUri`) to discover BookKeeper cluster metadata store and uses metadata service URI to initialize BookKeeper clients.
-
-```
-# Metadata service uri that bookkeeper is used for loading corresponding metadata driver
-# and resolving its metadata service location.
-# This value can be fetched using `bookkeeper shell whatisinstanceid` command in BookKeeper cluster.
-# For example: zk+hierarchical://localhost:2181/ledgers
-# The metadata service uri list can also be semicolon separated values like below:
-# zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers
-bookkeeperMetadataServiceUri=
-```
-
-For more information about implementation details, see [PR-5985](https://github.com/apache/pulsar/pull/5985).
-
-### Support deleting inactive topics when subscriptions are caught up
-
-Previously, Pulsar supported deleting inactive topics which do not have active producers and subscriptions. This PR supports deleting inactive topics when all subscriptions of the topic are caught up and when there are no active producers or consumers. This PR exposes inactive topic delete mode in `broker.conf`. In the future, we can support a namespace level configuration for the inactive topic delete mode.
-
-```
-# Set the inactive topic delete mode. Default is delete_when_no_subscriptions
-# 'delete_when_no_subscriptions' mode only delete the topic which has no subscriptions and no active producers
-# 'delete_when_subscriptions_caught_up' mode only delete the topic that all subscriptions has no backlogs(caught up)
-# and no active producers/consumers
-brokerDeleteInactiveTopicsMode=delete_when_no_subscriptions
-```
-
-For more information about implementation details, see [PR-6077](https://github.com/apache/pulsar/pull/6077).
-
-### Add a flag to skip broker shutdown on transient OOM
-
-A high dispatch rate on one of the topics may cause a broker to go OOM temporarily. It is a transient error and the broker can recover within a few seconds as soon as some memory gets released. However, in 2.4 release ([#4196](https://github.com/apache/pulsar/pull/4196)), the “restarted broker on OOM” feature can cause huge instability in a cluster, where a topic moves from one broker to another and restarts multiple brokers and disrupts other topics as well. So this PR provides a dynami [...]
-
-For more information about implementation details, see [PR-6634](https://github.com/apache/pulsar/pull/6634).
-
-### Make ZooKeeper cache expiry time configurable
-
-Previously, ZooKeeper cache expiry time was hardcoded and it needed to be configurable to refresh the value based on various requirements, for example, refreshing the value quickly in case of zk-watch miss, avoiding frequent cache refresh to avoid zk-read or avoiding issue due to zk read timeout, and so on. Now you can configure ZooKeeper cache expiry time in `broker.conf` as below.
-
-```
-# ZooKeeper cache expiry time in seconds
-zooKeeperCacheExpirySeconds=300
-```
-
-For more information about implementation details, see [PR-6668](https://github.com/apache/pulsar/pull/6668).
-
-### Optimize consumer fetch messages in case of batch message
-
-When a consumer sends a fetch request to a broker server, it contains a fetch message number telling the server how many messages should be pushed to a consumer client. However, the broker server stores data in BookKeeper or broker cache according to entry rather than a single message if the producer produces messages using the batch feature. There is a gap to map the number of messages to the number of entries when dealing with consumer fetch requests. This PR adds a variable `avgMessag [...]
-
-You can enable `preciseDispatcherFlowControl` in ` broker.conf` as below.
-
-```
-# Precise dispatcher flow control according to history message number of each entry
-preciseDispatcherFlowControl=false
-```
-
-For more information about implementation details, see [PR-6719](https://github.com/apache/pulsar/pull/6719)
-
-### Introduce precise topic publish rate limiting
-
-Previously, Pulsar supported the publish rate limiting but it is not a precise control. Now, for some use cases that need precise control, you can enable it in `broker.conf` as below.
-
-```
-preciseTopicPublishRateLimiterEnable=true
-```
-
-For more information about implementation details, see [PR-7078](https://github.com/apache/pulsar/pull/7078).
-
-### Expose check delay of new entries in `broker.conf`
-
-Previously, the check delay of new entries was 10 ms and could not be changed by users. Currently, for consumption latency sensitive scenarios, you can set the value of check delay of new entries to a smaller value or 0 in `broker.conf` as below. Using a smaller value may degrade consumption throughput.
-
-```
-managedLedgerNewEntriesCheckDelayInMillis=10
-```
-
-For more information about implementation details, see [PR-7154](https://github.com/apache/pulsar/pull/7154).
-
-### [Schema] Supports `null` key and `null` value in KeyValue schema
-
-For more information about implementation details, see [PR-7139](https://github.com/apache/pulsar/pull/7139).
-
-### Support triggering ledger rollover when `maxLedgerRolloverTimeMinutes` is met
-
-This PR implements a monitoring thread to check if the current topic ledger meets the constraint of `managedLedgerMaxLedgerRolloverTimeMinutes` and triggers a rollover to make the configuration take effect. Another important idea is that if you trigger a rollover, you can close the current ledger so that you can release the storage of the current ledger. For some less commonly used topics, the current ledger data is likely to be expired and the current rollover logic is only triggered wh [...]
-
-For more information about implementation details, see [PR-7116](https://github.com/apache/pulsar/pull/7111).
-
-## Proxy
-
-### Add REST API to get connection and topic stats
-
-Previously, Pulsar proxy did not have useful stats to get internal information about the proxy. It is better to have internal-stats of proxy to get information, such as live connections, topic stats (with higher logging level), and so on. This PR adds REST API to get stats for connection and topics served by proxy.
-
-For more information about implementation details, see [PR-6473](https://github.com/apache/pulsar/pull/6473).
-
-## Admin
-
-### Support getting a message by message ID in pulsar-admin
-
-This PR adds a new command `get-message-by-id` to the pulsar-admin. It allows users to check a single message by providing ledger ID and entry ID.
-
-For more information about implementation details, see [PR-6331](https://github.com/apache/pulsar/pull/6331).
-
-### Support deleting subscriptions forcefully
-
-This PR adds the method `deleteForcefully` to support force deleting subscriptions.
-
-For more information about implementation details, see [PR-6383](https://github.com/apache/pulsar/pull/6383).
-
-## Functions
-
-### Built-in functions
-
-This PR implements the possibility of creating built-in functions in the same way as adding built-in connectors.
-
-For more information about implementation details, see [PR-6895](https://github.com/apache/pulsar/pull/6895).
-
-### Add Go Function heartbeat (and gRPC service) for production usage
-
-For more information about implementation details, see [PR-6031](https://github.com/apache/pulsar/pull/6031).
-
-### Add custom property options to functions
-
-This PR allows users to set custom system properties while submitting functions. This can be used to pass credentials via a system property.
-
-For more information about implementation details, see [PR-6348](https://github.com/apache/pulsar/pull/6348).
-
-### Separate TLS configurations of function worker and broker
-
-For more information about implementation details, see [PR-6602](https://github.com/apache/pulsar/pull/6602).
-
-### Add the ability to build consumers in functions and sources
-
-Previously, function and source context give their writers an ability to create publishers but not consumers. This PR fixes this issue.
-
-For more information about implementation details, see [PR-6954](https://github.com/apache/pulsar/pull/6954).
-
-## Pulsar SQL
-
-### Support KeyValue schema
-
-Previously, Pulsar SQL could not read the KeyValue schema data.
-
-This PR adds KeyValue schema support for Pulsar SQL. It adds the prefix `key.` for the key field name and `value.` for the value field name.
-
-For more information about implementation details, see [PR-6325](https://github.com/apache/pulsar/pull/6325).
-
-### Support multiple Avro schema versions
-
-Previously, if you have multiple Avro schema versions for a topic, using the Pulsar SQL to query data from this topic will introduce some problems. With this change, You can evolve the schema of the topic and keep transitive backward compatibility of all schemas of the topic if you want to query data from this topic.
-
-For more information about implementation details, see [PR-4847](https://github.com/apache/pulsar/pull/4847).
-
-## Java client
-
-### Support waiting for inflight messages while closing a producer
-
-Previously, when you closed a producer, the pulsar-client immediately failed inflight messages even if it persisted successfully at the broker. Most of the time, users want to wait for those inflight messages rather than fail them. While the pulsar-client library did not provide a way to wait for inflight messages before closing the producer. This PR supports closing API with a flag where you can control waiting for inflight messages. With this change, you can close a producer by waiting [...]
-Previously, when you closed a producer, the pulsar-client immediately failed inflight messages even if it persisted successfully at the broker. Most of the time, users want to wait for those inflight messages rather than fail them. While the pulsar-client library did not provide a way to wait for inflight messages before closing the producer. This PR supports closing API with a flag where you can control waiting for inflight messages. With this change, you can close a producer by waiting [...]
-
-For more information about implementation details, see [PR-6648](https://github.com/apache/pulsar/pull/6648).
-
-### Support loading TLS certs/key dynamically from input stream
-
-Previously, the pulsar-client provided TLS authentication support and the default TLS provider `AuthenticationTls` expected file path of cert and key files. However, there were use cases where it was difficult for user applications to store certs/key files locally for TLS authentication. This PR adds stream support in `AuthenticationTls` to provide X509Certs and PrivateKey which also perform auto-refresh when streaming changes in a given provider.
-
-For more information about implementation details, see [PR-6760](https://github.com/apache/pulsar/pull/6760).
-
-### Support returning sequence ID when throwing an exception for async send messages
-
-Previously, when sending messages asynchronously failed, an exception was thrown, but did not know which message was abnormal, and users did not know which messages needed to be retried. This PR makes changes supported on the client side. When throwing an exception, the sequenceId `org.apache.pulsar.client.api.PulsarClientException` is set.
-
-For more information about implementation details, see [PR-6825](https://github.com/apache/pulsar/pull/6825).
-
-
-## More information
-
-- To download Apache Pulsar 2.6.0, click [here](https://pulsar.apache.org/en/download/).
-- For more information about Apache Pulsar 2.6.0, see [2.6.0 release notes](https://pulsar.apache.org/release-notes/#2.6.0) and [2.6.0 PR list](https://github.com/apache/pulsar/pulls?q=milestone%3A2.6.0+-label%3Arelease%2F2.5.2+-label%3Arelease%2F2.5.1+).
-
-If you have any questions or suggestions, contact us with mailing lists or slack.
-
-- [users@pulsar.apache.org](mailto:users@pulsar.apache.org)
-- [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-- Pulsar slack channel: https://apache-pulsar.slack.com/
-- Self-registration at https://apache-pulsar.herokuapp.com/
-
-Looking forward to your contributions to [Pulsar](https://github.com/apache/pulsar).
-
diff --git a/site2/website/blog/2020-08-21-Apache-Pulsar-2-6-1.md b/site2/website/blog/2020-08-21-Apache-Pulsar-2-6-1.md
deleted file mode 100644
index 95065ba5e9e..00000000000
--- a/site2/website/blog/2020-08-21-Apache-Pulsar-2-6-1.md
+++ /dev/null
@@ -1,274 +0,0 @@
----
-author: XiaoLong Ran
-authorURL: https://twitter.com/wolf4j1
-title: Apache Pulsar 2.6.1
----
-We are excited to see that the Apache Pulsar community has successfully released 2.6.1 version after a lot of hard work. It is a great milestone for this fast-growing project and the Pulsar community. 2.6.1 is the result of a big effort from the community, with over 100 commits and a long list of improvements and bug fixes.
-
-Here are some highlights and major features added in Pulsar 2.6.1.
-
-<!--truncate-->
-
-## Broker
-
-### Limit the batch size to the minimum of the `maxNumberOfMessages` and `maxSizeOfMessages`
-
-1. Batch size is not limited to the minimum of the `maxNumberOfMessages` and `maxSizeOfMessages` from the BatchReceive policy.
-2. When the batch size is greater than the `receiveQ` of the consumer (for example, the batch size is 3000 and a receiveQ is 500), the following issue occurs:
-
- In a multi-topic (pattern) consumer, the client stops receiving any messages. The client gets paused and never resumed when setting a timeout in the batch policy. Only one batch is fetched and the client is never resumed.
-
-For more information about implementation, see [PR-6865](https://github.com/apache/pulsar/pull/6865).
-
-### Fix hash range conflict issue in Key_Shared subscription with sticky hash range
-In `Key_Shared` subscription where the `stickyHashRange` is used, consumers are not allowed to use interleaving hashes.
-
-The pull request fixes the hash range conflict issue in `Key_Shared` with sticky hash range.
-
-For more information about implementation, see [PR-7231](https://github.com/apache/pulsar/pull/7231).
-
-### Fix get lookup permission error
-
-If the `canProduce` or `canConsume` method throws an exception, the `canLookup` method just throws the exception and does not check other permissions. The code snippet is as follows:
-
-```java
-try {
- return canLookupAsync(topicName, role, authenticationData)
- .get(conf.getZooKeeperOperationTimeoutSeconds(), SECONDS);
-}
-```
-
-PR-7234 invokes `canLookupAsync`. When Pulsar AuthorizationService checks lookup permission, if the user has the `canProducer` or `canConsumer` role, the user performs `canLookup` operations.
-
-For more information about implementation, see [PR-7234](https://github.com/apache/pulsar/pull/7234).
-
-### Avoid introducing null read position for the managed cursor
-
-Avoid introducing null read position for the managed cursor. The most doubtful thing is the `getNextValidPosition` method in the `ManagedLedgerImpl`. If a given position is greater than the position added last time, it returns a `null` value, and the read position is also `null`.
-
-In this PR, we add a log and print the stack trace to find the root cause and fallback to the next position if the `null` occurs at the next valid position.
-
-For more information about implementation, see [PR-7264](https://github.com/apache/pulsar/pull/7264).
-
-### Fix error in creation of non-durable cursor
-
-An NPE occurs when we fail to create a non-durable cursor and continue to create the subscription instance.
-
-```java
-try {
- cursor = ledger.newNonDurableCursor(startPosition, subscriptionName);
-} catch (ManagedLedgerException e) {
- subscriptionFuture.completeExceptionally(e);
-}
-
-return new PersistentSubscription(this, subscriptionName, cursor, false);
-```
-
-Additionally, the NPE leads to the topic usage count increasing to 1. When deleting a topic, the topic cannot be deleted even if you use the force flag.
-
-For more information about implementation, see [PR-7355](https://github.com/apache/pulsar/pull/7355).
-
-### Avoid an NPE occurs in the `ManagedLedgerImpl.isOffloadedNeedsDelete` method
-
-When the default value of the `offload-deletion-lag` is set to `null`, an NPE occurs. To fix the bug, null check is added in the `ManagedLedgerImpl.isOffloadedNeedsDelete` method.
-
-For more information about implementation, see [PR-7389](https://github.com/apache/pulsar/pull/7389).
-
-### Fix producer stuck issue due to NPE when creating a new ledger
-
-NPE occurs when creating a ledger if the network address is unresolvable. If NPE occurs before adding the timeout task, the timeout mechanism does not work. The unresolvable network address is common in the Kubernetes environment. It happens when a bookie pod or a worker node restarts.
-
-This pull request fixes from the following perspectives:
-
-1. Catch the NPE when creating a new ledger.
-2. When the timeout task is triggered, it always executes the callback. It is totally fine because we already have the logic to ensure the callback is triggered only once.
-3. Add a mechanism to detect that the `CreatingLedger` state is not moving.
-
-For more information about implementation, see [PR-7401](https://github.com/apache/pulsar/pull/7401).
-
-
-### Fix NPE when using advertisedListeners
-
-The broker failed to acquire ownership for the namespace bundle when using `advertisedListeners=internal:pulsar://node1:6650,external:pulsar://node1.external:6650` with external listener name. Correct `BrokerServiceUrlTls` when TLS is not enabled.
-
-For more information about implementation, see [PR-7620](https://github.com/apache/pulsar/pull/7620).
-
-### Fix the issue that the deduplication cursor cannot be deleted after message deduplication is disabled
-
-When enabling the message deduplication in the `broker.conf` file, disabling it and then restarting the broker, the deduplication cursor is not deleted.
-
-This PR fixes the issue, so when you disable message deduplication, you can delete the deduplication cursor.
-
-For more information about implementation, see [PR-7656](https://github.com/apache/pulsar/pull/7656).
-
-### Fix the issue that GetLastEntry() reads entry `-1`
-
-Previously, the code does not include a return statement. If the entry is set to `-1`, after sending code, the response reads the entry and sends a second response, as shown in the following example.
-```
-16:34:25.779 [pulsar-io-54-7:org.apache.bookkeeper.client.LedgerHandle@748] ERROR org.apache.bookkeeper.client.LedgerHandle - IncorrectParameterException on ledgerId:0 firstEntry:-1 lastEntry:-1
-16:34:25.779 [pulsar-client-io-82-1:org.apache.pulsar.client.impl.ConsumerImpl@1986] INFO org.apache.pulsar.client.impl.ConsumerImpl - [persistent://external-repl-prop/pulsar-function-admin/assignment][c-use-fw-localhost-0-function-assignment-initialize-reader-b21f7607c9] Successfully getLastMessageId 0:-1
-16:34:25.779 [pulsar-client-io-82-1:org.apache.pulsar.client.impl.ClientCnx@602] WARN org.apache.pulsar.client.impl.ClientCnx - [id: 0xc78f4a0e, L:/127.0.0.1:55657 - R:localhost/127.0.0.1:55615] Received error from server: Failed to get batch size for entry org.apache.bookkeeper.mledger.ManagedLedgerException: Incorrect parameter input
-16:34:25.779 [pulsar-client-io-82-1:org.apache.pulsar.client.impl.ClientCnx@612] WARN org.apache.pulsar.client.impl.ClientCnx - [id: 0xc78f4a0e, L:/127.0.0.1:55657 - R:localhost/127.0.0.1:55615] Received unknown request id from server: 10
-```
-
-PR-7495 adds a return statement to code, so GetLastEntry() reads the last entry, instead of `-1`.
-
-For more information about implementation, see [PR-7495](https://github.com/apache/pulsar/pull/7495).
-
-### Fix the error of updating partitions for non-persistent topic
-
-When updating partitions on a non-persistent topic, Error 409 is returned. The pull request fixes partitions errors for non-persistent topics.
-
-For more information about implementation, see [PR-7459](https://github.com/apache/pulsar/pull/7459).
-
-## ZooKeeper
-
-### Use hostname for bookie rack awareness mapping
-
-In [PR-5607](https://github.com/apache/pulsar/pull/5607), the `useHostName()` is added with `return false`. The rack-aware policy passes the Bookie's hostname into an IP address and then uses that IP address to figure out to which rack the bookie belongs.
-
-Then two issues occur:
- 1. The IP does not match the hostname which is recorded in the `/bookies` z-node
- 2. If there is an error in parsing the bookie hostname (eg: transient DNS error), an NPE is triggered and the BK client never realizes that this bookie is available in the cluster.
-
-The exception is thrown at Line 77(as shown in the following code snippet), since `getAddress()` returns a `null` given that the address is parsed.
-
-```java
-74 if (dnsResolver.useHostName()) {
-75 names.add(addr.getHostName());
-76 } else {
-77 names.add(addr.getAddress().getHostAddress());
-78 }
-```
-
-The default implementation for the `DnsResolver.useHostName()` returns `true`.
-
-For more information about implementation, see [PR-7361](https://github.com/apache/pulsar/pull/7361).
-
-## Java Client
-
-### Fix the issue that the HTTP header used in Athenz authentication can not be renamed
-
-The authentication plugin for Athenz allows users to change the name of the HTTP header for sending an authentication token to a broker server with a parameter named `roleHeader`. The change uses the value of the `roleHeader` parameter on the `AuthenticationAthenz` side, and uses it directly as the header name.
-
-For more information about implementation, see [PR-7311](https://github.com/apache/pulsar/pull/7311).
-
-### Fix the issue that batch ack set is recycled multiple times
-
-The batch ack sets are recycled multiple times, due to race condition in group ack flush and cumulative Ack. So we add a recycled state check for the ack set in PR-7409, and fix the recycle issue.
-
-For more information about implementation, see [PR-7409](https://github.com/apache/pulsar/pull/7409).
-
-### Add authentication client with OAuth2 support
-
-Pulsar supports authenticating clients using OAuth 2.0 access tokens. You can use tokens to identify a Pulsar client and associate with some "principal" (or "role") that is permitted to do some actions, for example, publish messages to a topic or consume messages from a topic.
-
-This module is to support Pulsar Client Authentication Plugin for OAuth 2.0 directly. The client communicates with the Oauth 2.0 server, gets an `access token` from the Oauth 2.0 server, and passes the `access token` to Pulsar broker to do the authentication.
-
-So, the broker can use `org.apache.pulsar.broker.authentication.AuthenticationProviderToken`,
-and the user can add their own `AuthenticationProvider` to work with this module.
-
-For more information about implementation, see [PR-7420](https://github.com/apache/pulsar/pull/7420).
-
-
-### Not subscribe to the topic when the consumer is closed
-
-Fix race condition on the closed consumer while reconnecting to the broker.
-
-The race condition happens when the consumer reconnects to the broker. The connection of the consumer is set to `null` when the consumer reconnects to the broker. If the consumer is not connected to broker at this time, the client does not send the consumer command to the broker. So, when the consumer reconnects to the broker, the consumer sends the subscribe command again.
-
-This pull request adds a state check when the `connectionOpened()` of the consumer opens. If the consumer is in closing or closed state, the consumer does not send the subscribe command.
-
-For more information about implementation, see [PR-7589](https://github.com/apache/pulsar/pull/7589).
-
-### OAuth2 authentication plugin uses AsyncHttpClient
-
-Previously, the OAuth2 client authentication plugin used Apache HTTP client lib to make requests, Apache HTTP client is used to validate hostname. As suggested in [#7612](https://github.com/apache/pulsar/issues/7612), we get rid of the dependency of using Apache HTTP client.
-
-In PR-7615, OAuth2 client authentication plugin uses AsyncHttpClient, which is used in client and broker. For more information about implementation, see [PR-7615](https://github.com/apache/pulsar/pull/7615).
-
-
-## CPP Client
-
-### CPP Oauth2 authentication client
-
-Pulsar supports authenticating clients using OAuth 2.0 access tokens. You can use tokens to identify a Pulsar client and associate with some "principal" (or "role") that is permitted to do some actions (eg: publish messages to a topic or consume messages from a topic). This change tries to support it in cpp client.
-
-For more information about implementation, see [PR-7467](https://github.com/apache/pulsar/pull/7467).
-
-### Fix partition index error in close callback
-
-In partitioned producer/consumer's close callback, the partition index is always `0`. The `ProducerImpl/ConsumerImpl` internal partition index field should be passed to `PartitionedProducerImpl/PartitionedConsumerImpl` close callback.
-
-For more information about implementation, see [PR-7282](https://github.com/apache/pulsar/pull/7282).
-
-### Fix segment crashes caused by race condition of timer in CPP client
-
-Segment crashes occur in a race condition:
- - The close operation calls the `keepAliveTimer_.reset()`.
- - The `keepAliveTimer` is called by `startConsumerStatsTimer` and `handleKeepAliveTimeout` methods. Actually, the `keepAliveTimer` should not be called by those two methods.
-
-This pull request fixes those issues.
-
-For more information about implementation, see [PR-7572](https://github.com/apache/pulsar/pull/7572).
-
-### Add support to read credentials from file
-
-Support reading credentials from a file to make it align with the Java client.
-
-For more information about implementation, see [PR-7606](https://github.com/apache/pulsar/pull/7606).
-
-### Fix multi-topic consumer segfault on connection error
-
-The multi-topic consumer triggers a segfault when an error occurs in creating a consumer. This is due to the calls to close the partial consumers with a null callback.
-
-For more information about implementation, see [PR-7588](https://github.com/apache/pulsar/pull/7588).
-
-## Functions
-
-### Use fully qualified hostname as default to advertise worker
-
-There is a difference in getting hostnames between `Java 8` and `Java 11`. In Java 8, `InetAddress.getLocalHost().getHostName()` returns the fully qualified hostname; in Java 11, it returns a simple hostname. In this case, we should rather use the `getCanonicalHostName()`, which returns the fully qualified hostname. This is the same method to get the advertised address for workers as well.
-
-For more information about implementation, see [PR-7360](https://github.com/apache/pulsar/pull/7360).
-
-### Fix the function BC issue introduced in release 2.6.0
-
-A backwards compatibility breakage is introduced in [PR-5985](https://github.com/apache/pulsar/pull/5985). When the running function workers are separated from brokers, updating workers and brokers independently from release 2.5.0 to 2.6.0 results in the following error:
-
-```text
-java.lang.NullPointerException: null\n\tat java.net.URI$Parser.parse(URI.java:3104) ~[?:?]
-java.net.URI.<init>(URI.java:600) ~[?:?]\n\tat java.net.URI.create(URI.java:881) ~[?:?]
-org.apache.pulsar.functions.worker.WorkerUtils.initializeDlogNamespace(WorkerUtils.java:160) ~[org.apache.pulsar-pulsar-functions-worker-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
-org.apache.pulsar.functions.worker.Worker.initialize(Worker.java:155) ~[org.apache.pulsar-pulsar-functions-worker-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
-org.apache.pulsar.functions.worker.Worker.start(Worker.java:69) ~[org.apache.pulsar-pulsar-functions-worker-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
-org.apache.pulsar.functions.worker.FunctionWorkerStarter.main(FunctionWorkerStarter.java:67) [org.apache.pulsar-pulsar-functions-worker-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
-```
-
-This is because the broker 2.5.0 supports "bookkeeperMetadataServiceUri" and the admin client returns a `null` field, thus causing the NPE.
-
-For more information about implementation, see [PR-7528](https://github.com/apache/pulsar/pull/7528).
-
-## pulsar-perf
-
-### Support `tlsAllowInsecureConnection` in pulsar-perf produce/consume/read performance tests
-
-Add `tlsAllowInsecureConnection` config to the CLI tool **pulsar-perf**, to support produce/consume/read performance tests to clusters with insecure TLS connections.
-
-For more information about implementation, see [PR-7300](https://github.com/apache/pulsar/pull/7300).
-
-## More information
-
-- To download Apache Pulsar 2.6.1, click [download](https://pulsar.apache.org/en/download/).
-- For more information about Apache Pulsar 2.6.1, see [2.6.1 release notes](https://pulsar.apache.org/release-notes/#2.6.1) and [2.6.1 PR list](https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.6.1+is%3Aclosed).
-
-If you have any questions or suggestions, contact us with mailing lists or slack.
-
-- [users@pulsar.apache.org](mailto:users@pulsar.apache.org)
-- [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-- Pulsar slack channel: https://apache-pulsar.slack.com/
-- Self-registration at https://apache-pulsar.herokuapp.com/
-
-Looking forward to your contributions to [Pulsar](https://github.com/apache/pulsar).
-
-
diff --git a/site2/website/blog/2020-08-24-Pulsar-300-contributors.md b/site2/website/blog/2020-08-24-Pulsar-300-contributors.md
deleted file mode 100644
index d58fbb319bd..00000000000
--- a/site2/website/blog/2020-08-24-Pulsar-300-contributors.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-author: Jennifer Huang
-authorURL: https://twitter.com/Jennife06125739
-title: Apache Pulsar Celebrates 300 Contributors
-
----
-
-Dear Pulsar community,
-
-Over the last few years, the shift to real-time streaming technologies has bolstered the adoption of Pulsar and there has been a major increase in both the interest and adoption of Pulsar in 2020 alone. With Pulsar being sought out by companies developing messaging and event-streaming applications — from Fortune 100 companies to forward-thinking start-ups — the community is growing quickly.
-
-This community growth has contributed to a new milestone for Pulsar - our [300th contributor](https://github.com/apache/pulsar/graphs/contributors) to the Pulsar repository. This milestone is even more exciting given that we added 100 contributors in the last 8 months alone!
-
-As many of you know, Apache Pulsar is a cloud-native messaging and event streaming platform that has experienced rapid growth since it was committed to open source in 2016. Pulsar graduated as a Top-Level Project (TLP) in September 2018, has launched 92 releases, attracted 5100+ commits from 300 contributors, received 6.5k+ stars, 1.6k+ forks, and 2.2k+ Slack users.
-
-The influx of developers joining the Pulsar community is in large part due to the high market demand for next-generation messaging technologies, big-data insights, and real-time streaming. Top developers and industry leaders are joining the Pulsar community for the opportunity to help shape the future of this technology.
-
-## Community Events
-To meet the high demand for education and training in the Pulsar community, the community has launched some key initiatives this year. We host weekly TGIP(Thank God It's Pulsar) training, which features Pulsar thought-leaders and Pulsar PMC Members. To meet global demand, we currently host two different weekly trainings. One [TGIP training](https://www.youtube.com/watch?v=Vc_a2ppRzlI&list=PLqRma1oIkcWhWAhKgImEeRiQi5vMlqTc-) runs on Pacific Time, and the other [TGIP-CN training](https://g [...]
-
-We also host monthly [webinars](https://www.youtube.com/watch?v=mncXc_T6JkU&list=PLqRma1oIkcWhfmUuJrMM5YIG8hjju62Ev) to bring together Pulsar and messaging community thought-leaders to share best practices, insights and product news. Thank [Matteo Merli](https://twitter.com/merlimat), [Addison Higham](https://twitter.com/addisonjh), Joe Francis, [Shivji Kumar Jha](https://twitter.com/ShivjiJha), [Devin Bost](https://twitter.com/DevinBost), [Pierre Zemb](https://twitter.com/PierreZ), [Jes [...]
-
-This year also marked our first global summit, held in June 2020. Hosted by StreamNative and Splunk, the first-ever [Pulsar Summit Virtual Conference](https://pulsar-summit.org/) featured 30+ talks from 20+ organizations. Thank all speakers for sharing your stories about Pulsar, and thank you to all of the attendees for joining the event.
-
-We are excited to announce that we will be hosting Pulsar Summit Asia 2020 on November 28 and 29, and the call for presentations for this event will be coming soon.
-
-## Pulsar Adoption
-In addition to the growth in contributors, we are excited to see accelerated adoption of Pulsar in PoC and production environments. Pulsar is helping companies globally to unlock the power of real-time data and to grow their businesses with efficiency and simplicity.
-
-Key adoption stories illustrate Pulsar's ability to handle mission-critical applications. These include [Tencent’s adoption](https://streamnative.io/success-stories/tencent) of Pulsar for its transactional billing system, which processes more than 10 billion transactions and 10+ TBs of data daily. [Verizon Media is another success story](https://www.youtube.com/watch?v=FXQvsHz_S1A), having operated Pulsar in production for more than 5 years, managing millions of write requests/second, an [...]
-
-For more insights on Pulsar adoption, you can find a list for companies using or contributing to Apache Pulsar on [Pulsar Powered by page](http://pulsar.apache.org/en/powered-by/).
-
-## Ecosystem Development
-Committed community partners have also contributed to key project advancements. Below, we look at two recent product launches.
-
-### OVHCloud Helps Companies Move from Kafka to Pulsar
-In March 2020, [OVHCloud and StreamNative launched Kafka-on-Pulsar (KoP)](https://streamnative.io/blog/tech/2020-03-24-bring-native-kafka-protocol-support-to-apache-pulsar), the result of the two companies working closely in partnership. [KoP](https://github.com/streamnative/kop) enables Kafka users to migrate their existing Kafka applications and services to Pulsar without modifying the code. Although only recently released, KoP has already been adopted by several organizations and is b [...]
-
-### China Mobile Helps Companies Move from RabbitMQ to Pulsar
-In June 2020, [China Mobile and StreamNative announced the launch of another major platform upgrade, AMQP-on-Pulsar (AoP)](https://streamnative.io/blog/tech/2020-06-15-announcing-aop-on-pulsar). Similar to KoP, [AoP](https://github.com/streamnative/aop) allows organizations currently using RabbitMQ (or other AMQP message brokers) to migrate existing applications and services to Pulsar without code modification. Again, this is a key initiative that will help drive the adoption and usage o [...]
-
-You can find a number of other connections and integrations, such as MQTT-on-Pulsar for building IoT applications, in the [StreamNative Hub](https://hub.streamnative.io/).
-
-These events and initiatives illustrate the Pulsar community's firm commitment to education and ecosystem development. More importantly, they demonstrate the momentum and growth we can expect in the future.
-
-## Special Thanks
-We would like to thank the Pulsar community, contributors and committers, who have helped to drive development, growth and adoption for Pulsar. We would especially like to recognize our distinguished contributors and committers (including but not limited to):
-- [Matteo Merli](https://github.com/merlimat) from [Splunk](https://www.splunk.com/)
-- [Rajan Dhabalia](https://github.com/rdhabalia) from [Verizon Media](https://www.verizonmedia.com/)
-- [Sijie Guo](https://github.com/sijie) from [StreamNative](https://streamnative.io/)
-- [Sanjeev Kulkarni](https://github.com/srkukarni) from [Splunk](https://www.splunk.com/)
-- [Boyang Jerry Peng](https://github.com/jerrypeng) from [Splunk](https://www.splunk.com/)
-- [Ivan Brendan Kelly](https://github.com/ivankelly) from [Splunk](https://www.splunk.com/)
-- [Penghui Li](https://github.com/codelipenghui) from [Zhaopin.com](http://www.zhaopin.com/)
-- [Jia Zhai](https://github.com/jiazhai) from [StreamNative](https://streamnative.io/)
-
-To view other contributors, see [Pulsar contributor list](https://github.com/apache/pulsar/graphs/contributors).
-
-## Get Involved
-We invite you to join this fast-growing community. Together, we will continue to develop technology to meet today’s most innovative messaging and event-streaming use cases and to help companies unlock the value of real-time data.
-
-Whether it is joining our [Pulsar Slack channel](https://apache-pulsar.slack.com/), sharing your Pulsar story via a sponsored [webinar](https://www.youtube.com/watch?v=mncXc_T6JkU&list=PLqRma1oIkcWhfmUuJrMM5YIG8hjju62Ev) or case study, joining a [TGIP](https://github.com/streamnative/tgip)/[TGIP-CN](https://github.com/streamnative/tgip-cn), or attending or speaking at the next Pulsar Summit, we look forward to connecting with you.
-
-You can also subscribe our mailing lists: [users@pulsar.apache.org](mailto:users-subscribe@pulsar.apache.org) and [dev@pulsar.apache.org](mailto:dev-subscribe@pulsar.apache.org).
\ No newline at end of file
diff --git a/site2/website/blog/2020-09-01-pulsar-summit-asia-2020-cfp.md b/site2/website/blog/2020-09-01-pulsar-summit-asia-2020-cfp.md
deleted file mode 100644
index aed413c8331..00000000000
--- a/site2/website/blog/2020-09-01-pulsar-summit-asia-2020-cfp.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-author: Jennifer Huang
-authorURL: https://twitter.com/Jennife06125739
-title: Pulsar Summit Asia 2020 CFP is now open
-
----
-
-The Pulsar Summit is an annual conference dedicated to the Apache Pulsar community. The summit brings together an international audience of CTOs/CIOs, developers, data architects, data scientists, Apache Pulsar committers/contributors, and the messaging and streaming community. Together, they share experiences, ideas, and insights on Pulsar and its growing community, and receive hands-on training sessions led by Pulsar experts.
-
-After a very successful Pulsar Summit Virtual Conference in June, we have decided to present our Pulsar Summit Asia 2020 in the same way on November 28-29, 2020. The two-day conference will be free to attend! Are you interested in presenting? Suggested topics include Pulsar use cases, operations, technology deep dive, and ecosystem. CFP and registration are now open!
-
-
-
-## Speak at Pulsar Summit
-The opportunity to speak at the second global Pulsar Summit is a great chance to participate in the rapidly growing Apache Pulsar community. Join us for the opportunity to be on stage with top Pulsar thought-leaders, including Apache Pulsar PMC members Sijie Guo and Jia Zhai from [StreamNative](https://streamnative.io/), Penghui Li from Zhaopin.com, Nozomi Kurihara from [Yahoo Japan Corporation](https://about.yahoo.co.jp/), and other community leaders such as Dezhi Liu from [Tencent](htt [...]
-
-If you have questions about submitting a proposal, or want some feedback or advice in general, please do not hesitate to reach out to [organizers@pulsar-summit.org](mailto:organizers@pulsar-summit.org). We are happy to help out! Details are available on the [CFP website](https://pulsar-summit.org/en/event/asia-2020/cfp).
-
-## Dates to remember
-- CFP opens: September 1, 2020
-- CFP closes: October 21, 2020 - 23:59 (CST: China Standard Time/UTC+8 time zone)
-- CFP notification: October 28, 2020
-- Schedule announcement: November 4, 2020
-
-## Speaker benefits
-When your speaking proposal is approved, you will enjoy the following benefits:
-
-- The opportunity to expand your network and raise your profile in the Apache Pulsar community.
-- The chance to demonstrate your experience and deep knowledge in the rapidly growing event streaming space.
-- Your name, title, company, and bio will be featured on the Pulsar Summit Asia 2020 website.
-- Your session will be added to the Pulsar Summit YouTube Channel and promoted on Twitter and LinkedIn.
-- A professionally produced video of your presentation.
-
-## Speaker requirements
-In addition to your talk, we ask that you actively participate in promoting the event via your personal and company channels. These include posting on your Twitter, LinkedIn, WeChat, Weibo, blog and other channels. We would also like to work directly with your marketing team on co-marketing opportunities. These include, but are not limited to, posting to your company’s Twitter, LinkedIn, WeChat and other developer communities and sending a dedicated Pulsar Summit email to your company’s [...]
-
-## Registration
-If you are interested in attending Pulsar Summit Asia 2020, please sign in Hopin and [checkout our event](https://hopin.to/events/pulsar-summit-asia-2020). Your ideas are very important to us, and we will prepare the content accordingly.
-
-After you checkout the event in Hopin, you will be notified with the event update at the first time when announcing.
-
-## Sponsor Pulsar Summit
-Pulsar Summit is a community run conference and your support is needed. Sponsoring this event will provide a great opportunity for your organization to further engage with the Apache Pulsar community. [Contact us](mailto:partners@pulsar-summit.org) to learn more.
-
-Help us make #PulsarSummit 2020 a big success by spreading the word and submitting your proposal! Follow us on Twitter ([@pulsarsummit](https://twitter.com/PulsarSummit)) to receive the latest updates of the conference!
-
-Hope to see you at Pulsar Summit Asia 2020!
-
-## About Apache Pulsar
-Apache Pulsar is a cloud-native, distributed messaging and streaming platform that manages hundreds of billions of events per day. Pulsar was originally developed and deployed inside Yahoo as the consolidated messaging platform connecting critical Yahoo applications such as Yahoo Finance, Yahoo Mail, and Flickr, to data. Pulsar was contributed to open source by Yahoo in 2016 and became a top-level Apache Software Foundation project in 2018.
-
-## About StreamNative
-StreamNative is the organizer of Pulsar Summit Asia 2020. StreamNative is enabling organizations to build the next generation of messaging and event streaming applications. Leveraging Apache Pulsar and BookKeeper, we optimize for scalability and resiliency while reducing the overhead management and complexity required by incumbent technologies. We do this by offering Pulsar and StreamNative’s "products as a service". StreamNative is building a world-class team that is passionate about bu [...]
diff --git a/site2/website/blog/2020-11-04-pulsar-summit-asia-schedule.md b/site2/website/blog/2020-11-04-pulsar-summit-asia-schedule.md
deleted file mode 100644
index 5fdc4b7e01d..00000000000
--- a/site2/website/blog/2020-11-04-pulsar-summit-asia-schedule.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-author: Carolyn King, Dianjin Wang
-title: Pulsar Summit Asia 2020 Schedule is Now Online
----
-
-The Pulsar Summit is a global conference dedicated to sharing best practices, project updates, and insights across the Apache Pulsar community. Pulsar’s inaugural global summit, the [Pulsar Summit Virtual Conference 2020](https://pulsar-summit.org/en/event/virtual-conference-2020), took place in June 2020 and featured more than 30 sessions from top Pulsar experts, developers and thought-leaders from companies such as Salesforce, Verizon Media, and Splunk, and the conference attracted 600 [...]
-
-The rapid adoption of Apache Pulsar over the past few years has led to a high demand for Pulsar events. Today, StreamNative, a cloud-native event streaming company powered by Apache Pulsar, and also the host of [Pulsar Summit Asia 2020](https://pulsar-summit.org/en/event/asia-2020), announced more details on the upcoming event. Taking place on November 28th & 29th, the two-day event will feature more than 30 live sessions by tech leads, open-source developers, software engineers, and sof [...]
-
-See below for some of our featured sessions, which include both English and Mandarin tracks:
-- [How Splunk is using Pulsar IO （English）](https://pulsar-summit.org/en/event/asia-2020/sessions/how-splunk-is-using-pulsar-io) - In this talk, Jerry Peng, Principal Software Engineer at Splunk will share insights on Splunk’s evaluation and decision to adopt the Pulsar IO framework, details on how Splunk's DSP product leverages the Pulsar IO framework, and insights on batch sources, a feature that was recently added to Pulsar IO.
-- [Apache Pulsar at Yahoo! JAPAN - Adoption, Operational Insights and the Future（English）](https://pulsar-summit.org/en/event/asia-2020/sessions/apache–pulsar–at–yahoo–japan–adoption–operational–experiences–and–future) - In this talk, Nozomi Kurihara, Manager of the Messaging Platform team in Yahoo!Japan Corporation will share practical use cases of Apache Pulsar on production and insights on how to operate Apache Pulsar for large scale data streams.
-- [Running Apache Pulsar on Tencent Cloud: New Challenges, Discussion, Practice (Mandarin)](https://pulsar-summit.org/en/event/asia-2020/sessions/running-apache-pulsar-on-tencent-cloud-new-challenges-discussion-practice) - In this talk, Lin Lin, senior engineer of Tencent Cloud will address how Pulsar helps solve challenges with message queues on Tencent Cloud, such as dynamic expansion and contraction, and large numbers of partitions.
-- [How BIGO built a Real-Time Message System with Apache Pulsar and Flink (Mandarin) ](https://pulsar-summit.org/en/event/asia-2020/sessions/how-bigo-builds-real-time-message-system-with-apache-pulsar-and-flink) - In this talk, Hang Chen, Leader of the Messaging Platform team from BIGO will share how BIGO leveraged Apache Pulsar to build a real-time message system and how they tune Pulsar for production.
-- [A Daredevil' Story: Apache Pulsar in Zhaopin.com (Mandarin)](https://pulsar-summit.org/en/event/asia-2020/sessions/a-daredevil-story-apache-pulsar-in-zhaopin-com) - In this talk, Shunli Gao, Senior Engineer at Zhaopin will share details on the development and future prospects of Apache Pulsar at Zhaopin.
-- [Transactional Event Streaming with Apache Pulsar (Mandarin)](https://pulsar-summit.org/en/event/asia-2020/sessions/transactional-event-streaming-with-apache-pulsar) - In this talk, Bo Cong, software engineer at StreamNative will share how Pulsar transaction works and how it is supported by Pulsar Functions.
-- [Benchmarking Pulsar vs. Kafka on AWS: Process & Results (Mandarin) ](https://pulsar-summit.org/en/event/asia-2020/sessions/benchmarking-pulsar-vs-kafka-on-aws-process-results) - In this talk, Penghui Li, the Apache Pulsar PMC member and software engineer at StreamNative will share the results of a benchmark test comparing Pulsar and Kafka that was run on AWS. The test ran Pulsar and Kafka under the same hardware environments on the write throughput, tailing read throughput, catchup re [...]
-
-More featured talks coming soon!
-
-The number and diversity of the sessions demonstrate the accelerated adoption of Pulsar in PoC and production environments, as well as the rapid development in functionalities and diverse ecosystems. To learn more about how companies leverage Pulsar for **messaging and event streaming, serverless computing, real-time analytics, event-driven applications, and mission-critical deployment management in production**, [RSVP](https://hopin.to/events/pulsar-summit-asia-2020) today!
-
-We would like to say special thanks to the speakers for sharing their Pulsar expertise and experience with the community.
-
-
-# About Apache Pulsar
-[Apache Pulsar](https://pulsar.apache.org) is a cloud-native, distributed messaging and streaming platform that manages hundreds of billions of events per day. Pulsar was originally developed at Yahoo! as the unified messaging platform connecting critical Yahoo applications such as Yahoo Finance, Yahoo Mail, and Flickr to data.
-
-Today, Pulsar is used for real-time event streaming use cases, including data pipelines, microservices, and stream processing. Its cloud-native architecture and built-in multi-tenancy differentiate it from its predecessors and uniquely position it as an enterprise-ready, event streaming platform. Pulsar's multi-layer architecture enables stability, reliability, scalability, and high performance, simplifies management and reduces costs. Its built-in multi-tenancy and geo-replication ensur [...]
-
-
-# About StreamNative
-[StreamNative](https://streamnative.io), founded by the original developers of Apache Pulsar and Apache BookKeeper, enables organizations to build the next generation of messaging and event streaming applications. Leveraging Apache Pulsar and BookKeeper, we optimize for scalability and resiliency while reducing the overhead management and complexity required by incumbent technologies. We do this by offering Pulsar and StreamNative’s ‘products as a service’. StreamNative is building a wor [...]
diff --git a/site2/website/blog/2020-11-09-Apache-Pulsar-2-6-2.md b/site2/website/blog/2020-11-09-Apache-Pulsar-2-6-2.md
deleted file mode 100644
index 3bf2f93bb78..00000000000
--- a/site2/website/blog/2020-11-09-Apache-Pulsar-2-6-2.md
+++ /dev/null
@@ -1,326 +0,0 @@
----
-author: Xiaolong Ran
-authorURL: https://twitter.com/wolf4j1
-title: Apache Pulsar 2.6.2
----
-We are excited to see that the Apache Pulsar community has successfully released the 2.6.2 version after a lot of hard work. It is a great milestone for this fast-growing project and the Pulsar community. 2.6.2 is the result of a big effort from the community, with over 154 commits and a long list of improvements and bug fixes.
-
-Here are some highlights and major features added in Pulsar 2.6.2.
-
-<!--truncate-->
-
-## Broker
-
-### Catch `throwable` when starting Pulsar
-
-Before 2.6.2, Pulsar catched exceptions only when `BrokerStarter.start()` failed. Some errors such as `NoSuchMethodError` or `NoClassDefFoundError` could not be caught, and Pulsar was in abnormal status yet no error log was found in the log file.
-
-In 2.6.2, we modify exceptions to use `throwable` to avoid this issue.
-
-For more information about implementation, see [PR-7221](https://github.com/apache/pulsar/pull/7221).
-
-### Handle SubscriptionBusyException in resetCursor API
-
-In `PersistentSubscription.resetCursor` method, `SubscriptionFencedException` is thrown in several places, but it is not handled in `PersistentTopicBase`, so error messages are not clear.
-
-In 2.6.2, we export `SubscriptionBusyException` in `PersistentTopicBase` for `resetCursor`, so error messages in the REST API are clear.
-
-For more information about implementation, see [PR-7335](https://github.com/apache/pulsar/pull/7335).
-
-### Update Jersey to 2.31
-
-Before 2.6.1, Pulsar used the Jersey 2.27, which has security concerns. In Pulsar 2.6.2, we update the Jersey version to the latest stable version(2.31) to enhance security.
-
-For more information about implementation, see [PR-7515](https://github.com/apache/pulsar/pull/7515).
-
-### Stop to dispatch when consumers using the Key_Shared subscription stuck
-
-Consumers using the `Key_Shared` subscription would encounter disorder messages occasionally. The following are steps to reproduce the situation:
-
-1. Connect Consumer1 to Key_Shared subscription `sub` and stop to receive
- - receiverQueueSize: 500
-2. Connect Producer and publish 500 messages with key `(i % 10)`
-3. Connect Consumer2 to same subscription and start to receive
- - receiverQueueSize: 1
- - since https://github.com/apache/pulsar/pull/7106, Consumer2 can't receive (expected)
-4. Producer publish more 500 messages with same key generation algorithm
-5. After that, Consumer1 start to receive
-6. Check Consumer2 message ordering
- - sometimes message ordering was broken in same key
-
-In 2.6.2, when consumers use the Key_Shared subscription, Pulsar stops dispatching messages to consumers that are stuck on delivery to guarantee message order.
-
-For more information about implementation, see [PR-7553](https://github.com/apache/pulsar/pull/7553).
-
-### Reestablish namespace bundle ownership from false negative releasing and false positive acquiring
-
-In acquiring/releasing namespace bundle ownership, ZooKeeper might be disconnected before or after these operations are persisted in the ZooKeeper cluster. It leads to inconsistency between the local ownership cache and ZooKeeper cluster.
-
-In 2.6.2, we fix the issue with the following:
-
-* In ownership releasing, do not retain ownership in failure.
-* In ownership checking, querying and acquiring, reestablish the lost ownership in false negative releasing and false positive acquiring.
-
-For more information about implementation, see [PR-7773](https://github.com/apache/pulsar/pull/7773).
-
-### Enable users to configure the executor pool size
-
-Before 2.6.2, the executor pool size in Pulsar was set to `20` when starting Pulsar services. Users could not configure the executor pool size.
-
-```
-private final ScheduledExecutorService executor = Executors.newScheduledThreadPool(20,
- new DefaultThreadFactory("pulsar"));
-```
-
-In 2.6.2, users can configure the executor pool size in the `broker.conf` file based on their needs.
-
-For more information about implementation, see [PR-7782](https://github.com/apache/pulsar/pull/7782).
-
-### Add replicated check for `checkInactiveSubscriptions`
-
-After the replicated subscription is deleted by `checkInactiveSubscriptions`, replicated subscriptions are created with `receiveSubscriptionUpdated`. In this case, the position becomes the latest position.
-
-```
-topic.createSubscription(update.getSubscriptionName(),
- InitialPosition.Latest, true /* replicateSubscriptionState */);
-```
-
-In 2.6.2, the replicated subscription is excluded from automatic deletion by fixing the `PersistentTopic`.
-
-For more information about implementation, see [PR-8066](https://github.com/apache/pulsar/pull/8066).
-
-### Upgrade jetty-util version to 9.4.31
-
-Pulsar client depends on jetty-util. Jetty-util versions earlier than 9.4.30 contain known vulnerabilities.
-
-In 2.6.2, we upgrade the jetty-util version to `9.4.31` to enhance security.
-
-For more information about implementation, see [PR-8035](https://github.com/apache/pulsar/pull/8035).
-
-### Add command to delete a cluster's metadata from ZooKeeper
-
-When we share the same ZooKeeper and BookKeeper cluster among multiple broker clusters, if a cluster was removed, its metadata in ZooKeeper were also removed.
-
-In 2.6.2, we fix the issue in the following ways:
-
-- Add a `PulsarClusterMetadataTeardown` class to delete the relative nodes from ZooKeeper;
-- Wrap the class to `bin/pulsar` script.
-
-For more information about implementation, see [PR-8169](https://github.com/apache/pulsar/pull/8169).
-
-### Replace EventLoop with ThreadPoolExecutor to improve performance instead of EventLoop
-
-In 2.6.2, we replace EventLoop with a native JDK thread pool(ThreadPoolExecutor) to improve performance.
-
-The following is the test result with pulsar perf.
-
-Before 2.6.1:
-
-```
-Aggregated throughput stats --- 11715556 records received --- 68813.420 msg/s --- 537.605 Mbit/s
-```
-
-In 2.6.2：
-
-```
-Aggregated throughput stats --- 18392800 records received --- 133314.602 msg/s --- 1041.520 Mbit/s
-```
-
-For more information about implementation, see [PR-8208](https://github.com/apache/pulsar/pull/8208).
-
-### Fix deadlock that occurred during topic ownership check
-
-Some broker servers had deadlocks while splitting namespace bundles. When checking the thread dump of the broker, some threads were blocked in `NamespaceService#getBundle()`.
-
-```
-"pulsar-ordered-OrderedExecutor-7-0" #34 prio=5 os_prio=0 tid=0x00007eeeab05a800 nid=0x81a5 waiting on condition [0x00007eeeafbd2000]
- java.lang.Thread.State: WAITING (parking)
- at sun.misc.Unsafe.park(Native Method)
- - parking to wait for <0x00007f17fa965418> (a java.util.concurrent.CompletableFuture$Signaller)
- at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
- at org.apache.pulsar.common.naming.NamespaceBundleFactory.getBundles(NamespaceBundleFactory.java:155)
-...
-```
-
-The reason for the issue is that the `getBundle()` method leads to deadlock in `NamespaceService#isTopicOwned()`. To fix the issue, we remove the `getBundle()` method. When `isTopicOwned()` returns `false`, the bundle metadata is cached and can be got asynchronously. When the client reconnects the next time, Pulsar returns the correct bundle metadata from the cache.
-
-For more information about implementation, see [PR-8406](https://github.com/apache/pulsar/pull/8406).
-
-## Proxy
-
-### Enable users to configure `advertisedAddress` in proxy
-
-Before 2.6.2, users could not configure `advertisedAddress` on the proxy side. In 2.6.2, users can configure `advertisedAddress` in proxy just as they do in Pulsar broker.
-
-For more information about implementation, see [PR-7542](https://github.com/apache/pulsar/pull/7542).
-
-### Add proxy plugin interface to support user defined additional servlet
-
-To enable users to access the broker flexibly, Pulsar provides plugins similar to broker protocol and broker interceptor. However, users could not access the proxy before 2.6.2.
-
-To enable users to customize data requests in proxy, we add the protocol plugin for proxy in 2.6.2.
-
-For more information about implementation, see [PR-8067](https://github.com/apache/pulsar/pull/8067).
-
-### Fix the null exception when starting the proxy service
-
-When enabling the broker TLS and broker client authentication with OAuth2 plugin,
-the proxy service exits with an unexpected null exception.
-
-The reason is that when initializing the flow, authentication is called, so the token client is not initialized before using.
-
-In 2.6.2, we fix the null exception when starting the proxy service.
-
-For more information about implementation, see [PR-8019](https://github.com/apache/pulsar/pull/8019).
-
-## Java Client
-
-### Support input-stream for trustStore cert
-
-In 2.6.1, Pulsar supports dynamic cert loading by using input stream for TLS cert and key file. The feature is mainly used by container. However, container also requires dynamic loading for truststore certs and users cannot store trust-store cert into file-system.
-
-In 2.6.2, Pulsar supports loading truststore cert dynamically using input stream.
-
-For more information about implementation, see [PR-7442](https://github.com/apache/pulsar/pull/7442).
-
-### Avoid subscribing the same topic
-
-The current key of `MultiTopicsConsumerImpl.topics` is the topic name passed by the user. The `topicNameValid` method checks if the name is valid and `topics` doesn't contain the key.
-
-However, if a multi-topic consumer subscribes a partition of a subscribed partitioned topic, `subscribeAsync` succeeds and a new `ConsumerImpl` of the same partition is created, which is redundant.
-
-Also, if a multi-topic consumer subscribes `public/default/topic` or `persistent://public/default/topic`, while the initial subscribed topic is `topic`, the redundant consumers would be created.
-
-In 2.6.2, we fix the issue in the following ways to avoid subscribing the same topic again:
-
-- Use the full topic name as key for `MultiTopicsConsumerImpl.topics`.
-- Check that both the full topic name and the full partitioned topic name do not exist in `MultiTopicsConsumerImpl.topics` when `subscribeAsync` is called.
-- Throw a different exception to a different topic is invalid and the topic is already subscribed
-
-For more information about implementation, see [PR-7823](https://github.com/apache/pulsar/pull/7823).
-
-## CPP Client
-
-### Wait for all seek operations complete
-
-When a partitioned consumer calls `seek`, it waits for only one partition's seek operation completion because each internal consumer calls callback(result) to complete the same promise.
-
-In 2.6.2, we use the following methods to avoid this problem:
-
-- Add a `MultiResultCallback` implementation, the callback completes only when all N events complete successfully or one of N events fails.
-- Use `MultiResultCallback` to wrap callback from `PartitionedConsumerImpl::seekAsync`.
-
-For more information about implementation, see [PR-7216](https://github.com/apache/pulsar/pull/7216).
-
-### Make `clear()` thread-safe
-
-Before 2.6.2, the `clear()` methods of `BatchAcknowledgementTracker` and `UnAckedMessageTrackerEnabled` are not thread-safe.
-
-In 2.6.2, we acquire a mutex in these `clear()` methods to make it thread-safe.
-
-For more information about implementation, see [PR-7862](https://github.com/apache/pulsar/pull/7862).
-
-### Add Snappy library to Docker images for building C++ packages
-
-The program crashes when Snappy compression is enabled on the C++ client packaged as RPM/DEB. This is because Snappy library is not included in the Docker image for building the RPM/DEB package.
-
-In 2.6.2, we add the Snappy library to the docker images to avoid the issue.
-
-For more information about implementation, see [PR-8086](https://github.com/apache/pulsar/pull/8086).
-
-### Support key based batching
-
-Support key based batching for the C++ client. In addition, currently, the implementation of `BatchMessageContainer` is coupling to `ProducerImpl` tightly. The batch message container registers a timer to the producer's executor and the timeout callback is also the producer's method. Even its `add` method could call `sendMessage` to send a batch to the producer's pending queue. These should be the producer's work.
-
-In 2.6.2, we implement the feature in the following ways:
-
-- Add a `MessageAndCallbackBatch` to store a `MessageImpl` of serialized single messages and a callback list.
-- Add a `BatchMessageContainerBase` to provide interface methods and methods like update/clear message number/bytes, create `OpSendMsg`.
-- Let `ProducerImpl` manage the batch timer and determine whether to create `OpSendMsg` from `BatchMessageContainerBase` and send it.
-- Make `BatchMessageContainer` inherit `BatchMessageContainerBase`, it only manages a `MessageAndCallbackBatch`.
-- Add a `BatchMessageKeyBasedContainer` that inherits `BatchMessageContainerBase`, it manages a map of message key and `MessageAndCallbackBatch`.
-- Add a producer config to change batching type.
-
-For more information about implementation, see [PR-7996](https://github.com/apache/pulsar/pull/7996).
-
-## Functions
-
-### Enable Kubernetes runtime to customize function instance class path
-
-Before 2.6.2, the function worker's classpath is used to configure the function instance (runner)'s classpath. When the broker (function worker) uses an image that is different from the function instance (runner) for Kubernetes runtime, the classpath is wrong and the function instance could not load the instance classes.
-
-In 2.6.2, we add a function instance classpath entry to the Kubernetes runtime config, and construct the function launch command accordingly.
-
-For more information about implementation, see [PR-7844](https://github.com/apache/pulsar/pull/7844).
-
-### Set `dryrun` of Kubernetes Runtime to null
-
-Before 2.6.2, we upgraded the `client-java` of Kubernetes to `0.9.2` to enhance security. However, during the creation of statefulsets, secrets, and services, the value of `dryrun` was set to `true`, which was not accepted by Kubernetes. Only `All` is allowed in Kubernetes.
-
-In 2.6.2, we set the `dryrun` of Kubernetes Runtime to null.
-
-For more information about implementation, see [PR-8064](https://github.com/apache/pulsar/pull/8064).
-
-## Pulsar SQL
-
-### Upgrade Presto version to 332
-
-Upgrade Presto version to 332. Resolve different packages between prestosql and prestodb. Although the latest version is 334, versions higher than 333 require Java 11.
-
-For more information about implementation, see [PR-7194](https://github.com/apache/pulsar/pull/7194).
-
-## pulsar-admin
-
-### Add CLI command to get the last message ID
-
-Add `last-message-id` command in CLI, so users can get the last message ID with this command.
-
-For more information about implementation, see [PR-8082](https://github.com/apache/pulsar/pull/8082).
-
-### Support deleting schema ledgers when deleting topics
-
-Users could not delete schema of topics with the `PersistentTopics#deleteTopic` and `PersistentTopics#deletePartitionedTopic` in REST APIs. After topics were deleted, the schema ledgers still existed with adding an empty schema ledger.
-
-In 2.6.2, we implement the feature in the following ways:
-
-- Add a `deleteSchema` query param to REST APIs of deleting topics/partitioned topics;
-- Add a map to record the created ledgers in `BookkeeperSchemaStorage`;
-- Expose `deleteSchema` param in pulsar-admin APIs;
-- Delete schema ledgers when deleting the cluster with `-a` option.
-
-For more information about implementation, see [PR-8167](https://github.com/apache/pulsar/pull/8167).
-
-### Support deleting all data associated with a cluster
-
-When multiple broker clusters shared the same bookie cluster, if users wanted to remove a broker cluster, the associated ledgers in bookies were not deleted as expected.
-
-In 2.6.2, we add a `cluster delete` command to enable users to delete all the data associated with the cluster.
-
-For more information about implementation, see [PR-8133](https://github.com/apache/pulsar/pull/8133).
-
-## Pulsar Perf
-
-### Enable users to configure ioThread number in pulsar-perf
-
-In pulsar-perf, the default Pulsar client ioThread number is `Runtime.getRuntime().availableProcessors()` and users could not configure it in the command line. When running a pulsar-perf producer, it may cause messages to enqueue competition and lead to high latency.
-
-In 2.6.2, we implement the feature in the following ways:
-
-1. Enable users to configure the ioThread number in the command line;
-2. Change the default ioThead number from `Runtime.getRuntime().availableProcessors()` to `1`
-
-For more information about implementation, see [PR-8090](https://github.com/apache/pulsar/pull/8090).
-
-## More information
-
-- To download Apache Pulsar 2.6.2, click [download](https://pulsar.apache.org/en/download/).
-- For more information about Apache Pulsar 2.6.2, see [2.6.2 release notes](https://pulsar.apache.org/release-notes/#2.6.2 and [2.6.2 PR list](https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.6.2+is%3Aclosed).
-
-If you have any questions or suggestions, contact us with mailing lists or slack.
-
-- [users@pulsar.apache.org](mailto:users@pulsar.apache.org)
-- [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-- Pulsar slack channel: https://apache-pulsar.slack.com/
-- Self-registration at https://apache-pulsar.herokuapp.com/
-
-Looking forward to your contributions to [Pulsar](https://github.com/apache/pulsar).
diff --git a/site2/website/blog/2020-12-24-Apache-Pulsar-2-7-0.md b/site2/website/blog/2020-12-24-Apache-Pulsar-2-7-0.md
deleted file mode 100644
index 92449682512..00000000000
--- a/site2/website/blog/2020-12-24-Apache-Pulsar-2-7-0.md
+++ /dev/null
@@ -1,148 +0,0 @@
----
-author: Penghui Li
-authorURL: https://twitter.com/lipenghui6
-title: Apache Pulsar 2.7.0
----
-We are very glad to see the Apache Pulsar community has successfully released the wonderful 2.7.0 version after accumulated hard work. It is a great milestone for this fast-growing project and the whole Pulsar community. This is the result of a huge effort from the community, with over 450 commits and a long list of new features, improvements, and bug fixes.
-
-Here is a selection of the most interesting and major features added to Pulsar 2.7.0.
-
-<!--truncate-->
-
-## Major features
-
-### Transaction support
-
-Transactional semantics enable event streaming applications to consume, process, and produce messages in one atomic operation. With transactions, Pulsar achieves the exactly-once semantics for a single partition and multiple partitions as well. This enables new use cases with Pulsar where a client (either as a producer or consumer) can work with messages across multiple topics and partitions and ensure those messages will all be processed as a single unit. This will strengthen the messag [...]
-
-Currently, Pulsar transactions are in developer preview. The community will work further to enhance the feature to be used in the production environment soon.
-
-To enable transactions in Pulsar, you need to configure the parameter in the `broker.conf` file.
-
-```
-transactionCoordinatorEnabled=true
-```
-
-Initialize transaction coordinator metadata, so the transaction coordinators can leverage advantages of the partitioned topic, such as load balance.
-
-```
-bin/pulsar initialize-transaction-coordinator-metadata -cs 127.0.0.1:2181 -c standalone
-```
-
-From the client-side, you can also enable the transactions for the Pulsar client.
-
-```java
-PulsarClient pulsarClient = PulsarClient.builder()
- .serviceUrl("pulsar://localhost:6650")
- .enableTransaction(true)
- .build();
-```
-
-Here is an example to demonstrate the Pulsar transactions.
-
-```java
-// Open a transaction
-Transaction txn = pulsarClient
- .newTransaction()
- .withTransactionTimeout(5, TimeUnit.MINUTES)
- .build()
- .get();
-
-// Publish messages with the transaction
-producer.newMessage(txn).value("Hello Pulsar Transaction".getBytes()).send();
-
-// Consume and acknowledge messages with the transaction
-Message<byte[]> message = consumer.receive();
-consumer.acknowledgeAsync(message.getMessageId(), txn);
-
-// Commit the transaction
-txn.commit()
-```
-For more details about the Pulsar transactions, refer to [here](http://pulsar.apache.org/docs/en/transactions/). For more details about the design of Pulsar transactions, refer to [here](https://github.com/apache/pulsar/wiki/PIP-31%3A-Transaction-Support).
-
-### Topic level policy
-
-Pulsar 2.7.0 introduces the system topic which can maintain all policy change events to achieve the topic level policy. All policies at the namespace level are now also available at the topic level, so users can set different policies at the topic level flexibly without using lots of metadata service resources. The topic level policy enables users to manage topics more flexibly and adds no burden to ZooKeeper.
-
-To enable topic level policy in Pulsar, you need to configure the parameter in the `broker.conf` file.
-
-```
-systemTopicEnabled=true
-topicLevelPoliciesEnabled=true
-```
-
-After topic level policy is enabled, you can use Pulsar Admin to update the policy of a topic. Here is an example for setting the data retention for a specific topic.
-
-```
-bin/pulsar-admin topics set-retention -s 10G -t 7d persistent://public/default/my-topic
-```
-
-For more details about the system topic and topic level policy, refer to [here](https://github.com/apache/pulsar/wiki/PIP-39%3A-Namespace-Change-Events)
-
-### Support Azure BlobStore offloader
-
-In Pulsar 2.7.0, we add support for Azure BlobStore offloader, which allows users to offload topic data into Azure BlobStore. You can configure the Azure BlobStore offloader driver in the configuration `broker.conf` file.
-
-```
-managedLedgerOffloadDriver=azureblob
-```
-
-For more details, refer to [here](https://github.com/apache/pulsar/pull/8436).
-
-### Native protobuf schema support
-
-Pulsar 2.7.0 introduces a native protobuf schema support, which can provide more ability for protobuf users who want to integrate with Pulsar. Here is an example to show how to use native protobuf schema in Java client:
-
-```java
-Consumer<PBMessage> consumer = client.newConsumer(Schema.PROTOBUFNATIVE(PBMessage.class))
-.topic(topic)
-.subscriptionName("my-subscription-name")
-.subscribe();
-```
-
-For more details, refer to [here](https://github.com/apache/pulsar/pull/8372).
-
-### Resource limitation
-
-In Pulsar, tenant, namespace, and topic are the core resources of a cluster. Pulsar 2.7.0 enables you to limit the maximum tenants of a cluster, the maximum namespaces per tenant, the maximum topics per namespace, and the maximum subscriptions per topic.
-
-You can configure the resource limitations in the `broker.conf` file.
-
-```
-maxTenants=0
-maxNamespacesPerTenant=0
-maxTopicsPerNamespace=0
-maxSubscriptionsPerTopic=0
-```
-
-This provides Pulsar administrators with great convenience in resource management.
-
-### Support e2e encryption for Pulsar Functions
-
-Pulsar 2.7.0 enables you to add End-to-End (e2e) encryption for Pulsar Functions. You can use the public and private key pair that the application configured to perform encryption. Only consumers with a valid key can decrypt encrypted messages.
-
-To enable End-to-End encryption on Functions Worker, you can set it by specifying `--producer-config` in the command line terminal. For more information, refer to [Pulsar Encryption](http://pulsar.apache.org/docs/en/security-encryption/).
-
-For more details, you can see [here](https://github.com/apache/pulsar/pull/8432)
-
-### Function rebalance
-
-Before 2.7.0, there was no mechanism for rebalancing functions scheduler on workers. The workload for functions m become skewed. Pulsar 2.7.0 supports manual trigger functions rebalance and automatic periodic functions rebalance.
-
-For more details, refer to https://github.com/apache/pulsar/pull/7388 and https://github.com/apache/pulsar/pull/7449.
-
-## More information
-
-- To download Apache Pulsar 2.7.0, click [here](https://pulsar.apache.org/en/download/).
-- For more information about Apache Pulsar 2.7.0, see [2.7.0 release notes](https://pulsar.apache.org/release-notes/#2.7.0) and [2.7.0 PR list](https://github.com/apache/pulsar/pulls?q=milestone%3A2.7.0+-label%3Arelease%2F2.6.2+-label%3Arelease%2F2.6.1+).
-
-If you have any questions or suggestions, contact us with mailing lists or slack.
-
-- [users@pulsar.apache.org](mailto:users@pulsar.apache.org)
-- [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-- Pulsar slack channel: https://apache-pulsar.slack.com/
-- Self-registration at https://apache-pulsar.herokuapp.com/
-
-Looking forward to your contributions to [Apache Pulsar](https://github.com/apache/pulsar).
-
-
diff --git a/site2/website/blog/2021-05-13-Apache-Pulsar-2-7-2.md b/site2/website/blog/2021-05-13-Apache-Pulsar-2-7-2.md
deleted file mode 100644
index f93a2012701..00000000000
--- a/site2/website/blog/2021-05-13-Apache-Pulsar-2-7-2.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-author: Enrico Olivelli
-authorURL: https://twitter.com/eolivelli
-title: Apache Pulsar 2.7.2
----
-We are very glad to see the Apache Pulsar community has successfully released the 2.7.2 version.
-This is a minor release that introduces stability fixes and a few new features without breaking changes.
-
-<!--truncate-->
-
-### News and noteworthy
-
-Here is a selection of the most awesome and major enhancements added to Pulsar 2.7.2.
-
-- Improvement in stability in the Kinesis connector [#10420](https://github.com/apache/pulsar/pull/10420).
-- Improvement in passing ENV variables to the bookie (PULSAR_EXTRA_OPTS) [#10397](https://github.com/apache/pulsar/pull/10397).
-- Allow the C++ client to be built in Windows and add CI for verification [#10387](https://github.com/apache/pulsar/pull/10387).
-- Allow activating every BookKeeper client features in the broker [#9232](https://github.com/apache/pulsar/pull/9232).
-- Improvement in Pulsar proxy.
-- Upgrade core networking libraries: Jetty and Netty.
-
-[Here](https://github.com/apache/pulsar/pulls?page=1&q=is%3Apr+label%3Arelease%2F2.7.2]) you can find the list of all the improvements and bug fixes.
-
-### Contributors for 2.7.2 release
-
-We would like to thank all the contributors for this release.
-Same to other sustainable open source projects, Apache Pulsar is great because it is supported by a vibrant community.
-
-Code contributors (names taken from GitHub API):
-Ali Ahmed, Andrey Yegorov, Binbin Guo, David Kjerrumgaard, Deon van der Vyver, Devin Bost, Enrico Olivelli, Guangning E, Kevin Wilson,
-Lari Hotari, Marvin Cai, Masahiro Sakamoto, Matteo Merli, Michael Marshall, Rajan Dhabalia, Shen Liu, Ting Yuan, Vincent Royer,
-Yong Zhang, Yunze Xu, Zhanpeng Wu, Zike Yang, baomingyu, CongBo, dockerzhang, feynmanlin, hangc0276, li jinquan, limingnihao,
-linlinnn, mlyahmed, PengHui Li, Ran.
-
-Documentation contributors:
-Anonymitaet (Yu Liu), Jennifer Huang
-
-Also, we want to thank everyone who spent his time reporting issues and sharing the story about using Pulsar.
-
-Looking forward to your contributions to [Apache Pulsar](https://github.com/apache/pulsar).
diff --git a/site2/website/blog/2021-06-12-Apache-Pulsar-2-8-0.md b/site2/website/blog/2021-06-12-Apache-Pulsar-2-8-0.md
deleted file mode 100644
index a9ac5c0ab4a..00000000000
--- a/site2/website/blog/2021-06-12-Apache-Pulsar-2-8-0.md
+++ /dev/null
@@ -1,149 +0,0 @@
----
-author: Matteo Merli, Sijie Guo
-title: Apache Pulsar 2.8.0
----
-
-# An Overview of the 2.8.0 Release
-
-We are very glad to see the Apache Pulsar community has successfully released the 2.8.0 version, which includes a number of exciting upgrades and enhancements. This blog provides a deep dive into the updates from the 2.8.0 release as well as a detailed look at the major Pulsar developments that have helped it evolve into the unified messaging and streaming platform it is today.
-
-Note: The Pulsar community typically releases a major release every 3 months, but it has been 6 months since the release of 2.7.0. We spent more time on 2.8.0 in order to make the transaction API generally available to the Pulsar community.
-
-# Release 2.8 Overview
-
-The key features and updates in this release are:
-- Exclusive Producer
-- Package Management API
-- Simplified Client Memory Limit Settings
-- Broker Entry Metadata
-- New Protobuf Code Generator
-- Transactions
-
-## Exclusive Producer
-
-By default, the Pulsar producer API provides a “multi-writer” semantic to append messages to a topic. However, there are several use cases that require exclusive access for a single writer, such as ensuring a linear non-interleaved history of messages or providing a mechanism for leader election.
-
-This new feature allows applications to require exclusive producer access in order to achieve a “single-writer” situation. It guarantees that there should be 1 single writer in any combination of errors. If the producer loses its exclusive access, no more messages from it can be published on the topic.
-
-One use case for this feature is the metadata controller in Pulsar Functions. In order to write a single linear history of all the functions metadata updates, the metadata controller requires to elect one leader and that all the “decisions” made by this leader be written on the metadata topic. By leveraging the exclusive producer feature, Pulsar guarantees that the metadata topic contains different segments of updates, one per each successive leader, and there is no interleaving across d [...]
-
-## Package Management API
-
-Since its introduction in version 2.0, the Functions API has become hugely popular among Pulsar users. While it offers many benefits, there are a number of ways to improve the user experience. For example, today, if a function is deployed multiple times, the function package ends up being uploaded multiple times. Also, there is no version management in Pulsar for Functions and IO connectors. The newly introduced package management API provides an easier way to manage the packages for Fun [...]
-
-## Simplified Client Memory Limit Settings
-
-Prior to 2.8, there are multiple settings in producers and consumers that allow controlling the sizes of the internal message queues. These settings ultimately control the amount of memory the Pulsar client uses. However, there are few issues with this approach that make it complicated to select an overall configuration that controls the total usage of memory.
-
-For example, the settings are based on the “number of messages”, so the expected message size must be adjusted per producer or consumer. If an application has a large (or unknown) number of producers or consumers, it’s very difficult to select an appropriate value for queue sizes. The same is true for topics that have many partitions.
-
-In 2.8, we introduced a new API to set the memory limit. This single `memoryLimit` setting specifies a maximum amount of memory on a given Pulsar client. The producers and consumers compete for the memory assigned. It ensures the memory used by the Pulsar client will not go beyond the set limit. Read “[PIP-74: Pulsar client memory limits](https://github.com/apache/pulsar/wiki/PIP-74%3A-Pulsar-client-memory-limits)” for more details.
-
-## Broker Entry Metadata
-
-Pulsar messages define a very comprehensive set of metadata properties. However, to add a new property, the `MessageMetadata` definition in Pulsar protocol must change to inform both broker and client of the newly introduced property.
-
-But in certain cases, this metadata property might need to be added from the broker side, or need to be retrieved by the broker at a very low cost. To prevent deserializing these properties from the message metadata, we introduced “Broker Entry Metadata” in 2.8.0 to provide a lightweight approach to add additional metadata properties without serializing and deserializing the protobuf-encoded `MessageMetadata`.
-
-This feature unblocks a new set of capabilities for Pulsar. For example, we can leverage broker entry metadata to generate broker publish time for the messages appended to the Pulsar topic. The other example is to generate a monotonically increasing sequence-id for messages produced to a Pulsar topic. We use this feature in Kafka-on-Pulsar to implement Kafka offset.
-
-## New Protobuf Code Generator
-
-Pulsar uses Google Protobuf in order to perform serialization and deserialization of the commands that are exchanged between clients and brokers. Because of the overhead involved with the regular Protobuf implementation, we have been using a modified version of Protobuf 2.4.1. The modifications were done to ensure a more efficient serialization code that used thread local cache for the objects used in the process.
-
-This approach introduced a few issues. For example, the patch to the Protobuf code generator is only based on Protobuf version 2.4.1 and cannot be upgraded to the newer Protobuf versions. In 2.8, we switched the patched Protobuf 2.4.1 to Splunk LightProto as the code generator. The new code generator generates the fastest possible Java code for Protobuf SerDe, is 100% compatible with proto2 definition and wire protocol, and provides zero-copy deserialization using Netty ByteBuf.
-
-## Transactions
-
-Prior to Pulsar 2.8, Pulsar only supported exactly-once semantics on single topic through Idempotent Producer. While powerful, Idempotent producer only solves a narrow scope of challenges for exactly-once semantics. For example, there is no `atomicity` when a producer attempts to produce messages to multiple topics. A publish error can occur when the broker serving one of the topics crashes. If the producer doesn’t retry publishing the message again, it results in some messages being per [...]
-
-In order to address the remaining challenges described above, we’ve strengthened the Pulsar’s delivery semantics by introducing a Pulsar Transaction API to support atomic writes and acknowledgements across multiple topics. The addition of the Transaction API to Apache Pulsar completes our vision of making Pulsar a complete unified messaging and streaming platform.
-
-Pulsar PMC member, Penghui Li, goes over this functionality in great detail in his recent blog, Exactly-once Semantics with Transactions in Pulsar. You can read it to learn more about the [exactly-once semantics support in Pulsar](https://streamnative.io/en/blog/release/2021-06-14-exactly-once-semantics-with-transactions-in-pulsar).
-
-# Building a Unified Messaging and Streaming Platform with Apache Pulsar
-
-## The Evolution of Apache Pulsar
-
-Apache Pulsar is widely adopted by hundreds of companies across the globe, including Splunk, Tencent, Verizon, and Yahoo! JAPAN, just to name a few. Born as a cloud-native distributed messaging system, Apache Pulsar has evolved into a complete messaging and streaming platform for publishing and subscribing, storing, and processing streams of data at scale and in real-time.
-
-Back in 2012 the Yahoo! team was looking for a global, geo-replicated infrastructure that could manage all of Yahoo!’s messaging data. After vetting the messaging and streaming landscape it became clear that existing technologies were not able to serve the need for an event-driven organization. As a result, the team at Yahoo! set out to build its own.
-
-At the time, there were generally two types of systems to handle in-motion data: message queues that handled mission-critical business events in real-time, and streaming systems that handled scalable data pipelines at scale. Companies had to limit their capabilities to one or the other, or they had to adopt multiple different technologies. If they chose multiple technologies, they would end up with a complex infrastructure that often resulted in data segregation and data silos, with one [...]
-
-
-
-However, with the diversity of data that companies need to process beyond operational data (like log data, click events, etc), coupled with the increase in the number of downstream systems that need access to combined business data and operational data, the system would need to support message queueing and streaming.
-
-Beyond that, companies need an infrastructure platform that would allow them to build all of their applications on top of it, and then have those applications handle in-motion data (messaging and streaming data) by default. This way real-time data infrastructure could be significantly simplified, as illustrated in the diagram below.
-
-
-
-With that vision, the Yahoo! team started working on building a unified messaging and streaming platform for in-motion data. Below is an overview of the key milestones on the Pulsar journey, from inception to today.
-
-## Step 1: A scalable storage for streams of data
-
-The journey of Pulsar began with Apache BookKeeper. Apache BookKeeper implements a log-like abstraction for continuous streams and provides the ability to run it at internet-scale with simple write-read log APIs. A log provides a great abstraction for building distributed systems, such as distributed databases and pub-sub messaging. The write APIs are in the form of appends to the log. And the read APIs are in the form of continuous read from a starting offset defined by the readers. The [...]
-
-## Step 2: A multi-layered architecture that separates compute from storage.
-
-On top of the scalable log storage, a stateless serving layer was introduced which runs stateless brokers for publishing and consuming messages. This multi-layered architecture separates serving/compute from storage, allowing Pulsar to manage serving and storage in separate layers.
-
-This architecture also ensures instant scalability and higher availability. Both of these factors are extremely important and make Pulsar well-suited for building mission-critical services, such as billing platforms for financial use cases, transaction processing systems for e-commerce and retailers, and real-time risk control systems for financial institutions.
-
-## Step 3: Unified messaging model and API
-
-In a modern data architecture, the real-time use cases can typically be categorized into two categories: queueing and streaming. Queueing is typically used for building core business application services while streaming is typically used for building real-time data services such as data pipelines.
-
-To provide one platform able to serve both application and data services required a unified messaging model that integrates queuing and streaming semantics. The Pulsar topics become the source of truth for consumption. Messages can be stored only once on topics, but can be consumed in different ways via different subscriptions. Such unification significantly reduces the complexity of managing and developing messaging and streaming applications.
-
-## Step 4: Schema API
-
-Next, a new Pulsar schema registry and a new type-safe producer & consumer API were added. The built-in schema registry enables message producers and consumers on Pulsar topics to coordinate on the structure of the topic’s data through the Pulsar broker itself, without needing an external coordination mechanism. With data schemas, every single piece of data traveling through Pulsar is completely discoverable, enabling you to build systems that can easily adapt as the data changes.
-
-Furthermore, the schema registry keeps track of data compatibility between versions of the schema. As the new schemas are uploaded the registry ensures that new schema versions are able to be read by old consumers. This ensures that Producers cannot break Consumers.
-
-## Step 5: Functions and IO API
-
-The next step was to build APIs that made it easy to get data in and out of Pulsar and process it. The goal was to make it easy to build event-driven applications and real-time data pipelines with Apache Pulsar, so you can then process those events when they arrive, no matter where they originated from.
-
-The Pulsar IO API allows you to build real-time streaming data pipelines by plugging various source connectors to get data from external systems into Pulsar and sink connectors to get data from Pulsar into external systems. Today, Pulsar provides several built-in connectors that you can use.
-
-Additionally, StreamNative Hub (a registry of Pulsar connectors) provides dozens of connectors integrated with popular data systems. If the IO API is for building streaming data pipelines, the Functions API is for building event-driven applications and real-time stream processors.
-
-The serverless function concepts were adopted into stream processing and then built the Functions API as a lightweight serverless library that you can write any event processing logic using any language you like. The underlying motivation was to enable your engineering team to write stream processing logic without the operational complexity of running and maintaining yet another cluster.
-
-## Step 6: Infinite storage for Pulsar via Tiered Storage
-
-As adoption of Apache Pulsar continued and the amount of data stored in Pulsar increased, users eventually hit a “retention cliff”, at which point it became significantly more expensive to store, manage, and retrieve data in Apache BookKeeper. To work around this, operators and application developers typically use an external store like AWS S3 as a sink for long-term storage. This means you lose most of the benefits of Pulsar’s immutable stream and ordering semantics, and instead end up [...]
-
-The introduction of Tiered Storage allows Pulsar to offload the majority of the data to a remote cloud-native storage. This cheaper form of storage readily scales with the volume of data. More importantly, with the addition of Tiered Storage, Pulsar provides the batch storage capabilities needed to support batch processing when integrating with a unified batch and stream processor like Flink. The unified batch and stream processing capabilities integrated with Pulsar enable companies to [...]
-
-## Step 7: Protocol Handler
-
-After introducing tiered storage, Pulsar evolved from a Pub/Sub messaging system into a scalable stream data system that can ingest, store, and process streams of data. However, existing applications written using other messaging protocols such as Kafka, AMQP, MQTT, etc had to be rewritten to adopt Pulsar’s messaging protocol.
-
-The Protocol Handler API further reduces the overhead of adopting Pulsar for building messaging and streaming applications, and allows developers to extend Pulsar capabilities to other messaging domains by leveraging all the benefits provided by Pulsar architecture. This resulted in major collaborations between Pulsar and other industry leaders to develop popular protocol handlers including:
-- [Kafka-on-Pulsar (KoP)](https://hub.streamnative.io/protocol-handlers/kop/0.2.0), which was [launched in March 2020](https://streamnative.io/en/blog/tech/2020-03-24-bring-native-kafka-protocol-support-to-apache-pulsar) by OVHCloud and StreamNative.
-- [AMQP-on-Pulsar (AoP)](https://hub.streamnative.io/protocol-handlers/aop/0.1.0), which was [announced in June 2020](https://streamnative.io/en/blog/tech/2020-06-15-announcing-aop-on-pulsar) by China Mobile and StreamNative.
-- [MQTT-on-Pulsar (MoP)](https://hub.streamnative.io/protocol-handlers/mop/0.2.0), which was [announced in August 2020](https://streamnative.io/en/blog/tech/2020-09-28-announcing-mqtt-on-pulsar) by StreamNative.
-- [RocketMQ-on-Pulsar (RoP)](https://github.com/streamnative/rop), which was launched in May 2021 by Tencent Cloud and StreamNative.
-
-## Step 8: Transaction API for exactly-once stream processing
-
-More recently, transactions were added to Apache Pulsar to enable exactly-once semantics for stream processing. This is a fundamental feature that provides a strong guarantee for streaming data transformations, making it easy to build scalable, fault-tolerant, stateful messaging and streaming applications that process streams of data.
-
-Furthermore, the transaction API capabilities are not limited to a given language client. Pulsar’s support for transactional messaging and streaming is primarily a protocol-level capability that can be presented in any language. Such protocol-level capability can be leveraged in all kinds of applications.
-
-# Building an ecosystem for unified messaging and streaming
-
-In addition to contributing to the Pulsar technology, the community is also working to build a robust ecosystem to support it. Pulsar’s ability to support a rich ecosystem of pub-sub libraries, connectors, functions, protocol handlers, and integrations with popular query engines will enable Pulsar adopters to streamline workflows and achieve new use cases.
-
-# What is Next?
-
-If you are interested in learning more about Pulsar 2.8.0, you can [download 2.8.0](https://pulsar.apache.org/en/versions/) and try it out today!
-
-If you want to learn more about how companies have adopted Pulsar, you can [sign up](https://hopin.com/events/pulsar-summit-north-america-2021) for Pulsar Summit NA 2021!
-
-For more information about the Apache Pulsar project and the progress, please visit the official website at https://pulsar.apache.org and follow the project on Twitter [@apache_pulsar](https://twitter.com/apache_pulsar).
-
diff --git a/site2/website/blog/2021-08-11-Apache-Pulsar-2-7-3.md b/site2/website/blog/2021-08-11-Apache-Pulsar-2-7-3.md
deleted file mode 100644
index 750db2fc6c1..00000000000
--- a/site2/website/blog/2021-08-11-Apache-Pulsar-2-7-3.md
+++ /dev/null
@@ -1,140 +0,0 @@
----
-author: Bo Cong, Anonymitaet
-title: Apache Pulsar 2.7.3
----
-
-# What’s New in Apache Pulsar 2.7.3
-
-The Apache Pulsar community releases version 2.7.3! 34 contributors provided improvements and bug fixes that delivered 79 commits.
-
-## Highlights
-
-- Cursor reads adhere to the dispatch byte rate limiter setting and no longer cause unexpected results. [PR-11249](https://github.com/apache/pulsar/pull/11249)
-
-- The ledger rollover scheduled task runs as expected. [PR-11226](https://github.com/apache/pulsar/pull/11226)
-
-This blog walks through the most noteworthy changes. For the complete list including all enhancements and bug fixes, check out the [Pulsar 2.7.3 Release Notes](https://pulsar.apache.org/release-notes/#273-mdash-2021-07-27-a-id273a).
-
-# Notable bug fixes and enhancements
-
-## Broker
-
-### Cursor reads adhere to the dispatch byte rate limiter setting. [PR-9826](https://github.com/apache/pulsar/pull/9826)
-
-- **Issue**: When using byte rates, the dispatch rates were not respected (regardless
-of being a namespace or topic policy).
-
-- **Resolution**: Fixed behavior of dispatch byte rate limiter setting. Cursor reads adhere to the setting and no longer cause unexpected results.
-
-### The ledger rollover scheduled task runs as expected. [PR-11226](https://github.com/apache/pulsar/pull/11226)
-
-- **Issue**: Previously, the ledger rollover scheduled task was executed before reaching the ledger maximum rollover time, which caused the ledger not to roll over in time.
-
-- **Resolution**: Fixed the timing of the ledger rollover schedule, so the task runs only after the ledger is created successfully.
-
-### The topic-level retention policy works correctly when restarting a broker. [PR-11136](https://github.com/apache/pulsar/pull/11136)
-
-- **Issue**: Previously, when setting a topic-level retention policy for a topic and then restarting the broker, the topic-level retention policy did not work.
-
-- **Resolution**: Fixed behavior of the policy so it replays all policy messages after initiating `policyCacheInitMap` and added a retention policy check test when restarting the broker.
-
-### The lastMessageId API call no longer causes a memory leak. [PR-10977](https://github.com/apache/pulsar/pull/10977)
-
-- **Issue**: Previously, there was a memory leak when calling the `lastMessageId` API, which caused the broker process to be stopped by Kubernetes.
-
-- **Resolution**: Added the missing entry.release() call to PersistentTopic.getLastMessageId to ensure the broker does not run out of memory.
-
-### ZooKeeper reads are cached by brokers. [PR-10594](https://github.com/apache/pulsar/pull/10594)
-
-- **Issue**: When performing the admin operation to get the namespace of a tenant, ZooKeeper reads were issued on the ZooKeeper client and not getting cached by the brokers.
-
-- **Resolution**: Fixed ZooKeeper caching when fetching a list of namespaces for a tenant.
-
-### Monitoring threads that call `LeaderService.isLeader()` are no longer blocked. [PR-10512](https://github.com/apache/pulsar/pull/10512)
-
-- **Issue**: When `LeaderService` changed leadership status, it was locked with a `synchronized` block, which also blocked other threads calling `LeaderService.isLeader()`.
-
-- **Resolution**: Fixed the deadlock condition on the monitoring thread so it is not blocked by `LeaderService.isLeader() by modifying `ClusterServiceCoordinator` and `WorkerStatsManager` to check if it is a leader from `MembershipManager`.
-
-### `hasMessageAvailable` can read messages successfully. [PR-10414](https://github.com/apache/pulsar/pull/10414)
-
-- **Issue**: When `hasMessageAvailableAsync` returned `true`, it could not read messages because messages were filtered by `acknowledgmentsGroupingTracker`.
-
-- **Resolution**: Fixed the race conditions by modifying `acknowledgmentsGroupingTracker` to filter duplicate messages, and then cleanup the messages when the connection is open.
-
-## Proxy
-
-### Proxy supports creating partitioned topics automatically. [PR-8048](https://github.com/apache/pulsar/pull/8048)
-
-- **Issue**: Proxies were not creating partitions because they were using the current ZooKeeper metadata.
-
-- **Resolution**: Changed the proxy to handle `PartitionMetadataRequest` by selecting and fetching from an available broker instead of using current ZooKeeper metadata.
-
-## Pulsar admin
-
-### Flag added to indicate whether or not to create a metadata path on replicated clusters. [PR-11140](https://github.com/apache/pulsar/pull/11140)
-
-- **Issue**: When creating a partitioned topic in a replicated namespace, it did not
-create a metadata path `/managed-ledgers` on replicated clusters.
-
-- **Resolution**: Added a flag (createLocalTopicOnly) to indicate whether or not to create a metadata path for a partitioned topic in replicated clusters.
-
-### A topic policy can no longer be set for a non-existent topic. [PR-11131](https://github.com/apache/pulsar/pull/11131)
-
-- **Issue**: Due to a redirect loop in a topic policy, you can set a policy for a non-existing topic or a partition of a partitioned topic.
-
-- **Resolution**: The fix added an authoritative flag for a topic policy to avoid a redirect loop. You can not set a topic policy for a non-existent topic or a partition of a partitioned topic. If you set a topic policy for a partition of a 0-partition topic, it redirects to the broker.
-
-### Discovery service no longer hard codes the topic domain as persistent. [PR-10806](https://github.com/apache/pulsar/pull/10806)
-
-- **Issue**: When using the lookup discovery service for a partitioned non-persistent topic, it returned zero rather than the number of partitions. The Pulsar client tried to connect to the topic as if it were a normal topic.
-
-- **Resolution**: Implemented `topicName.getDomain().value()` rather than hard coding `persistent.` Now you can use the discovery service for a partitioned, non-persistent topic successfully.
-
-### Other connectors can now use the Kinesis `Backoff` class. [PR-10744](https://github.com/apache/pulsar/pull/10744)
-
-- **Issue**: The Kinesis sink connector `Backoff` class in the Pulsar client implementation project in combination with the dependency `org.apache.pulsar:pulsar-client-original` increased the connector size.
-
-- **Resolution**: Added a new class `Backoff` in the function io-core project so that the Kinesis sink connector and other connectors can use the class.
-
-## Client
-
-### A `FLOW` request with zero permits can not be sent. [PR-10506](https://github.com/apache/pulsar/pull/10506)
-
-- **Issue**: When a broker received a `FLOW` request with zero permits, an exception was thrown and then the connection was closed. This triggered frequent reconnections and caused duplicate or out-of-order messages.
-
-- **Resolution**: Added a validation that verifies the permits of a `FLOW` request before sending it. If the permit is zero, the `FLOW` request can not be sent.
-
-## Function and connector
-
-### The Kinesis sink connector acknowledges successful messages. [PR-10769](https://github.com/apache/pulsar/pull/10769)
-
-- **Issue**: The Kinesis sink connector did not acknowledge messages after they were sent successfully.
-
-- **Resolution**: Added acknowledgement for the Kinesis sink connector once a message is sent successfully.
-
-## Docker
-
-### Function name length cannot exceed 52 characters when using Kubernetes runtime. [PR-10531](https://github.com/apache/pulsar/pull/10531)
-
-- **Issue**: When using Kubernetes runtime, if a function was submitted with a valid length (less than 55 characters), a StatefulSet was created but it was unable to spawn pods.
-
-- **Resolution**: Changed the maximum length of a function name from 55 to 53 characters for Kubernetes runtime. With this fix, the length of a function name can not exceed 52 characters.
-
-## Dependency
-
-### `pulsar-admin` connection to proxy is stable when TLS is enabled. [PR-10907](https://github.com/apache/pulsar/pull/10907)
-
-- **Issue**: `pulsar-admin` was unstable over the TLS connection because of the Jetty bug in SSL buffering introduced in Jetty 9.4.39. It caused large function jar uploads to fail frequently.
-
-- **Resolution**: Upgraded Jetty to 9.4.42.v20210604, so that `pulsar-admin` connection to proxy is stable when TLS is enabled.
-
-# What is Next?
-
-If you are interested in learning more about Pulsar 2.7.3, you can [download 2.7.3](https://pulsar.apache.org/en/versions/) and try it out now!
-
-The first-ever Pulsar Virtual Summit Europe 2021 will take place in October. [Register now](https://hopin.com/events/pulsar-summit-europe-2021) and help us make it an even bigger success by spreading the word on social!
-
-For more information about the Apache Pulsar project and the progress, visit
-the [Pulsar website](https://pulsar.apache.org), follow the project on Twitter
-[@apache_pulsar](https://twitter.com/apache_pulsar), and join [Pulsar Slack](https://apache-pulsar.herokuapp.com/)!
diff --git a/site2/website/blog/2021-08-18-asia-cfp.md b/site2/website/blog/2021-08-18-asia-cfp.md
deleted file mode 100644
index cf60648735c..00000000000
--- a/site2/website/blog/2021-08-18-asia-cfp.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-author: Dianjin
-title: Announcing Pulsar Summit Asia 2021: CFP Is Open!
----
-We’re proud to announce the Pulsar Summit Asia 2021!
-
-2021 has been a remarkable year for the Apache Pulsar community. [Both the technology and community are growing rapidly this year](https://streamnative.io/en/blog/community/2021-06-14-pulsar-hits-its-400th-contributor-and-passes-kafka-in-monthly-active-contributors), and [Pulsar Virtual Summit North America 2021](https://www.na2021.pulsar-summit.org) was a big success with 33 break-out sessions and more than 550 registrations.
-
-Last year, [Pulsar Summit Asia](https://pulsar-summit.org/en/event/asia-2020) featured more than 40 interactive sessions by tech leads, open-source developers, software engineers, and software architects from Tencent Group, BIGO, Kingsoft Cloud, Splunk, Yahoo! JAPAN, Nutanix, Dada Group, TIBCO, Huawei Cloud, and more. The conference garnered nearly 1,000 attendees around the globe mostly from Asia, including attendees from top tech, fintech and media companies.
-
-Cumulatively, the Pulsar Summits drew more than 100 speakers, thousands of attendees, and hundreds of companies from diverse industries. It is a unique opportunity to network and learn about Pulsar project updates, ecosystem developments, best practices, and adoption stories.
-
-**This year, the Pulsar Summit Asia will be hosted on November 20-21, 2021 by StreamNative. You can join us offline in Beijing for one day of Pulsar Training and one day of keynotes and breakout sessions. All the talks will be streamed live online.**
-# CFP Details
-Join us and speak at the Pulsar Summit Asia 2021!
-We are looking for Pulsar stories that are innovative, informative, or thought-provoking. Here are some suggestions:
-- Your Pulsar use case / success story
-- A technical deep dive
-- Pulsar best practices
-- Pulsar ecosystem updates
-
-To speak at the summit, please [submit an abstract](https://sessionize.com/pulsar-summit-asia-2021/) about your presentation. Remember to keep your proposal short, relevant and engaging.
-# First-time Speakers Welcomed!
-First time submitting? Don't feel intimidated. We strongly encourage first-time speakers to submit talks for the Pulsar Summit Asia 2021. If your submission is similar to a previous talk in the past Pulsar Summits, please include information on how this version will be different. We hope to see some exciting updates on the topic.
-
-We welcome submissions from around the globe. Our hybrid conference model has taken time differences into consideration. After your talk is accepted, we will schedule the sessions and send you the presentation options.
-
-# Speaker Benefits
-As a speaker, you will receive:
-- The chance to demonstrate your experience and deep knowledge in the rapidly growing event streaming space.
-- Your name, title, company, and bio will be featured on the Pulsar Summit Asia 2021 website.
-- Your session will be added to the Pulsar Summit YouTube Channel and promoted on Twitter, LinkedIn, and WeChat.
-- A professionally produced video of your presentation.
-Exclusive Pulsar swag only available to the speakers.
-
-# Important Dates
-- CFP opens: August 18th, 2021
-- CFP closes: September 8th, 2021
-- Speaker notifications: September 22th, 2021
-- Schedule announcement: October 13th, 2021
-
-Submissions are open until September 8th. If you want some advice or feedback on your proposal, or have any questions about the summit, please do not hesitate to contact us at organizers@pulsar-summit.org. We are happy to help!
-
-# Sponsor Pulsar Summit Asia
-Pulsar Summit is a conference for the community and sponsorship is needed. Sponsoring this event provides a great opportunity for your organization to further engage with the Apache Pulsar community. Contact us at organizers@pulsar-summit.org to learn more.
-
-Help us make Pulsar Summit Asia 2021 a big success by spreading the word and submitting your proposal! Follow Pulsar Summit on [Twitter](https://twitter.com/PulsarSummit) to receive the latest updates of the conference.
\ No newline at end of file
diff --git a/site2/website/blog/2021-09-23-Apache-Pulsar-2-8-1.md b/site2/website/blog/2021-09-23-Apache-Pulsar-2-8-1.md
deleted file mode 100644
index 8f493c7f963..00000000000
--- a/site2/website/blog/2021-09-23-Apache-Pulsar-2-8-1.md
+++ /dev/null
@@ -1,148 +0,0 @@
----
-author: Hang Chen, Anonymitaet
-title: Apache Pulsar 2.8.1
----
-
-# What’s New in Apache Pulsar 2.8.1
-
-The Apache Pulsar community releases version 2.8.1! 49 contributors provided improvements and bug fixes that delivered 213 commits.
-
-Highlights of this release are as below:
-
-- Key-shared subscriptions no longer stop dispatching to consumers when repeatedly opening and closing consumers. [PR-10920](https://github.com/apache/pulsar/pull/10920)
-
-- System topic no longer has potential data loss when not configured for compaction. [PR-11003](https://github.com/apache/pulsar/pull/11003)
-
-- Consumers are not allowed to read data on topics to which they are not subscribed. [PR-11912](https://github.com/apache/pulsar/pull/11912)
-
-This blog walks through the most noteworthy changes grouped by component. For the complete list including all features, enhancements, and bug fixes, check out the [Pulsar 2.8.1 Release Notes](https://pulsar.apache.org/release-notes/#281-mdash-2021-09-10-a-id281a).
-
-# Notable bug fixes and enhancements
-
-## Broker
-
-### Precise publish rate limit takes effect as expected. [PR-11446](https://github.com/apache/pulsar/pull/11446)
-
-**Issue**: Previously, when setting precise publish rate limits on topics, it did not work.
-
-**Resolution**: Implemented a new `RateLimiter` using the `LeakingBucket` and `FixedWindow` algorithms.
-
-### Messages with the same keys are delivered to the correct consumers on Key-Shared subscriptions. [PR-10762](https://github.com/apache/pulsar/pull/10762)
-
-**Issue**: Messages with the same keys were out of order when message redelivery occurred on a Key-Shared subscription.
-
-**Resolution**: When sending a message to `messagesToRedeliver`, the broker saved the hash value of the key. If the dispatcher attempted to send newer messages to the consumer that had a key corresponding to any one of the saved hash values, they were added to `messagesToRedeliver` instead of being sent. This prevented messages with the same key from being out of order.
-
-### Active producers with the same name are no longer removed from the topic map. [PR-11804](https://github.com/apache/pulsar/pull/11804)
-
-**Issue**: Previously, when there were producers with the same name, an error would be triggered and the old producer would be removed even though it was still writing to a topic.
-
-**Resolution**: Validated producers based on a connection ID (local & remote addresses and unique ID) and a producer ID within that connection rather than a producer name.
-
-### Topics in a fenced state can recover when producers continue to reconnect to brokers. [PR-11737](https://github.com/apache/pulsar/pull/11737)
-
-**Issue**: Previously, when a producer continued to reconnect to a broker, the fenced state of the topic was always set to true, which caused the topic to be unable to recover.
-
-**Resolution**: Add an entry to `ManagedLedgerException` when the polled operation is not equal to the current operation.
-
-### Topic properly initializes the cursor to prevent data loss. [PR-11547](https://github.com/apache/pulsar/pull/11547)
-
-**Issue**: Previously, when subscribing to a topic with the earliest position, data would be lost because `ManagedLedger` used a wrong position to initialize a cursor.
-
-**Resolution**: Added a test to check a cursor's position when subscribing to a topic with the earliest position.
-
-### Deadlock no longer occurs when using `hasMessageAvailableAsync` and `readNextAsync`. [PR-11183](https://github.com/apache/pulsar/pull/11183)
-
-**Issue**: Previously, when messages were added to an incoming queue, a deadlock might occur. The deadlock might happen in two possible scenarios. First, if the message was added to the queue before the message was read. Second, if `readNextAsync` was completed before `future.whenComplete` was called.
-
-**Resolution**: Used an internal thread to process the callback of `hasMessageAvailableAsync`.
-
-### Memory leak does not occur when calling getLastMessageId API. [PR-10977](https://github.com/apache/pulsar/pull/10977)
-
-**Issue**: Previously, the broker ran out of memory when calling the `getLastMessageId` API.
-
-**Resolution**: Added the `entry.release()` call to the `PersistentTopic.getLastMessageId`.
-
-### Compaction is triggered for system topics. [PR-10941](https://github.com/apache/pulsar/pull/10941)
-
-**Issue**: Previously, when a topic had only non-durable subscriptions, the compaction was not triggered because it had 0 estimated backlog size.
-
-**Resolution**: Used the total backlog size to trigger the compaction. Changed the behavior in the case of no durable subscriptions to use the total backlog size
-
-### Key-shared subscriptions no longer stop dispatching to consumers when repeatedly opening and closing consumers. [PR-10920](https://github.com/apache/pulsar/pull/10920)
-
-**Issue**: Repeatedly opening and closing consumers with a Key-Shared subscription might occasionally stop dispatching messages to all consumers.
-
-**Resolution**: Moved the mark-delete position and removed the consumer from the selector before calling `removeConsumer()`.
-
-### Consumers are not allowed to read data on topics to which they are not subscribed. [PR-11912](https://github.com/apache/pulsar/pull/11912)
-
-**Issue**: Previously, the request ledger was not checked whether it belonged to a consumer’s connected topic, which allowed the consumer to read data that does not belong to the connected topic.
-
-**Resolution**: Added a check on the `ManagedLedger` level before executing read operations.
-
-## Topic Policy
-
-### Retention policy works as expected. [PR-11021](https://github.com/apache/pulsar/pull/11021)
-
-**Issue**: Previously, the retention policy did not work because it was not set in the `managedLedger` configuration.
-
-**Resolution**: Set the retention policy in the `managedLedger` configuration to the `onUpdate` listener method.
-
-### System topic no longer has potential data loss when not configured for compaction. [PR-11003](https://github.com/apache/pulsar/pull/11003)
-
-**Issue**: Previously, data might be lost if there were no durable subscriptions on topics.
-
-**Resolution**: Leveraged the topic compaction cursor to retain data.
-
-## Proxy
-
-### Pulsar proxy correctly shuts down outbound connections. [PR-11848](https://github.com/apache/pulsar/pull/11848)
-
-**Issue**: Previously, there was a memory leak of outgoing TCP connections in the Pulsar proxy because the `ProxyConnectionPool` instances were created outside the `PulsarClientImpl` instance and not closed when the client was closed.
-
-**Resolution**: Shut down the `ConnectionPool` correctly.
-
-## Function
-
-### Pulsar Functions support Protobuf schema. [PR-11709](https://github.com/apache/pulsar/pull/11709)
-
-**Issue**: Previously, the exception `GeneratedMessageV3 is not assignable` was thrown when using a Protobuf schema.
-
-**Resolution**: Added the relevant dependencies to the Pulsar instance.
-
-## Client
-
-### Partitioned-topic consumers clean up resources after a failure. [PR-11754](https://github.com/apache/pulsar/pull/11754)
-
-**Issue**: Previously, partitioned-topic consumers did not clean up the resources when failing to create consumers. If this failure occurred with non-recoverable errors, it triggered a memory leak, which made applications unstable.
-
-**Resolution**: Closed and cleaned timer task references.
-
-### Race conditions do not occur on multi-topic consumers. [PR-11764](https://github.com/apache/pulsar/pull/11764)
-
-**Issue**: Previously, there was a race condition between 2 threads when one of the individual consumers was in a "paused" state and the shared queue was full.
-
-**Resolution**: Validated the state of the shared queue after marking the consumer as "paused". The consumer is not blocked if the other thread has emptied the queue in the meantime.
-
-### Consumers are not blocked on `batchReceive`. [PR-11691](https://github.com/apache/pulsar/pull/11691)
-
-**Issue**: Previously, consumers were blocked when `Consumer.batchReceive()` was called concurrently by different threads due to a race condition in `ConsumerBase.java`.
-
-**Resolution**: Put `pinnedInternalExecutor` in `ConsumerBase` to allow batch timer, `ConsumerImpl`, and `MultiTopicsConsumerImpl` to submit work in a single thread.
-
-### Python client correctly enables custom logging. [PR-11882](https://github.com/apache/pulsar/pull/11882)
-
-**Issue**: Previously, deadlock might happen when custom logging was enabled in the Python client.
-
-**Resolution**: Detached the worker thread and reduced log level.
-
-# What is Next?
-
-If you are interested in learning more about Pulsar 2.8.1, you can [download](https://pulsar.apache.org/en/download/) and try it out now!
-
-The first-ever Pulsar Virtual Summit Europe 2021 will take place in October. [Register now](https://hopin.com/events/pulsar-summit-europe-2021) and help us make it an even bigger success by spreading the word on social media!
-
-For more information about the Apache Pulsar project and the progress, visit
-the [Pulsar website](https://pulsar.apache.org), follow the project on Twitter
-[@apache_pulsar](https://twitter.com/apache_pulsar), and join [Pulsar Slack](https://apache-pulsar.herokuapp.com/)!
diff --git a/site2/website/blog/2021-12-11-Log4j-CVE.md b/site2/website/blog/2021-12-11-Log4j-CVE.md
deleted file mode 100644
index cbbf0fd672a..00000000000
--- a/site2/website/blog/2021-12-11-Log4j-CVE.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-author: Matteo Merli
-title: Log4j2 Zero Day vulnerability (CVE-2021-44228)
----
-
-Yesterday, a new serious vulnerability was reported regarding Log4j that can
-allow remote execution for attackers.
-
-The vulnerability issue is described and tracked under [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228).
-
-Current releases of Apache Pulsar are bundling Log4j2 versions that are affected by this vulnerability.
-Default configuration, combined with JVM version and other factors, can render it exploitable.
-We strongly recommend to follow the advisory of the Apache Log4j community and patch your systems
-as soon as possible, as well as looking for unexpected behavior in your Pulsar logs.
-
-There are 2 workarounds to patch a Pulsar deployments. You can set either of:
-
- 1. Java property: `-Dlog4j2.formatMsgNoLookups=true`
- 2. Environment variable: `LOG4J_FORMAT_MSG_NO_LOOKUPS=true`
-
-Both approaches are effective in mitigating the vulnerability for Pulsar
-services.
-
-Additionally, when running Pulsar Functions with Kubernetes runtime, you should update
-your Docker images, following the example described [here](https://github.com/lhotari/pulsar-docker-images-patch-CVE-2021-44228).
-
-If you are using the Pulsar Helm Chart for deploying in Kubernetes, a [new
-version of the chart](https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-2.7.6) is already available and it applies the above mentioned workaround.
-If upgrading is not an option, you may also mitigate by adding `-Dlog4j2.formatMsgNoLookups=true` to the `PULSAR_EXTRA_OPTS` in the `configData` section for proxy, broker, bookkeeper, zookeeper, auto-recovery, and relative components in the helm values file.
-
-We are already preparing new patch releases, 2.7.4, 2.8.2 and 2.9.1. These
-releases will be ready in the next few days and will bundle the Log4j2 2.15.0,
-which contains the vulnerability fix.
diff --git a/site2/website/blog/2021-12-14-Apache-Pulsar-2-7-4.md b/site2/website/blog/2021-12-14-Apache-Pulsar-2-7-4.md
deleted file mode 100644
index 57e69ab9fe1..00000000000
--- a/site2/website/blog/2021-12-14-Apache-Pulsar-2-7-4.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-author: Technoboy-, Anonymitaet
-title: What’s New in Apache Pulsar 2.7.4
----
-
-The Apache Pulsar community releases version 2.7.4! 32 contributors provided improvements and bug fixes that delivered 98 commits.
-
-Highlights of this release are as below:
-
-- Upgrade Log4j to 2.17.0 - [CVE-2021-45105](https://pulsar.apache.org/blog/2021/12/11/Log4j-CVE/). [PR-13392](https://github.com/apache/pulsar/pull/13392)
-
-- `ManagedLedger` can be referenced correctly when `OpAddEntry` is recycled. [PR-12103](https://github.com/apache/pulsar/pull/12103)
-
-- NPE does not occur on `OpAddEntry` while ManagedLedger is closing. [PR-12364](https://github.com/apache/pulsar/pull/12364)
-
-This blog walks through the most noteworthy changes grouped by the affected functionalities. For the complete list including all enhancements and bug fixes, check out the [Pulsar 2.7.4 Release Notes](https://pulsar.apache.org/en/release-notes/#274).
-
-# Notable bug fixes and enhancements
-
-### Upgrade Log4j to 2.17.0 - [CVE-2021-45105](https://pulsar.apache.org/blog/2021/12/11/Log4j-CVE/). [PR-13392](https://github.com/apache/pulsar/pull/13392)
-
-- **Issue**
-
- A serious vulnerability was reported regarding Log4j that can allow remote execution for attackers. The vulnerability issue is described and tracked under [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228).
-
-- **Resolution**
-
- Pulsar 2.7.4 upgraded Log4j to 2.17.0.
-
-### `ManagedLedger` can be referenced correctly when `OpAddEntry` is recycled. [PR-12103](https://github.com/apache/pulsar/pull/12103)
-
-- **Issue**
-
- Previously, after a write failure, a task was scheduled in the background to force close the ledger and trigger the creation of a new ledger. If the `OpAddEntry` instance was already recycled, that could lead to either an NPE or undefined behavior.
-
-- **Resolution**
-
- The `ManagedLedgerImpl` object reference is copied to a final variable so the background task will not be dependent on the lifecycle of the `OpAddEntry` instance.
-
-### No potential race condition in the `BlobStoreBackedReadHandler`. [PR-12123](https://github.com/apache/pulsar/pull/12123)
-
-- **Issue**
-
- Previously, `BlobStoreBackedReadHandler` entered an infinite loop when reading an offload ledger. There was a race condition between the operation of reading entries and closing BlobStoreBackedReadHandler.
-
-- **Resolution**
-
- Added a state check before reading entries and made the `BlobStoreBackedReadHandler` exit loop when the `entryID` is bigger than the `lastEntryID`.
-
-### NPE does not occur on `OpAddEntry` while ManagedLedger is closing. [PR-12364](https://github.com/apache/pulsar/pull/12364)
-
-- **Issue**
-
- Previously, the test `ManagedLedgerBkTest#managedLedgerClosed` closed ManagedLedger object on some `asyncAddEntry` operations and failed with NPE.
-
-- **Resolution**
-
- Closed `OpAddEntry` when ` ManagedLedger` signaled `OpAddEntry` to fail. In this way, the `OpAddEntry` object was correctly recycled and the failed callback was correctly triggered.
-
-### Set a topic policy through the topic name of a partition correctly. [PR-11294](https://github.com/apache/pulsar/pull/11294)
-
-- **Issue**
-
- Previously, the topic name of a partition could not be used to set a topic policy.
-
-- **Resolution**
-
- Allowed setting a topic policy through a topic name of a partition by converting the topic name of a partition in `SystemTopicBasedTopicPoliciesService`.
-
-### Dispatch rate limiter takes effect for consumers. [PR-8611](https://github.com/apache/pulsar/pull/8611)
-
-- **Issue**
-
- Previously, dispatch rate limiter did not take effect in cases where all consumers started reading in the next second since `acquiredPermits` was reset to 0 every second.
-
-- **Resolution**
-
- Changed the behaviour of `DispatchRateLimiter` by minus `permits` every second instead of reset `acquiredPermits` to 0. Consumers stopped reading entries temporarily until `acquiredPermits` returned to a value less than `permits` .
-
-### NPE does not occur when executing unload bundles operations. [PR-11310](https://github.com/apache/pulsar/pull/11310)
-
-- **Issue**
-
- When performing pressure tests on persistent partitioned topics, NPE occurred when executing unload bundles operations. Concurrently, producers did not write messages.
-
-- **Resolution**
-
- Added more safety checks to fix this issue.
-
-### Fix inconsistent behavior for Namespace bundles cache. [PR-11346](https://github.com/apache/pulsar/pull/11346)
-
-- **Issue**
-
- Previously, namespace bundle cache was not invalidated after a namespace was deleted.
-
-- **Resolution**
-
- Invalidated namespace policy cache when bundle cache was invalidated.
-
-### Close the replicator and replication client after a cluster is deleted. [PR-11342](https://github.com/apache/pulsar/pull/11342)
-
-- **Issue**
-
- Previously, the replicator and the replication client were not closed after a cluster was deleted. The producer of the replicator would then try to reconnect to the deleted cluster continuously.
-
-- **Resolution**
-
- Closed the relative replicator and replication client.
-
-### Publish rate limiter takes effect as expected. [PR-10384](https://github.com/apache/pulsar/pull/10384)
-
-- **Issue**
-
- Previously, there were various issues if `preciseTopicPublishRateLimiterEnable` was set to `true` for rate limiting:
-
- - Updating the limits did not set a boundary when changing the limits from a bounded limit to an unbounded limit.
-
- - Each topic created a scheduler thread for each limiter instance.
-
- - Topics did not release the scheduler thread when the topic was unloaded or the operation closed.
-
- - Updating the limits did not close the scheduler thread related to the replaced limiter instance
-
-- **Resolution**
-
- - Cleaned up the previous limiter instances before creating new limiter instances.
-
- - Used `brokerService.pulsar().getExecutor()` as the scheduler for the rate limiter instances.
-
- - Added resource cleanup hooks for topic closing (unload).
-
-### Clean up newly created ledgers if fails to update ZNode list. [PR-12015](https://github.com/apache/pulsar/pull/12015)
-
-- **Issue**
-
- When updating a ZNode list, ZooKeeper threw an exception and did not clean up the created ledger. Newly created ledgers were not indexed to a topic `managedLedger` list and could not be cleared up as topic retention. Also, ZNode numbers increased in ZooKeeper if the ZNode version mismatch exception was thrown out.
-
-- **Resolution**
-
- Deleted the created ledger from broker cache and BookKeeper regardless of exception type when the ZNode list failed to update.
-
-# What’s Next?
-
-If you are interested in learning more about Pulsar 2.7.4, you can [download](https://pulsar.apache.org/en/versions/) and try it out now!
-
-Pulsar Summit Asia 2021 will take place on January 15-16, 2022. [Register now](https://pulsar-summit.org/) and help us make it an even bigger success by spreading the word on social media!
-
-For more information about the Apache Pulsar project and current progress, visit
-the [Pulsar website](https://pulsar.apache.org), follow the project on Twitter
-[@apache_pulsar](https://twitter.com/apache_pulsar), and join [Pulsar Slack](https://apache-pulsar.herokuapp.com/)!
diff --git a/site2/website/blog/2022-04-08-Apache-Pulsar-2-9-2.md b/site2/website/blog/2022-04-08-Apache-Pulsar-2-9-2.md
deleted file mode 100644
index 69d144e7a40..00000000000
--- a/site2/website/blog/2022-04-08-Apache-Pulsar-2-9-2.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-author: gaoran10, Anonymitaet
-title: What’s New in Apache Pulsar 2.9.2
----
-
-The Apache Pulsar community releases version 2.9.2! 60 contributors provided improvements and bug fixes that delivered 317 commits.
-
-Highlights of this release are as below:
-
-- Transactions performance test tool is available. [PR-11933](https://github.com/apache/pulsar/pull/11933)
-
-- Brokers decrease the number of unacked messages. [PR-13383](https://github.com/apache/pulsar/pull/13383)
-
-- Readers continue to read data from the compacted ledgers. [PR-13629](https://github.com/apache/pulsar/pull/13629)
-
-This blog walks through the most noteworthy changes grouped by the affected functionalities. For the complete list including all features, enhancements, and bug fixes, check out the [Pulsar 2.9.2 Release Notes](https://github.com/apache/pulsar/releases/tag/v2.9.2).
-
-# Notable bug fixes and enhancements
-
-### Readers continue to read data from the compacted ledgers. [PR-13629](https://github.com/apache/pulsar/pull/13629)
-
-#### Issue
-
-Previously, when topics were unloaded, some data was lost to be read by readers if they have consumed some messages from some compacted ledgers.
-
-#### Resolution
-
-Rewound the reader cursor to the next message of the mark delete position if `readCompacted = true`.
-
-### Brokers decrease the number of unacked messages. [PR-13383](https://github.com/apache/pulsar/pull/13383)
-
-#### Issue
-
-Previously, brokers did not decrease the number of unacked messages if batch ack was enabled. Consequently, consumers were blocked if they reached `maxUnackedMessagesPerConsumer` limit.
-
-#### Resolution
-
-Decreased the number of unacked messages when `individualAckNormal` was called.
-
-### Chunked messages can be queried through Pulsar SQL. [PR-12720](https://github.com/apache/pulsar/pull/12720)
-
-#### Issue
-
-Previously, chunked messages could not be queried through Pulsar SQL.
-
-#### Resolution
-
-Add a chunked message map in `PulsarRecordCursor` to maintain incomplete chunked messages. If one chunked message was received completely, it would be offered in the message queue to wait for deserialization.
-
-### Support enable or disable schema upload at the broker level. [PR-12786](https://github.com/apache/pulsar/pull/12786)
-
-#### Issue
-
-Previously, Pulsar didn't support enabling or disabling schema upload at the broker level.
-
-#### Resolution
-
-Added the configuration `isSchemaAutoUploadEnabled` on the broker side.
-
-### Readers can read the latest messages in compacted topics. [PR-14449](https://github.com/apache/pulsar/pull/14449)
-
-#### Issue
-
-Previously, readers were not able to read the latest messages in compacted topics if readers enabled `readCompacted` and all the data of topics has been compacted to compacted ledgers.
-
-#### Resolution
-
-Added the `forceReset` configuration for the managed cursor, so that the cursor could be reset to a given position and readers can read data from compacted ledgers.
-
-### Transaction sequenceId can be recovered correctly. [PR-13209](https://github.com/apache/pulsar/pull/13209)
-
-#### Issue
-
-Previously, the wrong transaction sequenceId was recovered due to incorrect `managedLedger` properties.
-
-#### Resolution
-
-Used `ManagedLedgerInterceptor ` to update current sequenceId to `managedLedger` properties and more.
-
-### Transactions performance test tool is available. [PR-11933](https://github.com/apache/pulsar/pull/11933)
-
-#### Issue
-
-Previously, it was hard to test transaction performance (such as the delay and rate of sending and consuming messages) when opening a transaction.
-
-#### Resolution
-
-Added `PerformanceTransaction` class to support this enhancement.
-
-### Port exhaustion and connection issues no longer exist in Pulsar Proxy. [PR-14078](https://github.com/apache/pulsar/pull/14078)
-
-#### Issue
-
-Previously, Pulsar proxy would get into a state where it stopped proxying broker connections while Admin API proxying kept working.
-
-#### Resolution
-
-Optimized the proxy connection to fail-fast if the target broker was not active, added connect timeout handling to proxy connection, and more.
-
-### No race condition in `OpSendMsgQueue` when publishing messages. [PR-14231](https://github.com/apache/pulsar/pull/14231)
-
-#### Issue
-
-After the method `getPendingQueueSize()` was called and the send receipt came back, the peek from the `pendingMessages` might get NPE during the process.
-
-#### Resolution
-
-Added a thread-safe message count object in `OpSendMsgQueue` for each compute process.
-
-### Change `ContextClassLoader` to `NarClassLoader` in AdditionalServlet. [PR-13501](https://github.com/apache/pulsar/pull/13501)
-
-#### Issue
-
-Previously, if a class was dynamically loaded by `NarClassLoader`, `ClassNotFoundException` occurred when it was used by the default class load.
-
-#### Resolution
-
-Changed context class loader through `Thread.currentThread().setContextClassLoader(classLoader)` before every plugin calling back and changed the context class loader back to original class loader afterwards.
-
-# What’s Next?
-
-If you are interested in learning more about Pulsar 2.9.2, you can [download](https://pulsar.apache.org/en/versions/) and try it out now!
-
-**Pulsar Summit San Francisco 2022** will take place on August 18th, 2022. [Register now](https://pulsar-summit.org/) and help us make it an even bigger success by spreading the word on social media!
-
-For more information about the Apache Pulsar project and current progress, visit
-the [Pulsar website](https://pulsar.apache.org), follow the project on Twitter
-[@apache_pulsar](https://twitter.com/apache_pulsar), and join [Pulsar Slack](https://apache-pulsar.herokuapp.com/)!
-
-
-
diff --git a/site2/website/blog/2022-05-11-apache-pulsar-community-welcomes-500th-contributor.md b/site2/website/blog/2022-05-11-apache-pulsar-community-welcomes-500th-contributor.md
deleted file mode 100644
index 34d6468c2c6..00000000000
--- a/site2/website/blog/2022-05-11-apache-pulsar-community-welcomes-500th-contributor.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "The Apache Pulsar Community Welcomes 500th Contributor!"
-date: 2022-05-11
-author: "Matteo Merli, Karin Landers, Alice Bi"
----
-
-
-Apache Pulsar is one of the fastest growing, most engaged open source projects, recognized by the [Apache Software Foundation](https://thestack.technology/top-apache-projects-in-2021-from-superset-to-nuttx/) as a Top 5 Project based on engagement in 2021. The vitality of any open source project relies on continued community growth and engagement, and this month, the Apache Pulsar community hit another major milestone: **welcoming its 500th contributor!**
-
-<!--truncate-->
-
-A cloud-native messaging and event streaming platform, Apache Pulsar was committed to open source in 2016, and graduated as a Top-Level Project (TLP) in September 2018. Since its inception, the project has received 10k+ Github stars, 2.7k+ forks, and 6.1k+ Slack users.
-
-
-
-The number of contributors in an open-source project is meaningful because it signals project adoption, growth, advancement, and accelerated development of the technology. This milestone is even more exciting, considering the speed at which the community is growing, adding an additional 100 contributors in under seven months, representing 8X contributor growth since becoming a top-level Apache Software Foundation project.
-
-
-
-## Get Involved
-
-Community growth leads to additional adoption and project enhancement, and new contributors are an excellent way to track progress of the Pulsar project. Thank you to the community and contributors for your continued involvement!
-
-Looking for more ways to stay connected with the Pulsar community?
-
-- [Pulsar Summit Global 2022](https://pulsar-summit.org/) is taking place in-person in San Francisco later this year. Follow @PulsarSummit on Twitter for updates and details of this much-anticipated event.
-- For information about the Apache Pulsar project and current progress, visit the [Pulsar website](https://pulsar.apache.org/), follow the project on Twitter @apache_pulsar, and join [Pulsar on Slack](https://apache-pulsar.herokuapp.com/)!
-
diff --git a/site2/website/blog/2022-05-11-whats-new-in-pulsar-210.md b/site2/website/blog/2022-05-11-whats-new-in-pulsar-210.md
deleted file mode 100644
index 5c3e240eb26..00000000000
--- a/site2/website/blog/2022-05-11-whats-new-in-pulsar-210.md
+++ /dev/null
@@ -1,177 +0,0 @@
----
-title: "What’s New in Apache Pulsar 2.10"
-date: 2022-05-11
-author: "Penghui Li, Dave Duggins"
----
-
-The Apache Pulsar community releases version 2.10. 99 contributors provided improvements and bug fixes that delivered over 800 commits.
-
-<!--truncate-->
-
-# Highlights of this release:
-
-- Pulsar provides automatic failure recovery between the primary and backup clusters. #13316
- - Original PIP [#13315](https://www.google.com/url?q=https://github.com/apache/pulsar/issues/13315&sa=D&source=docs&ust=1646058957138073&usg=AOvVaw3mGki2sHW2QpIsoYf5pt3w)
-- Fewer producers needed and more efficient use of broker memory with lazy-loading feature added to `PartitionedProducer`. #10279
-- Topic map support added with new `TableView` type using key values in received messages.
-
-This blog documents the most noteworthy changes in this release. For the complete list including all features, enhancements, and bug fixes, check out the [Pulsar 2.10.1 Release Notes](https://pulsar.apache.org/release-notes/#placeholder).
-
-# Notable bug fixes and enhancements
-***
-#### Cluster
-***
-
-##### Pulsar cluster level auto failover on client side #13316
-
-**Issue:** A Pulsar administrator must manually failover a cluster.
-
-**Resolution:** Added Pulsar cluster-level auto-failover, which automatically and seamlessly switches from primary to one or more secondary clusters when a failover event is detected. When the primary cluster recovers, the client automatically switches back.
-
-##### Topic policy across multiple clusters #12517
-
-**Issue:** Some topic policies for a geo-replicated cluster affect the entire geo-replicated cluster while some only affect the local cluster.
-
-**Resolution:** Topic policies now support cross-cluster replication.
-- For local topic policies, set the `replicateTo` property of the message to avoid being replicated to the remote.
-- Retention supports setting global parameters.
-- Added global topic policies for `SystemTopicBasedTopicPoliciesService`.
-
-***
-#### Producer
-***
-
-##### Add lazy-loading feature to PartitionedProducer #10279
-
-**Issue:** With the number of partitions set according to the highest rate producer, the lowest rate producer does not always need to connect to every partition, so extra producers take up broker memory.
-
-**Resolution:** Reduced the number of producers to use broker memory more efficiently by introducing lazy-loading for partitioned producers; also added round-robin routing mode class to limit the number of partitions.
-
-##### [Client] Introduce chunk message ID #12403
-
-**Issue:** When sending chunked messages, the producer returns the message-id of the last chunk, causing incorrect behaviors in some processes.
-
-**Resolution:** Introduced the new `ChunkMessage-ID` type. The chunk message-id inherits from ``MessageIdImpl`` and adds two new methods: ``getFirstChunkMessageId`` and ``getLastChunkMessageID``. For other method implementations, the ``lastChunkMessageID`` is called directly, which is compatible with much of the existing business logic.
-
-***
-#### Broker
-***
-
-##### Broker extensions to allow operators of enterprise wide cluster better control and flexibility #12536
-
-**Issue:** Operators of enterprise Pulsar cluster(s) need greater flexibility and control to intercept broker events (including ledger writes/reads) for template validations, observability and access control.
-
-**Resolution:**
-- Enhanced org.apache.pulsar.broker.intercept.BrokerInterceptor interface to include additional events for tracing
-- Created a new interface org.apache.pulsar.common.intercept.MessagePayloadProcessor to allow interception of ledger write/read operations
-- Enhanced PulsarAdmin to give operators a control in managing super-users
-
-***
-#### Consumer
-***
-
-##### Redeliver command add epoch #10478
-
-**Issue:** Pull and redeliver operations are asynchronous, so the client consumer may receive a new message, execute a cumulative ack based on a new messageID, and fail to consume older messages.
-
-**Resolution:** The Pulsar client synchronizes redeliver and pull messages operations using an incrementing epoch for the server and client consumer.
-
-##### Support pluggable entry filter in Dispatcher #12269
-
-**Issue:** Message tagging is not natively supported.
-
-**Resolution:** Implemented an entry filter framework at the broker level. Working to support namespace and topic level in an upcoming release.
-
-##### Create init subscription before sending message to DLQ #13355
-
-**Issue:** DLQ data in unprocessed messages is removed automatically without a data retention policy for the namespace or a subscription for the DLQ.
-
-**Resolution:** Initial subscription is now created before sending messages to the DLQ.
-When ``deadLetterProducer`` is initialized, the consumer sets the initial subscription according to ``DeadLetterPolicy``.
-
-##### Apply redelivery backoff policy for ack timeout #13707
-
-**Issue:** The redelivery backoff policy recently introduced in PIP 106 only applies to the negative acknowledgment API. If ack timeout is used to trigger the message
-redelivery instead of the negative acknowledgment API, the backoff policy is bypassed.
-
-**Resolution:**
-- Applied message redelivery policy for ack timeout.
-- Alerted ``NegativeAckBackoff`` interface to ``RedeliveryBackoff``.
-- Exposed ``AckTimeoutRedeliveryBackoff`` in ``ConsumerBuilder``.
-- Added unit test case.
-
-Currently only the Java client is modified.
-
-##### Resolve produce chunk messages failed when topic level maxMessageSize is set #13599
-
-**Issue:** Currently, chunk messages produce fails if topic level maxMessageSize is set to [1].
-
-**Resolution:** Added ``isChunked`` in ``PublishContext``. Skips the``maxMessageSize`` check if it's chunked.
-
-***
-#### Function
-***
-
-##### Pulsar Functions: Preload and release external resources #13205
-
-**Issue:** External resource initialization and release was accomplished either manually or through use of a complicated initialization logic.
-
-**Resolution:** Introduced ``RichFunction`` interface to extend ``Function`` by providing a setup and tearDown API.
-
-***
-##### Update Authentication Interfaces to Include Async Authentication Methods #12104
-
-**Issue:** Pulsar's current ``AuthenticationProvider`` interface only exposes synchronous methods for authenticating a connection. To date, this has been sufficient because we do not have any providers that rely on network calls. However, in looking at the OAuth2.0 spec, there are some cases where network calls are necessary to verify a token.
-
-**Resolution:**
-###### AuthenticationProvider
-- Added ``AuthenticationProvider#authenticateAsync``. Included a default implementation that calls the authenticate method.
-- Deprecated ``AuthenticationProvider#authenticate``.
-- Added ``AuthenticationProvider#authenticateHttpRequestAsync``.
-- Deprecated ``AuthenticationProvider#authenticateHttpRequest``.
-##### AuthenticationState
-- Added ``AuthenticationState#authenticateAsync``.
-- Deprecated ``AuthenticationState#authenticate``. The preferred method is ``AuthenticationState#authenticateAsync``.
-- Deprecated ``AuthenticationState#isComplete``. This method can be avoided by inferring authentication completeness from the result of ``AuthenticationState#authenticateAsync``.
-##### AuthenticationDataSource
-- Deprecated ``AuthenticationDataSource#authenticate``. There is no need for an async version of this method.
-
-***
-##### Initial commit for TableView #12838
-
-**Issue:** In many use cases, applications use Pulsar consumers or readers to fetch
-all the updates from a topic and construct a map with the latest value of each
-key for received messages. This is common when constructing a local cache of the data. We do not offer support for This access pattern was not included in the Pulsar client API.
-
-**Resolution:** Added new ``TableView`` type and updated the PulsarClient.
-
-***
-#### Topic
-***
-##### Support Topic metadata - PART-1 create topic with properties #12818
-
-**Issue:** Can’t store topic metadata.
-
-**Resolution:**
-- Added new storage methods in topics.java.
-- Added two new paths to REST API to reduce compatibility issues.
-
-***
-#### Metadata Store
-***
-##### Added Etcd MetadataStore implementation #13225
-
-**Issue:** We’re working to add metadata backends that support non-Zookeeper implementations.
-
-**Resolution:** Added Etcd support for:
-- Batching of read/write requests
-- Session watcher
-- Lease manager
-
-
-
-
-
-
-
-
diff --git a/site2/website/brodocs/actions.js b/site2/website/brodocs/actions.js
deleted file mode 100644
index ce2b504b9e0..00000000000
--- a/site2/website/brodocs/actions.js
+++ /dev/null
@@ -1,58 +0,0 @@
-// https://jsfiddle.net/upqwhou2/
-
-$(document).ready(function() {
- var navigationLinks = $('#sidebar-wrapper > ul li a');
- var navigationSections = $('#sidebar-wrapper > ul > ul');
- var sectionIdTonavigationLink = {};
- var sections = $('#page-content-wrapper').find('h1, h2').map(function(index, node) {
- if (node.id) {
- sectionIdTonavigationLink[node.id] = $('#sidebar-wrapper > ul li a[href="#' + node.id + '"]');
- return node;
- }
- });
- var sectionIdToNavContainerLink = {};
- var topLevelSections = $('#page-content-wrapper').find('h1').map(function(index, node) {
- if (node.id) {
- sectionIdToNavContainerLink[node.id] = $('#sidebar-wrapper > ul > ul[id="' + node.id + '-nav' +'"]');
- return node;
- }
- });
-
- var firstLevelNavs = $('#sidebar-wrapper > li');
- var secondLevelNavs = $('#sidebar-wrapper > ul > ul');
- var secondLevelNavContents = $('#sidebar-wrapper > ul > ul > li');
- var thirdLevelNavs = null; // TODO: When compile provides 3 level nav, implement
-
- var sectionsReversed = $(sections.get().reverse());
-
- function checkScroll(event) {
- var scrollPosition = $(window).scrollTop();
- var offset = 50;
- scrollPosition += offset;
- sections.each(function() {
- var currentSection = $(this);
- var sectionTop = $(this).offset().top;
- var id = $(this).attr('id');
- if (scrollPosition >= sectionTop) {
- navigationLinks.removeClass('selected');
- sectionIdTonavigationLink[id].addClass('selected');
- var sectionNavContainer = sectionIdToNavContainerLink[id];
- var sectionNavContainerDisplay;
- if (sectionNavContainer) {
- sectionNavContainerDisplay = sectionNavContainer.css('display');
- }
- if (sectionNavContainer && sectionNavContainerDisplay === 'none') {
- navigationSections.toggle(false);
- sectionNavContainer.toggle(true);
- }
- }
- if (($(this).offset().top < window.pageYOffset + 50) && $(this).offset().top + $(this).height() > window.pageYOffset) {
- window.location.hash = id;
- }
- });
- }
- checkScroll();
- $(window).on('scroll', function(event) {
- checkScroll(event);
- });
-});
\ No newline at end of file
diff --git a/site2/website/brodocs/brodoc.js b/site2/website/brodocs/brodoc.js
deleted file mode 100644
index 84533e04041..00000000000
--- a/site2/website/brodocs/brodoc.js
+++ /dev/null
@@ -1,214 +0,0 @@
-const docFolder = './documents/';
-const fs = require('fs');
-const marked = require('marked');
-const highlight = require('highlight.js');
-const renderer = new marked.Renderer();
-const brodocDec = require('./markedDecorations.js');
-
-
-marked.setOptions({
- renderer: renderer,
- gfm: true,
- tables: true,
- breaks: false,
- pedantic: false,
- sanitize: false,
- smartLists: true,
- smartypants: false,
- highlight: function (code, lang) {
- return highlight.highlightAuto(code).value;
- }
-});
-brodocDec.decorateMarked(renderer);
-
-var config = require('./manifest');
-var docs = config.docs;
-
-var files = [];
-var fileArray = [];
-docs.forEach(file => {
- files.push(file.filename);
- fileArray.push(file);
-});
-
-var bodyContent = '';
-var navIds = brodocDec.navIds;
-var codeTabs = brodocDec.codeTabs;
-
-
-// const lexer = new marked.Lexer();
-// lexer.rules.bdoc = /^(\/{4} )(\w+).*$/;
-
-var path = docFolder;
-var fIndex = 0;
-var rIndex = 0;
-var fileObj = {toc: [], content: [], tabs: []};
-fileArray.forEach((file, index) => {
- fs.readFile(path + file.filename, 'utf8', (err, data) => {
- rIndex++;
- file.content = data;
-
- if (rIndex >= files.length) {
- // do the things
- parseFileContent(fileArray);
- var navData = generateNavItems(navIds);
- var navContent = navData.content;
- var navDataArray = navData.navDataArray;
- var codeTabContent = generateCodeTabItems(codeTabs);
- var bodyContent = flattenContent(parsedContentArray);
- generateDoc(navContent, bodyContent, codeTabContent);
- generateNavJson(navDataArray);
- }
- });
-});
-
-function flattenContent(content) {
- var flattenedContent = content.reduce(function(accum, val) {
- return accum + val;
- });
- return flattenedContent;
-}
-
-var parsedContentArray = [];
-function parseFileContent(files) {
- files.forEach((file, index) => {
- parsedContentArray[index] = parseDoc(file.content);
- });
-}
-function parseDoc(doc) {
- return marked(doc, { renderer: renderer });
-}
-
-function generateNavItems(navObjs) {
- var reversedNavs = navObjs.reverse();
- var currentNestArray = [];
- var currentStrongArray = [];
- var flattenedNest = '';
- var nestedNavArray = []; // Array containing generated html menu items - is flattened into a string.
- var navArrayInvert = []; // Deals with data layer of navigation;
- var navSectionArray = [];
- var navStrongSectionArray = [];
- var navSectionArrayClone;
- var flatNavArrayInvert = [];
- reversedNavs.forEach(obj => {
- flatNavArrayInvert.push(obj.id);
- var strong = (obj.id.indexOf('-strong-') !== -1);
- if (obj.level !== 1) {
- if (strong && currentNestArray.length !== 0) {
- flattenedNest = flattenContent(currentNestArray.reverse());
- currentStrongArray.push(generateNestedNav(obj, flattenedNest));
- currentNestArray.length = 0;
-
- navSectionArrayClone = Object.assign([], navSectionArray);
- navStrongSectionArray.push({section: obj.id, subsections: navSectionArrayClone});
- navSectionArray.length = 0;
- } else {
- currentNestArray.push(generateNav(obj));
- navSectionArray.push({section: obj.id});
- }
- } else if (obj.level === 1) {
- if (currentStrongArray.length !== 0) {
- currentNestArray.forEach(obj => {
- currentStrongArray.push(obj);
- });
- flattenedNest = flattenContent(currentStrongArray.reverse());
- } else if (currentNestArray.length !== 0) {
- flattenedNest = flattenContent(currentNestArray.reverse());
- }
- nestedNavArray.push(generateNestedNav(obj, flattenedNest));
- currentNestArray.length = 0;
- currentStrongArray.length = 0;
- flattenedNest = '';
-
- navSectionArray.forEach(obj => {
- navStrongSectionArray.push(obj);
- });
- navSectionArrayClone = Object.assign([], navStrongSectionArray);
- navStrongSectionArray.length = 0;
- navArrayInvert.push({section: obj.id, subsections: navSectionArrayClone});
- navSectionArray.length = 0;
- }
- });
-
- var navContent = flattenContent(nestedNavArray.reverse());
- return {content: navContent, navDataArray: {toc: navArrayInvert, flatToc: flatNavArrayInvert}};
-}
-
-function generateNav(obj) {
- var classString = 'nav-level-' + obj.level;
- var isStrong = obj.id.indexOf('-strong-') !== -1;
- if (isStrong) {
- classString += ' strong-nav';
- }
- if (obj.level === 2) {
- return '<li class="' + classString + '">' + '<a href="#' + obj.id + '" class="nav-item">' + obj.text + '</a></li>';
- }
- return '<li class="' + classString + '">' + '<a href="#' + obj.id + '" class="nav-item">' + obj.text + '</a></li>';
-}
-
-function generateNestedNav(parent, nest) {
- var nestContent = '';
- if (nest.length > 0) {
- nestContent = nest ? '<ul id="' + parent.id + '-nav" style="display: none;">' + nest + '</ul>' : '';
- }
- return '<ul>' + generateNav(parent) + nestContent + '</ul>';
-}
-
-function generateNavJson(data) {
- var navJson = JSON.stringify(data);
- navScript = `(function(){navData = ${navJson};})();`;
- fs.writeFile('./navData.js', navScript, function(err) {
- if (err) {
- return console.log(err);
- }
- console.log("navData.js saved!");
- });
-}
-
-function generateCodeTabItems(tabs) {
- var codeTabList = '';
- tabs.forEach(tab => {
- codeTabList += generateCodeTab(tab);
- });
- return codeTabList;
-}
-
-function generateCodeTab(tab) {
- return '<li class="code-tab" id="' + tab + '">' + tab + '</li>';
-}
-
-function generateDoc(navContent, bodyContent, codeTabContent) {
- var doc =
-`<!DOCTYPE html>
-<html>
-<head>
-<meta charset="UTF-8">
-<title>${config.title}</title>
-<link rel="shortcut icon" href="favicon.ico" type="image/vnd.microsoft.icon">
-<!-- Latest compiled and minified CSS -->
-<link rel="stylesheet" href="node_modules/bootstrap/dist/css/bootstrap.min.css">
-<link rel="stylesheet" href="node_modules/font-awesome/css/font-awesome.min.css" type="text/css">
-<link rel="stylesheet" href="node_modules/highlight.js/styles/default.css" type="text/css">
-<link rel="stylesheet" href="stylesheet.css" type="text/css">
-</head>
-<body>
-<div id="sidebar-wrapper" class="side-nav side-bar-nav">${navContent}<br/><div class="copyright">${config.copyright}</div></div>
-<div id="wrapper">
-<div id="code-tabs-wrapper" class="code-tabs"><ul class="code-tab-list">${codeTabContent}</ul></div>
-<div id="page-content-wrapper" class="body-content container-fluid">${bodyContent}</div>
-</div>
-<script src="node_modules/jquery/dist/jquery.min.js"></script>
-<script src="node_modules/jquery.scrollto/jquery.scrollTo.min.js"></script>
-<script src="navData.js"></script>
-<script src="scroll.js"></script>
-<!--<script src="actions.js"></script>-->
-<script src="tabvisibility.js"></script>
-</body>
-</html>`;
- fs.writeFile('./index.html', doc, function (err) {
- if (err) {
- return console.log(err);
- }
- console.log("index.html saved!");
- });
-}
\ No newline at end of file
diff --git a/site2/website/brodocs/favicon.ico b/site2/website/brodocs/favicon.ico
deleted file mode 100644
index a3d664ebe6d..00000000000
Binary files a/site2/website/brodocs/favicon.ico and /dev/null differ
diff --git a/site2/website/brodocs/manifest.json b/site2/website/brodocs/manifest.json
deleted file mode 100644
index 290edb9cf5b..00000000000
--- a/site2/website/brodocs/manifest.json
+++ /dev/null
@@ -1,45 +0,0 @@
-{
- "docs": [
- {
- "filename": "brokers.md"
- },
- {
- "filename": "broker-stats.md"
- },
- {
- "filename": "clusters.md"
- },
- {
- "filename": "functions.md"
- },
- {
- "filename": "namespaces.md"
- },
- {
- "filename": "ns-isolation-policy.md"
- },
- {
- "filename": "sources.md"
- },
- {
- "filename": "sinks.md"
- },
- {
- "filename": "topics.md"
- },
- {
- "filename": "tenants.md"
- },
- {
- "filename": "resource-quotas.md"
- },
- {
- "filename": "schemas.md"
- },
- {
- "filename": "packages.md"
- }
- ],
- "title": "Docs",
- "copyright": "<a href='http://pulsar.apache.org/'>Apache Pulsar</a>"
-}
diff --git a/site2/website/brodocs/markedDecorations.js b/site2/website/brodocs/markedDecorations.js
deleted file mode 100644
index 9171226b7a7..00000000000
--- a/site2/website/brodocs/markedDecorations.js
+++ /dev/null
@@ -1,101 +0,0 @@
-;(function() {
- var brodocDec = {};
-
- var navIds = [];
- var bodyContent = '';
- var codeTabs = [];
-
- var idAffix = 0;
- var uniqueNav = [];
-
- brodocDec.decorateMarked = function(renderer) {
- renderer.heading = (text, level, raw) => {
- var id = raw.toLowerCase().replace(/[^\w]+/g, '-');
- if ((uniqueNav.indexOf(id) !== -1) && (level === 2)) {
- idAffix++;
- id += '-' + idAffix;
- } else {
- uniqueNav.push(id);
- }
- if (level < 3) {
- navIds.push(
- {
- id: id,
- text: text,
- level: level
- }
- );
- }
- return '<h'
- + level
- + ' id="'
- + renderer.options.headerPrefix
- + id
- + '">'
- + text
- + '</h'
- + level
- + '>\n';
- };
-
- renderer.blockquote = function(quote) {
- var bdregex = /(bdocs-tab:)[^\s]*/;
- var bdoc = quote.match(bdregex);
- if (bdoc) {
- var bdocTab = bdoc[0].split(':')[1];
- var bdquote = quote.replace(bdoc[0], '');
- return '<blockquote class="code-block ' + bdocTab + '">\n' + bdquote + '</blockquote>\n';
- } else {
- return '<blockquote>\n' + quote + '</blockquote>\n';
- }
- };
-
- renderer.code = function (code, lang, escaped) {
- var bdocGroup = lang.substring(0, lang.indexOf('_'));
- var bdocTab = bdocGroup.split(':')[1];
- var hlang = lang.substring(lang.indexOf('_')+1);
-
- if (renderer.options.highlight) {
- var out = renderer.options.highlight(code, hlang);
- if (out !== null && out !== code) {
- escaped = true;
- code = out;
- }
- }
-
- var tabLang = hlang ? hlang : 'generic';
- if (codeTabs.indexOf(bdocTab) === -1) {
- codeTabs.push(bdocTab);
- }
-
- if (!hlang) {
- return '<pre class="code-block"><code class="generic">'
- + (escaped ? code : escape(code, true))
- + '\n</code></pre>';
- }
-
- return '<pre class="code-block '
- + bdocTab
- + '"><code class="'
- + renderer.options.langPrefix
- + escape(hlang, true)
- + '">'
- + (escaped ? code : escape(code, true))
- + '\n</code></pre>\n';
- };
- };
-
- if (typeof module !== 'undefined' && typeof exports === 'object') {
- module.exports = brodocDec;
- } else if (typeof define === 'function' && define.amd) {
- define(function() { return brodocDec; });
- } else {
- this.brodocDec = brodocDec;
- }
- brodocDec.navIds = navIds;
- brodocDec.codeTabs = codeTabs;
- return brodocDec;
-
-}).call(function() {
- return this || (typeof window !== 'undefined' ? window : global);
-}());
\ No newline at end of file
diff --git a/site2/website/brodocs/pulsar-admin-manifest.json b/site2/website/brodocs/pulsar-admin-manifest.json
deleted file mode 100644
index 210908e16fa..00000000000
--- a/site2/website/brodocs/pulsar-admin-manifest.json
+++ /dev/null
@@ -1,25 +0,0 @@
-{
- "docs": [
- { "filename": "broker-stats.md" },
- { "filename": "brokers.md" },
- { "filename": "bookies.md" },
- { "filename": "clusters.md" },
- { "filename": "functions-worker.md" },
- { "filename": "functions.md" },
- { "filename": "namespaces.md" },
- { "filename": "ns-isolation-policy.md" },
- { "filename": "packages.md" },
- { "filename": "proxy-stats.md" },
- { "filename": "resource-quotas.md" },
- { "filename": "resourcegroups.md" },
- { "filename": "schemas.md" },
- { "filename": "sinks.md" },
- { "filename": "sources.md" },
- { "filename": "tenants.md" },
- { "filename": "topics.md" },
- { "filename": "topicPolicies.md" },
- { "filename": "transactions.md" }
- ],
- "title": "Docs",
- "copyright": "<a href='http://pulsar.apache.org/'>Apache Pulsar</a>"
-}
diff --git a/site2/website/brodocs/pulsar-client-manifest.json b/site2/website/brodocs/pulsar-client-manifest.json
deleted file mode 100644
index b48d6b4471b..00000000000
--- a/site2/website/brodocs/pulsar-client-manifest.json
+++ /dev/null
@@ -1,9 +0,0 @@
-{
- "docs": [
- {
- "filename": "pulsar-client.md"
- }
- ],
- "title": "Docs",
- "copyright": "<a href='http://pulsar.apache.org/'>Apache Pulsar</a>"
-}
diff --git a/site2/website/brodocs/pulsar-manifest.json b/site2/website/brodocs/pulsar-manifest.json
deleted file mode 100644
index 9a6c67d5abe..00000000000
--- a/site2/website/brodocs/pulsar-manifest.json
+++ /dev/null
@@ -1,45 +0,0 @@
-{
- "docs": [
- {
- "filename": "broker.md"
- },
- {
- "filename": "broker-tool.md"
- },
- {
- "filename": "compact-topic.md"
- },
- {
- "filename": "tokens.md"
- },
- {
- "filename": "proxy.md"
- },
- {
- "filename": "websocket.md"
- },
- {
- "filename": "functions-worker.md"
- },
- {
- "filename": "standalone.md"
- },
- {
- "filename": "initialize-cluster-metadata.md"
- },
- {
- "filename": "delete-cluster-metadata.md"
- },
- {
- "filename": "initialize-transaction-coordinator-metadata.md"
- },
- {
- "filename": "initialize-namespace.md"
- },
- {
- "filename": "version.md"
- }
- ],
- "title": "Docs",
- "copyright": "<a href='http://pulsar.apache.org/'>Apache Pulsar</a>"
-}
diff --git a/site2/website/brodocs/pulsar-perf-manifest.json b/site2/website/brodocs/pulsar-perf-manifest.json
deleted file mode 100644
index 217090af02c..00000000000
--- a/site2/website/brodocs/pulsar-perf-manifest.json
+++ /dev/null
@@ -1,9 +0,0 @@
-{
- "docs": [
- {
- "filename": "pulsar-perf.md"
- }
- ],
- "title": "Docs",
- "copyright": "<a href='http://pulsar.apache.org/'>Apache Pulsar</a>"
-}
diff --git a/site2/website/brodocs/scroll.js b/site2/website/brodocs/scroll.js
deleted file mode 100644
index 957af65bbcc..00000000000
--- a/site2/website/brodocs/scroll.js
+++ /dev/null
@@ -1,196 +0,0 @@
-$(document).ready(function() {
-
- /**
- * TODO: Refactor with intent toward pure functions. Mutation of state can lead to bugs and difficult debugging.
- */
-
- var toc = navData.toc;
- var flatToc = navData.flatToc.reverse();
-
- function collectNodes(tocMap) {
- var tocNodes = {};
- tocMap.map(function(node, index) {
- var sectionNode = $('#' + node.section);
- var tocSubsections = {};
- tocItem = {section: sectionNode};
- var subsectionNodes;
- if (node.subsections) {
- subsectionNodes = (collectNodes(node.subsections));
- tocItem.subsections = subsectionNodes;
- }
- tocNodes[node.section] = tocItem;
- });
- return tocNodes;
- }
- var tocItems = collectNodes(toc);
-
- function collectNodesFlat(tocMap, obj) {
- var collect = obj || {};
- tocMap.map(function(node, index) {
- var sectionNode = $('#' + node.section);
- tocItem = {section: sectionNode};
- if (node.subsections) {
- subsectionNodes = (collectNodesFlat(node.subsections, collect));
- }
- collect[node.section] = sectionNode;
- });
- return collect;
- }
- var tocFlat = collectNodesFlat(toc);
-
- var prevSectionToken;
- var prevSubsectionToken;
- var activeTokensObj = {};
-
- function scrollActions(scrollPosition) {
- var activeSection = checkNodePositions(toc, tocFlat, scrollPosition);
- var activeSubSection,
- prevL1Nav,
- currL1Nav,
- prevL2Nav,
- currL2Nav;
-
- // No active section - return existing activeTokensObj (may be empty)
- if (!activeSection) {
- return activeTokensObj;
- }
-
- /**
- * This block deals with L1Nav sections
- */
-
- // If no previous token, set previous to current active and show L1Nav
- if (!prevSectionToken) {
- prevSectionToken = activeSection.token;
- currL1Nav = getNavNode(activeSection.token);
- currL1Nav.show('fast');
- }
- // If active is not the same as previous, hide previous L1Nav and show current L1Nav; set previous to current
- else if (activeSection.token !== prevSectionToken) {
- prevL1Nav = getNavNode(prevSectionToken);
- currL1Nav = getNavNode(activeSection.token);
- prevL1Nav.hide('fast');
- currL1Nav.show('fast');
- prevSectionToken = activeSection.token;
- }
-
- /**
- * This block deals with L2Nav subsections
- */
-
- // If there is a subsections array and it has a non-zero length, set active subsection
- if (activeSection.subsections && activeSection.subsections.length !== 0) {
- activeSubSection = checkNodePositions(activeSection.subsections, tocFlat, scrollPosition);
- if (activeSubSection) {
- if (!prevSubsectionToken) {
- prevSubsectionToken = activeSubSection.token;
- currL2Nav = getNavNode(activeSubSection.token);
- currL2Nav.show('fast');
- } else if (activeSubSection.token !== prevSubsectionToken) {
- prevL2Nav = getNavNode(prevSubsectionToken);
- currL2Nav = getNavNode(activeSubSection.token);
- prevL2Nav.hide('fast');
- currL2Nav.show('fast');
- prevSubsectionToken = activeSubSection.token;
- }
- } else {
- prevL2Nav = getNavNode(prevSubsectionToken);
- prevL2Nav.hide('fast');
- prevSubsectionToken = null;
- }
- }
- activeTokensObj.L1 = prevSectionToken;
- activeTokensObj.L2 = prevSubsectionToken;
- return activeTokensObj;
- }
-
- /**
- * Checks for active elements by scroll position
- */
-
- var prevElemToken;
- var activeElemToken;
-
- function checkActiveElement(items, scrollPosition) {
- var offset = 50;
- var offsetScroll = scrollPosition + offset;
- var visibleNode;
- for (var i = 0; i < items.length; i++) {
- var token = items[i];
- var node = getHeadingNode(token);
- if (offsetScroll >= node.offset().top) {
- activeElemToken = token;
- }
- }
- if (!prevElemToken) {
- getNavElemNode(activeElemToken).addClass('selected');
- prevElemToken = activeElemToken;
- return;
- }
- if (activeElemToken !== prevElemToken) {
- getNavElemNode(prevElemToken).removeClass('selected');
- getNavElemNode(activeElemToken).addClass('selected');
- prevElemToken = activeElemToken;
- }
- return activeElemToken;
- }
-
- function getHeadingNode(token) {
- return $('#' + token);
- }
-
- function getNavNode(token) {
- return $('#' + token + '-nav');
- }
-
- function getNavElemNode(token) {
- return $('#sidebar-wrapper > ul a[href="#' + token + '"]');
- }
-
- function checkNodePositions(nodes, flatNodeMap, scrollPosition) {
- var activeNode;
- for (var i = 0; i < nodes.length; i++) {
- var item = nodes[i];
- var node = flatNodeMap[item.section];
- var nodeTop = node.offset().top - 50;
- if (scrollPosition >= nodeTop) {
- activeNode = {token: item.section, node: node};
-
- if (item.subsections) {
- activeNode.subsections = item.subsections;
- }
- break;
- }
- }
- return activeNode;
- }
-
- function scrollToNav(token) {
- setTimeout(function() {
- var scrollPosition = $(window).scrollTop();
- var activeSectionTokens = scrollActions(scrollPosition);
- var activeElemToken = checkActiveElement(flatToc, scrollPosition);
- var navNode = $('#sidebar-wrapper > ul a[href="#' + token + '"]');
- $('#sidebar-wrapper').scrollTo(navNode, {duration: 'fast', axis: 'y'});
- }, 200);
- }
-
- $(window).on('hashchange', function(event) {
- var scrollPosition = $(window).scrollTop();
- var activeSectionTokens = scrollActions(scrollPosition);
- var activeElemToken = checkActiveElement(flatToc, scrollPosition);
- var scrollToken = activeSectionTokens.L2 ? activeSectionTokens.L2 : activeSectionTokens.L1;
- scrollToNav(scrollToken);
- var token = location.hash.slice(1);
- });
-
- var scrollPosition = $(window).scrollTop();
- scrollActions(scrollPosition);
- checkActiveElement(flatToc, scrollPosition);
- // TODO: prevent scroll on sidebar from propogating to window
- $(window).on('scroll', function(event) {
- var scrollPosition = $(window).scrollTop();
- var activeSectionTokens = scrollActions(scrollPosition);
- var activeElemToken = checkActiveElement(flatToc, scrollPosition);
- });
-});
diff --git a/site2/website/brodocs/stylesheet.css b/site2/website/brodocs/stylesheet.css
deleted file mode 100644
index 61bf3c5dc60..00000000000
--- a/site2/website/brodocs/stylesheet.css
+++ /dev/null
@@ -1,271 +0,0 @@
-/*
-Kubernetes colors
-
-kubernetes blue - rgb(50, 109, 230)
-dark blue - rgb(51, 113, 227)
-dark grey - rgb(48, 48, 48)
-light grey - rgb(161, 160, 158)
-*/
-
-/* User agent CSS overrides */
-#sidebar-wrapper ul, #sidebar-wrapper li {
- margin-left: 10px;
- padding-left: 0;
-}
-
-/* Inspired by Slate CSS */
-.body-content aside {
- padding: 1.6em;
- margin: 1.8em 0;
- background: lightsteelblue;
- line-height: 1.6;
- border-radius: 15px;
-}
-
-.body-content aside.warning {
- background-color: peachpuff;
-}
-
-.body-content aside.success {
- background-color: olivedrab;
-}
-
-.body-content aside:before {
- vertical-align: middle;
- padding-right: 1em;
- font-size: 16px;
-}
-
-.body-content aside.warning:before, .body-content aside.notice:before, .body-content aside.success:before {
- font-family: 'FontAwesome';
- font-style: normal;
- font-weight: normal;
- font-variant: normal;
- text-transform: none;
- line-height: 1;
-}
-
-.body-content aside.warning:before {
- content: "\f071";
-}
-
-.body-content aside.notice:before {
- content: "\f05a";
-}
-
-.body-content hr {
- margin: 2em 0;
- border-top: 2px solid dimgrey;
- border-bottom: 2px solid antiquewhite;
-}
-
-.body-content table {
- margin-bottom: 1em;
- overflow: auto;
-}
-
-.body-content table th, .body-content table td {
- text-align: left;
- vertical-align: top;
- line-height: 1.6;
-}
-
-.body-content table th {
- padding: 15px 20px;
- border-bottom: 1px solid lightsteelblue;
- vertical-align: bottom;
-}
-
-.body-content table td {
- padding: 10px;
-}
-
-.body-content table tr:last-child {
- border-bottom: 1px solid lightsteelblue;
-}
-
-.body-content table tr:nth-child(odd) > td {
- background-color: whitesmoke;
-}
-
-.body-content table tr:nth-child(even) > td {
- background-color: lightsteelblue;
-}
-
-.body-content dt {
- font-weight: bold;
-}
-
-.body-content dd {
- margin-left: 15px;
-}
-
-.body-content p, .body-content li, .body-content dt, .body-content dd {
- line-height: 1.6;
- margin-top: 0;
-}
-
-/* Brodoc CSS */
-
-body > #wrapper {
- display: block;
- padding-bottom: 500px;
- background-image: linear-gradient(90deg, #FFFFFF 63%, rgb(48, 48, 48) 63%);
-}
-
-#sidebar-wrapper {
- display: block;
- height: 100%;
- width: 20%;
- position: fixed;
- z-index: 1;
- top: 0;
- left: 0;
- background-color: whitesmoke;
- border-right: 2px solid slategrey;
- overflow-x: hidden;
- padding-top: 60px;
-}
-
-#sidebar-wrapper a {
- text-decoration: none;
- white-space: nowrap;
- overflow: hidden;
- text-overflow: ellipsis;
- padding: 0 5px;
-}
-
-#sidebar-wrapper ul {
- list-style: none;
-}
-
-#sidebar-wrapper a.selected {
- font-style: bold;
- color: whitesmoke;
- border: 1px solid rgb(161, 160, 158);
- background-color: rgb(51, 113, 227);
- border-radius: 5px;
-}
-
-#sidebar-wrapper .strong-nav {
- font-family: monospace;
- font-weight: bold;
-}
-
-#sidebar-wrapper .nav-level-1.strong-nav {
- margin-top: 25px;
-}
-
-#sidebar-wrapper .copyright {
- padding-left: 10px;
- padding-top: 50px;
- padding-bottom: 50px;
- text-decoration: underline;
-}
-
-#page-content-wrapper {
- margin-left: 20%;
- padding-top: 60px;
-}
-
-.body-content h1, .body-content h2 {
- width: 52%;
- clear: both;
- border-bottom: 3px solid lightslategrey;
-}
-
-.body-content > h3, .body-content > h4, .body-content > h5, .body-content > h6, .body-content > p, .body-content > aside, .body-content > ul > li, .body-content > ul > li {
- width: 52%;
- padding-top: 20px;
-}
-
-.body-content table {
- width: 52%;
- word-break: break-word;
-}
-
-.body-content table tr td:not(:first-child) {
- overflow-wrap: break-word;
- word-wrap: break-word;
-}
-
-.body-content table tr td a {
- word-break: break-word;
-}
-
-.body-content p code {
- text-overflow: ellipsis;
- display: inline-block;
- font-size: smaller;
- word-break: break-word;
-}
-
-.body-content blockquote {
- border-left: 0;
- border-radius: 5px;
-}
-
-.body-content pre.code-block {
- margin-bottom: 80px;
-}
-
-.body-content blockquote p, .body-content pre {
- color: black;
- font-size: 13px;
-}
-
-.body-content blockquote.code-block {
- background: lightsteelblue;
-}
-
-.body-content pre.code-block code {
- overflow: auto;
- overflow-wrap: normal;
- word-wrap: normal;
- white-space: pre;
-}
-
-.code-block {
- display: none;
- width: 45%;
- float: right;
- clear: right;
-}
-
-.code-block.active {
- display: initial;
-}
-
-#code-tabs-wrapper {
- width: 35%;
- height: 60px;
- position: fixed;
- top: 0;
- right: 0;
-}
-
-#code-tabs-wrapper .code-tab-list {
- float: right;
- margin-top: 0;
- padding: 0 10px;
-}
-
-#code-tabs-wrapper .code-tab {
- color: white;
- display: inline-block;
- padding: 0 30px;
- background: rgb(48, 48, 48);
- border: 1px solid rgb(161, 160, 158);
- border-radius: 5px;
-}
-
-#code-tabs-wrapper .tab-selected {
- background: rgb(51, 113, 227);
- font-style: bold;
- border-radius: 5px;
-}
-
-.side-nav a {
- color: black;
-}
-
diff --git a/site2/website/brodocs/tabvisibility.js b/site2/website/brodocs/tabvisibility.js
deleted file mode 100644
index 48c0df7fe26..00000000000
--- a/site2/website/brodocs/tabvisibility.js
+++ /dev/null
@@ -1,27 +0,0 @@
-$(document).ready(function() {
- var codeTabs = $('#code-tabs-wrapper').find('li');
-
- for (var i = 0; i < codeTabs.length; i++) {
- createCodeTabListeners(codeTabs, i);
- }
-
- function createCodeTabListeners(codeTabs, index) {
- var tab = $(codeTabs[index]),
- id = tab.attr('id'),
- codeClass = '.' + id;
- tab.on('click', function() {
- codeTabs.removeClass('tab-selected');
- tab.addClass('tab-selected');
- $('.code-block').removeClass('active');
- $(codeClass).addClass('active');
-
- });
- }
-
- function setDefautTab() {
- $(codeTabs[0]).addClass('tab-selected');
- $('.' + codeTabs[0].id).addClass('active');
- }
-
- setDefautTab();
-});
\ No newline at end of file
diff --git a/site2/website/coding-guide.md b/site2/website/coding-guide.md
deleted file mode 100644
index b23b5be4e76..00000000000
--- a/site2/website/coding-guide.md
+++ /dev/null
@@ -1,79 +0,0 @@
-The guidelines help to encourage consistency and best practices among people working on _Apache Pulsar_ code base. You should observe the guidelines unless there is compelling reason to ignore them. We use checkstyle to enforce coding style, refer to our [checkstyle rules](https://github.com/apache/pulsar/blob/master/buildtools/src/main/resources/pulsar/checkstyle.xml) for all enforced checkstyle rules.
-
-## Java
-
-Apache Pulsar code follows the [Sun Java Coding Convention](http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html), with the following additions.
-
-* Lines can not be longer than 120 characters.
-* Indentation should be **4 spaces**. Tabs should never be used.
-* Use curly braces even for single-line ifs and elses.
-* No @author tags in any javadoc.
-* Use try-with-resources blocks whenever is possible.
-* **TODO**s should be associated to at least one issue.
-
-## Dependencies
-
-Apache Pulsar uses the following libraries a lot:
-
-* [Guava](https://github.com/google/guava): as a fundamental core library
-* [Netty](http://netty.io/): for network communications and memory buffer management.
-
-Use these libraries whenever possible rather than introducing more dependencies.
-
-Dependencies are bundled with our binary distributions, so we need to attach the relevant licenses. See [Third party dependencies and licensing](https://pulsar.apache.org/docs/en/client-libraries/) for a guide on how to do it correctly.
-
-## Future
-
-Java-8 Future is preferred over Guava's Listenable Future. Use Java-8 Future whenever possible.
-
-## Memory
-
-Use netty _ByteBuf_ over java nio _ByteBuffer_ for internal usage. As we are using Netty Buffer for memory management.
-
-## Logging
-
-* Logging should be taken seriously. Please take the time to access the logs when making a change to ensure that the important things are getting logged and there is no junk there.
-* Logging statements should be complete sentences with proper capitalization that are written to be read by a person not necessarily familiar with the source code.
-* All loggings should be done with **SLF4j**, never _System.out_ or _System.err_.
-
-### Logging levels
-
-- _INFO_ is the level you should assume the software will be run in. INFO messages are things which are not bad but which the user will definitely want to know about every time they occur.
-- _TRACE_ and _DEBUG_ are both things you turn on when something is wrong and you want to figure out what is going on. _DEBUG_ should not be so fine grained that it will seriously affect performance of the program. _TRACE_ can be anything. You should wrap _DEBUG_ and _TRACE_ statements in the `if (logger.isDebugEnabled)` or `if (logger.isTraceEnabled)` check to avoid performance degradation.
-- _WARN_ and _ERROR_ indicate something that is **BAD**. Use _WARN_ if you aren't totally sure it is bad, and _ERROR_ if you are.
-
-Log the _stack traces_ at **ERROR** level, but never at **INFO** level or below. You can log at **WARN** level if you are interested in debugging.
-
-## Monitoring
-
-* Any new features should come with appropriate metrics, so monitoring the feature is working correctly.
-* Those metrics should be taken seriously and only export useful metrics that would be used on production on monitoring/alerting healthy of the system, or troubleshooting problems.
-
-## Unit tests
-
-* New changes should come with unit tests that verify the functionality being added.
-* Unit tests should test the least amount of code possible. Don't start the whole server unless there is no other way to test a single class or small group of classes in isolation.
-* Tests should not depend on any external resources. They need to setup and teardown their own stuff.
-* It is okay to use the filesystem and network in tests since that's our business, but you need to clean up them after test.
-* _Do not_ use sleep or other timing assumptions in tests. It is wrong and will fail intermittently on any test server with other things going on that causes delays.
-* You'd better add a _timeout_ value to all test cases, to prevent a build from completing indefinitely. For example, `@Test(timeout=60000)`
-
-## Configuration
-
-* When you use the config files, think of the names from the very beginning.
-* If you run the program without tuning parameters, use the default values.
-* All configuration settings should be added accordingly in the [default configuration file](https://github.com/apache/pulsar/tree/master/conf) directory and documented accordingly.
-
-## Concurrency
-
-Apache Pulsar is a low latency system, it is implemented as a purely asynchronous service, which is accomplished as follows:
-
-* All public classes should be **thread-safe**.
-* We prefer using [OrderedExecutor](https://github.com/apache/bookkeeper/blob/master/bookkeeper-common/src/main/java/org/apache/bookkeeper/common/util/OrderedExecutor.java) for executing any asynchronous actions. The mutations to the same instance should be submitted to the same thread to execute.
-* If synchronization and locking are required, they should be in a fine granularity way.
-* All threads should have proper meaningful name.
-* If a class is not thread-safe, it should be annotated [@NotThreadSafe](https://github.com/misberner/jsr-305/blob/master/ri/src/main/java/javax/annotation/concurrent/NotThreadSafe.java). The instances that use this class is responsible for its synchronization.
-
-## Backwards compatibility
-* Wire protocol should support backwards compatibility to enable no-downtime upgrades. This means the servers **MUST** be able to support requests from both old and new clients simultaneously.
-* Metadata formats and data formats should support backwards compatibility.
diff --git a/site2/website/contributing.md b/site2/website/contributing.md
deleted file mode 100644
index d9b4081c216..00000000000
--- a/site2/website/contributing.md
+++ /dev/null
@@ -1,348 +0,0 @@
-
-The Apache Pulsar community welcomes contributions from anyone with a passion for distributed systems! Pulsar has many different opportunities for contributions --
-write new examples/tutorials, add new user-facing libraries, write new Pulsar IO connectors, or participate on the documentation effort.
-
-We use a review-then-commit workflow in Pulsar for all contributions.
-
-**For larger contributions or those that affect multiple components:**
-
-1. **Engage**: We encourage you to work with the Pulsar community on the
- [Github Issues](https://github.com/apache/pulsar/issues) and
- [developer’s mailing list](/contact) to identify
- good areas for contribution.
-1. **Design:** More complicated contributions will likely benefit from some early discussion in
- order to scope and design them well.
-
-**For all contributions:**
-
-1. **Code:** code changes are always welcomed.
-2. **Doc**: it is worth taking the time to make users know your code changes. Pulsar's long-term success rests on its ease of use, maintainability, etc.
-3. **Review:** Submit a pull request with your contribution to our
- [GitHub Repo](https://github.com/apache/pulsar). Work with a committer to review and
- iterate on the code, if needed.
-4. **Commit:** Once at least 2 Pulsar committers have approved the pull request, a Pulsar committer
- will merge it into the master branch (and potentially backport to stable branches in case of
- bug fixes).
-
-We look forward to working with you!
-
-## Engage
-
-### Mailing list(s)
-
-We discuss design and implementation issues on the [dev@pulsar.apache.org](mailto:dev@pulsar.apache.org)
-mailing list, which is archived [here](https://lists.apache.org/list.html?dev@pulsar.apache.org).
-Join by emailing [`dev-subscribe@pulsar.apache.org`](mailto:dev-subscribe@pulsar.apache.org).
-
-If interested, you can also join the other [mailing lists](/contact).
-
-### Github Issues
-
-We are using [Github Issues](https://github.com/apache/pulsar/issues) as the issue tracking
-and project management tool, as well as a way to communicate among a very diverse and distributed set
-of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all
-Pulsar related work are being tracked there.
-
-If you do not already have an Github account, sign up [here](https://github.com/join).
-
-If a quick [search](https://github.com/apache/pulsar/issues) doesn’t turn up an existing
-Github issue for the work you want to contribute, create it. Please discuss your idea with a
-committer in Github or, alternatively, on the developer mailing list.
-
-If there’s an existing Github issue for your intended contribution, please comment about your intended
-work. Once the work is understood, a committer will assign the issue to you. If an issue is currently
-assigned, please check with the current assignee before reassigning.
-
-For moderate or large contributions, you should not start coding or writing a design document unless
-there is a corresponding Github issue assigned to you for that work. Simple changes, like fixing typos,
-do not require an associated issue.
-
-### Online discussions
-
-We are using [Apache Pulsar Slack channel](https://apache-pulsar.slack.com/) for online discussions.
-You can self-invite yourself by accessing [this link](https://apache-pulsar.herokuapp.com/).
-
-Slack channels are great for quick questions or discussions on specialized topics. Remember that we
-strongly encourage communication via the mailing lists, and we prefer to discuss more complex subjects
-by email. Developers should be careful to move or duplicate all the official or useful discussions to
-the issue tracking system and/or the dev mailing list.
-
-## Design
-
-To avoid potential frustration during the code review cycle, we encourage you to clearly scope and
-design non-trivial contributions with the Pulsar community before you start coding.
-
-We are using "Pulsar Improvement Proposals" (or "PIP") for managing major changes to Pulsar. The
-list of all PIPs is maintained in the Pulsar wiki at https://github.com/apache/pulsar/wiki.
-
-## Code
-
-To contribute code to Apache Pulsar, you’ll have to do a few administrative steps once, and then
-follow the [Coding Guide](../coding-guide).
-
-### One-time Setup
-
-#### [Optionally] Submit Contributor License Agreement
-
-Apache Software Foundation (ASF) desires that all contributors of ideas, code, or documentation to the Apache projects complete, sign, and submit an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) (ICLA). The purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to the ASF and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time.
-
-We require you to have an ICLA on file with the Apache Secretary for larger contributions only. For smaller ones, however, we rely on [clause five](http://www.apache.org/licenses/LICENSE-2.0#contributions) of the Apache License, Version 2.0, describing licensing of intentionally submitted contributions and do not require an ICLA in that case.
-
-#### Obtain a GitHub account
-
-We use GitHub’s pull request functionality to review proposed code changes.
-
-If you do not already have a personal GitHub account, sign up [here](https://github.com/join).
-
-#### Fork the repository on GitHub
-
-Go to the [Pulsar GitHub Repo](https://github.com/apache/pulsar/) and fork the repository
-to your own private account. This will be your private workspace for staging changes.
-
-#### Clone the repository locally
-
-You are now ready to create the development environment on your local machine. Feel free to repeat
-these steps on all machines that you want to use for development.
-
-We assume you are using SSH-based authentication with GitHub. If necessary, exchange SSH keys with
-GitHub by following [their instructions](https://help.github.com/articles/generating-an-ssh-key/).
-
-Clone your personal Pulsar’s GitHub fork.
-
- $ git clone https://github.com/<Github_user>/pulsar.git
- $ cd pulsar
-
-Add Apache Repo as additional Git remotes, where you can sync the changes (for committers, you need
-these two remotes for pushing changes).
-
- $ git remote add apache https://github.com/apache/pulsar
-
-You are now ready to start developing!
-
-#### IDE Setup
-
-For how to set up IDE, see [here](https://github.com/apache/pulsar/blob/master/README.md#setting-up-your-ide).
-
-
-### Create a branch in your fork
-
-You’ll work on your contribution in a branch in your own (forked) repository. Create a local branch, initialized with the state of the branch you expect your changes to be merged into. Keep in mind that we use several branches, including `master`, feature-specific, and release-specific branches. If you are unsure, initialize with the state of the `master` branch.
-
- $ git fetch apache
- $ git checkout -b <my-branch> apache/master
-
-At this point, you can start making and committing changes to this branch in a standard way.
-
-### Syncing and pushing your branch
-
-Periodically while you work, and certainly before submitting a pull request, you should update your branch with the most recent changes to the target branch.
-
- $ git pull --rebase
-
-Remember to always use `--rebase` parameter to avoid extraneous merge commits.
-
-Then you can push your local, committed changes to your (forked) repository on GitHub. Since rebase may change that branch's history, you may need to force push. You'll run:
-
- $ git push <GitHub_user> <my-branch> --force
-
-### Testing
-
-All code should have appropriate unit testing coverage. New code should have new tests in the same contribution. Bug fixes should include a regression test to prevent the issue from reoccurring.
-
-### Licensing
-
-All code contributed to Pulsar will be licensed under [Apache License V2](https://www.apache.org/licenses/LICENSE-2.0). You need to ensure every new files you are adding have the right
-license header. You can add license header to your files by running following command:
-
-```shell
-$ mvn initialize license:format
-```
-
-### Develop C++/Python Client
-
-Currently C++ and Python client are developed under `pulsar-client-cpp` directory. You can use following commands to build and test your c++ or python code changes.
-
-#### Build C++/Python Client
-
-```
-$ ./pulsar-client-cpp/docker-build.sh
-```
-
-### Run C++/Python Client Tests
-
-```
-$ ./pulsar-client-cpp/docker-test.sh
-```
-
-### Checkstyle
-
-Before you push the C++/Python changes for review, you should format the files to apply the checkstyle rule Pulsar is using for C++/Python code.
-
-```
-$ ./pulsar-client-cpp/docker-format.sh
-```
-
-## Review
-
-Once the initial code is complete and the tests pass, it’s time to start the code review process. We review and discuss all code, no matter who authors it. It’s a great way to build community, since you can learn from other developers, and they become familiar with your contribution. It also builds a strong project by encouraging a high quality bar and keeping code consistent throughout the project.
-
-### Create a pull request
-
-Organize your commits to make a committer’s job easier when reviewing. Committers normally prefer multiple small pull requests, instead of a single large pull request. Within a pull request, a relatively small number of commits that break the problem into logical steps is preferred. For most pull requests, you'll squash your changes down to 1 commit. You can use the following command to re-order, squash, edit, or change description of individual commits.
-
- $ git rebase -i apache/master
-
-You'll then push to your branch on GitHub. Note: when updating your commit after pull request feedback and use squash to get back to one commit, you will need to do a force submit to the branch on your repo.
-
-Navigate to the [Pulsar GitHub Repo](https://github.com/apache/pulsar) to create a pull request.
-
-> **Note**
->
-> Vague, boring, and unclear PR titles decrease team efficiency and productivity. Good titles speed up the review process and increase search efficiency. PR titles should be engaging, easy to understand, and readable. For how to **write self-explanatory PR titles** and **quality PR title examples**, see [[Guideline] Pulsar PR Naming Convention](https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit#).
-
-In the pull request description, please include:
-
- * Motivation : Why is this change needed? What problem is addressing?
- * Changes: Summary of what this pull request is changing, to help reviewers at better understanding
- the changes.
-
-Please include a descriptive pull request message to help make the committer’s job easier when reviewing.
-It’s fine to refer to existing design docs or the contents of the associated issue as appropriate.
-
-If the pull request is fixing an issue, include a mention to in the description, like:
-
-```
-Fixes #1234
-```
-
-This will automatically change the state on the referenced issues.
-
-If you know a good committer to review your pull request, please make a comment like the following. If not, don’t worry -- a committer will pick it up.
-
- Hi @<GitHub-committer-username>, can you please take a look?
-
-When choosing a committer to review, think about who is the expert on the relevant code, who the stakeholders are for this change, and who else would benefit from becoming familiar with the code. If you’d appreciate comments from additional folks but already have a main committer, you can explicitly cc them using `@<GitHub-committer-username>`.
-
-### Code Review and Revision
-
-During the code review process, don’t rebase your branch or otherwise modify published commits, since this can remove existing comment history and be confusing to the committer when reviewing. When you make a revision, always push it in a new commit.
-
-Our GitHub repo automatically provides pre-commit testing coverage using Jenkins. Please make sure those tests pass; the contribution cannot be merged otherwise.
-
-### LGTM
-
-Once the committer is happy with the change, they’ll approve the pull request with an LGTM (“*looks good to me!*”) or a `+1`. At this point, the committer will take over, possibly make some additional touch ups, and merge your changes into the codebase.
-
-In the case the author is also a committer, either can merge the pull request. Just be sure to communicate clearly whose responsibility it is in this particular case.
-
-Thank you for your contribution to Pulsar!
-
-### Deleting your branch
-Once the pull request is merged into the Pulsar repository, you can safely delete the branch locally and purge it from your forked repository.
-
-From another local branch, run:
-
- $ git fetch origin
- $ git branch -d <my-branch>
- $ git push origin --delete <my-branch>
-
-## Commit (committers only)
-
-Once the code has been peer reviewed by a committer, the next step is for the committer to merge it into the Github repo.
-
-Pull requests should not be merged before the review has approved from at least 2 committers.
-
-> **Tip**
->
-> Git commit message is not only the best way to communicate context about code changes, but also shows whether a developer is a good collaborator. If the first commit message of a PR is not clear but the PR description is clear and concise, when merging a PR, consider copying the PR description to the commit message box or writing a proper one rather than using the default (first) commit message (see image below). In this way, others know the changes clearly, which is beneficial to cut [...]
-
-
-
-### Contributor License Agreement
-
-If you are merging a larger contribution, please make sure that the contributor has an ICLA on file with the Apache Secretary. You can view the list of committers [here](http://home.apache.org/phonebook.html?unix=committers), as well as [ICLA-signers who aren’t yet committers](http://home.apache.org/unlistedclas.html).
-
-For smaller contributions, however, this is not required. In this case, we rely on [clause five](http://www.apache.org/licenses/LICENSE-2.0#contributions) of the Apache License, Version 2.0, describing licensing of intentionally submitted contributions.
-
-## Documentation
-
-### Website
-
-The Pulsar website is in the same [Pulsar Github Repo](https://github.com/apache/pulsar). The source files are hosted under `site2` directory in `master` branch,
-the static content is generated by CI job and merged into the `asf-site` branch.
-
-Follow the [README](https://github.com/apache/pulsar/tree/master/site2) for making contributions to the website.
-
-#### Updating user logo
-The Apache Pulsar Community welcomes all users to update their company logos on Pulsar website. If your team or organization has adopted Pulsar in production, you can update your company logos on [Pulsar website](https://pulsar.apache.org/en/powered-by/).
-
-To update your company logo, follow these steps:
-1. Open [link](https://github.com/apache/pulsar/blob/master/site2/website/data/users.js) in your browser, then click the **Edit** icon to fork Pulsar repo, create a new branch and edit this file.
-2. Add your company’s information at the end of file.
-
- Example:
- ```
- {
- name: 'StreamNative',
- url: 'https://streamnative.io/',
- logo: 'https://streamnative.io/static/images/streamnative-logo-white-bakground.png',
- logo_white: true
- }
- ```
- >Note
- ></br>The `logo_white` parameter is set to `true` only when your company logo is in white color. Otherwise, you only need to add `name`, `url` and `logo`.
-
-3. Commit the changes in your account’s repo, publish the branch and create pull request.
-4. Update comments, if any. If no more comment, your pull request will be approved and merged by reviewers.
-
-## Becoming a committer
-
-Committers are community members that have write access to the project’s
-repositories, i.e., they can modify the code, documentation, and website
-by themselves and also accept other contributions.
-
-There is no strict protocol for becoming a committer. Candidates for new
-committers are typically people that are active contributors and
-community members.
-
-Being an active community member means participating on mailing list
-discussions, helping to answer questions, verifying release candidates,
-being respectful towards others, and following the meritocratic
-principles of community management. Since the
-[Apache Way](https://www.apache.org/foundation/governance/)
-has a strong focus on the project community, this part is very important.
-
-Of course, contributing code and documentation to the project is
-important as well. A good way to start is contributing improvements, new
-features, or bug fixes. You need to show that you take responsibility
-for the code that you contribute, add tests and documentation, and help
-maintaining it.
-
-Every new committer has to be proposed by a current committer and then
-privately discussed and voted in by the members of the Pulsar PMC.
-For details about this process and for candidate requirements see the
-general [Apache guidelines for assessing new candidates for committership](https://community.apache.org/newcommitter.html).
-Candidates prepare for their nomination as committer by contributing
-to the Pulsar project and its community, by acting according to the
-[Apache Way](https://www.apache.org/foundation/how-it-works.html),
-and by generally following the path from
-[contributor to committer](https://community.apache.org/contributors/)
-for Apache projects.
-
-If you would like to become a committer, you should engage with the
-community and start contributing to Apache Pulsar in any of the above
-ways. You might also want to talk to other committers and ask for their
-advice and guidance.
-
-## Becoming member of PMC
-
-The PMC is the project governance body. Committers or contributors that
-have demonstrated continued involvement with the community can be
-nominated to become members of the PMC.
-
-PMC members nominate new contributors to the project as either
-committers or as new PMC members, and PMC members cast votes on electing
-new committers or PMC members to the project. PMC members also have
-binding votes on any project matters. Refer to
-[ASF PMCs governance](http://www.apache.org/foundation/governance/pmcs.html)
-for a more detailed explanation of the duties and roles of the PMC.
diff --git a/site2/website/core/Footer.js b/site2/website/core/Footer.js
deleted file mode 100644
index 03a430e11ae..00000000000
--- a/site2/website/core/Footer.js
+++ /dev/null
@@ -1,180 +0,0 @@
-/**
- * Copyright (c) 2017-present, Facebook, Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-
-const React = require('react');
-
-/*
-class Footer extends React.Component {
- docUrl(doc, language) {
- const baseUrl = this.props.config.baseUrl;
- return baseUrl + 'docs/' + (language ? language + '/' : '') + doc;
- }
-
- pageUrl(doc, language) {
- const baseUrl = this.props.config.baseUrl;
- return baseUrl + (language ? language + '/' : '') + doc;
- }
-
- render() {
- const currentYear = new Date().getFullYear();
- return (
- <footer className="nav-footer" id="footer">
- <section className="sitemap">
- <a href={this.props.config.baseUrl} className="nav-home">
- {this.props.config.footerIcon && (
- <img
- src={this.props.config.baseUrl + this.props.config.footerIcon}
- alt={this.props.config.title}
- width="66"
- height="58"
- />
- )}
- </a>
- <div>
- <h5>Docs</h5>
- <a href={this.docUrl('doc1.html', this.props.language)}>
- Getting Started (or other categories)
- </a>
- <a href={this.docUrl('doc2.html', this.props.language)}>
- Guides (or other categories)
- </a>
- <a href={this.docUrl('doc3.html', this.props.language)}>
- API Reference (or other categories)
- </a>
- </div>
- <div>
- <h5>Community</h5>
- <a href={this.pageUrl('users.html', this.props.language)}>
- User Showcase
- </a>
- <a
- href="http://stackoverflow.com/questions/tagged/"
- target="_blank"
- rel="noreferrer noopener">
- Stack Overflow
- </a>
- <a href="https://discordapp.com/">Project Chat</a>
- <a
- href="https://twitter.com/"
- target="_blank"
- rel="noreferrer noopener">
- Twitter
- </a>
- </div>
- <div>
- <h5>More</h5>
- <a href={this.props.config.baseUrl + 'blog'}>Blog</a>
- <a href="https://github.com/">GitHub</a>
- <a
- className="github-button"
- href={this.props.config.repoUrl}
- data-icon="octicon-star"
- data-count-href="/facebook/docusaurus/stargazers"
- data-show-count={true}
- data-count-aria-label="# stargazers on GitHub"
- aria-label="Star this project on GitHub">
- Star
- </a>
- </div>
- </section>
-
- <a
- href="https://code.facebook.com/projects/"
- target="_blank"
- rel="noreferrer noopener"
- className="fbOpenSource">
- <img
- src={this.props.config.baseUrl + 'img/oss_logo.png'}
- alt="Facebook Open Source"
- width="170"
- height="45"
- />
- </a>
- <section className="copyright">{this.props.config.copyright}</section>
- </footer>
- );
- }
-}
-*/
-
-class Footer extends React.Component {
- docUrl(doc, language) {
- const baseUrl = this.props.config.baseUrl;
- return baseUrl + 'docs/' + (language ? language + '/' : '') + doc;
- }
-
- pageUrl(doc, language) {
- const baseUrl = this.props.config.baseUrl;
- return baseUrl + (language ? language + '/' : '') + doc;
- }
-
- render() {
- const currentYear = new Date().getFullYear();
-
- const contactUrl = this.pageUrl('contact', this.props.language)
- const eventsUrl = this.pageUrl('events', this.props.language)
- const twitterUrl = 'https://twitter.com/Apache_Pulsar'
- const wikiUrl = 'https://github.com/apache/pulsar/wiki'
- const issuesUrl = 'https://github.com/apache/pulsar/issues'
- const summitUrl = 'https://pulsar-summit.org/'
- const resourcesUrl = this.pageUrl('resources', this.props.language)
- const teamUrl = this.pageUrl('team', this.props.language)
- const poweredByUrl = this.pageUrl('powered-by', this.props.language)
- const contributingUrl = this.pageUrl('contributing', this.props.language)
- const codingUrl = this.pageUrl('coding-guide', this.props.language)
-
- const communityMenuJs = `
- const community = document.querySelector("a[href='#community']").parentNode;
- const communityMenu =
- '<li>' +
- '<a id="community-menu" href="#">Community <span style="font-size: 0.75em"> ▼</span></a>' +
- '<div id="community-dropdown" class="hide">' +
- '<ul id="community-dropdown-items">' +
- '<li><a href="${contactUrl}">Contact</a></li>' +
- '<li><a href="${contributingUrl}">Contributing</a></li>' +
- '<li><a href="${codingUrl}">Coding guide</a></li>' +
- '<li><a href="${eventsUrl}">Events</a></li>' +
- '<li><a href="${twitterUrl}" target="_blank">Twitter ❐</a></li>' +
- '<li><a href="${wikiUrl}" target="_blank">Wiki ❐</a></li>' +
- '<li><a href="${issuesUrl}" target="_blank">Issue tracking ❐</a></li>' +
- '<li><a href="${summitUrl}" target="_blank">Pulsar Summit ❐</a></li>' +
- '<li> </li>' +
- '<li><a href="${resourcesUrl}">Resources</a></li>' +
- '<li><a href="${teamUrl}">Team</a></li>' +
- '<li><a href="${poweredByUrl}">Powered By</a></li>' +
- '</ul>' +
- '</div>' +
- '</li>';
-
- community.innerHTML = communityMenu;
-
- const communityMenuItem = document.getElementById("community-menu");
- const communityDropDown = document.getElementById("community-dropdown");
- communityMenuItem.addEventListener("click", function(event) {
- event.preventDefault();
-
- if (communityDropDown.className == 'hide') {
- communityDropDown.className = 'visible';
- } else {
- communityDropDown.className = 'hide';
- }
- });
- `
-
- return (
- <footer className="nav-footer" id="footer">
- <section className="copyright">{this.props.config.copyright}</section>
- <span>
- <script dangerouslySetInnerHTML={{__html: communityMenuJs }} />
- </span>
- </footer>
- );
- }
-}
-
-
-module.exports = Footer;
diff --git a/site2/website/crowdin.yaml b/site2/website/crowdin.yaml
deleted file mode 100644
index 359ff71642b..00000000000
--- a/site2/website/crowdin.yaml
+++ /dev/null
@@ -1,53 +0,0 @@
-project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
-api_key_env: CROWDIN_DOCUSAURUS_API_KEY
-base_path: "../"
-preserve_hierarchy: true
-
-files:
- -
- source: '/docs/**/*.md'
- translation: '/website/translated_docs/%locale%/**/%original_file_name%'
- languages_mapping: &anchor
- locale:
- 'af': 'af'
- 'ar': 'ar'
- 'bs-BA': 'bs-BA'
- 'ca': 'ca'
- 'cs': 'cs'
- 'da': 'da'
- 'de': 'de'
- 'el': 'el'
- 'es-ES': 'es-ES'
- 'fa': 'fa-IR'
- 'fi': 'fi'
- 'fr': 'fr'
- 'he': 'he'
- 'hu': 'hu'
- 'id': 'id-ID'
- 'it': 'it'
- 'ja': 'ja'
- 'ko': 'ko'
- 'mr': 'mr-IN'
- 'nl': 'nl'
- 'no': 'no-NO'
- 'pl': 'pl'
- 'pt-BR': 'pt-BR'
- 'pt-PT': 'pt-PT'
- 'ro': 'ro'
- 'ru': 'ru'
- 'sk': 'sk-SK'
- 'sr': 'sr'
- 'sv-SE': 'sv-SE'
- 'tr': 'tr'
- 'uk': 'uk'
- 'vi': 'vi'
- 'zh-CN': 'zh-CN'
- 'zh-TW': 'zh-TW'
- -
- source: '/website/versioned_docs/**/*.md'
- translation: '/website/translated_docs/%locale%/**/%original_file_name%'
- languages_mapping: *anchor
- -
- source: '/website/i18n/en.json'
- translation: '/website/i18n/%locale%.json'
- languages_mapping: *anchor
diff --git a/site2/website/data/connectors.js b/site2/website/data/connectors.js
deleted file mode 100644
index 5c664e328ea..00000000000
--- a/site2/website/data/connectors.js
+++ /dev/null
@@ -1,194 +0,0 @@
-module.exports = [
- {
- name: 'aerospike',
- longName: 'Aerospike sink',
- type: 'Sink',
- link: 'https://www.aerospike.com/'
- },
- {
- name: 'canal',
- longName: 'Alibaba Canal CDC source',
- type: 'Source',
- link: 'https://github.com/alibaba/canal'
- },
- {
- name: 'cassandra',
- longName: 'Apache Cassandra source and sink',
- type: 'Source and sink',
- link: 'https://cassandra.apache.org'
- },
- {
- name: 'kafka-connect-adaptor',
- longName: 'Apache Kafka Connect Adaptor source and sink',
- type: 'Source and sink',
- link: 'http://kafka.apache.org/'
- },
- {
- name: 'dynamodb',
- longName: 'AWS DynamoDB source',
- type: 'Source',
- link: 'https://aws.amazon.com/dynamodb/'
- },
- {
- name: 'kinesis',
- longName: 'AWS Kinesis source and sink',
- type: 'Source and sink',
- link: 'https://aws.amazon.com/kinesis/'
- },
- {
- name: 'debezium-mysql',
- longName: 'Debezium MySQL CDC source',
- type: 'Source',
- link: 'https://debezium.io/'
- },
- {
- name: 'debezium-postgres',
- longName: 'Debezium PostgreSQL CDC source',
- type: 'Source',
- link: 'https://debezium.io/'
- },
- {
- name: 'debezium-mongodb',
- longName: 'Debezium MongoDB CDC source',
- type: 'Source',
- link: 'https://debezium.io/'
- },
- {
- name: 'debezium-mssql',
- longName: 'Debezium SQL Server CDC source',
- type: 'Source',
- link: 'https://debezium.io/'
- },
- {
- name: 'debezium-oracle',
- longName: 'Debezium Oracle CDC source',
- type: 'Source',
- link: 'https://debezium.io/'
- },
- {
- name: 'elastic-search',
- longName: 'ElasticSearch source and sink',
- type: 'Source and sink',
- link: 'https://www.elastic.co/'
- },
- {
- name: 'file',
- longName: 'File source',
- type: 'Source',
- link: 'https://github.com/apache/pulsar/tree/master/pulsar-io/file'
- },
- {
- name: 'flume',
- longName: 'Flume source and sink',
- type: 'Source and sink',
- link: 'https://flume.apache.org/'
- },
- {
- name: 'hbase',
- longName: 'HBase sink',
- type: 'Sink',
- link: 'https://hbase.apache.org/'
- },
- {
- name: 'hdfs2',
- longName: 'HDFS2 sink',
- type: 'Sink',
- link: 'https://hadoop.apache.org/'
- },
- {
- name: 'hdfs3',
- longName: 'HDFS3 sink',
- type: 'Sink',
- link: 'https://hadoop.apache.org/'
- },
- {
- name: 'influxdb',
- longName: 'InfluxDB sink',
- type: 'Sink',
- link: 'https://www.influxdata.com/'
- },
- {
- name: 'jdbc-clickhouse',
- longName: 'JDBC ClickHouse sink',
- type: 'Sink',
- link: 'https://clickhouse.tech/'
- },
- {
- name: 'jdbc-mariadb',
- longName: 'JDBC MariaDB sink',
- type: 'Sink',
- link: 'https://mariadb.org/'
- },
- {
- name: 'jdbc-postgres',
- longName: 'JDBC PostgresSQL sink',
- type: 'Sink',
- link: 'https://www.postgresql.org/'
- },
- {
- name: 'jdbc-sqlite',
- longName: 'JDBC SQLite sink',
- type: 'Sink',
- link: 'https://www.sqlite.org/'
- },
- {
- name: 'kafka',
- longName: 'Kafka source and sink',
- type: 'Source and sink',
- link: 'https://kafka.apache.org/'
- },
- {
- name: 'mongo',
- longName: 'MongoDB sink',
- type: 'Sink',
- link: 'https://www.mongodb.com/'
- },
- {
- name: 'netty',
- longName: 'Netty source',
- type: 'Source',
- link: 'https://netty.io/'
- },
- {
- name: 'nsq',
- longName: 'NSQ source',
- type: 'Source',
- link: 'https://nsq.io/',
- },
- {
- name: 'rabbitmq',
- longName: 'RabbitMQ source and sink',
- type: 'Source and sink',
- link: 'https://www.rabbitmq.com/'
- },
- {
- name: 'redis',
- longName: 'Redis sink',
- type: 'Sink',
- link: 'https://redis.io/'
- },
- {
- name: 'solr',
- longName: 'Solr sink',
- type: 'Sink',
- link: 'https://lucene.apache.org/solr/'
- },
- {
- name: 'netty',
- longName: 'TCP/UDP with Netty source',
- type: 'Source',
- link: 'https://netty.io/'
- },
- {
- name: 'data-generator',
- longName: 'Test Data Generator source',
- type: 'Source',
- link: 'https://github.com/apache/pulsar/tree/master/pulsar-io/data-generator'
- },
- {
- name: 'twitter',
- longName: 'Twitter Firehose source',
- type: 'Source',
- link: 'https://developer.twitter.com/en/docs'
- }
-]
diff --git a/site2/website/data/resources.js b/site2/website/data/resources.js
deleted file mode 100644
index 2158c74f4eb..00000000000
--- a/site2/website/data/resources.js
+++ /dev/null
@@ -1,1026 +0,0 @@
-module.exports = {
- books: [
- {
- book: 'Apache Pulsar in Action',
- author: "David Kjerrumgaard",
- link: 'https://www.manning.com/books/apache-pulsar-in-action/'
- },
- {
- book: 'Mastering Apache Pulsar',
- author: "Jowanza Joseph",
- link: 'https://www.oreilly.com/library/view/mastering-apache-pulsar/9781492084891/'
- },
- {
- book: 'Cloud-Native Microservices with Apache Pulsar',
- author: "Rahul Sharma, Mohammad Atyab",
- link: 'https://link.springer.com/book/10.1007/978-1-4842-7839-0'
- },
- {
- book: '深入解析 Apache Pulsar（Chinese Book, which means "Deep Dive into Apache Pulsar")',
- author: "Lin Lin",
- link: 'https://www.phei.com.cn/module/goods/wssd_content.jsp?bookid=59310'
- }
- ],
- articles: [
- {
- forum: 'Pedro Silvestre',
- forum_link: 'https://www.doc.ic.ac.uk/~pms20/',
- date: 'Oct 2021',
- title: "On the Internals of Stream Processing Systems",
- link: 'https://www.doc.ic.ac.uk/~pms20/post/stream-processing-thread-model/'
- },
- {
- forum: 'Memgraph Blog',
- forum_link: 'https://memgraph.com/blog',
- date: 'Nov 2021',
- title: "Announcing Memgraph 2.1",
- link: 'https://memgraph.com/blog/memgraph-2-1-release'
- },
- {
- forum: 'DataStax Blog',
- forum_link: 'https://www.datastax.com/blog',
- date: 'Nov 2021',
- title: "Infinite Scale without Fail",
- link: 'https://www.datastax.com/blog/infinite-scale-without-fail-starlight-rabbitmq'
- },
- {
- forum: 'Splunk-MaaS',
- forum_link: 'https://medium.com/splunk-maas',
- date: 'Oct/Nov 2021',
- title: "Apache BookKeeper Observability — Part 1 of 5 ",
- link: 'https://medium.com/splunk-maas/apache-bookkeeper-observability-part-1-introducing-the-metrics-7f0acb32d0dc'
- },
- {
- forum: 'BetterProgramming',
- forum_link: 'https://betterprogramming.pub/',
- date: 'Nov 2021',
- title: "Distributed Locks With Apache Pulsar",
- link: 'https://betterprogramming.pub/distributed-locks-with-apache-pulsar-2d95a4d5ff5e'
- },
- {
- forum: 'Data in Motion',
- forum_link: 'https://www.datainmotion.dev/',
- date: 'Nov 2021',
- title: "Producing and Consuming Pulsar messages with Apache NiFi",
- link: 'https://www.datainmotion.dev/2021/11/producing-and-consuming-pulsar-messages.html'
- },
- {
- forum: 'Umut Bayram\'s Medium',
- forum_link: 'https://medium.com/@ubayram',
- date: 'Nov 2021',
- title: "Apache Pulsar- Apache Kafka vs Apache Pulsar (Turkish)",
- link: 'https://medium.com/@ubayram/apache-pulsar-apache-kafka-vs-apache-pulsar-418a998084d'
- },
- {
- forum: 'StreamNative Blog ',
- forum_link: 'https://streamnative.io/blogs/',
- date: 'Nov 2021',
- title: "Building Edge Applications With Apache Pulsar",
- link: 'https://streamnative.io/blog/engineering/2021-11-17-building-edge-applications-with-apache-pulsar/'
- },
- {
- forum: 'The New Stack',
- forum_link: 'https://thenewstack.io/',
- date: 'Nov 2021',
- title: "Apache Pulsar: A Unified Queueing and Streaming Platform",
- link: 'https://thenewstack.io/apache-pulsar-a-unified-queueing-and-streaming-platform/'
- },
- {
- forum: 'jaxenter',
- forum_link: 'https://jaxenter.com/',
- date: 'Nov 2021',
- title: "Why Pulsar Beats Kafka for a Scalable, Distributed Data Architecture",
- link: 'https://jaxenter.com/pulsar-kafka-175830.html'
- },
- {
- forum: 'RT Instights',
- forum_link: 'https://www.rtinsights.com/',
- date: 'Oct 2021',
- title: "The Critical Role Streaming Plays in a Data Stack",
- link: 'https://www.rtinsights.com/the-critical-role-streaming-plays-in-a-data-stack/'
- },
- {
- forum: 'Mikel\'s TechBlog',
- forum_link: 'https://mikeldeltio.com/',
... 1721834 lines suppressed ...