You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, there is an issue with the reader implementation. If the reader is creating, it won't get the topic metadata from the topic. The reader can only read messages from a single topic. If the topic is a partitioned topic, the reader won't know that and will try to create a non-partition topic with the same name. And it will lead to this issue: apache/pulsar#22032
Describe the solution you'd like
Support multi-topics reader
Describe alternatives you've considered
No
Additional context
No
The text was updated successfully, but these errors were encountered:
Master Issue: #1177
### Motivation
Currently, there is an issue with the reader implementation. If the reader is creating, it won't get the topic metadata from the topic. The reader can only read messages from a single topic. If the topic is a partitioned topic, the reader won't know that and will try to create a non-partition topic with the same name. And it will lead to this issue: apache/pulsar#22032
### Modifications
- Support partitioned topic reader
Master Issue: #1177
### Motivation
Currently, there is an issue with the reader implementation. If the reader is creating, it won't get the topic metadata from the topic. The reader can only read messages from a single topic. If the topic is a partitioned topic, the reader won't know that and will try to create a non-partition topic with the same name. And it will lead to this issue: apache/pulsar#22032
### Modifications
- Support partitioned topic reader
(cherry picked from commit 3b9b1f8)
Is your feature request related to a problem? Please describe.
Currently, there is an issue with the reader implementation. If the reader is creating, it won't get the topic metadata from the topic. The reader can only read messages from a single topic. If the topic is a partitioned topic, the reader won't know that and will try to create a non-partition topic with the same name. And it will lead to this issue: apache/pulsar#22032
Describe the solution you'd like
Describe alternatives you've considered
No
Additional context
No
The text was updated successfully, but these errors were encountered: