You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/09/22 06:20:05 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#d9c9d73)
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new d818d0ffac4 Docs sync done from apache/pulsar(#d9c9d73)
d818d0ffac4 is described below
commit d818d0ffac432770444ccc592da403d8570395d5
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Thu Sep 22 06:20:00 2022 +0000
Docs sync done from apache/pulsar(#d9c9d73)
---
.../blog/2022-08-22-pulsar-summit-asia-2022-cfp.md | 54 ++++++++++++++++++++++
.../version-2.8.x/admin-api-permissions.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.8.x/security-tls-keystore.md | 8 ++--
.../version-2.9.x/admin-api-permissions.md | 2 +-
.../version-2.9.x/client-libraries-java.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.9.x/security-tls-keystore.md | 8 ++--
8 files changed, 67 insertions(+), 13 deletions(-)
diff --git a/site2/website-next/blog/2022-08-22-pulsar-summit-asia-2022-cfp.md b/site2/website-next/blog/2022-08-22-pulsar-summit-asia-2022-cfp.md
new file mode 100644
index 00000000000..37441c8d4b1
--- /dev/null
+++ b/site2/website-next/blog/2022-08-22-pulsar-summit-asia-2022-cfp.md
@@ -0,0 +1,54 @@
+---
+author: Sherlock Xu
+title: "Pulsar Summit Asia 2022: CFP Is Open Now!"
+date: 2022-08-22
+---
+
+Pulsar Summit is the conference dedicated to Apache Pulsar, and the messaging and event streaming community. The conference gathers an international audience of developers, data architects, data scientists, Apache Pulsar committers and contributors, as well as the messaging and streaming community. Together, they share experiences, exchange ideas and knowledge, and receive hands-on training sessions led by Pulsar experts.
+
+In January this year, Pulsar Summit Asia 2021 (delayed due to the COVID-19 pandemic) featured more than 25 interactive sessions by technologists, developers, software engineers, and software architects from StreamNative, BIGO, China Mobile, Nutanix, Tencent, and more. The conference drew over 1000 attendees around the world, including attendees from top technology, internet, and media companies, such as Tencent, TikTok, Alibaba, and Microsoft.
+
+Pulsar Summit Asia 2022 will be hosted virtually on November 19th and 20th, 2022. It is expected to cover the pivotal topics and technologies at the core of Apache Pulsar.
+
+<!--truncate-->
+
+## Join us and speak at Pulsar Summit Asia 2022
+
+Share your Pulsar story and speak at the summit! It is a great opportunity to participate and raise your profile in the rapidly growing Apache Pulsar community. We are looking for Pulsar stories that are innovative, informative, or thought-provoking. Here are some suggestions:
+
+- Use cases, operations, tools, techniques, or the Pulsar ecosystem
+- A deep dive into technologies
+- Best practices and lessons learned
+- A Pulsar success story or case study
+- Anything else related to Pulsar that inspires the audience
+
+To speak at the summit, [submit an abstract](https://sessionize.com/pulsar-summit-asia-2022/) about your session. All levels of talks (beginner, intermediate, and advanced) are welcome. Remember to keep your proposal short, relevant, and engaging. The following session formats are acceptable:
+
+- **Presentation**: 40-minute presentation, maximum of 2 speakers
+- **Panel**: 40-minute of discussion amongst 3 to 5 speakers
+- **Workshop**: 60-90 minutes, in-depth, hands-on tutorials, maximum of 2 speakers
+- **Lightning talk**: 10-minute presentation, maximum of 2 speakers
+
+You need to pre-record your session after the proposal is approved. For time zone and network reasons, we do not recommend speakers present their talk live.
+
+## Dates to remember
+
+- **CFP opens**: August 22nd, 2022
+- **CFP closes**: October 9th, 2022
+- **CFP notifications**: October 19th, 2022
+- **Schedule announcement**: November 4th, 2022
+- **Event dates**: November 19th, 2022 - November 20th, 2022
+
+## Sponsor Pulsar Summit
+
+Pulsar Summit is a conference for the community and your support is needed. Sponsoring this event provides a great opportunity for your organization to further engage with the Apache Pulsar community. For more information on becoming a sponsor, contact us at organizers@pulsar-summit.org.
+
+Help us make #PulsarSummit Asia 2022 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 on the summit!
+
+## About Apache Pulsar
+
+Apache Pulsar is a cloud-native, distributed messaging and streaming platform that empowers companies around the world to manage trillions of events per day. The Pulsar community has witnessed rapid growth since it became a top-level Apache Software Foundation project in 2018. Over the past four years, the vibrant community keeps driving innovation and improvements to the project.
+
+## About the organizer
+
+StreamNative is the organizer of Pulsar Summit Asia 2022. Founded by the original developers of Apache Pulsar and Apache BookKeeper, StreamNative builds a cloud-native event streaming platform that enables enterprises to easily access data as real-time event streams. As the core developers of Pulsar, the StreamNative team is deeply versed in the technology, the community, and the use cases. Today, StreamNative is focusing on growing the Apache Pulsar and BookKeeper communities and bringi [...]
\ No newline at end of file
diff --git a/site2/website-next/versioned_docs/version-2.8.x/admin-api-permissions.md b/site2/website-next/versioned_docs/version-2.8.x/admin-api-permissions.md
index 6897517553f..f0978187cc7 100644
--- a/site2/website-next/versioned_docs/version-2.8.x/admin-api-permissions.md
+++ b/site2/website-next/versioned_docs/version-2.8.x/admin-api-permissions.md
@@ -102,7 +102,7 @@ You can see which permissions have been granted to which roles in a namespace.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`permissions`](reference-pulsar-admin#permissions) subcommand and specify a namespace:
+Use the [`permissions`](reference-pulsar-admin.md#permissions) subcommand and specify a namespace:
```shell
diff --git a/site2/website-next/versioned_docs/version-2.8.x/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.8.x/deploy-bare-metal-multi-cluster.md
index 782ffa8e213..40b7deaedc8 100644
--- a/site2/website-next/versioned_docs/version-2.8.x/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.8.x/deploy-bare-metal-multi-cluster.md
@@ -25,7 +25,7 @@ A Pulsar *instance* consists of multiple Pulsar clusters working in unison. You
If you want to deploy a single Pulsar cluster, see [Clusters and Brokers](getting-started-standalone.md#start-the-cluster).
> #### Run Pulsar locally or on Kubernetes?
-> This guide shows you how to deploy Pulsar in production in a non-Kubernetes environment. If you want to run a standalone Pulsar cluster on a single machine for development purposes, see the [Setting up a local cluster](getting-started-standalone.md) guide. If you want to run Pulsar on [Kubernetes](https://kubernetes.io), see the [Pulsar on Kubernetes](deploy-kubernetes.md) guide, which includes sections on running Pulsar on Kubernetes on [Google Kubernetes Engine](deploy-kubernetes#pul [...]
+> This guide shows you how to deploy Pulsar in production in a non-Kubernetes environment. If you want to run a standalone Pulsar cluster on a single machine for development purposes, see the [Setting up a local cluster](getting-started-standalone.md) guide. If you want to run Pulsar on [Kubernetes](https://kubernetes.io), see the [Pulsar on Kubernetes](deploy-kubernetes.md) guide, which includes sections on running Pulsar on Kubernetes on [Google Kubernetes Engine](deploy-kubernetes.md# [...]
## System requirement
diff --git a/site2/website-next/versioned_docs/version-2.8.x/security-tls-keystore.md b/site2/website-next/versioned_docs/version-2.8.x/security-tls-keystore.md
index 170bb6697bc..45caf011f92 100644
--- a/site2/website-next/versioned_docs/version-2.8.x/security-tls-keystore.md
+++ b/site2/website-next/versioned_docs/version-2.8.x/security-tls-keystore.md
@@ -181,11 +181,11 @@ Optional settings that may worth consider:
### Configuring Clients
-This is similar to [TLS encryption configuing for client with PEM type](security-tls-transport.md#Client configuration).
-For a a minimal configuration, user need to provide the TrustStore information.
+This is similar to [TLS encryption configuring for clients with PEM type](security-tls-transport.md#client-configuration).
+For a minimal configuration, you need to provide the TrustStore information.
e.g.
-1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools#pulsar-admin), [`pulsar-perf`](reference-cli-tools#pulsar-perf), and [`pulsar-client`](reference-cli-tools#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
+1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools.md#pulsar-admin), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
```properties
@@ -278,7 +278,7 @@ webSocketServiceEnabled=false
Besides the TLS encryption configuring. The main work is configuring the KeyStore, which contains a valid CN as client role, for client.
e.g.
-1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools#pulsar-admin), [`pulsar-perf`](reference-cli-tools#pulsar-perf), and [`pulsar-client`](reference-cli-tools#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
+1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools.md#pulsar-admin), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
```properties
diff --git a/site2/website-next/versioned_docs/version-2.9.x/admin-api-permissions.md b/site2/website-next/versioned_docs/version-2.9.x/admin-api-permissions.md
index 2496c9be54e..0846c5c7201 100644
--- a/site2/website-next/versioned_docs/version-2.9.x/admin-api-permissions.md
+++ b/site2/website-next/versioned_docs/version-2.9.x/admin-api-permissions.md
@@ -112,7 +112,7 @@ You can see which permissions have been granted to which roles in a namespace.
values={[{"label":"pulsar-admin","value":"pulsar-admin"},{"label":"REST API","value":"REST API"},{"label":"Java","value":"Java"}]}>
<TabItem value="pulsar-admin">
-Use the [`permissions`](reference-pulsar-admin#permissions) subcommand and specify a namespace:
+Use the [`permissions`](reference-pulsar-admin.md#permissions) subcommand and specify a namespace:
```shell
diff --git a/site2/website-next/versioned_docs/version-2.9.x/client-libraries-java.md b/site2/website-next/versioned_docs/version-2.9.x/client-libraries-java.md
index 2a481a5a913..56fb54d633d 100644
--- a/site2/website-next/versioned_docs/version-2.9.x/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.9.x/client-libraries-java.md
@@ -579,7 +579,7 @@ private void receiveMessageFromConsumer(Object consumer) {
### Subscription modes
-Pulsar has various [subscription modes](concepts-messaging#subscription-modes) to match different scenarios. A topic can have multiple subscriptions with different subscription modes. However, a subscription can only have one subscription mode at a time.
+Pulsar has various [subscription modes](concepts-messaging.md#subscription-modes) to match different scenarios. A topic can have multiple subscriptions with different subscription modes. However, a subscription can only have one subscription mode at a time.
A subscription is identical to the subscription name which can specify only one subscription mode at a time. You cannot change the subscription mode unless all existing consumers of this subscription are offline.
diff --git a/site2/website-next/versioned_docs/version-2.9.x/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.9.x/deploy-bare-metal-multi-cluster.md
index e2cb90b5dd6..ccdc3a4c878 100644
--- a/site2/website-next/versioned_docs/version-2.9.x/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.9.x/deploy-bare-metal-multi-cluster.md
@@ -13,7 +13,7 @@ original_id: deploy-bare-metal-multi-cluster
:::
-A Pulsar instance consists of multiple Pulsar clusters working in unison. You can distribute clusters across data centers or geographical regions and replicate the clusters amongst themselves using [geo-replication](administration-geo.md).Deploying a multi-cluster Pulsar instance consists of the following steps:
+A Pulsar instance consists of multiple Pulsar clusters working in unison. You can distribute clusters across data centers or geographical regions and replicate the clusters amongst themselves using [geo-replication](administration-geo.md). Deploying a multi-cluster Pulsar instance consists of the following steps:
1. Deploying two separate ZooKeeper quorums: a local quorum for each cluster in the instance and a configuration store quorum for instance-wide tasks
2. Initializing cluster metadata for each cluster
diff --git a/site2/website-next/versioned_docs/version-2.9.x/security-tls-keystore.md b/site2/website-next/versioned_docs/version-2.9.x/security-tls-keystore.md
index 0b3b50fcebb..6ca77b9d050 100644
--- a/site2/website-next/versioned_docs/version-2.9.x/security-tls-keystore.md
+++ b/site2/website-next/versioned_docs/version-2.9.x/security-tls-keystore.md
@@ -181,11 +181,11 @@ Optional settings that may worth consider:
### Configuring Clients
-This is similar to [TLS encryption configuing for client with PEM type](security-tls-transport.md#Client configuration).
-For a a minimal configuration, user need to provide the TrustStore information.
+This is similar to [TLS encryption configuring for clients with PEM type](security-tls-transport.md#client-configuration).
+For a minimal configuration, you need to provide the TrustStore information.
e.g.
-1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools#pulsar-admin), [`pulsar-perf`](reference-cli-tools#pulsar-perf), and [`pulsar-client`](reference-cli-tools#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
+1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools.md#pulsar-admin), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
```properties
@@ -278,7 +278,7 @@ webSocketServiceEnabled=false
Besides the TLS encryption configuring. The main work is configuring the KeyStore, which contains a valid CN as client role, for client.
e.g.
-1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools#pulsar-admin), [`pulsar-perf`](reference-cli-tools#pulsar-perf), and [`pulsar-client`](reference-cli-tools#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
+1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools.md#pulsar-admin), [`pulsar-perf`](reference-cli-tools.md#pulsar-perf), and [`pulsar-client`](reference-cli-tools.md#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
```properties