Re: [ANNOUNCE] Zili Chen (tison) as new PMC member in Apache Pulsar

[tison]

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  wrote:
> > >
> > > Congrats, Tison!
> > >
> > > Best,
> > > Xiaoyu Hou
> > >
> > > Dave Fisher  于2023年7月22日周六 22:23写道：
> > >
> > > > Congratulations!
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On Jul 21, 2023, at 10:05 AM, Michael Marshall 
> > > > wrote:
> > > > >
> > > > > Hi Pulsar Community,
> > > > >
> > > > > The Apache Pulsar Project Management Committee (PMC) has invited
> Zili
> > > > Chen
> > > > > (https://github.com/tisonkun) as a member of the PMC and we are
> > > > > pleased to announce that tison has accepted.
> > > > >
> > > > > tison is very active in the community by contributing and reviewing
> > > > > many PRs, actively engaging on the mailing list, triaging GitHub
> > > > > Issues, and helping out with the website.
> > > > >
> > > > > On behalf of the Pulsar PMC, welcome and congratulations to tison!
> > > > >
> > > > > Best,
> > > > > Michael
> > > >
> >

[DISCUSS] PIP-286: Add findNewestPosition method in the TopicCompactionService API

[Cong Zhao]

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

[DISCUSS] Generic Secret Injection for Sink/Source Configuration

[Michael Marshall]

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 preferred solution.

I don't think this change requires a PIP, but since it introduces a
new configuration, I am mentioning it on the mailing list.

Thanks,
Michael

[0] https://github.com/apache/pulsar/issues/20862
[1] https://github.com/apache/pulsar/issues/20863

Re: [DISCUSS] Apache Pulsar 3.1.0 release

[Zike Yang]

+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 more
> than 330 commits, including new PIP-255, PIP-275, and PIP-278, and fixing
> too many bugs and improvements.
>As mentioned in PIP-175 ,
> feature releases every 3 months, we need to prepare for release 3.1.0.
>Please let me know what you think.
>
>
> Regards
> Jiwei Guo (Tboy)

Re: [DISCUSS] Release Pulsar C++ Client 3.3.0

[Zike Yang]

+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 version.
>
> Please let me know if you have any PRs that need to be included in 3.3.0.
>
> Thanks,
> Yunze

[DISCUSS] Release Pulsar Go Client 0.10.1 and 0.11.1

[Zike Yang]

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://github.com/apache/pulsar-client-go/pull/805 in v0.10.0
- https://github.com/apache/pulsar-client-go/pull/1055 fixes
inaccurate producer memory limit issue . This bug was introduced by
https://github.com/apache/pulsar-client-go/pull/955 in v0.10.0.
Although it's introduced by the new feature, it may affect the
existing behavior.
- https://github.com/apache/pulsar-client-go/pull/1034 and
https://github.com/apache/pulsar-client-go/pull/1015 fix message
metadata not be set correctly issue introduced by
https://github.com/apache/pulsar-client-go/pull/805 in v0.10.0. These
fixes have already been included in v0.11.0
- https://github.com/apache/pulsar-client-go/pull/1058 fixes flush
operation cannot guarantee to flush all messages. This bug is
introduced by https://github.com/apache/pulsar-client-go/pull/1029 in
v0.11.0

I would like to propose releasing the Pulsar Go client 0.10.1 and
0.11.1 to release these regression bug fixes.

Please let me know if you have any PRs that need to be included in
v0.10.1 and v0.11.1.

Special thanks to @gunli and @Jiaqi Shen for helping to fix these
regression issues!

Thanks,
Zike Yang

Re: [DISCUSS] PIP-285: Add pulsar_subscription_back_log_duration metric

[houxiaoyu]

+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
>

[DISCUSS] PIP-285: Add pulsar_subscription_back_log_duration metric

[丛搏]

Hi, Pulsar Community

I opened a new PIP design PR.

https://github.com/apache/pulsar/pull/20859

Thanks,
Bo

[DISCUSS] The existing issue of querying the non-persistent topics

[Yufan Sheng]

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 are currently being tracked for
resolution.

However, even after the release of Pulsar 3.0 LTS, we are still
experiencing the same behavior. Therefore, I would like to initiate a
discussion regarding this issue. Specifically, I would like to
understand why Pulsar is dropping the queries on non-persistent topics
and explore potential solutions that would require minimal changes to
the codebase in the 3.0 LTS version.

[1]: https://github.com/apache/pulsar/issues/19316
[2]: https://github.com/apache/pulsar/issues/19493