This message was deleted.

Hi, using key_shared is warranted, if you can give a key to split the messages: https://pulsar.apache.org/docs/3.1.x/concepts-messaging/#key_shared

@David K - any additional input? Ingvord, we are also happy to set up a call to discuss your challenges if that would help.

@Ingvord It currently isn’t possible to seek/find messages by sequenceID. That field is intended to be used for message deduplication in conjunction with the producer name. What processing engine are you using to consume the messages? One strategy might be to assign a unique key to each message that contains a “hit” and then tag all subsequent messages with the same key. Doing this allows you to use the key shared subscription type which provides the following guarantee. Messages with the same key will be delivered to the same consumer in the order they were received.

@David K thanks for your prompt answer. At the moment processing engine is still an open question to us. Unique key strategy seems decent though.

Great! This week is a tough one with Pulsar Summit (most of the company is traveling this week), but I'll DM you and we can find some time.