Re: [VOTE] PIP-313 Support force unsubscribe using consumer api

+1 (binding) Thanks, Penghui On Thu, Dec 7, 2023 at 4:37 PM Rajan Dhabalia wrote: > Hi, > > I would like to start voting thread for PIP-313 which also addresses issue > # https://github.com/apache/pulsar/issues/21451 > > PIP design PR: > https://github.com/apache/pulsar/pull/21452 > > Thread:

Re: [VOTE] PIP-313 Support force unsubscribe using consumer api

+1 (binding) Regards Jiwei Guo (Tboy) On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia wrote: > Hi, > > I would like to start voting thread for PIP-313 which also addresses issue > # https://github.com/apache/pulsar/issues/21451 > > PIP design PR: > https://github.com/apache/pulsar/pull/21452 >

[RESULT][VOTE] DotPulsar Release 3.1.1 RC 1

Thanks for your participation! I'll close this vote with 3 +1 binding votes and 1 +1 non-binding vote: +1 binding Daniel Blankensteiner Zili Chen Yunze Xu +1 non-binding David Jensen I'll upload the artifacts and send an announcement later. Best, tison. David Jensen 于2023年12月9日周六 05:08写道： > >

[ANNOUNCE] Apache Pulsar C# Client DotPulsar 3.1.1 released

The Apache Pulsar team is proud to announce DotPulsar version 3.1.1. 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 management for subscribe

Re: [DISCUSS] PIP-322: Pulsar Rate Limiting Refactoring

+1 Thanks Yubiao Feng On Thu, Dec 7, 2023 at 12:56 AM Lari Hotari wrote: > Dear Pulsar community, > > As a follow-up to the action point of the Pulsar Community Meeting on > 2023/11/23, > I have created "PIP-322: Pulsar Rate Limiting Refactoring" > and a draft PR with the proposed refactoring c

Re: [VOTE] PIP-313 Support force unsubscribe using consumer api

+1 (non-binding) On Sun, Dec 10, 2023 at 6:12 PM guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia > wrote: > > > Hi, > > > > I would like to start voting thread for PIP-313 which also addresses > issue > > # https://github.com

[VOTE] PIP-322: Pulsar Rate Limiting Refactoring

Dear Pulsar community, I am starting a vote thread for "PIP-322: Pulsar Rate Limiting Refactoring". PIP-322 document: https://github.com/apache/pulsar/pull/21680 Draft changes for "PIP-322: Pulsar Rate Limiting Refactoring": https://github.com/apache/pulsar/pull/21681 Discussion thread: https:/

[VOTE] PIP-320: OpenTelemetry Scaffolding

Hi, I'm starting the vote for PIP-320 (1st sub-PIP of PIP-264) Link: https://github.com/apache/pulsar/pull/21635 Reminder: This PIPs goal is to introduce OpenTelemetry into Apache Pulsar. When this PIP is implemented, we will be able to start converting (not replacing) existing metrics into Open

Re: [VOTE] PIP-320: OpenTelemetry Scaffolding

+1 (binding) Thanks, Yunze On Mon, Dec 11, 2023 at 3:34 PM Asaf Mesika wrote: > > Hi, > > I'm starting the vote for PIP-320 (1st sub-PIP of PIP-264) > > Link: https://github.com/apache/pulsar/pull/21635 > > Reminder: > This PIPs goal is to introduce OpenTelemetry into Apache Pulsar. When this >

Re: [VOTE] PIP-322: Pulsar Rate Limiting Refactoring

+1 (binding) Regards Jiwei Guo (Tboy) On Mon, Dec 11, 2023 at 2:20 PM Lari Hotari wrote: > Dear Pulsar community, > > I am starting a vote thread for "PIP-322: Pulsar Rate Limiting > Refactoring". > > PIP-322 document: > https://github.com/apache/pulsar/pull/21680 > > Draft changes for "PIP-3