Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.6 Candidate 1

2024-06-12 Thread guo jiwei
+1 (binding) - validate the checksum and signature - validate the binaries Regards Jiwei Guo (Tboy) On Thu, Jun 13, 2024 at 3:20 AM Chris Bono wrote: > Following PIP-205: Reactive Java client for Apache Pulsar ( > https://github.com/apache/pulsar/issues/17335), this is release > candidate 1

[VOTE] Reactive Java client for Apache Pulsar 0.5.6 Candidate 1

2024-06-12 Thread Chris Bono
Following PIP-205: Reactive Java client for Apache Pulsar ( https://github.com/apache/pulsar/issues/17335), this is release candidate 1 for the Reactive Java client for Apache Pulsar, version 0.5.6. *** Please download, test and vote on this release. This vote will stay open for at least 72 hours

Re: Preparing for Pulsar 4.0: cleaning up the Managed Ledger interfaces

2024-06-12 Thread Asaf Mesika
In high level I see this work as needed cleanup indeed and very much needed On Tue, 11 Jun 2024 at 20:29 Lari Hotari wrote: > Hi all, > > We have the next LTS release, Pulsar 4.0, scheduled for October. The > current master branch will most likely become the 4.0 release branch in > September. >

Re: [DISCUSS] PIP-358: let resource weight work for OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl.

2024-06-12 Thread Yubiao Feng
Sounds good Thanks Yubiao Feng On Tue, Jun 11, 2024 at 11:50 AM thetumbled wrote: > Hi, Pulsar Community. > I open a new PIP for making resource weight conf work for > OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl, so that > we can avoid the impact of memory usage and di