Thanks for your proposal, Heesung. Sorry for my late response. Just
want to make a few points to hopefully improve the implementation.
Overall, I think this feature is absolutely the right direction for
Pulsar and will be a great improvement. I remember discussing this at
some community meetings la
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.3.0.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
This is the first release candidate for Apache Pulsar version 3.1.0.
It fixes the following issues:
https://github.com/apache/pulsar/milestone/35?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Note that we are voting upon the sourc
Thanks Baodi Shi. The proposed implementation is available in this PR:
https://github.com/apache/pulsar/pull/20901.
- Michael
On Fri, Aug 4, 2023 at 9:33 PM Baodi Shi wrote:
>
> Hi, Michael:
>
> I left some comments on the PR.
>
> if you could explain the implementation part in a little more det
Hi Pulsar Community,
This is the discussion thread for PIP
https://github.com/apache/pulsar/pull/20953.
This PIP will help improve Pulsar Websockets by enforcing the expiration time
of tokens used to authenticate.
Currently this enforcement is only implemented in the Pulsar Broker, and not in
t
Thanks Tison,
I fully agree that we should have a clear representation of the actual
status of the Helm chart, so that users can have the correct expectation.
In particular I think we should have this Helm chart to provide basic
functionality out of the box and serve as a template/example on top
