Re: [DISCUSS] Enhance dynamic topic subscription management in PatternMultiTopicsConsumer

Thanks for sharing details about the broader context of the use case. I think we could start drafting ideas of what the API solution could be. One of the first things to address in designing APIs is to focus on the naming of concepts. Concepts should be clear and not conflicting with other names

Re: [VOTE] Release Apache Pulsar 3.3.4 based on 3.3.4-candidate-1

+1 (non-binding) - Built from source - Checked the signatures of the source and binary release artifacts - Ran pulsar standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Thanks, Philipp

Re: [VOTE] Release Apache Pulsar 3.0.9 based on 3.0.9-candidate-1

+1 (non-binding) - Built from source - Checked the signatures of the source and binary release artifacts - Ran pulsar standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Thanks, Philipp

Re: [DISCUSS] Enhance dynamic topic subscription management in PatternMultiTopicsConsumer

I would like to momentarily set aside the issue of topic processing speed disparities causing bottlenecks and instead focus on enhancing our dynamic subscription management capabilities. Currently, when a consumer subscribes to topics using a pattern, any modification to this pattern necessitates