Re: [DISCUSS] Reject create non-existent persistent partitions.

[Haiting Jiang]

> Should we allow the user to create the non-partitioned topic name like 
> `persistent://tenant/namespace/localname-partition-0`?

+1, I support this to be the default behavior.
But we need to consider the compatibility issue, so maybe the check
should happen on the server side and it can be turned off with a flag.

Thanks,
Haiting

On Thu, Dec 29, 2022 at 1:33 PM  wrote:
>
> Hi, All
>
> I have another question that needs to discuss.
>
> Should we allow the user to create the non-partitioned topic name like 
> `persistent://tenant/namespace/localname-partition-0`?
>
> If so, this is a little confusing with the partitioned topic.
>
> e.g.:
> TopicName#isPartitioned method.
>
> Best,
> Mattison
> On Dec 28, 2022, 12:43 +0800, mattisonc...@gmail.com, wrote:
> > Hi, All
> >
> > I'd like to start a discussion of this behaviour change as follow.
> >
> > The issue is described here:  https://github.com/apache/pulsar/issues/19085
> > And the fix PR here:  https://github.com/apache/pulsar/pull/19086
> >
> > ---
> >
> > Behaviour change:
> >
> > Before: we can create non-existent persistent partitions.
> >
> > After: we will get `PulsarClientException.TopicDoesNotExistException` when 
> > we create non-existent persistent partitions.
> >
> > Please feel free to leave comments if you have any concerns.
> >
> > Best,
> > Mattison

Re: [DISCUSS] PIP-235: Add metric for subscription backlog size

[Girish Sharma]

Hello Xiao,

When you say that the meaning of the metric will change, could you
elaborate further? The PIP does not talk about what all labels you are
proposing in this new metric, so maybe you can add more details in the PIP.

Here is what I understood from your PIP description. You will add a new
metric `pulsar_subscription_back_log_size` which will have granularity of
backlog size at a topic-subscription combination. Which means the general
use of the metric would be like sum(pulsar_subscription_back_log_size) by
(topic, subscription[, ...]) .
If this understanding is correct, then when the config to enable this new
metric is true, then these two expressions:

*`sum(pulsar_storage_backlog_size) by (cluster, topic)`*
and
*`sum(pulsar_subscription_back_log_size) by (cluster, topic)`*
will always result in the same value.
The only difference is that the new metric will also allow you to do
*`sum(pulsar_subscription_back_log_size) by (cluster, topic, subscription)`*
to get value for each subscription of the topic.

Regards

On Fri, Dec 30, 2022 at 10:26 PM 萧 易客  wrote:

