You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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.
All reactions