-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support - Producer for Partitioned topics #4
Comments
I'm still wrapping my head around the internal structure of the code, but one thought I had was: In PulsarClient CreateProducer, it checks if the topic is partitioned and if yes returns a PartitionedTopicProducer which implements IProducer but acts as a wrapper over a collection of N Producers (1 for each partition). At this layer is where the partition routing happens, so the caller still makes the same calls and this special class takes care of routing it to the appropriate underlying Producer object. |
Hi @vp89 |
Hi, Am I assuming right, that producing to partionated topics does not work at all? |
Hi @imaramos |
Seems this issue is more related with partitioned producer, changed the issue name to make it clear. :) |
@jiazhai the issue is related to both producing and consuming partitioned topics. |
@blankensteiner Sorry for the misunderstanding. I thought the consumer part work would be included in #5 Multi-topics consumer. In Java client, the partitioned consumer is a special case of |
Ah yes, you could also see it like that. So, fine with the subject change :-) |
Partitioned topic support should be a top priority for this library. It's one of things that makes Pulsar great and it's a central feature of Pulsar itself. It can be a dealbreaker when it comes to using this library for many cases, especially if you're coming into a system you didn't design and which already has use of partitioned topics throughout. Given this library is now the "officially" supported library, this is a must have. |
Producer support for partitioned topics is available in release 1.1.0 |
As described here:
The text was updated successfully, but these errors were encountered: