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/23 06:18:20 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#08df28a)
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 d83bb47cd5a Docs sync done from apache/pulsar(#08df28a)
d83bb47cd5a is described below
commit d83bb47cd5ab722f941ed1d187717f53aa328f48
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Fri Sep 23 06:18:15 2022 +0000
Docs sync done from apache/pulsar(#08df28a)
---
site2/website-next/docs/concepts-messaging.md | 4 ++--
site2/website-next/docs/io-debezium-source.md | 2 +-
.../website-next/versioned_docs/version-2.10.x/io-debezium-source.md | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/site2/website-next/docs/concepts-messaging.md b/site2/website-next/docs/concepts-messaging.md
index ea278c5e989..368fd45c71f 100644
--- a/site2/website-next/docs/concepts-messaging.md
+++ b/site2/website-next/docs/concepts-messaging.md
@@ -541,7 +541,7 @@ In the *Failover* type, multiple consumers can attach to the same subscription.
* For partitioned topics, the broker will sort consumers by priority level and lexicographical order of consumer name. The broker will try to evenly assign partitions to consumers with the highest priority level.
* For non-partitioned topics, the broker will pick consumers in the order they subscribe to the non-partitioned topics.
-For example, a partitioned topic has 15 partitions, and 3 consumers. Each consumer will be active for 5 partitions. Each partition will have 1 active consumer and 4 stand-by consumers.
+For example, a partitioned topic has 3 partitions, and 15 consumers. Each partition will have 1 active consumer and 4 stand-by consumers.
In the diagram below, **Consumer-B-0** is the master consumer while **Consumer-B-1** would be the next consumer in line to receive messages if **Consumer-B-0** is disconnected.
@@ -794,7 +794,7 @@ Non-persistent messaging is usually faster than persistent messaging because bro
### Client API
-Producers and consumers can connect to non-persistent topics in the same way as persistent topics, with the crucial difference that the topic name must start with `non-persistent`. All three subscription types---[exclusive](#exclusive), [shared](#shared), and [failover](#failover)---are supported for non-persistent topics.
+Producers and consumers can connect to non-persistent topics in the same way as persistent topics, with the crucial difference that the topic name must start with `non-persistent`. All the subscription types---[exclusive](#exclusive), [shared](#shared), [key-shared](#key_shared) and [failover](#failover)---are supported for non-persistent topics.
Here's an example [Java consumer](client-libraries-java.md#consumers) for a non-persistent topic:
diff --git a/site2/website-next/docs/io-debezium-source.md b/site2/website-next/docs/io-debezium-source.md
index e660d48c34e..0f7dd19b5d7 100644
--- a/site2/website-next/docs/io-debezium-source.md
+++ b/site2/website-next/docs/io-debezium-source.md
@@ -585,7 +585,7 @@ For the full list of configuration properties supported by Debezium, see [Debezi
### Configuration
Debezium [requires](https://debezium.io/documentation/reference/1.5/connectors/sqlserver.html#sqlserver-overview) SQL Server with CDC enabled.
-Steps outlined in the [documentation](https://debezium.io/documentation/reference/1.5/connectors/sqlserver.html#setting-up-sqlserver) and used in the [integration test](https://github.com/apache/pulsar/blob/master/tests/integration/src/test/java/org/apache/pulsar/tests/integration/src/test/java/org/apache/pulsar/tests/integration/io/sources/debezium/DebeziumMsSqlSourceTester.java).
+Steps outlined in the [documentation](https://debezium.io/documentation/reference/1.5/connectors/sqlserver.html#setting-up-sqlserver) and used in the [integration test](https://github.com/apache/pulsar/blob/master/tests/integration/src/test/java/org/apache/pulsar/tests/integration/io/sources/debezium/DebeziumMsSqlSourceTester.java).
For more information, see [Enable and disable change data capture in Microsoft SQL Server](https://docs.microsoft.com/en-us/sql/relational-databases/track-changes/enable-and-disable-change-data-capture-sql-server).
Similarly to other connectors, you can use JSON or YAML to configure the connector.
diff --git a/site2/website-next/versioned_docs/version-2.10.x/io-debezium-source.md b/site2/website-next/versioned_docs/version-2.10.x/io-debezium-source.md
index b487ab6477e..cd934c3acbe 100644
--- a/site2/website-next/versioned_docs/version-2.10.x/io-debezium-source.md
+++ b/site2/website-next/versioned_docs/version-2.10.x/io-debezium-source.md
@@ -684,7 +684,7 @@ For the full list of configuration properties supported by Debezium, see [Debezi
### Configuration
Debezium [requires](https://debezium.io/documentation/reference/1.5/connectors/sqlserver.html#sqlserver-overview) SQL Server with CDC enabled.
-Steps outlined in the [documentation](https://debezium.io/documentation/reference/1.5/connectors/sqlserver.html#setting-up-sqlserver) and used in the [integration test](https://github.com/apache/pulsar/blob/master/tests/integration/src/test/java/org/apache/pulsar/tests/integration/src/test/java/org/apache/pulsar/tests/integration/io/sources/debezium/DebeziumMsSqlSourceTester.java).
+Steps outlined in the [documentation](https://debezium.io/documentation/reference/1.5/connectors/sqlserver.html#setting-up-sqlserver) and used in the [integration test](https://github.com/apache/pulsar/blob/master/tests/integration/src/test/java/org/apache/pulsar/tests/integration/io/sources/debezium/DebeziumMsSqlSourceTester.java).
For more information, see [Enable and disable change data capture in Microsoft SQL Server](https://docs.microsoft.com/en-us/sql/relational-databases/track-changes/enable-and-disable-change-data-capture-sql-server).
Similarly to other connectors, you can use JSON or YAMl to configure the connector.