Re: [VOTE] Pulsar Release 2.10.2 Candidate 2

Hi Haiting, There is a significant performance regression about publish throughput, more context is here: https://github.com/apache/pulsar/issues/17931 The fixed PR is here: https://github.com/apache/pulsar/pull/17948 This should be a release blocker I think. Thanks, Xiaoyu Hou Haiting Jiang

Re: [DISCUSS] Planning for Apache Pulsar 3.0

Thanks Lari. I have a pain point that is about documentation and developer awareness where we can help improve quality and suggest improvements. 1) Work on clear documentation about each thread pool and how it is used by the classes in the message path. 2) Add thread pool impacts to the PR temp

Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2

+1 (non-binding) - Build from the source code - Run producer and consumer guo jiwei 于2022年10月8日周六 11:27写道： > +1 (binding) > > - Build from the source code > - Run producer and consumer > > > Regards > Jiwei Guo (Tboy) > > > On Sat, Oct 8, 2022 at 11:17 AM Zike Yang wrote: > > > +1 (non-binding)

Re: Pulsar Summit Asia 2022 CFP is Open Now!

Dear community members, The CFP will be closed soon! If you have any great ideas, do not forget to submit a proposal. Thank you. Sherlock Xu > On Sep 20, 2022, at 11:36, Sherlock Xu wrote: > > Hi Apache Pulsar community members, > > Pulsar Summit Asia 2022

Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2

+1 (binding) - Build from the source code - Run producer and consumer Regards Jiwei Guo (Tboy) On Sat, Oct 8, 2022 at 11:17 AM Zike Yang wrote: > +1 (non-binding) > - Build from the source code > - Run producer and consumer > - Run pulsar-perf produce and consume > > Thanks, > Zike Yang > >

Re: [DISCUSS] Planning for Apache Pulsar 3.0

Thank you, Matteo. I'm just adding that it all makes sense that what you said. I hope that my other email clarified the need to get loose of any restrictions for a while in the planning of Pulsar 3.0. Making the changes a reality is something where the practice of incremental changes that you ha

Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2

+1 (non-binding) - Build from the source code - Run producer and consumer - Run pulsar-perf produce and consume Thanks, Zike Yang On Sat, Oct 8, 2022 at 10:53 AM Hang Chen wrote: > > +1(binding) > - Check sha 512 for the source code > - Build from the source code > - Run produce and consume > >

Re: [DISCUSS] Planning for Apache Pulsar 3.0

Thanks, Dave for sharing your views. I entirely agree. -Lari On 2022/10/08 01:41:47 Dave Fisher wrote: > To me the point of this discussion is for the community to discuss both > improvement ideas along with current pain points in the broker. Whether or > not the ideas and proposed solutions ar

Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2

+1(binding) - Check sha 512 for the source code - Build from the source code - Run produce and consume Thanks, Hang PengHui Li 于2022年9月29日周四 22:06写道： > > +1 (binding) > > - build from the source code > - test the produce and consume > > Penghui > > On Thu, Sep 29, 2022 at 2:43 PM Guangning E wr

Re: [DISCUSS] Planning for Apache Pulsar 3.0

We could all have our own favorite names for this work. :) There's advice that you should disrupt yourself before someone disrupts you. Shouldn't we follow that advice for Apache Pulsar? We can disrupt Pulsar together with our Apache hats on. The catch is that since we are doing this, we will be

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

Hi Matteo, Thank you for this critical work pulling the C++ (and Python) clients out of the main repository and into separate repositories and release cycles! I think this will be a significant benefit for the community. All the best, Dave Sent from my iPhone > On Oct 6, 2022, at 1:07 PM, Mat

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

+1 Thanks, Jiaqi Shen Xiangying Meng 于2022年10月8日周六 10:17写道： > +1 > > Thanks, > Xiangying > > > On Sat, Oct 8, 2022 at 9:43 AM Hang Chen wrote: > > > +1 > > > > Thanks, > > Hang > > > > Zike Yang 于2022年10月8日周六 09:19写道： > > > > > > +1 > > > > > > Thanks, > > > Zike Yang > > > > > > On Sat, Oct

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

+1 Thanks, Xiangying On Sat, Oct 8, 2022 at 9:43 AM Hang Chen wrote: > +1 > > Thanks, > Hang > > Zike Yang 于2022年10月8日周六 09:19写道： > > > > +1 > > > > Thanks, > > Zike Yang > > > > On Sat, Oct 8, 2022 at 9:17 AM PengHui Li wrote: > > > > > > +1 > > > > > > Regards, > > > Penghui > > > > > > On

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

+1 Thanks, Hang Zike Yang 于2022年10月8日周六 09:19写道： > > +1 > > Thanks, > Zike Yang > > On Sat, Oct 8, 2022 at 9:17 AM PengHui Li wrote: > > > > +1 > > > > Regards, > > Penghui > > > > On Fri, Oct 7, 2022 at 11:34 PM tison wrote: > > > > > +1 cool! > > > > > > Best, > > > tison. > > > > > > > > >

Re: [DISCUSS] Planning for Apache Pulsar 3.0

Thank you Rajan for explaining the crucial importance of client compatibility in a very clear way. Ensuring client compatibility is a "must" requirement. We happened to have some discussions about this topic at ApacheCon, and how to ensure protocol compatibility in the cases where there would be

Re: [DISCUSS] Planning for Apache Pulsar 3.0

To me the point of this discussion is for the community to discuss both improvement ideas along with current pain points in the broker. Whether or not the ideas and proposed solutions are breaking or incremental is yet to be determined. Let’s not get hung up on versions or nomenclature. All the

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

