This is the 2nd release candidate for Apache Pulsar Client Python,
version 3.5.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-python/milestone/6?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Python wheel
Closing this vote with 4 binding and 4 non-binding +1s
Binding +1s:
* Lari
* Mattison
* PengHui
* Matteo
Non-Binding +1s:
* Dao Jun
* Apurva
* Asaf
* Zixuan
Thanks,
Matteo
--
Matteo Merli
On Thu, Mar 14, 2024 at 11:54 PM Zixuan Liu wrote:
> +1 (non-binding)
>
> Thanks,
> Zixuan
>
Bumping this thread. Looking forward to some feedback.
Thanks!
-Lari
On 2024/03/18 10:32:03 Lari Hotari wrote:
> Hi all,
>
> I'd like to start a discussion about improving Pulsar broker cache design.
>
> In the Pulsar broker, there are two main scenarios for message
> dispatching to consumers:
Hi all,
The GEO-replication can be enabled on the Namespace and topic levels. When
GEO-replication is enabled on the namespace level, it automatically creates
the topic for the remote cluster, but the topic level misses this feature,
which can cause unexpected problems.
When two clusters use dif
I will cancel this release since I want to add the same API
(`Consumer.get_name())` that is introduced in
https://github.com/apache/pulsar-client-cpp/pull/360.
Thanks,
Yunze
On Fri, Mar 22, 2024 at 2:28 PM Yunze Xu wrote:
>
> This is the Nth release candidate for Apache Pulsar Client Python,
> v
