Thank you all! Let's collaborate for a better Pulsar community :D
Best,
tison.
lifepuzzlefun 于2023年7月23日周日 15:40写道:
> Congrats!
>
>
> Best,
> lifepuzzlefun
>
> On 2023/07/23 04:13:35 Haiting Jiang wrote:
> > Congrats!
> >
> > Best,
> > Haiting
> >
> > On Sun, Jul 23, 2023 at 9:38 AM houxiaoyu
Hi Pulsar Community, I am writing to start the discussion on PIP 286 PR
with PIP contents: https://github.com/apache/pulsar/pull/20867 Thanks,
Cong Zhao
Hi Pulsar Community,
I would like to find a generic way to inject secrets into connector
configuration without needing to rewrite existing connectors. I
created this issue [0] to describe the current state of connector
secret management and to discuss potential solutions. I created [1] to
show my
+1
Do we have the timeline for this release? Such as the code-freeze time
point, when to release RC-X, and when to announce the release.
Thanks,
Zike Yang
On Mon, Jul 17, 2023 at 8:48 PM guo jiwei wrote:
>
> Hi community,
>It has been more than 2 months since releasing 3.0.x. We now have m
+1
Thanks,
Zike Yang
On Mon, Jul 24, 2023 at 8:37 AM Yunze Xu wrote:
>
> Hi all,
>
> I would like to propose releasing the Pulsar C++ Client 3.2.0. It has
> been about 2 months since the last release. There have been many new
> features and bug fixes since then. It's time to release a new versio
Hi all,
Currently, we have found several regression bugs introduced in 0.10.0
and 0.11.0.
Here are the bug-fix PRs for them:
- https://github.com/apache/pulsar-client-go/pull/1052 fixes a
blocking issue when publishing a message with Value and Payload both
set. The bug was introduced by
https://g
+1
Thanks
Xiaoyu Hou
丛搏 于2023年7月24日周一 19:58写道:
> Hi, Pulsar Community
>
> I opened a new PIP design PR.
>
> https://github.com/apache/pulsar/pull/20859
>
> Thanks,
> Bo
>
Hi, Pulsar Community
I opened a new PIP design PR.
https://github.com/apache/pulsar/pull/20859
Thanks,
Bo
After upgrading to Pulsar 2.11.0, we encountered an issue where we
were unable to immediately query non-persistent topics that were
created in Pulsar. This behavior was unexpected as everything was
functioning properly prior to this release. We have identified two
known issues ([1] and [2]) that ar