+1 Thanks, Zike Yang On Sat, Oct 8, 2022 at 9:17 AM PengHui Li wrote: > > +1 > > Regards, > Penghui > > On Fri, Oct 7, 2022 at 11:34 PM tison wrote: > > > +1 cool! > > > > Best, > > tison. > > > > > > Baodi Shi 于2022年10月7日周五 23:31写道： > > > > > +1 > > > > > > Thanks, > > > Baodi Shi > > > > > >

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

+1 Regards, Penghui On Fri, Oct 7, 2022 at 11:34 PM tison wrote: > +1 cool! > > Best, > tison. > > > Baodi Shi 于2022年10月7日周五 23:31写道： > > > +1 > > > > Thanks, > > Baodi Shi > > > > > 在 2022年10月7日，22:00，Max Xu 写道： > > > > > > +1 > > > Thanks, Matteo. It's a great work! > > > > > > Best, > > >

Re: [DISCUSS] Planning for Apache Pulsar 3.0

I actually disagree with the term "Pulsar Next Gen", because I haven't seen any proposal for which that would make sense to me to be called so. Rajan: That's the whole point of breaking it down. If you accumulate many "big" changes it introduces a lot of risk for instabilities and incompatibilitie

Re: [DISCUSS] Planning for Apache Pulsar 3.0

Hi, Can we get the list of changes at one place which we are planning to get as part of 3.0. One thing I would like to see as a part of a major release, it CAN NOT impact existing usecases and users in any way which can force them to upgrade the client library. Applications using < 3.0 version sho

Re: [DISCUSS] Planning for Apache Pulsar 3.0

Thank you, Matteo. I agree that features should be delivered continuously when that is possible. In this case, that might not apply. I also agree that calling this Pulsar 3.0 isn't necessarily aligned with PIP-175 since an LTS release is when the major version is bumped. I'm fine in calling th

Re: [DISCUSS] Planning for Apache Pulsar 3.0

Given the past experiences and the discussions that already happened around "PIP-175: Extend time based release process", the idea is to detach the 3.0 from "big-features" items or "incompatible changes". The changes are going to get included as they are ready, within feature releases, and in a fu

[DISCUSS] Planning for Apache Pulsar 3.0

Hi all, Greeting from ApacheCon North America 2022 from New Orleans! We had a great conference with a dedicated Pulsar track. Thanks to all presenters and everyone who attended. The talks weren't recorded, but the slides will be later on posted on the conference website [1]. At ApacheCon ther

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

+1 cool! Best, tison. Baodi Shi 于2022年10月7日周五 23:31写道： > +1 > > Thanks, > Baodi Shi > > > 在 2022年10月7日，22:00，Max Xu 写道： > > > > +1 > > Thanks, Matteo. It's a great work! > > > > Best, > > Max Xu > > > > > >> On Fri, Oct 7, 2022 at 2:07 AM Matteo Merli wrote: > >> > >> We have moved the C++

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

+1 Thanks, Baodi Shi > 在 2022年10月7日，22:00，Max Xu 写道： > > +1 > Thanks, Matteo. It's a great work! > > Best, > Max Xu > > >> On Fri, Oct 7, 2022 at 2:07 AM Matteo Merli wrote: >> >> We have moved the C++ client to its own separate repo >> (https://github.com/apache/pulsar-client-cpp) as par

[GitHub] [pulsar-helm-chart] tisonkun commented on issue #290: Release Pulsar Helm Chart in GitHub Pages flavor

tisonkun commented on issue #290: URL: https://github.com/apache/pulsar-helm-chart/issues/290#issuecomment-1271745474 Thanks for your feedback @michaeljmarshall @ericsyh @yaalsn. Sorry for the late reply. Although any Apache TLP needs not to follow approaches adopted by other projec

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

+1 Thanks, Matteo. It's a great work! Best, Max Xu On Fri, Oct 7, 2022 at 2:07 AM Matteo Merli wrote: > We have moved the C++ client to its own separate repo > (https://github.com/apache/pulsar-client-cpp) as part of PIP-209. > > There are several new features and fixes in the main branch that

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

+1 Thanks, Kai On Oct 7, 2022, 2:07 AM +0800, Matteo Merli , wrote: > We have moved the C++ client to its own separate repo > (https://github.com/apache/pulsar-client-cpp) as part of PIP-209. > > There are several new features and fixes in the main branch that it > would be good to get released, a

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

+1 Thanks, Yunze > On Oct 7, 2022, at 02:07, Matteo Merli wrote: > > We have moved the C++ client to its own separate repo > (https://github.com/apache/pulsar-client-cpp) as part of PIP-209. > > There are several new features and fixes in the main branch that it > would be good to get relea

Re:[VOTE] Pulsar Release 2.10.2 Candidate 2

+1, non-binding Checked; - Checksum - Run standalone from apache-pulsar-2.10.2-bin.tar.gz and produce-consume from client-go - Run standalone from container image of jason918/pulsar:2.10.2 and produce-consume from client-go Best Regards, Lan Liang Replied Message | From | Hai

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

+1. Zixuan Enrico Olivelli 于2022年10月7日周五 03:55写道： > Sure! > > > Enrico > > Il Gio 6 Ott 2022, 20:07 Matteo Merli ha scritto: > > > We have moved the C++ client to its own separate repo > > (https://github.com/apache/pulsar-client-cpp) as part of PIP-209. > > > > There are several new features