> Hi Sharma,
>
> If a metric has different meaning with different config, it confuses user
> cause they need to check the config before use it. It's not best practice
> cause it's easy to made a mistake if user forgot or config changed.
> For example, if user has multiple clusters with different config, the same
> metric has different meaning on each cluser, it's add extra work to
> maintaining alarm rule.
>
> Yike Xiao
>
> 
> 发件人: Girish Sharma 
> 发送时间: 2022年12月31日 0:07
> 收件人: dev@pulsar.apache.org 
> 主题: Re: [DISCUSS] PIP-235: Add metric for subscription back size
>
> How about adding a new label subscription in the same metric? It should
> also not break any existing usage of the metric as well for those only
> aggregating on topic or cluster label. The documentation can clearly
> mention that this is an addon on top of existing metrics.
>
> Please pardon my mistake as I am new to this mailing list, but if new
> additions to the same metrics are not considered by default as a general
> guideline in pulsar codebase, then this can go on its own new metric. It is
> just that this new metric would then again need the same labels (cluster,
> broker, topic etc) causing a lot of duplicate data.
> In our in-house usage of pulsar, metrics finally flow into a central
> platform and we have to be careful on the size (number of metrics and
> labels) that we are ingesting into this platform.
>
> Regards
>
> On Fri, Dec 30, 2022 at 8:55 PM 萧 易客  wrote:
>
> > Hi pulsar community,
> >
> > Motivation
> > Now we have pulsar_storage_backlog_size for topic backlog size, user can
> > create an alarm rule like pulsar_storage_backlog_size > THRESHOLD​,
> > typically this alarm is going to notify corresponding subscription owner,
> > but it need extra process to identify subscriptions that backlog size
> > exceed the threshold. So we could add a new metric for subscription back
> > size.
> >
> > For more detail, please read PIP-235 issue page [1]
> >
> > It's my first PIP, I'm looking forward to hearing what you think and open
> > for any suggestions.
> >
> > [1]:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fissues%2F19112=05%7C01%7C%7C830f15a75a5e4834f0f808daea7ffc58%7C84df9e7fe9f640afb435%7C1%7C0%7C638080132677757011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hNjo6llUJ0gbi3PTjXwcYAipQ3cTSWmzFWFJCr3auZc%3D=0
> > [
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopengraph.githubassets.com%2Fabebee001c4e8297f9418e3b78bd77a854f26d1c4b73bfea5fb203251968a18e%2Fapache%2Fpulsar%2Fissues%2F19112=05%7C01%7C%7C830f15a75a5e4834f0f808daea7ffc58%7C84df9e7fe9f640afb435%7C1%7C0%7C638080132677757011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=p%2F7ZpaqFn5nJzVOP46cYjuN1KQZ0mhuiG8kUfJtkq7Q%3D=0
> > ]<
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fissues%2F19112=05%7C01%7C%7C830f15a75a5e4834f0f808daea7ffc58%7C84df9e7fe9f640afb435%7C1%7C0%7C638080132677757011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hNjo6llUJ0gbi3PTjXwcYAipQ3cTSWmzFWFJCr3auZc%3D=0
> >
> > PIP-235: Add metric for subscription back size · Issue #19112 ·
> > apache/pulsar<
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fissues%2F19112=05%7C01%7C%7C830f15a75a5e4834f0f808daea7ffc58%7C84df9e7fe9f640afb435%7C1%7C0%7C638080132677757011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hNjo6llUJ0gbi3PTjXwcYAipQ3cTSWmzFWFJCr3auZc%3D=0
> >
> > Motivation Now we have pulsar_storage_backlog_size for topic backlog
> size,
> 

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

[Dave Fisher]

Congratulations Yunze! Well deserved!

All the best,
Dave


