[pulsar] branch master updated: [fix][doc] Message Deduplication: Add more links for how it works under the hood (#15715)

[li...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

liuyu 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 8964b4da71b [fix][doc] Message Deduplication: Add more links for how it works under the hood (#15715)
8964b4da71b is described below

commit 8964b4da71bdcb7160a69bb6adef26bc95e32aad
Author: Asaf Mesika <as...@gmail.com>
AuthorDate: Thu May 26 03:44:35 2022 +0300

    [fix][doc] Message Deduplication: Add more links for how it works under the hood (#15715)
---
 site2/docs/concepts-messaging.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site2/docs/concepts-messaging.md b/site2/docs/concepts-messaging.md
index 484099fc8f1..fc50500ef49 100644
--- a/site2/docs/concepts-messaging.md
+++ b/site2/docs/concepts-messaging.md
@@ -908,7 +908,7 @@ Message deduplication is disabled in the scenario shown at the top. Here, a prod
 In the second scenario at the bottom, the producer publishes message 1, which is received by the broker and persisted, as in the first scenario. When the producer attempts to publish the message again, however, the broker knows that it has already seen message 1 and thus does not persist the message.
 
 > Message deduplication is handled at the namespace level or the topic level. For more instructions, see the [message deduplication cookbook](cookbooks-deduplication).
-
+> You can read the design of Message Deduplication in [PIP-6](https://github.com/aahmed-se/pulsar-wiki/blob/master/PIP-6:-Guaranteed-Message-Deduplication.md)
 
 ### Producer idempotency