in consumer, supports multi-partition topic consuming #45
Description
The question
I notice the implementation of this client handles message through only one connection to broker.
relative code here
But multiple listeners are created for each partition in the cpp-version-client when consuming multi-partition topics.
Does it means this pulsar go client do not support consume multi-partition topics？
Describe the solution you'd like
Please consider add this feature If my question is correct:
- consumer supports multi-partition topic consuming.