You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by te...@apache.org on 2022/05/16 04:01:01 UTC
[pulsar] branch master updated: Fix misaligned tables in website documents (#15579)
This is an automated email from the ASF dual-hosted git repository.
technoboy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new d4070c41e9a Fix misaligned tables in website documents (#15579)
d4070c41e9a is described below
commit d4070c41e9a270cdf22ef901e038f28ac2702fd8
Author: VOPEN.XYZ <x_...@yeah.net>
AuthorDate: Mon May 16 12:00:49 2022 +0800
Fix misaligned tables in website documents (#15579)
---
site2/docs/concepts-messaging.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/site2/docs/concepts-messaging.md b/site2/docs/concepts-messaging.md
index 4b7e0ed623e..daabf132672 100644
--- a/site2/docs/concepts-messaging.md
+++ b/site2/docs/concepts-messaging.md
@@ -61,11 +61,11 @@ Producers send messages to brokers synchronously (sync) or asynchronously (async
You can have different types of access modes on topics for producers.
-| Access mode | Description [...]
-|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| `Shared` | Multiple producers can publish on a topic. <br><br>This is the **default** setting. [...]
-| `Exclusive` | Only one producer can publish on a topic. <br><br>If there is already a producer connected, other producers trying to publish on this topic get errors immediately.<br><br>The “old” producer is evicted and a “new” producer is selected to be the next exclusive producer if the “old” producer experiences a network partition with the broker. [...]
-| `WaitForExclusive` | If there is already a producer connected, the producer creation is pending (rather than timing out) until the producer gets the `Exclusive` access.<br><br>The producer that succeeds in becoming the exclusive one is treated as the leader. Consequently, if you want to implement a leader election scheme for your application, you can use this access mode. Note that the leader pattern scheme mentioned refers to using Pulsar as a Write-Ahead Log (WAL) which means the lea [...]
+Access mode | Description
+:-----------|------------
+`Shared` | Multiple producers can publish on a topic. <br><br>This is the **default** setting.
+`Exclusive` | Only one producer can publish on a topic. <br><br>If there is already a producer connected, other producers trying to publish on this topic get errors immediately.<br><br>The “old” producer is evicted and a “new” producer is selected to be the next exclusive producer if the “old” producer experiences a network partition with the broker.
+`WaitForExclusive` | If there is already a producer connected, the producer creation is pending (rather than timing out) until the producer gets the `Exclusive` access.<br><br>The producer that succeeds in becoming the exclusive one is treated as the leader. Consequently, if you want to implement a leader election scheme for your application, you can use this access mode. Note that the leader pattern scheme mentioned refers to using Pulsar as a Write-Ahead Log (WAL) which means the leade [...]
> **Note**
>