> On Dec 29, 2022, at 4:42 AM, Haiting Jiang  wrote:
> 
> Hi all,
> 
> The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> (https://github.com/BewareMyPower) as a member of the PMC and we are
> pleased to announce that he has accepted.
> 
> He is very active in the community in the past few years and made a lot of 
> great contributions.
> 
> Welcome Yunze to the Apache Pulsar PMC.
> 
> Best Regards,
> Haiting Jiang on behalf of the Pulsar PMC

[THANKS] For taking care of Github Spam

[Dave Fisher]

Hi -

I was reviewing my junk folder today and noticed that yesterday there were a 
lot of Spam comments added to Github Discussions. I want to thank the community 
member who took care to delete all of these unwanted comments.

Thank you,
Dave

回复: [DISCUSS] PIP-235: Add metric for subscription backlog size

[萧 易客]

Hi Sharma,

If a metric has different meaning with different config, it confuses user cause 
they need to check the config before use it. It's not best practice cause it's 
easy to made a mistake if user forgot or config changed.
For example, if user has multiple clusters with different config, the same 
metric has different meaning on each cluser, it's add extra work to maintaining 
alarm rule.

Yike Xiao


发件人: Girish Sharma 
发送时间: 2022年12月31日 0:07
收件人: dev@pulsar.apache.org 
主题: Re: [DISCUSS] PIP-235: Add metric for subscription back size

How about adding a new label subscription in the same metric? It should
also not break any existing usage of the metric as well for those only
aggregating on topic or cluster label. The documentation can clearly
mention that this is an addon on top of existing metrics.

Please pardon my mistake as I am new to this mailing list, but if new
additions to the same metrics are not considered by default as a general
guideline in pulsar codebase, then this can go on its own new metric. It is
just that this new metric would then again need the same labels (cluster,
broker, topic etc) causing a lot of duplicate data.
In our in-house usage of pulsar, metrics finally flow into a central
platform and we have to be careful on the size (number of metrics and
labels) that we are ingesting into this platform.

Regards

On Fri, Dec 30, 2022 at 8:55 PM 萧 易客  wrote:

> Hi pulsar community,
>
> Motivation
> Now we have pulsar_storage_backlog_size for topic backlog size, user can
> create an alarm rule like pulsar_storage_backlog_size > THRESHOLD​,
> typically this alarm is going to notify corresponding subscription owner,
> but it need extra process to identify subscriptions that backlog size
> exceed the threshold. So we could add a new metric for subscription back
> size.
>
> For more detail, please read PIP-235 issue page [1]
>
> It's my first PIP, I'm looking forward to hearing what you think and open
> for any suggestions.
>
> [1]: 
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fissues%2F19112=05%7C01%7C%7C830f15a75a5e4834f0f808daea7ffc58%7C84df9e7fe9f640afb435%7C1%7C0%7C638080132677757011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hNjo6llUJ0gbi3PTjXwcYAipQ3cTSWmzFWFJCr3auZc%3D=0
> [
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopengraph.githubassets.com%2Fabebee001c4e8297f9418e3b78bd77a854f26d1c4b73bfea5fb203251968a18e%2Fapache%2Fpulsar%2Fissues%2F19112=05%7C01%7C%7C830f15a75a5e4834f0f808daea7ffc58%7C84df9e7fe9f640afb435%7C1%7C0%7C638080132677757011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=p%2F7ZpaqFn5nJzVOP46cYjuN1KQZ0mhuiG8kUfJtkq7Q%3D=0
> ]
> PIP-235: Add metric for subscription back size · Issue #19112 ·
> apache/pulsar
> Motivation Now we have pulsar_storage_backlog_size for topic backlog size,
> user can create an alarm rule like pulsar_storage_backlog_size 
> THRESHOLD, typically this alarm is going to notify cor...
> github.com
> 
> 
> 
> Yike Xiao
>


--
Girish Sharma

Re: [DISCUSS] PIP-235: Add metric for subscription back size

[Girish Sharma]

 How about adding a new label subscription in the same metric? It should
also not break any existing usage of the metric as well for those only
aggregating on topic or cluster label. The documentation can clearly
mention that this is an addon on top of existing metrics.

Please pardon my mistake as I am new to this mailing list, but if new
additions to the same metrics are not considered by default as a general
guideline in pulsar codebase, then this can go on its own new metric. It is
just that this new metric would then again need the same labels (cluster,
broker, topic etc) causing a lot of duplicate data.
In our in-house usage of pulsar, metrics finally flow into a central
platform and we have to be careful on the size (number of metrics and
labels) that we are ingesting into this platform.

Regards

On Fri, Dec 30, 2022 at 8:55 PM 萧 易客  wrote:

> Hi pulsar community,
>
> Motivation
> Now we have pulsar_storage_backlog_size for topic backlog size, user can
> create an alarm rule like pulsar_storage_backlog_size > THRESHOLD​,
> typically this alarm is going to notify corresponding subscription owner,
> but it need extra process to identify subscriptions that backlog size
> exceed the threshold. So we could add a new metric for subscription back
> size.
>
> For more detail, please read PIP-235 issue page [1]
>
> It's my first PIP, I'm looking forward to hearing what you think and open
> for any suggestions.
>
> [1]: https://github.com/apache/pulsar/issues/19112
> [
> https://opengraph.githubassets.com/abebee001c4e8297f9418e3b78bd77a854f26d1c4b73bfea5fb203251968a18e/apache/pulsar/issues/19112
> ]
> PIP-235: Add metric for subscription back size · Issue #19112 ·
> apache/pulsar
> Motivation Now we have pulsar_storage_backlog_size for topic backlog size,
> user can create an alarm rule like pulsar_storage_backlog_size 
> THRESHOLD, typically this alarm is going to notify cor...
> github.com
> 
> 
> 
> Yike Xiao
>


-- 
Girish Sharma

[DISCUSS] PIP-236: Upload AUTO_CONSUME SchemaType to Broker

[思楠刘]

Hi all,

I made a PIP to discuss: https://github.com/apache/pulsar/issues/19113.

Thanks,
Sinan

[DISCUSS] PIP-235: Add metric for subscription back size

[萧 易客]

Hi pulsar community,

Motivation
Now we have pulsar_storage_backlog_size for topic backlog size, user can create 
an alarm rule like pulsar_storage_backlog_size > THRESHOLD​, typically this 
alarm is going to notify corresponding subscription owner, but it need extra 
process to identify subscriptions that backlog size exceed the threshold. So we 
could add a new metric for subscription back size.

For more detail, please read PIP-235 issue page [1]

It's my first PIP, I'm looking forward to hearing what you think and open for 
any suggestions.

[1]: https://github.com/apache/pulsar/issues/19112
[https://opengraph.githubassets.com/abebee001c4e8297f9418e3b78bd77a854f26d1c4b73bfea5fb203251968a18e/apache/pulsar/issues/19112]
PIP-235: Add metric for subscription back size · Issue #19112 · 
apache/pulsar
Motivation Now we have pulsar_storage_backlog_size for topic backlog size, user 
can create an alarm rule like pulsar_storage_backlog_size  THRESHOLD, 
typically this alarm is going to notify cor...
github.com



Yike Xiao

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

[Christophe Bornet]

Congrats Yunze !

Le jeu. 29 déc. 2022 à 13:42, Haiting Jiang  a
écrit :

> Hi all,
>
> The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> (https://github.com/BewareMyPower) as a member of the PMC and we are
> pleased to announce that he has accepted.
>
> He is very active in the community in the past few years and made a lot of
> great contributions.
>
> Welcome Yunze to the Apache Pulsar PMC.
>
> Best Regards,
> Haiting Jiang on behalf of the Pulsar PMC
>

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

[萧 易客]

Congrats, xyz is a impressed id in the pulsar community.

Yike Xiao

> On Dec 29, 2022, at 20:42, Haiting Jiang  wrote:
> 
> Hi all,
> 
> The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBewareMyPower=05%7C01%7C%7Cc8130cf83cb646f85d5b08dae99a2bec%7C84df9e7fe9f640afb435%7C1%7C0%7C638079145633476094%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=MPiztpwl%2BL8jcmUkFUvrugplzi5o1iWl32UUNK6gK8k%3D=0)
>  as a member of the PMC and we are
> pleased to announce that he has accepted.
> 
> He is very active in the community in the past few years and made a lot of 
> great contributions.
> 
> Welcome Yunze to the Apache Pulsar PMC.
> 
> Best Regards,
> Haiting Jiang on behalf of the Pulsar PMC

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

[Nicolò Boschi]

Congrats!

Il giorno ven 30 dic 2022 alle 09:59 Yan Zhao  ha
scritto:

> Congratulations !
>
-- 
Nicolò Boschi

Re: [PROPOSAL] Website precommit and move the source of docs to the site repo

[tison]

Mail: https://lists.apache.org/thread/ff659j0y46j94c6jc6zlwotc78pq2n40
Issue: https://github.com/apache/pulsar/issues/19111

Best,
tison.


tison  于2022年12月30日周五 10:46写道：

> Hi Yu,
>
> Thanks for your recommendation! Yes, I'm going to do this.
>
> Best,
> tison.
>
>
> Yu  于2022年12月30日周五 09:20写道：
>
>> Thanks tison!
>>
>> It's better to
>> a) update the contribution processes of docs, website content, and release
>> notes [1] [2] [3] [4] [5]
>> b) inform the community about this breaking change officially in another
>> email (reminders for doc contributions)
>>
>> 
>>
>> docs:
>> [1] https://pulsar.apache.org/contribute/document-contribution/
>> [2]
>>
>> https://pulsar.apache.org/contribute/document-preview/#preview-documentation-changes
>> [3]
>>
>> https://pulsar.apache.org/contribute/document-preview/#preview-website-changes
>>
>> release notes:
>> [4] https://pulsar.apache.org/contribute/release-process/#update-the-site
>> [5] https://pulsar.apache.org/contribute/release-note-guide/
>>
>> On Thu, Dec 29, 2022 at 9:07 PM tison  wrote:
>>
>> > The new repo is reduced by 100MB:
>> >
>> > $ gh repo clone apache/pulsar -- --single-branch --depth=1
>> > $ du -sh pulsar | sort -rh
>> >  53M pulsar
>> >
>> > Best,
>> > tison.
>> >
>> >
>> > tison  于2022年12月29日周四 21:01写道：
>> >
>> > > Landed.
>> > >
>> > > Best,
>> > > tison.
>> > >
>> > >
>> > > tison  于2022年12月29日周四 17:51写道：
>> > >
>> > >> Here are the related PRs:
>> > >>
>> > >> * https://github.com/apache/pulsar/pull/19100
>> > >> * https://github.com/apache/pulsar-site/pull/348
>> > >>
>> > >> Best,
>> > >> tison.
>> > >>
>> > >>
>> > >> tison  于2022年12月26日周一 21:45写道：
>> > >>
>> > >>> FYI tracking issue has been created:
>> > >>> https://github.com/apache/pulsar/issues/19064
>> > >>>
>> > >>> I plan to finish it by the end of next month.
>> > >>>
>> > >>> Best,
>> > >>> tison.
>> > >>>
>> > >>>
>> > >>> tison  于2022年12月21日周三 11:33写道：
>> > >>>
>> >  Thanks for your feedback!
>> > 
>> >  @Yu
>> > 
>> >  Thanks for sharing the previous thread. I looped in
>> @michaeljmarshall
>> >  here.
>> > 
>> >  @Jun
>> > 
>> >  It's possible but causes a new shortcoming: Now you should tell the
>> >  contributor that the versioned docs are different from the NEXT
>> > version
>> >  docs, lol.
>> > 
>> >  If our developers don't complain about these separated sources.
>> Like
>> > @Asaf
>> >  comment:
>> > 
>> >  > We can take, let's say, five features and see if they were
>> actually
>> >  done in
>> >  > the same PR or separate PR. I guess that most documentation is
>> >  actually
>> >  > updated separately. Thus, from that perspective, maybe it’s not a
>> > con.
>> > 
>> >  Then we can do this refactor thoroughgoing.
>> > 
>> >  Also, if we keep, somehow several sources in the main repo. We
>> still
>> >  have shortcomings:
>> > 
>> >  1. Duplicated CI workflows.
>> >  2. Cumbersome preview scaffolding in the main repo.
>> > 
>> >  ... which is the original purpose I'd like to overcome.
>> > 
>> >  Best,
>> >  tison.
>> > 
>> > 
>> >  Jun Ma  于2022年12月21日周三 11:19写道：
>> > 
>> > > Is it possible to come up with a compromised solution that has the
>> > > pros of both sides but minimizes the side effect? I'm thinking
>> maybe
>> > it's
>> > > not necessary to sacrifice the current contribution process, as
>> long
>> > as it
>> > > can greatly reduce the load of back-end actions and source size.
>> For
>> > > example, if we only move out the versioned docs to the site repo
>> but
>> > keep
>> > > the source of the NEXT docs in the pulsar repo, does this help to
>> > win a
>> > > large proportion of those pros when people can still contribute as
>> > usual?
>> > >
>> > > 
>> > > From: Jiaqi Shen 
>> > > Sent: Tuesday, December 20, 2022 17:15
>> > > To: dev@pulsar.apache.org 
>> > > Subject: Re: [PROPOSAL] Website precommit and move the source of
>> docs
>> > > to the site repo
>> > >
>> > > +1, it makes sense to me.
>> > >
>> > > Thanks,
>> > > Jiaqi Shen
>> > >
>> > >
>> > > Yu  于2022年12月19日周一 20:57写道：
>> > >
>> > > > Hi tison,
>> > > >
>> > > > Thanks for raising this up!
>> > > >
>> > > > Our community had a similar discussion previously and chose to
>> > > "keep" the
>> > > > doc repo stay in the Pulsar main repo at that time.
>> > > >
>> > > > [1] lists the pros and cons of "keep" and "not keep" solutions.
>> > > >
>> > > > I'm +0 on this proposal because I think the total scores of
>> these
>> > two
>> > > > solutions are almost equal after weighing the pros and cons.
>> > > >
>> > > > 
>> > > >
>> > > > [1]
>> > https://lists.apache.org/thread/mf2xwntfgn84dq78ksqv22jk3drq6xb3
>> > > >
>> > > >
>> > 

