This message was deleted.

https://github.com/apache/pulsar/blob/master/pulsar-functions/instance/src/main/java/org/apache/pulsar/functions/source/PulsarSource.java#L75 The Function passes the configured pattern to consumer builder directly. This might be caused by a change on the pulsar client/consumer side.

This line of code hasn’t changed from 2.9 to 2.11. So I don’t think this is the issue @Neng. Perhaps the regex library changed or code was added to explicitly exclude partition topics from the returned list of topics that match the regex.

Thanks both. I’ll have a browse through the code and see what I can find. Can allow for the partition naming in our patterns, though it feels a bit more fragile + I’m already seeing warnings about max pattern length, so will need need to experiment.

@David K Yeah, I share this link to demonstrate Function doesn’t do anything to the pattern and just pass to client/consumer builder.

Gotcha. I think this is related to the new regex subscription improvements.

Funny enough, the message just above this one in the #C5Z4T36F7 channel is discussing what seems like the fix for this bug. Here is the issue: https://github.com/apache/pulsar/issues/20042. There should be a fix in 3.0.0 and also in 2.11.2.

Let’s get that PR merged already! 😃