Re: [VOTE] Pulsar Release 2.10.2 Candidate 2
Hi Xiaoyu, > The fixed PR is here: > https://github.com/apache/pulsar/pull/17948 > > This should be a release blocker I think. Great catch, Thank you! The publish throughput is down by almost half with default setup, this is definitely a release blocker. Thanks, Haiting On Sat, Oct 8, 2022 at 12:58 PM houxiaoyu wrote: > > 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 于2022年10月6日周四 10:46写道： > > > This is the second release candidate for Apache Pulsar, version 2.10.2. > > > > This release contains 249 commits by 57 contributors. > > https://github.com/apache/pulsar/compare/v2.10.1...v2.10.2-candidate-2 > > > > CI for this release candidate > > https://github.com/Jason918/pulsar/pull/10 > > > > *** Please download, test and vote on this release. This vote will stay > > open > > for at least 72 hours *** > > > > Note that we are voting upon the source (tag), binaries are provided for > > convenience. > > > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.2-candidate-2/ > > > > SHA-512 checksums: > > > > 26dc11e1514aa286d934e2f9698f4a04def6424307dcc452324bf935e88ba97c2d75b480a88a98640010c0117293d128e389c3e4fa98ab51cfc19e9312f5d00a > > ./apache-pulsar-2.10.2-bin.tar.gz > > > > 0eee2f47680966736acbdbdf309b0c7ccd4d10f737f49b6b8d9f5599a51d46568c1a0a18c75be6a44f78da60fe4287889d2e158fe530b20cee8b64411abe65f0 > > ./apache-pulsar-2.10.2-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1186/ > > > > The tag to be voted upon: > > v2.10.2-candidate-2 (850c9448a5ac32e2f94988b8bf80955c93ef9d6c) > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-2 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > Docker images: > > > > https://hub.docker.com/layers/jason918/pulsar/2.10.2/images/sha256-1ef93f17102e8193fc625fd5572f431d45935f7e2f11add3725a301c4321cef4 > > > > https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-6e6b49687b7debdf26feb71fedaa622de425885de5e2e7498dc476867cab85bc > > > > Please download the source package, and follow the > > release-candidate-validation doc to build > > and run the Pulsar standalone service. > > > > https://github.com/apache/pulsar/blob/master/wiki/release/release-candidate-validation.md > > > > Thanks, > > Haiting > >
Re: [DISCUSS] Release Pulsar Client C++ 3.0.0
+1 This is GREAT for simplifying the release process. Thanks, Haiting On Sat, Oct 8, 2022 at 10:44 AM Dave Fisher wrote: > > 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, 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, as well to get the new release process > > all flushed out. > > > > Matteo > > > > > > -- > > Matteo Merli > > >
Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2
+1 (non-binding) - Verify sha-512 checksum - Build from the source - Run tests - Run producer and consumer Best, Rui Fu 在 2022年10月8日 +0800 11:50，Qiang Huang ，写道： > +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) > > > - 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 > > > > > > > > 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 > > > wrote: > > > > > > > > > > > +1(non-binding) > > > > > > - Check sha 512 value for source code > > > > > > - Check go build producer example > > > > > > > > > > > > Thanks, > > > > > > Guangning > > > > > > > > > > > > r...@apache.org 于2022年9月29日周四 14:35写道： > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > Please review and vote on the release candidate #2 for the > > version > > > 0.9.0, > > > > > > > as follows: > > > > > > > [ ] +1, Approve the release > > > > > > > [ ] -1, Do not approve the release (please provide specific > > > comments) > > > > > > > > > > > > > > This is the second release candidate for Apache Pulsar Go client, > > > > > > > version 0.9.0. > > > > > > > > > > > > > > It fixes the following issues: > > > > > > > https://github.com/apache/pulsar-client-go/milestone/10?closed=1 > > > > > > > > > > > > > > Pulsar Client Go's KEYS file contains PGP keys we used to sign > > this > > > > > > > release: > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > > > > > > > > > Please download these packages and review this release candidate: > > > > > > > - Review release notes > > > > > > https://github.com/apache/pulsar-client-go/pull/804 > > > > > > > - Download the source package (verify shasum, and asc) and follow > > > the > > > > > > > README.md to build and run the pulsar-client-go. > > > > > > > > > > > > > > The vote will be open for at least 72 hours. It is adopted by > > > majority > > > > > > > approval, with at least 3 PMC affirmative votes. > > > > > > > > > > > > > > Source file: > > > > > > > > > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.9.0-candidate-2/ > > > > > > > > > > > > > > The tag to be voted upon: > > > > > > > v0.9.0 > > > > > > > > > > > > > > > > > > https://github.com/apache/pulsar-client-go/releases/tag/v0.9.0-candidate-2 > > > > > > > > > > > > > > SHA-512 checksums: > > > > > > > > > > > > > > > > > > > > > > > > > 9731d6a0615288e77feb4b73fedbbdf6d275ebefeee3cee5fc4e849f38789863f0532c7e8b93eb1e601bd98f9bb21d50a714fcf87fac9987a745a052bbe23ca3 > > > > > > > apache-pulsar-client-go-0.9.0-candidate-2-src.tar.gz > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > > Xiaolong Ran > > > > > > > > > > > > > > > > > > > > > -- > BR, > Qiang Huang
Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2
+1 (non-binding) - Verified the sha-512 checksum - Build from the source code - Run producer and consumer Best, Max Xu On Thu, Sep 29, 2022 at 2:35 PM r...@apache.org wrote: > Hi everyone, > > Please review and vote on the release candidate #2 for the version 0.9.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This is the second release candidate for Apache Pulsar Go client, > version 0.9.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-go/milestone/10?closed=1 > > Pulsar Client Go's KEYS file contains PGP keys we used to sign this > release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download these packages and review this release candidate: > - Review release notes https://github.com/apache/pulsar-client-go/pull/804 > - Download the source package (verify shasum, and asc) and follow the > README.md to build and run the pulsar-client-go. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Source file: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.9.0-candidate-2/ > > The tag to be voted upon: > v0.9.0 > https://github.com/apache/pulsar-client-go/releases/tag/v0.9.0-candidate-2 > > SHA-512 checksums: > > 9731d6a0615288e77feb4b73fedbbdf6d275ebefeee3cee5fc4e849f38789863f0532c7e8b93eb1e601bd98f9bb21d50a714fcf87fac9987a745a052bbe23ca3 > apache-pulsar-client-go-0.9.0-candidate-2-src.tar.gz > > Best, > > Xiaolong Ran >
Re: [DISCUSS] Planning for Apache Pulsar 3.0
This sounds like the current state of Apache Pulsar has a lot of issues and it requires fundamental design changes to make it promising which is definitely not true and I disagree with it. And I would be careful comparing with Kafka as I still don't think the Kafka release has anything to do with Pulsar's improvement. I would still recommend to list down all the changes at one place so we can bring everyone on the same page. discuss as a community and we make sure existing usecases continue using Pulsar and not try to find Pulsar alternatives with incorrect disruption impression and efforts they might have to put to upgrade or maintain pulsar. Thanks, Rajan On Fri, Oct 7, 2022 at 7:49 PM Lari Hotari wrote: > 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 able to learn and improve Pulsar so that we stay ahead of > competition. Pulsar was long ways ahead of competition for so many years, > but Kafka is finally catching up. Did Kafka surpass Pulsar in some aspects > with the recent 3.3 release, where Kraft became GA? That's a question that > many might be asking. Why wouldn't we rev up Pulsar's engine and show the > tail lights to Kafka? > > We don't have to have deadlines or any restrictions like that right now. > The sky's the limit. > Linus Torvalds has written a book called "Just for fun". I got my copy of > this book signed by Linus himself in year 2000 at an event that the book > publisher had organized in Finland. > > What if we did this "just for fun"? The intention could also be to beat > Kafka, but that could be a boring goal for many. What if we could unleash > some talent that is among us and hasn't had a chance to show its full > potential? Opensource is about joy. It is about welcoming everyone to join. > Opensource should be egoless, although we must all admit that we don't > succeed in that aspect. We must fight our biases. > > Jarek Potiuk explains the importance of being welcoming for success at > Apache, in a 3-minute YouTube interview: > https://www.youtube.com/watch?v=Dx5kQnVFo7E > This interview is about Jarek's blog post "Success at Apache: Welcoming > communities strengthens the Apache way": > > https://news.apache.org/foundation/entry/success-at-apache-welcoming-communities > I was pleased to meet Jarek at ApacheCon among so many other welcoming > personalities of the Apache community and the Apache Pulsar community. > > Goals have to be ambitious. What if we set the bar really high? > Apache Pulsar with 10 million topics in a cluster? > Why not go up to 100 million topics? > Just for fun. :) > > -Lari > > On 2022/10/07 22:53:59 Matteo Merli wrote: > > 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 > > incompatibilities. Breaking it down in multiple steps helps to see the > > incremental changes and introduced them in a phased manner. > > > > > > -- > > Matteo Merli > > > > > > On Fri, Oct 7, 2022 at 3:37 PM Rajan Dhabalia > wrote: > > > > > > 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 should > > > continue getting all the client and server side enhancements and bug > fixes. > > > Failing to provide bug-fixes and features to client < 3.0 means we are > > > forcing them to upgrade client version by putting efforts to handle all > > > incompatibility. and that's something we should definitely prevent > because > > > Apache Pulsar is used by many large scale business usecases and we > should > > > accommodate and motivate them to continue using Apache Pulsar. > > > I understand as a Pulsar community we should always try to progress and > > > build better but not at the cost of losing or reducing the Apache > Pulsar > > > community. > > > > > > Thanks, > > > Rajan > > > > > > > > > On Fri, Oct 7, 2022 at 12:41 PM Lari Hotari > wrote: > > > > > > > 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 this "Pulsar Next Gen" or something that calls out that > this is > > > > planning for making a major leap in Pulsa
Re: [DISCUSS] Planning for Apache Pulsar 3.0
I'm noticing some pushback on the idea of pre-emptively proposing any kind of breaking upgrade that would necessitate cutting a 3.0 release. I do understand the concern about introducing a breaking change... For a distributed messaging application like Pulsar, if clients needed to be simultaneously upgraded with brokers, that could be extremely difficult or infeasible for companies to coordinate without treating it like a migration to a new technology. At the same time, do we want to be completely closed to the possibility that a breaking change could be required at some point in the future? If a circumstance like that appears, those are the kinds of situations that can lead to a fork. Are there certain kinds of breaking changes that are more acceptable than others? Also, if the forward looking plan is to never introduce breaking changes, when *would* we ever cut a Pulsar 3.x release? Do we have any criteria on what kinds of changes would necessitate cutting a new major release but would still be considered acceptable by the community? -- Devin Bost Sent from mobile Cell: 801-400-4602 On Sat, Oct 8, 2022, 2:14 PM Rajan Dhabalia wrote: > This sounds like the current state of Apache Pulsar has a lot of issues and > it requires fundamental design changes to make it promising which is > definitely not true and I disagree with it. And I would be careful > comparing with Kafka as I still don't think the Kafka release has anything > to do with Pulsar's improvement. I would still recommend to list down all > the changes at one place so we can bring everyone on the same page. discuss > as a community and we make sure existing usecases continue using Pulsar and > not try to find Pulsar alternatives with incorrect disruption impression > and efforts they might have to put to upgrade or maintain pulsar. > > Thanks, > Rajan > > On Fri, Oct 7, 2022 at 7:49 PM Lari Hotari wrote: > > > 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 able to learn and improve Pulsar so that we stay ahead > of > > competition. Pulsar was long ways ahead of competition for so many years, > > but Kafka is finally catching up. Did Kafka surpass Pulsar in some > aspects > > with the recent 3.3 release, where Kraft became GA? That's a question > that > > many might be asking. Why wouldn't we rev up Pulsar's engine and show the > > tail lights to Kafka? > > > > We don't have to have deadlines or any restrictions like that right now. > > The sky's the limit. > > Linus Torvalds has written a book called "Just for fun". I got my copy of > > this book signed by Linus himself in year 2000 at an event that the book > > publisher had organized in Finland. > > > > What if we did this "just for fun"? The intention could also be to beat > > Kafka, but that could be a boring goal for many. What if we could unleash > > some talent that is among us and hasn't had a chance to show its full > > potential? Opensource is about joy. It is about welcoming everyone to > join. > > Opensource should be egoless, although we must all admit that we don't > > succeed in that aspect. We must fight our biases. > > > > Jarek Potiuk explains the importance of being welcoming for success at > > Apache, in a 3-minute YouTube interview: > > https://www.youtube.com/watch?v=Dx5kQnVFo7E > > This interview is about Jarek's blog post "Success at Apache: Welcoming > > communities strengthens the Apache way": > > > > > https://news.apache.org/foundation/entry/success-at-apache-welcoming-communities > > I was pleased to meet Jarek at ApacheCon among so many other welcoming > > personalities of the Apache community and the Apache Pulsar community. > > > > Goals have to be ambitious. What if we set the bar really high? > > Apache Pulsar with 10 million topics in a cluster? > > Why not go up to 100 million topics? > > Just for fun. :) > > > > -Lari > > > > On 2022/10/07 22:53:59 Matteo Merli wrote: > > > 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 > > > incompatibilities. Breaking it down in multiple steps helps to see the > > > incremental changes and introduced them in a phased manner. > > > > > > > > > -- > > > Matteo Merli > > > > > > > > > On Fri, Oct 7, 2022 at 3:37 PM Rajan Dhabalia > > wrote: > > > > > > > > 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 user
Re: [DISCUSS] Planning for Apache Pulsar 3.0
I would say first we should gather a list of changes which we want to target and find out which improvements really need major version release. We can take the Pulsar-1.0 to Pulsar-2.0 upgrade example to avoid major interruption and impact on existing systems and still achieve our goal. So, the first step is discovery of such features and then we can discuss how to introduce them in Pulsar with minimum impact on existing systems. Thanks, Rajan On Sat, Oct 8, 2022 at 1:05 PM Devin Bost wrote: > I'm noticing some pushback on the idea of pre-emptively proposing any kind > of breaking upgrade that would necessitate cutting a 3.0 release. > I do understand the concern about introducing a breaking change... For a > distributed messaging application like Pulsar, if clients needed to be > simultaneously upgraded with brokers, that could be extremely difficult or > infeasible for companies to coordinate without treating it like a migration > to a new technology. > > At the same time, do we want to be completely closed to the possibility > that a breaking change could be required at some point in the future? If a > circumstance like that appears, those are the kinds of situations that can > lead to a fork. Are there certain kinds of breaking changes that are more > acceptable than others? > > Also, if the forward looking plan is to never introduce breaking changes, > when *would* we ever cut a Pulsar 3.x release? Do we have any criteria on > what kinds of changes would necessitate cutting a new major release but > would still be considered acceptable by the community? > > -- > Devin Bost > Sent from mobile > Cell: 801-400-4602 > > On Sat, Oct 8, 2022, 2:14 PM Rajan Dhabalia wrote: > > > This sounds like the current state of Apache Pulsar has a lot of issues > and > > it requires fundamental design changes to make it promising which is > > definitely not true and I disagree with it. And I would be careful > > comparing with Kafka as I still don't think the Kafka release has > anything > > to do with Pulsar's improvement. I would still recommend to list down all > > the changes at one place so we can bring everyone on the same page. > discuss > > as a community and we make sure existing usecases continue using Pulsar > and > > not try to find Pulsar alternatives with incorrect disruption impression > > and efforts they might have to put to upgrade or maintain pulsar. > > > > Thanks, > > Rajan > > > > On Fri, Oct 7, 2022 at 7:49 PM Lari Hotari wrote: > > > > > 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 able to learn and improve Pulsar so that we stay ahead > > of > > > competition. Pulsar was long ways ahead of competition for so many > years, > > > but Kafka is finally catching up. Did Kafka surpass Pulsar in some > > aspects > > > with the recent 3.3 release, where Kraft became GA? That's a question > > that > > > many might be asking. Why wouldn't we rev up Pulsar's engine and show > the > > > tail lights to Kafka? > > > > > > We don't have to have deadlines or any restrictions like that right > now. > > > The sky's the limit. > > > Linus Torvalds has written a book called "Just for fun". I got my copy > of > > > this book signed by Linus himself in year 2000 at an event that the > book > > > publisher had organized in Finland. > > > > > > What if we did this "just for fun"? The intention could also be to beat > > > Kafka, but that could be a boring goal for many. What if we could > unleash > > > some talent that is among us and hasn't had a chance to show its full > > > potential? Opensource is about joy. It is about welcoming everyone to > > join. > > > Opensource should be egoless, although we must all admit that we don't > > > succeed in that aspect. We must fight our biases. > > > > > > Jarek Potiuk explains the importance of being welcoming for success at > > > Apache, in a 3-minute YouTube interview: > > > https://www.youtube.com/watch?v=Dx5kQnVFo7E > > > This interview is about Jarek's blog post "Success at Apache: Welcoming > > > communities strengthens the Apache way": > > > > > > > > > https://news.apache.org/foundation/entry/success-at-apache-welcoming-communities > > > I was pleased to meet Jarek at ApacheCon among so many other welcoming > > > personalities of the Apache community and the Apache Pulsar community. > > > > > > Goals have to be ambitious. What if we set the bar really high? > > > Apache Pulsar with 10 million topics in a cluster? > > > Why not go up to 100 million topics? > > > Just for fun. :) > > > > > > -Lari > > > > > > On 2022/10/07 22:53:59 Matteo Merli wrote: > > > > I actually disagree with the term "Pulsar Next Gen", because I > haven't > > > > seen any proposal for which that would mak
Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2
The vote is now closed and the release was approved with 8 +1s(3 bindings and 6 non-binding); Binding votes: * Penghui Li * Hang Chen * Jiwei Guo Non-Binding votes: * Xiaolong Ran * Guangning E * Zike Yang * Qiang Huang * Rui Fu * Max Xu Thank you all guys for voting! Max Xu 于2022年10月8日周六 16:38写道： > +1 (non-binding) > > - Verified the sha-512 checksum > - Build from the source code > - Run producer and consumer > > Best, > Max Xu > > > On Thu, Sep 29, 2022 at 2:35 PM r...@apache.org > wrote: > > > Hi everyone, > > > > Please review and vote on the release candidate #2 for the version 0.9.0, > > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > This is the second release candidate for Apache Pulsar Go client, > > version 0.9.0. > > > > It fixes the following issues: > > https://github.com/apache/pulsar-client-go/milestone/10?closed=1 > > > > Pulsar Client Go's KEYS file contains PGP keys we used to sign this > > release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > Please download these packages and review this release candidate: > > - Review release notes > https://github.com/apache/pulsar-client-go/pull/804 > > - Download the source package (verify shasum, and asc) and follow the > > README.md to build and run the pulsar-client-go. > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > Source file: > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.9.0-candidate-2/ > > > > The tag to be voted upon: > > v0.9.0 > > > https://github.com/apache/pulsar-client-go/releases/tag/v0.9.0-candidate-2 > > > > SHA-512 checksums: > > > > > 9731d6a0615288e77feb4b73fedbbdf6d275ebefeee3cee5fc4e849f38789863f0532c7e8b93eb1e601bd98f9bb21d50a714fcf87fac9987a745a052bbe23ca3 > > apache-pulsar-client-go-0.9.0-candidate-2-src.tar.gz > > > > Best, > > > > Xiaolong Ran > > >
[ANNOUNCE] Apache Pulsar Go Client v0.9.0 released
The Apache Pulsar team is proud to announce Apache Pulsar Go Client version v0.9.0. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: https://github.com/apache/pulsar-client-go/releases/tag/v0.9.0 Release Notes are at: https://github.com/apache/pulsar-client-go/blob/master/CHANGELOG.md We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
Re: [DISCUSS] Add an auth data const for refresh the original auth data
See https://github.com/apache/pulsar/issues/17517. Asaf Mesika 于2022年10月3日周一 19:47写道： > I kind of lost you here Zixuan. > > Is there any chance you describe the authentication flow including the > commands? Then specify the change you wish to make? > > > On Thu, Aug 18, 2022 at 5:21 AM Zixuan Liu wrote: > > > A little confusing here is that both ProxyClient and DirectProxyHandler > > pass original authentication and direct authentication data, but the > broker > > can only check if the original authentication data is expired. > > This is the expected behavior, right? What if the direct authentication > > data is expired? > > > > Proxy connect method: > > > > > https://github.com/apache/pulsar/blob/master/pulsar-proxy/src/main/java/org/apache/pulsar/proxy/server/DirectProxyHandler.java#L327 > > > > > https://github.com/apache/pulsar/blob/master/pulsar-proxy/src/main/java/org/apache/pulsar/proxy/server/ProxyClientCnx.java#L57 > > > > Broker refresh method: > > > > > https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/ServerCnx.java#L723 > > > > Thanks, > > Zixuan > > > > Zixuan Liu 于2022年8月18日周四 10:11写道： > > > > > > So the problem is that the Proxy is not requesting a refresh ? > > > > > > It should be the proxy client. > > > > > > Zixuan > > > > > > Enrico Olivelli 于2022年8月17日周三 23:35写道： > > > > > >> So the problem is that the Proxy is not requesting a refresh ? > > >> > > >> Enrico > > >> > > >> Il giorno mer 17 ago 2022 alle ore 16:26 Zixuan Liu > > >> ha scritto: > > >> > > > >> > Thank @Qiang! > > >> > > > >> > Update the diagram: > > >> > > > >> > > > https://drive.google.com/file/d/1E6z0dzXzvW5ZxG6d6YUghL9OikA8j4UC/view?usp=sharing > > >> > > > >> > Thanks, > > >> > Zixuan > > >> > > > >> > Qiang Huang 于2022年8月17日周三 19:13写道： > > >> > > > >> > > It makes sense to me. BTW, the image is broken. > > >> > > > > >> > > Zixuan Liu 于2022年8月17日周三 11:10写道： > > >> > > > > >> > > > Note that there are two clients, the user client, and the proxy > > >> client. > > >> > > > When the original authenticate data expires, the user client > > cannot > > >> send > > >> > > a > > >> > > > request to the proxy to find the broker URL. We haven't tests to > > >> cover > > >> > > this. > > >> > > > > > >> > > > A simple diagram represents workflow: > > >> > > > [image: image.png] > > >> > > > Both connections pass the proxy client and the user client > > >> authentication > > >> > > > data. > > >> > > > > > >> > > > Thanks, > > >> > > > Zixuan > > >> > > > > > >> > > > Zixuan Liu 于2022年8月16日周二 23:02写道： > > >> > > > > > >> > > >> Hi all, > > >> > > >> > > >> > > >> Refreshing the authentication data comes from the client is > > >> important. > > >> > > We > > >> > > >> have two types of authentication data, directly authentication > > >> data, and > > >> > > >> original authentication data: > > >> > > >> > > >> > > >> 1. Directly authentication data > > >> > > >> The client/proxy brings the authentication data directly > > connected > > >> to > > >> > > the > > >> > > >> broker, which is directly authentication data. > > >> > > >> > > >> > > >> When the directly authentication data is expired, the broker > > sends > > >> the > > >> > > >> `newAuthChallenge` command with `AuthData.REFRESH_AUTH_DATA` > data > > >> to the > > >> > > >> client to refresh the authentication data. > > >> > > >> > > >> > > >> 2. Original authentication data > > >> > > >> We add a proxy between the client and the broker, both the > proxy > > >> and the > > >> > > >> client bring the authentication data to request the broker, the > > >> > > >> authentication data from the proxy is directly authentication > > >> data, and > > >> > > the > > >> > > >> authentication data from the client is original authentication > > >> data. > > >> > > >> > > >> > > >> The broker can refresh the directly authentication data, but > when > > >> we are > > >> > > >> using the proxy, the broker could not refresh the original > > >> > > >> authentication data, because we haven't any action to request > to > > >> refresh > > >> > > >> the original authentication data, so we need to add an auth > data > > >> const > > >> > > to > > >> > > >> request to refresh the original authentication data, so like > > >> > > >> `AuthData.REFRESH_AUTH_DATA`. > > >> > > >> > > >> > > >> Once most people agree with this, I'll make a PIP. > > >> > > >> > > >> > > >> References: > > >> > > >> > > >> > > >> - https://github.com/apache/pulsar/pull/13339 > > >> > > >> - https://github.com/apache/pulsar/issues/10816 > > >> > > >> > > >> > > >> Thanks, > > >> > > >> Zixuan > > >> > > >> > > >> > > >> > > >> > > > > >> > > -- > > >> > > BR, > > >> > > Qiang Huang > > >> > > > > >> > > > > > >
[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-1272455470 I'm going to submit a pull request to this repo. And it still needs a committer to help create the `gh-pages` branch (identical to master is OK for initialization). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] tisonkun opened a new pull request, #292: replace handmade release script with official action
tisonkun opened a new pull request, #292: URL: https://github.com/apache/pulsar-helm-chart/pull/292 This refers to #290. The `helm/chart-releaser-action` update `index.yaml` in an incremental manner, so we need to push the existing `index.yaml` file to `gh-pages` later. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] tisonkun commented on a diff in pull request #292: replace handmade release script with official action
tisonkun commented on code in PR #292:
URL: https://github.com/apache/pulsar-helm-chart/pull/292#discussion_r990735145
##
.github/workflows/release.yml:
##
@@ -17,39 +17,36 @@
# under the License.
#
-name: Post commit - Publish Pulsar Helm Chart
+name: Release Pulsar Helm Charts
on:
+ workflow_dispatch:
push:
branches:
- - master
+ - master
+
jobs:
release:
runs-on: ubuntu-latest
timeout-minutes: 45
+permissions:
+ contents: write
steps:
- - name: checkout
-uses: actions/checkout@v2
+ - name: Checkout
+uses: actions/checkout@v3
with:
- token: ${{ secrets.PULSARBOT_TOKEN }}
fetch-depth: 0
- - name: Tune Runner VM
-uses: ./.github/actions/tune-runner-vm
+ - name: Configure Git
+run: |
+ git config user.name "$GITHUB_ACTOR"
+ git config user.email "$github_ac...@users.noreply.github.com"
- - name: Detect changed files
-id: changes
-uses: apache/pulsar-test-infra/paths-filter@master
+ - name: Install Helm
+uses: azure/setup-helm@v1
Review Comment:
This action is too complex to bundle. An INFRA ticket already adds this
action to the whitelist: https://issues.apache.org/jira/browse/INFRA-23716
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [pulsar-helm-chart] tisonkun commented on a diff in pull request #292: replace handmade release script with official action
tisonkun commented on code in PR #292:
URL: https://github.com/apache/pulsar-helm-chart/pull/292#discussion_r990736904
##
.github/workflows/lint.yml:
##
@@ -43,9 +42,22 @@ jobs:
id: check_changes
run: echo "::set-output name=docs_only::${{
fromJSON(steps.changes.outputs.all_count) ==
fromJSON(steps.changes.outputs.docs_count) &&
fromJSON(steps.changes.outputs.docs_count) > 0 }}"
- - name: Lint chart
+ - name: Set up Helm
+if: ${{ steps.check_changes.outputs.docs_only != 'true' }}
+uses: azure/setup-helm@v3
+with:
+ version: v3.10.0
+
+ - name: Set up Python
if: ${{ steps.check_changes.outputs.docs_only != 'true' }}
-id: lint
-uses: helm/chart-testing-action@v2.0.0
Review Comment:
This action is never allowed by INFRA settings and thus we always failed
before. Fix on the fly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [pulsar-helm-chart] tisonkun commented on pull request #292: replace handmade release script with official action
tisonkun commented on PR #292: URL: https://github.com/apache/pulsar-helm-chart/pull/292#issuecomment-1272464800 cc @michaeljmarshall @ericsyh @mattisonchao @yaalsn -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
