[DISCUSS] Release C++ Client 3.7.2 for RPM/DEB packages regression since 3.6.0

2025-06-23 Thread Yunze Xu
Hi all, I noticed a regression for RPM/DEB packages since 3.6.0, see details in https://github.com/apache/pulsar-client-cpp/issues/494. I pushed a fix here: https://github.com/apache/pulsar-client-cpp/pull/493. After it's merged, I'm going to start a new patch release 3.7.2 to include that fix as

Re: ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3.

2025-06-23 Thread Zixuan Liu
Thanks for your information! I've noticed that https://github.com/apache/pulsar/pull/24279 is causing CI failures on both the branch-3.0 and branch-3.3 branches. I recommend reverting this PR from those branches to restore CI stability. After that, we can create a new PR to cherry-pick #24279. To

Re: [VOTE] PIP-428: Change TopicPoliciesService interface to fix consistency issues

2025-06-23 Thread Tao Jiuming
+1 nonbinding Yunze Xu 于2025年6月22日 周日19:52写道: > +1 (binding) > > Thanks, > Yunze > > On Sat, Jun 21, 2025 at 8:53 PM Lari Hotari wrote: > > > > Hi, > > > > I'd like to start the voting thread for "PIP-428: Change > > TopicPoliciesService interface to fix consistency issues". > > > > Proposal PR:

[DISCUSS] Release Pulsar Node.js client v1.14.0

2025-06-23 Thread Baodi Shi
hi, I would start release node.js client v1.14.0, it include many fix and improve. Refer to: - https://github.com/apache/pulsar-client-node/milestone/19?closed=1 Please let me know if you have any fix that need to be included in 1.14.0 Thanks, Baodi Shi

Re: [DISCUSS]PIP-417: Provide ability for Pulsar clients to integrate with third-party schema registry service

2025-06-23 Thread SiNan Liu
I don't seem to have seen any description of the relevant behaviour of admin api. What should we do when calling pulsar-admin schemas get . Thanks, sinan PengHui Li 于2025年6月24日 周二05:02写道: > Hi Ran, > > Thanks for adding the compatibility explanation and the new schema type. > The proposal loo

Re: PIP-429: Client-Side Computation of Last Compacted Message ID

2025-06-23 Thread Yunze Xu
Hello, I updated the title to "Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing" now. Thanks, Yunze On Sat, Jun 21, 2025 at 7:34 PM Yunze Xu wrote: > > Hi all, > > I wrote a proposal to support client-side computation of last > compacted message ID: https://github.co

[VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls

2025-06-23 Thread Aurora Twinkle
Hi, Pulsar Community. I open a new PIP for support connecting with next available endpoint for multi-endpoint serviceUrls. PIP: https://github.com/apache/pulsar/pull/24394 DISCUSS: https://lists.apache.org/thread/44ztyhgm5ly6cljnlbnwrrowmk7jcrkj Thanks, Linlin Duan(AuroraTwinkle)

[VOTE] Pulsar Client C++ Release 3.7.2 Candidate 1

2025-06-23 Thread Yunze Xu
This is the first release candidate for Apache Pulsar Client C++, version 3.7.2. It fixes the following issues: https://github.com/apache/pulsar-client-cpp/pulls?q=is%3Apr+label%3Arelease%2F3.7.2+is%3Aclosed *** Please download, test and vote on this release. This vote will stay open for at least

Re: [VOTE] PIP-428: Change TopicPoliciesService interface to fix consistency issues

2025-06-23 Thread Lari Hotari
+1 (binding) -Lari On 2025/06/21 12:52:18 Lari Hotari wrote: > Hi, > > I'd like to start the voting thread for "PIP-428: Change > TopicPoliciesService interface to fix consistency issues". > > Proposal PR: https://github.com/apache/pulsar/pull/24428 > Rendered PIP document: > https://github.com

Re: [DISCUSS]PIP-417: Provide ability for Pulsar clients to integrate with third-party schema registry service

2025-06-23 Thread PengHui Li
Hi Ran, Thanks for adding the compatibility explanation and the new schema type. The proposal looks good to me. Regards, Penghui On Tue, Jun 10, 2025 at 2:47 AM Ran Gao wrote: > Thanks for the suggestions, I'll add them to the PIP. > > Thanks, > Ran Gao > > On 2025/06/03 00:15:58 PengHui Li wr

[DISCUSS] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count

2025-06-23 Thread Lari Hotari
Dear Pulsar Community, I'd like to propose PIP-430, which addresses performance and efficiency issues in Pulsar broker's entry cache eviction mechanisms and introduces a more efficient caching strategy. The current broker entry cache implementation has several production-impacting issues. The siz

Re: [DISCUSS] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count

2025-06-23 Thread Tao Jiuming
good work, lgtm Lari Hotari 于2025年6月24日 周二02:44写道: > Dear Pulsar Community, > > I'd like to propose PIP-430, which addresses performance and > efficiency issues in Pulsar broker's entry cache eviction mechanisms > and introduces a more efficient caching strategy. > > The current broker entry cach