+1 to Enrico's suggestion about the API to allow sharing resources among
multiple clients.
I think this could be a good way to hide the implementation details about event
loop groups and prevent exposing Netty classes in the API.
btw. The timer instance that would need to be shared besides the
This is the fifth release candidate for Apache Pulsar, version 2.11.0.
This release contains 1617 commits by 61 contributors.
https://github.com/apache/pulsar/compare/v2.10.2...v2.11.0-candidate-5
CI for this release candidate
https://github.com/Technoboy-/pulsar/pull/26
*** Please download, tes
This is an interesting proposal. However, I'd suggest changes to the current
proposal.
I think that the current proposal is too invasive for the Pulsar code base.
"Introduce thread monitor to check if thread is blocking for long time." seems
to mean multiple things.
When looking at the PR, it
What I am concerned about is that if the old clients with other
schemas (i.e. schema is neither null nor AUTO_CONSUME) subscribe to
the topic with AUTO_CONSUME schema, what will happen? What's the
schema compatibility check rule on a topic with AUTO_CONSUME schema?
Thanks,
Yunze
On Mon, Jan 2, 20
Congratulations!!! Yunze
Jun Ma 于2022年12月31日周六 17:26写道：
> Congrats and well deserved!
>
> From: Dave Fisher
> Sent: Saturday, December 31, 2022 1:52
> To: dev@pulsar.apache.org
> Subject: Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar
>
> Congra
