[VOTE] PIP-347: add role field in consumer's stat
Hi, Pulsar Community. I would like to start the voting thread for PIP-347: add role field in consumer's stat. Proposal PR: https://github.com/apache/pulsar/pull/22564 Implementation PR: https://github.com/apache/pulsar/pull/22562 Thanks, Wenzhi Feng(thetumbled).
Re: [VOTE] PIP-347: add role field in consumer's stat
+1 nonbinding Thanks, Tao Jiuming thetumbled 于2024年5月14日 周二17:26写道： > Hi, Pulsar Community. > I would like to start the voting thread for PIP-347: add role field in > consumer's stat. > Proposal PR: https://github.com/apache/pulsar/pull/22564 > Implementation PR: https://github.com/apache/pulsar/pull/22562 > > Thanks, > Wenzhi Feng(thetumbled).
Re: [VOTE] PIP-347: add role field in consumer's stat
+1 (binding) Enrico Il giorno mar 14 mag 2024 alle ore 11:31 太上玄元道君 ha scritto: > +1 nonbinding > > Thanks, > Tao Jiuming > > thetumbled 于2024年5月14日 周二17:26写道： > > > Hi, Pulsar Community. > > I would like to start the voting thread for PIP-347: add role field in > > consumer's stat. > > Proposal PR: https://github.com/apache/pulsar/pull/22564 > > Implementation PR: https://github.com/apache/pulsar/pull/22562 > > > > Thanks, > > Wenzhi Feng(thetumbled). >
Re: [VOTE] PIP-347: add role field in consumer's stat
+1 (binding) Regards, Penghui On Tue, May 14, 2024 at 5:50 PM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il giorno mar 14 mag 2024 alle ore 11:31 太上玄元道君 ha > scritto: > > > +1 nonbinding > > > > Thanks, > > Tao Jiuming > > > > thetumbled 于2024年5月14日 周二17:26写道： > > > > > Hi, Pulsar Community. > > > I would like to start the voting thread for PIP-347: add role field > in > > > consumer's stat. > > > Proposal PR: https://github.com/apache/pulsar/pull/22564 > > > Implementation PR: https://github.com/apache/pulsar/pull/22562 > > > > > > Thanks, > > > Wenzhi Feng(thetumbled). > > >
Re: [VOTE] PIP-347: add role field in consumer's stat
+1 (non-binding) Thanks, Zixuan PengHui Li 于2024年5月14日周二 18:08写道： > +1 (binding) > > Regards, > Penghui > > On Tue, May 14, 2024 at 5:50 PM Enrico Olivelli > wrote: > > > +1 (binding) > > > > Enrico > > > > Il giorno mar 14 mag 2024 alle ore 11:31 太上玄元道君 ha > > scritto: > > > > > +1 nonbinding > > > > > > Thanks, > > > Tao Jiuming > > > > > > thetumbled 于2024年5月14日 周二17:26写道： > > > > > > > Hi, Pulsar Community. > > > > I would like to start the voting thread for PIP-347: add role field > > in > > > > consumer's stat. > > > > Proposal PR: https://github.com/apache/pulsar/pull/22564 > > > > Implementation PR: https://github.com/apache/pulsar/pull/22562 > > > > > > > > Thanks, > > > > Wenzhi Feng(thetumbled). > > > > > >
Re: [VOTE] PIP-347: add role field in consumer's stat
+1 (binding) BR, Zike Yang On Tue, May 14, 2024 at 6:56 PM Zixuan Liu wrote: > > +1 (non-binding) > > Thanks, > Zixuan > > PengHui Li 于2024年5月14日周二 18:08写道： > > > +1 (binding) > > > > Regards, > > Penghui > > > > On Tue, May 14, 2024 at 5:50 PM Enrico Olivelli > > wrote: > > > > > +1 (binding) > > > > > > Enrico > > > > > > Il giorno mar 14 mag 2024 alle ore 11:31 太上玄元道君 ha > > > scritto: > > > > > > > +1 nonbinding > > > > > > > > Thanks, > > > > Tao Jiuming > > > > > > > > thetumbled 于2024年5月14日 周二17:26写道： > > > > > > > > > Hi, Pulsar Community. > > > > > I would like to start the voting thread for PIP-347: add role field > > > in > > > > > consumer's stat. > > > > > Proposal PR: https://github.com/apache/pulsar/pull/22564 > > > > > Implementation PR: https://github.com/apache/pulsar/pull/22562 > > > > > > > > > > Thanks, > > > > > Wenzhi Feng(thetumbled). > > > > > > > > >
Re: [VOTE] PIP-347: add role field in consumer's stat
The vote is approved with 3 binding votes and close now. Votes: - Tao Jiuming (non-binding) - Enrico Olivelli (binding) - Penghui Li (binding) - Zixuan Liu (non-binding) - Zike Yang (binding) Thank you all for verifying and voting! Wenzhi Feng.(thetumbled) On 2024/05/14 11:20:35 Zike Yang wrote: > +1 (binding) > > BR, > Zike Yang > > On Tue, May 14, 2024 at 6:56?6?2PM Zixuan Liu wrote: > > > > +1 (non-binding) > > > > Thanks, > > Zixuan > > > > PengHui Li ??2024??5??14?? 18:08?? > > > > > +1 (binding) > > > > > > Regards, > > > Penghui > > > > > > On Tue, May 14, 2024 at 5:50?6?2PM Enrico Olivelli > > > wrote: > > > > > > > +1 (binding) > > > > > > > > Enrico > > > > > > > > Il giorno mar 14 mag 2024 alle ore 11:31 ha > > > > scritto: > > > > > > > > > +1 nonbinding > > > > > > > > > > Thanks, > > > > > Tao Jiuming > > > > > > > > > > thetumbled ??2024??5??14?? 17:26?? > > > > > > > > > > > Hi, Pulsar Community. > > > > > > I would like to start the voting thread for PIP-347: add role field > > > > in > > > > > > consumer's stat. > > > > > > Proposal PR: https://github.com/apache/pulsar/pull/22564 > > > > > > Implementation PR: https://github.com/apache/pulsar/pull/22562 > > > > > > > > > > > > Thanks, > > > > > > Wenzhi Feng(thetumbled). > > > > > > > > > > > > >
[VOTE] Release Apache Pulsar 3.0.5 based on 3.0.5-candidate-1
Hello Apache Pulsar Community, This is a call for the vote to release the Apache Pulsar version 3.0.5 based on 3.0.5-candidate-1. Included changes since the previous release: https://github.com/apache/pulsar/compare/v3.0.4...v3.0.5-candidate-1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Only votes from PMC members are binding, but members of the community are encouraged to test the release and vote with "(non-binding)". Note that we are voting upon the source (tag), binaries are provided for convenience. The release candidate is available at: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.0.5-candidate-1/ SHA-512 checksums: a6940adc7237636ef2e9eac833feca18900b2a76658a3c8314cd074a258c580f8c8b01d7eadaa9c8936e0df97cf2d8850e60c9c7144f1b8b154825aa05ecb934 apache-pulsar-3.0.5-src.tar.gz e2cc1e60e41514dd60ccdc06d0ac51301ec2a6cf18dab5ce4e87c350340d50aa509e2e70b0ae337716bb8fb163397cc978ae9c224dc454803f63fd25bd644930 apache-pulsar-3.0.5-bin.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1288 The tag to be voted upon: v3.0.5-candidate-1 (commit 2da571eb2dc97bec413d70d3800bb150fcec9507) https://github.com/apache/pulsar/releases/tag/v3.0.5-candidate-1 Pulsar's KEYS file containing PGP keys you use to sign the release: https://downloads.apache.org/pulsar/KEYS Docker images: docker pull lhotari/pulsar:3.0.5-2da571e https://hub.docker.com/layers/lhotari/pulsar/3.0.5-2da571e/images/sha256-66c92070acc750def529bd9c104649cc6e28d3dd4df623a0dff17290aa61cc24?context=explore docker pull lhotari/pulsar-all:3.0.5-2da571e https://hub.docker.com/layers/lhotari/pulsar-all/3.0.5-2da571e/images/sha256-16060c85aae05d610b3ca6e5ed578e570de0debfc3fb2854288263f741e77750?context=explore Please download the source package, and follow the README to build and run the Pulsar standalone service. More advanced release validation instructions can be found at https://pulsar.apache.org/contribute/validate-release-candidate/ Thanks, Lari Hotari
Community over Code EU 2024: The countdown has started!
[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] We are very close to Community Over Code EU -- check out the amazing program and the special discounts that we have for you. Special discounts You still have the opportunity to secure your ticket for Community Over Code EU. Explore the various options available, including the regular pass, the committer and groups pass, and now introducing the one-day pass tailored for locals in Bratislava. We also have a special discount for you to attend both Community Over Code and Berlin Buzzwords from June 9th to 11th. Visit our website to find out more about this opportunity and contact te...@sg.com.mx to get the discount code. Take advantage of the discounts and register now! https://eu.communityovercode.org/tickets/ Check out the full program! This year Community Over Code Europe will bring to you three days of keynotes and sessions that cover topics of interest for ASF projects and the greater open source ecosystem including data engineering, performance engineering, search, Internet of Things (IoT) as well as sessions with tips and lessons learned on building a healthy open source community. Check out the program: https://eu.communityovercode.org/program/ Keynote speaker highlights for Community Over Code Europe include: * Dirk-Willem Van Gulik, VP of Public Policy at the Apache Software Foundation, will discuss the Cyber Resiliency Act and its impact on open source (All your code belongs to Policy Makers, Politicians, and the Law). * Dr. Sherae Daniel will share the results of her study on the impact of self-promotion for open source software developers (To Toot or not to Toot, that is the question). * Asim Hussain, Executive Director of the Green Software Foundation will present a framework they have developed for quantifying the environmental impact of software (Doing for Sustainability what Open Source did for Software). * Ruth Ikegah will discuss the growth of the open source movement in Africa (From Local Roots to Global Impact: Building an Inclusive Open Source Community in Africa) * A discussion panel on EU policies and regulations affecting specialists working in Open Source Program Offices Additional activities * Poster sessions: We invite you to stop by our poster area and see if the ideas presented ignite a conversation within your team. * BOF time: Don't miss the opportunity to discuss in person with your open source colleagues on your shared interests. * Participants reception: At the end of the first day, we will have a reception at the event venue. All participants are welcome to attend! * Spontaneous talks: There is a dedicated room and social space for having spontaneous talks and sessions. Get ready to share with your peers. * Lighting talks: At the end of the event we will have the awaited Lighting talks, where every participant is welcome to share and enlighten us. Please remember: If you haven't applied for the visa, we will provide the necessary letter for the process. In the unfortunate case of a visa rejection, your ticket will be reimbursed. See you in Bratislava, Community Over Code EU Team
[VOTE] Release Apache Pulsar 3.2.3 based on 3.2.3-candidate-1
Hello Apache Pulsar Community, This is a call for the vote to release the Apache Pulsar version 3.2.3 based on 3.2.3-candidate-1. Included changes since the previous release: https://github.com/apache/pulsar/compare/v3.2.2...v3.2.3-candidate-1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Only votes from PMC members are binding, but members of the community are encouraged to test the release and vote with "(non-binding)". Note that we are voting upon the source (tag), binaries are provided for convenience. The release candidate is available at: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.3-candidate-1/ SHA-512 checksums: 76b1075ec13608eed70b735d2c807d22134f3b28b578efc4fef05b6e740d84c9e00173ec8a2b60fa597d66bedc0ac4c9565e9acf817af26bd88adc095b3e6af4 apache-pulsar-3.2.3-src.tar.gz eaec1feac417949794a6a14c8ab7908235e36a34e644fe1c61fcc1cf39d621d8746492c2d5c8c6ae03c45de4c402e5baa0b1fc7c78b2368fccfff69d2abd9990 apache-pulsar-3.2.3-bin.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1290 The tag to be voted upon: v3.2.3-candidate-1 (commit 2f8a2bd5fd5b258dbe44c772b824f06c540975ea) https://github.com/apache/pulsar/releases/tag/v3.2.3-candidate-1 Pulsar's KEYS file containing PGP keys you use to sign the release: https://downloads.apache.org/pulsar/KEYS Docker images: docker pull lhotari/pulsar:3.2.3-2f8a2bd https://hub.docker.com/layers/lhotari/pulsar/3.2.3-2f8a2bd/images/sha256-23c45434fe7955ff3aba124609ab965132a6304e96441e668c5bd9507d1e4284?context=explore docker pull lhotari/pulsar-all:3.2.3-2f8a2bd https://hub.docker.com/layers/lhotari/pulsar-all/3.2.3-2f8a2bd/images/sha256-443831e5c40005756219f0840b9609d6ba27ecd0eb07df1afe17e8a1a1ed69c9?context=explore Please download the source package, and follow the README to build and run the Pulsar standalone service. More advanced release validation instructions can be found at https://pulsar.apache.org/contribute/validate-release-candidate/ Thanks, Lari Hotari
Re: [DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic
Hi, Yubiao
Is it better to create the same number of retry/dlq topic partitions as the
original topic?
I mean, if the original topic has 16 partitions, we also create 16(or some
other numbers, can be configurable) partitions for the retry/dlq topic.
If the topic/partition is a retry/dlq topic, it's name matches the pattern:
`{topic}-partition-{n}-{subscription}-DLQ`, right?
Can we just parse the name and then get the origin topic name, and create
retry/dlq topic with the same partitions?
Say, if client wants to create
`persistent://public/default/some_topic-partition-1-test_sub-DLQ`,
we parse the topic name, then we get the origin topic name
`persistent://public/default/some_topic` and the subscription name `test_sub`.
After this, we look up the number of partitions of the origin topic, for
instance, 16 partitions, in the last, create a partitioned topic
`admin.topics.createPartitionedTopic("persistent://public/default/some_topic-test_sub-DLQ",
16)`.
And we can also increase the retry/dlq topic partitions if the origin topic
partitions increased.
WDYT, is it feasible?
Thanks,
Tao Jiuming
On 2024/05/13 18:56:01 Yubiao Feng wrote:
> Hi community
>
> I want to change the behavior of DLQ/Retry Topic auto creation.
>
> ### Motivation
> After you set `defaultNumPartitions` to `16`, you will get `16` partitions
> per topic, and `16*16` DLQ partitions per subscription, you will get a huge
> number of DLQs if you have more than one subscription under one topic. For
> example:
> - create topic `t1` with `16` partitions
> - you will get `t1-partition-0`, `t1-partition-1`...`tp-partition-15`.
> - after you enable DLQ, you will get the following `16*16` DLQs per
> subscription
> - `t1-partition-0-{subscription}-DLQ-partition-0`
> - `t1-partition-0-{subscription}-DLQ-partition-1`
> - ...
> - `t1-partition-15-{subscription}-DLQ-partition-15`
> - `t1-partition-1-{subscription}-DLQ-partition-0`
> - `t1-partition-1-{subscription}-DLQ-partition-1`
> - ...
> - ...
> - ...
> - `t1-partition-15-{subscription}-partition-15`
>
> ### Goal
> - Do not create partitioned DLQs/Retry topics automatically.
> - Users can also create partitioned DLQ manually if they need it.
>
> I have drafted a PR, please take a look
> - https://github.com/apache/pulsar/pull/22705
>
> Thanks
> Yubiao Feng
>
Re: [DISCUSS] Regarding DLQ/Retry Topic auto creation, do not create partitioned DLQ/Retry Topic
Hi Jiuming
> Is it better to create the same number of retry/dlq topic
> partitions as the original topic?
That is what I want to change, in other words,
https://github.com/apache/pulsar/pull/22705 did this change.
But the topic name is not the same as you mentioned, the behavior is like
the below after the PR:
- create topic `t1` with `16` partitions
- you will get `t1-partition-0`, `t1-partition-1`...`tp-partition-15`.
- after you enable DLQ, you will get the following `16` DLQs:
`t1-partition-0-{subscription}-DLQ`,
`t1-partition-1-{subscription}-DLQ`...`t1-partition-15-{subscription}-DLQ`
We can not name the DLQ as `t1-DLQ` if the primary topic is partitioned
because we can not define the behavior after users expending the partitions
of `t1` to `20`. After the PR, the DLQ related to the partitions expanded
will be created automatically, which is expected.
Thanks
Yubiao Feng
On Wed, May 15, 2024 at 1:21 AM Tao Jiuming wrote:
> Hi, Yubiao
>
> Is it better to create the same number of retry/dlq topic partitions as
> the original topic?
>
> I mean, if the original topic has 16 partitions, we also create 16(or some
> other numbers, can be configurable) partitions for the retry/dlq topic.
>
> If the topic/partition is a retry/dlq topic, it's name matches the
> pattern:
> `{topic}-partition-{n}-{subscription}-DLQ`, right?
>
> Can we just parse the name and then get the origin topic name, and create
> retry/dlq topic with the same partitions?
>
> Say, if client wants to create
> `persistent://public/default/some_topic-partition-1-test_sub-DLQ`,
> we parse the topic name, then we get the origin topic name
> `persistent://public/default/some_topic` and the subscription name
> `test_sub`.
> After this, we look up the number of partitions of the origin topic, for
> instance, 16 partitions, in the last, create a partitioned topic
> `admin.topics.createPartitionedTopic("persistent://public/default/some_topic-test_sub-DLQ",
> 16)`.
>
> And we can also increase the retry/dlq topic partitions if the origin
> topic partitions increased.
>
> WDYT, is it feasible?
>
> Thanks,
> Tao Jiuming
>
> On 2024/05/13 18:56:01 Yubiao Feng wrote:
> > Hi community
> >
> > I want to change the behavior of DLQ/Retry Topic auto creation.
> >
> > ### Motivation
> > After you set `defaultNumPartitions` to `16`, you will get `16`
> partitions
> > per topic, and `16*16` DLQ partitions per subscription, you will get a
> huge
> > number of DLQs if you have more than one subscription under one topic.
> For
> > example:
> > - create topic `t1` with `16` partitions
> > - you will get `t1-partition-0`, `t1-partition-1`...`tp-partition-15`.
> > - after you enable DLQ, you will get the following `16*16` DLQs per
> > subscription
> > - `t1-partition-0-{subscription}-DLQ-partition-0`
> > - `t1-partition-0-{subscription}-DLQ-partition-1`
> > - ...
> > - `t1-partition-15-{subscription}-DLQ-partition-15`
> > - `t1-partition-1-{subscription}-DLQ-partition-0`
> > - `t1-partition-1-{subscription}-DLQ-partition-1`
> > - ...
> > - ...
> > - ...
> > - `t1-partition-15-{subscription}-partition-15`
> >
> > ### Goal
> > - Do not create partitioned DLQs/Retry topics automatically.
> > - Users can also create partitioned DLQ manually if they need it.
> >
> > I have drafted a PR, please take a look
> > - https://github.com/apache/pulsar/pull/22705
> >
> > Thanks
> > Yubiao Feng
> >
>
Re: [DISCUSS] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis
+1 Best, Ran Gao On 2024/05/10 03:31:13 Yong Zhang wrote: > Hi all, > > I pushed a new proposal to allow to use -1 to disable > the managedLedgerOffloadDeletionLagInMillis to not delete the data from > bookkeeper. > > Please take a look and share your thoughts. Thanks! > > PIP: https://github.com/apache/pulsar/pull/22688 > > Best Regards, > Yong >
Re: [VOTE] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis
+1 (binding) Regards Jiwei Guo (Tboy) On Tue, May 14, 2024 at 12:05 PM Zike Yang wrote: > +1 (binding) > > Thanks, > Zike Yang > > On Mon, May 13, 2024 at 3:08 PM ZhangJian He wrote: > > > > +1(nonbinding) > > > > Thanks > > ZhangJian He > > Twitter: shoothzj > > Wechat: shoothzj > > > > > > On Mon, May 13, 2024 at 2:35 PM Hang Chen wrote: > > > > > +1 (binding) > > > > > > Thanks, > > > Hang > > > > > > 太上玄元道君 于2024年5月13日周一 11:30写道： > > > > > > > > +1 nonbinding > > > > > > > > Thanks, > > > > Tao Jiuming > > > > > > > > Yong Zhang 于2024年5月13日周一 10:57写道： > > > > > > > > > Hi, > > > > > > > > > > I would like to start voting thread for PIP-350. > > > > > https://github.com/apache/pulsar/pull/22688 > > > > > > > > > > The implementation PR is: > > > > > https://github.com/apache/pulsar/pull/22689 > > > > > > > > > > Discuss thread: > > > > > https://lists.apache.org/thread/7tlpkcm2933ddg95kgrb42943r4gq3v9 > > > > > > > > > > Thanks, > > > > > Yong > > > > > > > > >
Re: [VOTE] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis
The vote closes with 3 binding votes. Votes: - Tao Jiuming (non-binding) - Hang Chen (binding) - ZhangJian He (non-binding) - Zike Yang (binding) - Jiwei Guo (binding) Thanks for all your help! Yong On Wed, 15 May 2024 at 09:40, guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Tue, May 14, 2024 at 12:05 PM Zike Yang wrote: > > > +1 (binding) > > > > Thanks, > > Zike Yang > > > > On Mon, May 13, 2024 at 3:08 PM ZhangJian He wrote: > > > > > > +1(nonbinding) > > > > > > Thanks > > > ZhangJian He > > > Twitter: shoothzj > > > Wechat: shoothzj > > > > > > > > > On Mon, May 13, 2024 at 2:35 PM Hang Chen wrote: > > > > > > > +1 (binding) > > > > > > > > Thanks, > > > > Hang > > > > > > > > 太上玄元道君 于2024年5月13日周一 11:30写道： > > > > > > > > > > +1 nonbinding > > > > > > > > > > Thanks, > > > > > Tao Jiuming > > > > > > > > > > Yong Zhang 于2024年5月13日周一 10:57写道： > > > > > > > > > > > Hi, > > > > > > > > > > > > I would like to start voting thread for PIP-350. > > > > > > https://github.com/apache/pulsar/pull/22688 > > > > > > > > > > > > The implementation PR is: > > > > > > https://github.com/apache/pulsar/pull/22689 > > > > > > > > > > > > Discuss thread: > > > > > > https://lists.apache.org/thread/7tlpkcm2933ddg95kgrb42943r4gq3v9 > > > > > > > > > > > > Thanks, > > > > > > Yong > > > > > > > > > > > > >
Re: [DISCUSS] Release Apache Pulsar Python Client 3.4.1
> I tried but it didn't work. Could you share the CI workflow so I can take a look? Meanwhile, would you like to start the release for Python client 3.5.1? Thanks, Yunze On Sat, May 11, 2024 at 5:54 PM Zixuan Liu wrote: > > > Please release 3.5.1 rather than 3.4.1 because 3.5.0 is already > released. It's too heavy to maintain old releases for client libraries > for now. > > Let's go to 3.5.1. > > > However, it would be better to remove the `functions` component from > pulsar-client-python because the Python client itself never uses these > dependencies. See my discussion [1] before. Since python functions is > maintained in the Pulsar main repository, we should maintain the extra > dependencies in the Pulsar main repo as well. > > Good idea +1. > > > Would this release block the Pulsar 3.3.0 release? > > Yes, the current Python client will cause a particularly long time(2 hours) > to build a pulsar ARM image. > > > If yes, a quicker way to fix it was to add a `requirements.txt` that > includes a proper > version of grpcio and then run `python -m pip install -r > python/requirements.txt`. > > I tried but it didn't work. > > Thanks, > Zixuan > > > Yunze Xu 于2024年5月11日周六 12:25写道： > > > Sorry I missed the discussion link: > > https://lists.apache.org/thread/5s2l9vgt5f973psb6xlttpmy4rpym7zh > > > > Would this release block the Pulsar 3.3.0 release? If yes, a quicker > > way to fix it was to add a `requirements.txt` that includes a proper > > version of grpcio and then run `python -m pip install -r > > python/requirements.txt`. > > > > Here is an example: > > > > ``` > > pulsar-client == 3.5.0 > > protobuf>=3.6.1,<=3.20.3 > > grpcio >= 1.60.0 > > apache-bookkeeper-client>=4.16.1 > > prometheus_client > > ratelimit > > ``` > > > > Thanks, > > Yunze > > > > On Sat, May 11, 2024 at 12:19 PM Yunze Xu wrote: > > > > > > Please release 3.5.1 rather than 3.4.1 because 3.5.0 is already > > > released. It's too heavy to maintain old releases for client libraries > > > for now. > > > > > > However, it would be better to remove the `functions` component from > > > pulsar-client-python because the Python client itself never uses these > > > dependencies. See my discussion [1] before. Since python functions is > > > maintained in the Pulsar main repository, we should maintain the extra > > > dependencies in the Pulsar main repo as well. > > > > > > Thanks, > > > Yunze > > > > > > On Wed, May 8, 2024 at 11:26 PM Zixuan Liu wrote: > > > > > > > > Hi all, > > > > > > > > https://github.com/apache/pulsar-client-python/pull/174 breaks the > > > > python-client installation in the pulsar arm image, and then the > > release > > > > manager of pulsar@3.3.0 will take about 2 hours to build the grpcio > > wheel, > > > > please see > > > > > > https://github.com/nodece/pulsar-python-deps-build/actions/runs/8891459473/job/24418839959#step:6:315 > > > > for > > > > details. > > > > > > > > https://github.com/apache/pulsar-client-python/pull/211 fixes that, > > but I'm > > > > not sure if a new version will be released. > > > > > > > > Thanks, > > > > Zixuan > >
Re: [DISCUSS] Cherry-pick topic load failed count metrics to release branches
The master metric name differs because we didn't add a metric with the pulsar prefix. https://github.com/apache/pulsar/pull/20720 fixes that. Another thing is that this cherry-pick broke the branch-2.10 CI: https://github.com/apache/pulsar/pull/13785 upgrades prometheus-client on the branch-2.11, which means we must take care of the metric name. Thanks, Zixuan Yubiao Feng 于2024年5月2日周四 23:44写道： > Hi all > > Both #19236 and #22580 have been cherry-picked. But the metric name in the > `branch-3.0`, `branch-2.11`, and `branch-2.10` is > `topic_load_failed_total`, it is named `pulsar_topic_load_failed_count` on > the branch `master`. > > Thanks > Yubiao Feng > > On Mon, Apr 22, 2024 at 5:40 PM PengHui Li wrote: > > > Hi, all > > > > I would like to start a discussion to cherry-pick > > https://github.com/apache/pulsar/pull/19236 > > to the release branches > > > > - branch-3.0 > > - branch-2.11 > > - branch-2.10 > > > > The topic load is a critical operation in Pulsar. If the topic > > not able to be loaded, the producer or consumer will not > > able to connect to the topic. > > > > Publishing and consumption are the staple features of Pulsar. > > So I think it should be worth having #19236 in all the release > > branches to allow users to monitor the topic load failures > > > > And the change is low risky with only a few line changes. > > > > The thread will keep open for 48 hours. If there is no objections, > > I will perform the cherry-picking. > > > > Regards, > > Penghui > > >
Re: [VOTE] Release Apache Pulsar 3.0.5 based on 3.0.5-candidate-1
+1 (binding) - Build from source - Checked the signatures - Start standalone - Verified producers and consumers - Verified Cassandra connect - Verified Stateful function Regards Jiwei Guo (Tboy) On Tue, May 14, 2024 at 8:57 PM Lari Hotari wrote: > Hello Apache Pulsar Community, > > This is a call for the vote to release the Apache Pulsar version 3.0.5 > based on 3.0.5-candidate-1. > > Included changes since the previous release: > https://github.com/apache/pulsar/compare/v3.0.4...v3.0.5-candidate-1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Only votes from PMC members are binding, but members of the community are > encouraged to test the release and vote with "(non-binding)". > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > The release candidate is available at: > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.0.5-candidate-1/ > > SHA-512 checksums: > a6940adc7237636ef2e9eac833feca18900b2a76658a3c8314cd074a258c580f8c8b01d7eadaa9c8936e0df97cf2d8850e60c9c7144f1b8b154825aa05ecb934 > apache-pulsar-3.0.5-src.tar.gz > e2cc1e60e41514dd60ccdc06d0ac51301ec2a6cf18dab5ce4e87c350340d50aa509e2e70b0ae337716bb8fb163397cc978ae9c224dc454803f63fd25bd644930 > apache-pulsar-3.0.5-bin.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1288 > > The tag to be voted upon: > v3.0.5-candidate-1 (commit 2da571eb2dc97bec413d70d3800bb150fcec9507) > https://github.com/apache/pulsar/releases/tag/v3.0.5-candidate-1 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Docker images: > docker pull lhotari/pulsar:3.0.5-2da571e > > https://hub.docker.com/layers/lhotari/pulsar/3.0.5-2da571e/images/sha256-66c92070acc750def529bd9c104649cc6e28d3dd4df623a0dff17290aa61cc24?context=explore > docker pull lhotari/pulsar-all:3.0.5-2da571e > > https://hub.docker.com/layers/lhotari/pulsar-all/3.0.5-2da571e/images/sha256-16060c85aae05d610b3ca6e5ed578e570de0debfc3fb2854288263f741e77750?context=explore > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > More advanced release validation instructions can be found at > https://pulsar.apache.org/contribute/validate-release-candidate/ > > Thanks, > > Lari Hotari >
Re: [VOTE] Release Apache Pulsar 3.2.3 based on 3.2.3-candidate-1
+1 (binding) - Build from source - Checked the signatures - Start standalone - Verified producers and consumers - Verified Cassandra connect - Verified Stateful function Regards Jiwei Guo (Tboy) On Wed, May 15, 2024 at 12:35 AM Lari Hotari wrote: > Hello Apache Pulsar Community, > > This is a call for the vote to release the Apache Pulsar version 3.2.3 > based on 3.2.3-candidate-1. > > Included changes since the previous release: > https://github.com/apache/pulsar/compare/v3.2.2...v3.2.3-candidate-1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Only votes from PMC members are binding, but members of the community are > encouraged to test the release and vote with "(non-binding)". > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > The release candidate is available at: > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.3-candidate-1/ > > SHA-512 checksums: > 76b1075ec13608eed70b735d2c807d22134f3b28b578efc4fef05b6e740d84c9e00173ec8a2b60fa597d66bedc0ac4c9565e9acf817af26bd88adc095b3e6af4 > apache-pulsar-3.2.3-src.tar.gz > eaec1feac417949794a6a14c8ab7908235e36a34e644fe1c61fcc1cf39d621d8746492c2d5c8c6ae03c45de4c402e5baa0b1fc7c78b2368fccfff69d2abd9990 > apache-pulsar-3.2.3-bin.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1290 > > The tag to be voted upon: > v3.2.3-candidate-1 (commit 2f8a2bd5fd5b258dbe44c772b824f06c540975ea) > https://github.com/apache/pulsar/releases/tag/v3.2.3-candidate-1 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Docker images: > docker pull lhotari/pulsar:3.2.3-2f8a2bd > > https://hub.docker.com/layers/lhotari/pulsar/3.2.3-2f8a2bd/images/sha256-23c45434fe7955ff3aba124609ab965132a6304e96441e668c5bd9507d1e4284?context=explore > docker pull lhotari/pulsar-all:3.2.3-2f8a2bd > > https://hub.docker.com/layers/lhotari/pulsar-all/3.2.3-2f8a2bd/images/sha256-443831e5c40005756219f0840b9609d6ba27ecd0eb07df1afe17e8a1a1ed69c9?context=explore > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > More advanced release validation instructions can be found at > https://pulsar.apache.org/contribute/validate-release-candidate/ > > Thanks, > > Lari Hotari >
