You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "GmaD-X (via GitHub)" <gi...@apache.org> on 2024/01/29 01:22:05 UTC
[D] Deduplication on namespace level [pulsar]
GitHub user GmaD-X created a discussion: Deduplication on namespace level
Hello everyone,
I was reading on the pulsar deduplication feature, specifically on the namespace level. On this I have a query and hope to get more clarity on this.
Consider multiple producers, multiple topics and multiple consumers (for the sake of it lets say 1:1:1) under a common namespace with deduplication enabled. There maybe cases of the same event being publish to all the topics. I want only one copy of it persisted to memory, but every consumer should be able to consume the same event. Can deduplication help in this scenario? I am asking because I noticed that we are able to set the producerName and sequenceId per event and pulsar uses a combination of these two to achieve deduplication.
Thank you.
GitHub link: https://github.com/apache/pulsar/discussions/21982
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Deduplication on namespace level [pulsar]
Posted by "GmaD-X (via GitHub)" <gi...@apache.org>.
GitHub user GmaD-X edited a discussion: Deduplication on namespace level
Hello everyone,
I was reading on the pulsar deduplication feature, specifically on the namespace level. On this I have a query and hope to get more clarity on this. Consider multiple producers, multiple topics and multiple consumers (for the sake of it lets say 1:1:1) under a common namespace with deduplication enabled. There maybe cases of the same event being publish to all the topics. I want only one copy of it persisted to memory, but every consumer should be able to consume the same event. Can deduplication help in this scenario? I am asking because I noticed that we are able to set the producerName and sequenceId per event and pulsar uses a combination of these two to achieve deduplication.
Thank you.
GitHub link: https://github.com/apache/pulsar/discussions/21982
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Deduplication on namespace level [pulsar]
Posted by "GmaD-X (via GitHub)" <gi...@apache.org>.
GitHub user GmaD-X edited a discussion: Deduplication on namespace level
Hello everyone,
I was reading on the pulsar deduplication feature, specifically on the namespace level. On this I have a query and hope to get more clarity on this. Consider multiple producers, multiple topics and multiple consumers (for the sake of it lets say 1:1:1) under a common namespace with deduplication enabled. There maybe cases of the same event being publish to all the topics. I want only one copy of it persisted to memory, but every consumer should be able to consume the same event. Can deduplication help in this scenario? I am asking because I noticed that we are able to set the producerName and sequenceId per event and pulsar uses a combination of these two to achieve deduplication.
Thank you.
GitHub link: https://github.com/apache/pulsar/discussions/21982
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org