Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

+1 (binding) - Built from source - Ran standalone with producer - Ran standalone with consumer Best, Mattison > On Feb 1, 2024, at 08:57, PengHui Li wrote: > > +1 (binding)

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

Thanks. Close this vote, and vote pass with 3(+1) binding Penghui. Jiwei Yubiao and 1 (+0) binding yunze Regards Jiwei Guo (Tboy) On Mon, Feb 5, 2024 at 12:08 AM Yubiao Feng wrote: > +1 (binding) > > - Run standalone > - Checked producer and consumer > - Verified the Cassandra connector >

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

+1 (binding) - Run standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Thanks Yubiao Feng On Wed, Jan 31, 2024 at 11:40 PM guo jiwei wrote: > This is the fifth release candidate for Apache Pulsar version 3.2.0. > > It fixes the followi

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

+1 (binding) - Built from source - Checked the signatures - Run standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Regards Jiwei Guo (Tboy) On Sun, Feb 4, 2024 at 3:42 PM Yunze Xu wrote: > I changed my binding -1 to +0 now. > > This

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

I changed my binding -1 to +0 now. This behavior change is implicit but acceptable. The previous way of setting up standalone should be wrong but it just accidentally works. When system topic policy is enabled, the `brokerClientXxx` arguments must be configured correctly to ensure the system topic

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

I pushed a fix: https://github.com/apache/pulsar/pull/22014 Thanks, Yunze On Fri, Feb 2, 2024 at 9:15 PM Yunze Xu wrote: > > Yes. I wrote a unit test in Java [1]. This breaking change is > introduced by #21445 [2], which requires the topic policies to be > available in `BrokerTopic#getTopic`. >

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

Yes. I wrote a unit test in Java [1]. This breaking change is introduced by #21445 [2], which requires the topic policies to be available in `BrokerTopic#getTopic`. However, when the built-in client is not configured correctly, e.g. `brokerClientXxx` authentication arguments are not configured cor

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

It looks like some tests are missed in the Java client? Otherwise, the java client detected this break change. Thanks, Penghui On Fri, Feb 2, 2024 at 11:40 AM Yunze Xu wrote: > -1 (binding) > > I observed a regression for Pulsar 3.1.2 recently because the latest > image was just updated yesterd

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

-1 (binding) I observed a regression for Pulsar 3.1.2 recently because the latest image was just updated yesterday [1]. It seems related to the SSL hostname verification because the failed tests come from https://github.com/apache/pulsar-client-cpp/pull/126. I tested the `technoboy8/pulsar:3.2.0-8

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

+1 (binding) - Built from source - Checked the signatures - Run standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Regards, Penghui On Wed, Jan 31, 2024 at 11:40 PM guo jiwei wrote: > This is the fifth release candidate for Apache Pul

[VOTE] Pulsar Release 3.2.0 Candidate 5

This is the fifth release candidate for Apache Pulsar version 3.2.0. It fixes the following issues: https://github.com/apache/pulsar/milestone/36?closed=1 *** Please download, test and verify on this release. This vote will stay open for at least 72 hours *** Note that we are verifying upon the