[ATTENTION] The source of Pulsar document is moved to apache/pulsar-site

[tison]

Hi,

With the resolution of [1], I moved the source of the Pulsar document to
the site repo[2][3][4][5].

Now, if you'd like to update Pulsar document, you should submit a PR
against the site repo (apache/pulsar-site) instead of the main repo
(apache/pulsar, the site2 folder).

I've updated the Edit URL on the page[6], so if you click the "Edit this
page" button, you will be guided to the correct place.

The docs layout is almost the same as former site2 folder. I'll update the
corresponding contribution guide and release guide later. You can keep an
eye on the tracking issue[7].

Best,
tison.

[1] https://lists.apache.org/thread/89wl112cflvtoyfg3l7kglr1dozsljm9
[2] https://github.com/apache/pulsar-site
[3] https://github.com/apache/pulsar/pull/19100
[4] https://github.com/apache/pulsar-site/pull/348
[5] https://github.com/apache/pulsar/issues/19090
[6]
https://github.com/apache/pulsar-site/commit/a2c2d23c21fd9cf936a4381901001b5889973d8e
[7] https://github.com/apache/pulsar/issues/19064

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

[Yan Zhao]

Congratulations !

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

[Enrico Olivelli]

Congratulations !

Enrico

Il giorno ven 30 dic 2022 alle ore 09:56 Cong Zhao
 ha scritto:
>
> Congratulations! Yunze
>
> Best,
> Cong
>
> On 2022/12/29 12:42:36 Haiting Jiang wrote:
> > Hi all,
> >
> > The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> > (https://github.com/BewareMyPower) as a member of the PMC and we are
> > pleased to announce that he has accepted.
> >
> > He is very active in the community in the past few years and made a lot of 
> > great contributions.
> >
> > Welcome Yunze to the Apache Pulsar PMC.
> >
> > Best Regards,
> > Haiting Jiang on behalf of the Pulsar PMC
> >

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

[Cong Zhao]

Congratulations! Yunze

Best,
Cong

On 2022/12/29 12:42:36 Haiting Jiang wrote:
> Hi all,
> 
> The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> (https://github.com/BewareMyPower) as a member of the PMC and we are
> pleased to announce that he has accepted.
> 
> He is very active in the community in the past few years and made a lot of 
> great contributions.
> 
> Welcome Yunze to the Apache Pulsar PMC.
> 
> Best Regards,
> Haiting Jiang on behalf of the Pulsar PMC
>