Broadcast mode subscription

[dsj017112]

Hello, I now have a need like this:
Consumers need to subscribe to topic. I need to make sure that the subscription name is not consistent, so as to achieve the effect of broadcasting, and to ensure that every consumer receives a message. Now the subscription name can only be written in the comments. If I start multiple containers, I can't adjust the code every time. Is there any better solution to solve my needs?

Or is there any other solution that can achieve broadcasting in the case of multi-container startup.

I have considered concatenating the timestamp after the subscription name, but the annotation can only support constant parameters, so this scheme does not work.

If I use native pulsar to initialize consumers, I think I can, or look forward to your reply, to see if there is a better solution to help me solve this problem.

Thank you !

[majusko]

I'm probably replying late, but if someone is trying to solve this, here is the solution:

If you need every consumer to receive the messages, you need to have them in the type of Exclusive and keep the subscription name to be created automatically for you instead of setting it manually. It will create a unique name for each subscription and therefore you can listen to every message. You cannot mix this behaviour as this is the basic architecture of Pulsar.

[dsj017112]

这是来自QQ邮箱的假期自动回复邮件。   您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。