+1
Penghui
> On Nov 26, 2022, at 19:05, Enrico Olivelli wrote:
>
> +1
>
> Thanks
> Enrico
>
> Il Sab 26 Nov 2022, 10:02 tison ha scritto:
>
>> Thanks for your feedback! I'll create a tracking issue and start working on
>> subtasks the next week :)
>>
>> Best,
>> tison.
>>
>>
>> Haiting J
Hi
Cancel this vote, details are here
https://github.com/apache/pulsar/issues/18598
Regards
Jiwei Guo (Tboy)
On Thu, Nov 24, 2022 at 5:54 PM guo jiwei wrote:
> Hi
> We found a case that may break the old users. could we discuss if we
> need to resolve that and then continue to validate t
Hi Yunze,
Sure. I will raise a new candidate vote after these PRs get merged.
BR,
Zike Yang
On Sat, Nov 26, 2022 at 11:47 PM Yunze Xu wrote:
>
> Hi Zike,
>
> There are two PRs to fix the regression introduced from 3.0.0, I hope
> they can be included:
>
> https://github.com/apache/pulsar-client
Michael has brought this up before. Thanks for taking action!
+1
Also I think we need to think about docs for versions including master the same
way,
Best,
Dave
Sent from my iPhone
> On Nov 25, 2022, at 1:08 AM, tison wrote:
>
> Hi,
>
> I'm working on the API docs generator tools and noti
> I would like to discuss whether to disconnect the broker and the client
after authorization failure.
I don't think we should close the connection for authorization failure.
A connection can be used across multiple topics. Irrationality is no
accessibility of a topic will disconnect producers and
Hi all,
I've opened a PIP to discuss: https://github.com/apache/pulsar/issues/18616.
The consumer's MessageId related APIs have some hidden requirements
and flakiness and some behaviors are not documented well. This
proposal will introduce a TopicMessageId interface that exposes a
method to get a
