Good day all, My sink connector is currently consuming messages from

public/default/.*

please is there a way to filter what topic it should consume mmessages from through

producer property, subscription name or topic's metadata

, without attaching a constant string to those topics i.e without adding somthing like this

public/default/consume-.*

Why can’t you just update the topic regex inside the sink configuration?

@David K I can actually, I think the right way to ask this question is, "is it possible to produce a message for a specify subscription, so that a topic that has multiple subcriptions will have distinct backlogs/message count values "

The short answer is no. One approach you can take is to have a filtering function on the main source topic that routes the messages to individual topics for each subscriber/consumer; then, the consumers can read directly from these curated topics. pfSQL is one way of implementing this pattern, but it can also be done by writing your own custom routing logic inside a pulsar function, etc.

@David K nice, please any code sample/doc/guide on writing filtering function for pulsar topic ?

pattern 2 from this blog post, just use whatever logic you want.

@David K I need to give you your flower, thank you so very much.

You only want to have a single subscription on the source topic, and it should belong to the filtering function. All over consumers will read from the output topics of the filtering function

Thank you