youg9203 commented on PR #233:
URL:
https://github.com/apache/pulsar-helm-chart/pull/233#issuecomment-1118256971
Is the PR still in progress? Any estimation of when it will be released? I
have been facing issues with TLS and if I'm going to use the old version
`v1.1.0` then it's not workin
justinwujian commented on PR #97:
URL: https://github.com/apache/pulsar-dotpulsar/pull/97#issuecomment-1118260517
Why is this request not processed? Now we are needing to use the
functionality of the consumer to handle dead letters.
--
This is an automated message from the Apache Git Serv
lluiscab opened a new issue, #214:
URL: https://github.com/apache/pulsar-client-node/issues/214
Hi,
Would it be possible to expose the `listenerName` configuration param from
the C++ client?
https://pulsar.apache.org/api/cpp/2.10.0-SNAPSHOT/classpulsar_1_1_client_configuration
GeroL commented on PR #97:
URL: https://github.com/apache/pulsar-dotpulsar/pull/97#issuecomment-1118287941
I could not finish this yet due to personal time constraints. I try to look
into it next week. Would be helpful if this gets some comments on the code
--
This is an automated message
Congrats! Qiang
On Thu, May 5, 2022 at 11:49 AM Lari Hotari wrote:
> Congrats Qiang!
>
> -Lari
>
> ke 4. toukok. 2022 klo 9.28 Enrico Olivelli
> kirjoitti:
>
> > The Project Management Committee (PMC) for Apache Pulsar
> > has invited Qiang Zhao to become a committer and we are pleased
> > to
Thanks, Dianjing! I've received the invitation email.
On Thu, May 5, 2022 at 10:58 AM Dianjin Wang
wrote:
> Thanks for your guys' project ideas. I can help to submit these ideas to
> the OSPP website this week and send invitations to your contact email,
> please remember to check it.
>
> The pro
urfreespace merged PR #64:
URL: https://github.com/apache/pulsar-site/pull/64
--
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...@pulsar.apa
urfreespace merged PR #65:
URL: https://github.com/apache/pulsar-site/pull/65
--
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...@pulsar.apa
Hello,
I am trying to use PIP-105 and I found out that we are missing a few
little things to cover my user case.
In my case I have two consumers who compete on the same SHARED
subscription with a "message filter".
The filter is passed as Consumer metadata.
When you have two Consumers connected on
> 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 has to be
rescheduled (RESCHEDULE)
It looks like different consumers have
urfreespace merged PR #66:
URL: https://github.com/apache/pulsar-site/pull/66
--
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...@pulsar.apa
urfreespace merged PR #63:
URL: https://github.com/apache/pulsar-site/pull/63
--
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...@pulsar.apa
urfreespace merged PR #67:
URL: https://github.com/apache/pulsar-site/pull/67
--
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...@pulsar.apa
13 matches
Mail list logo
