lluiscab commented on issue #214:
URL:
https://github.com/apache/pulsar-client-node/issues/214#issuecomment-1119858918
Yeah :/
I did make a try to implement it myself but I could not find anything
exposed by the C api, is there a reason why this module is using the c api when
it say
Matt-Esch commented on issue #192:
URL:
https://github.com/apache/pulsar-client-node/issues/192#issuecomment-1119856038
Resolved with async functions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to g
Matt-Esch closed issue #192: Producer send order with async workers
URL: https://github.com/apache/pulsar-client-node/issues/192
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
Matt-Esch commented on issue #212:
URL:
https://github.com/apache/pulsar-client-node/issues/212#issuecomment-1119855467
I would have made it return a promise if the underlying c api had an async
callback, but it doesn't.
--
This is an automated message from the Apache Git Service.
To res
Matt-Esch commented on issue #214:
URL:
https://github.com/apache/pulsar-client-node/issues/214#issuecomment-1119854249
It doesn't appear to be exposed in the c api which is used by this module
https://github.com/apache/pulsar/blob/master/pulsar-client-cpp/lib/c/c_ClientConfiguration.cc
-
Congratulations! Qiang
best,
Ran
On 2022/05/04 06:28:24 Enrico Olivelli wrote:
> The Project Management Committee (PMC) for Apache Pulsar
> has invited Qiang Zhao to become a committer and we are pleased
> to announce that he has accepted.
>
> Qiang Zhao (with GH id mattisonchao) contributed lo
The addition of this feature looks like a matter of consumer selection.
Should the consumer selection of each Dispatcher be abstracted into an
extensible interface?
Thanks
Lin Lin
Thanks for Penghui and Dianjin,
Project Name: Query compacted data of topic by Pulsar SQL
Project Description:
The Pulsar SQL is a SQL query engine for Pulsar topics data analytics based on
the Trino, users could get data from Pulsar topics by SQL scripts. The topic
compaction is used to compr
addisonj closed issue #261: Add Support for HorizontalPodAutoscale in Broker
and Proxy
URL: https://github.com/apache/pulsar-helm-chart/issues/261
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
addisonj merged PR #262:
URL: https://github.com/apache/pulsar-helm-chart/pull/262
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pulsa
> The problem is that If I use multiple subscriptions then I am not
guaranteed that each message is delivered only to one consumer.
It is a weird use case, but it is something that is possible according
to the JMS specs.
I am mapping a JMS Queue with a Subscription, and everything works well,
but
It looks like we can add something like `EntryDispatcher` before the
EntryFilter.
Mixing entry filtering and consumer selecting seems a little confusing.
The `EntryDispatcher` could works as a consumer selector in
`PersistentDispatcherMultipleConsumers`.
It accepts an entry and a consumer li
Il giorno ven 6 mag 2022 alle ore 01:50 PengHui Li
ha scritto:
>
> > The Message goes through the EntryFilter that decides if the Entry
> matches the requirements of the Consumer.
> - if the message matches the consumer then it returns ACCEPT
> - if the message does not match the consumer then it
13 matches
Mail list logo
