+1
It allows users to only have one consumer but with different priority
levels for different topics.
Penghui
On Tue, Jul 12, 2022 at 4:18 PM Dave Maughan
wrote:
> Hi Zike,
>
> > What about using the Pattern type to store the compiled Pattern in the
> TopicConsumerConfigurationData?
>
> Thanks
Hi Zike,
> What about using the Pattern type to store the compiled Pattern in the
TopicConsumerConfigurationData?
Thanks for the suggestion - yes that's a good idea. I'll update the doc.
- Dave
On Mon, Jul 11, 2022 at 12:04 PM Zike Yang wrote:
> Hi, Dave
>
> Thanks for your proposals. Overal
Hi, Dave
Thanks for your proposals. Overall looks good to me. Just a minor comment:
What about using the Pattern type to store the compiled Pattern in the
TopicConsumerConfigurationData? Like below:
```
public class TopicConsumerConfigurationData implements Serializable {
private static final
Hi Enrico,
Why can't you create multiple independent Consumers ?
> They will share the same resources (memory pools, thread pools)
You can do that but it means the user has to manage the consumption from
each of the consumer instances manually. This is already solved in the
existing multi topic
Dave,
Why can't you create multiple independent Consumers ?
They will share the same resources (memory pools, thread pools)
Enrico
Il giorno ven 8 lug 2022 alle ore 15:00 Dave Maughan
ha scritto:
>
> Hi Pulsar community,
>
> I've opened a PIP to discuss a new Java client option to allow setti
Hi Pulsar community,
I've opened a PIP to discuss a new Java client option to allow setting
topic specific consumer priorityLevel.
Proposal Link: https://github.com/apache/pulsar/issues/16481
---
## Motivation
The Pulsar Java consumer supports setting a priority level for priority
message
disp
