> 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
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
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
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
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,
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
Hi all,
I made a PIP to discuss: https://github.com/apache/pulsar/issues/19113.
Thanks,
Sinan
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
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
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
>
Congrats!
Il giorno ven 30 dic 2022 alle 09:59 Yan Zhao ha
scritto:
> Congratulations !
>
--
Nicolò Boschi
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写道：
>
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
Congratulations !
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
> >
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
16 matches
Mail list logo
