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

2024-02-29 Thread Yunze Xu
This is the first release candidate for Apache Pulsar Client C++, version 3.5.0. It fixes the following issues: https://github.com/apache/pulsar-client-cpp/milestone/6?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are

Re: [DISCUSS] Do not create partitioned metadata when calling pulsarClient.getPartitionsForTopic(topicName)

2024-02-29 Thread Matteo Merli
Rather than raise the protocol version, there’s a feature flag mechanism in the connect/connected handshake for this purpose -- Matteo Merli On Thu, Feb 29, 2024 at 6:38 AM PengHui Li wrote: > Yes, it’s better to bump a protocol version to keep the compatibility. > > Regards, > Penghui > > On

Re: [DISCUSS] Do not create partitioned metadata when calling pulsarClient.getPartitionsForTopic(topicName)

2024-02-29 Thread PengHui Li
Yes, it’s better to bump a protocol version to keep the compatibility. Regards, Penghui On Thu, Feb 29, 2024 at 16:13 Enrico Olivelli wrote: > Il Gio 29 Feb 2024, 08:46 PengHui Li ha scritto: > > > +1 for the motivation > > > > We should not create partitioned topics when calling > > `pulsarCl

Re: [DISCUSS] Do not create partitioned metadata when calling pulsarClient.getPartitionsForTopic(topicName)

2024-02-29 Thread Enrico Olivelli
Il Gio 29 Feb 2024, 08:46 PengHui Li ha scritto: > +1 for the motivation > > We should not create partitioned topics when calling > `pulsarClient.getPartitionsForTopic` > > The tricky part is the broker doesn't know if the partition metadata > getting request is from create produce/consumer or ju