Re: [VOTE] Pulsar Client Go Release 0.13.0 Candidate 2
+1(binding) - verified the shasum and asc. - `make build` and `make test` fine on go1.20.13 Thanks, Baodi Shi Zixuan Liu 于2024年7月16日周二 15:41写道： > > +1 (non-binding) > > - Verified the shasum and asc. > - `make build` works fine on go1.22.5 > > Thanks, > Zixuan > > > Zike Yang 于2024年7月15日周一 19:14写道： > > > Hi everyone, > > Please review and vote on the release candidate #2 for the version > > 0.13.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.13.0. > > > > It fixes the following issues: > > https://github.com/apache/pulsar-client-go/milestone/15?closed=1 > > > > Pulsar Client Go's KEYS file contains PGP keys we used to sign this > > release: > > https://downloads.apache.org/pulsar/KEYS > > > > Please download these packages and review this release candidate: > > - Review release notes: > > https://github.com/apache/pulsar-client-go/pull/1245 > > - 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.13.0-candidate-2/ > > > > The tag to be voted upon: > > v0.13.0-candidate-2 > > https://github.com/apache/pulsar-client-go/tree/v0.13.0-candidate-2 > > > > SHA-512 checksums: > > > > 9a52fb25cbb6d86651a0d56c1d6e17826810b91f3ba6299f632630f5b5a1d85c6a0842e36aaa2da6fc50d4e9406fe6d7b557368f9d99d876345c987f51d554fb > > apache-pulsar-client-go-0.13.0-src.tar.gz > >
[ANNOUNCE] Apache Pulsar Node.js client 1.11.1 released
The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.11.1. 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 Node.js client release details and downloads, visit: https://www.npmjs.com/package/pulsar-client Release Notes are at: https://github.com/apache/pulsar-client-node/releases We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
Re: [VOTE] Pulsar Node.js Client Release 1.11.1 Candidate 2
Closed this vote with 3 binding +1 - yunze - baodi - zike Thanks, Baodi Shi Zike Yang 于2024年7月8日周一 11:51写道： > > +1 (binding) > > - Verified checksum and signature > - Built from source on macOS arm64 and run the example > - Installed from the npm registry using Node 16,18,20 on Ubuntu 22.04 > amd64 and macOS arm64 > - Ran the end-to-end example successfully > > Thanks, > Zike Yang > > On Mon, Jul 8, 2024 at 9:19 AM Baodi Shi wrote: > > > > +1(binding) > > > > - Verified checksum and signatures > > - Built from source and ran examples on macOS with Node.js v20.4.0 > > - Verify batch_receive API on ubuntu 22.04 > > > > Thanks, > > Baodi Shi > > > > Yunze Xu 于2024年7月5日周五 15:43写道： > > > > > > +1 (binding) > > > > > > - Verified checksum and signatures > > > - Built from source and ran examples on macOS with Node.js v20.4.0 > > > - Install the npm and ran examples on Rocky Linux 8 with Node.js v16.6.0 > > > > > > Thanks, > > > Yunze > > > > > > On Wed, Jul 3, 2024 at 10:01 AM Baodi Shi wrote: > > > > > > > > Hi everyone, > > > > > > > > This is the second release candidate for Apache Pulsar Node.js client, > > > > version 1.11.1. > > > > (Candidate 1 build failed, so skip voting for it.) > > > > > > > > It fixes the following issues: > > > > - > > > > https://github.com/apache/pulsar-client-node/compare/v1.11.0...v1.11.1-rc.2 > > > > > > > > Please download the source files and review this release candidate: > > > > - Download the source package, verify shasum and asc > > > > - Follow the README.md to build and run the Pulsar Node.js client. > > > > > > > > The release candidate package has been published to the npm registry: > > > > https://www.npmjs.com/package/pulsar-client/v/1.11.1-rc.2 > > > > > > > > You can install it and verify the package: > > > > "npm i pulsar-client@1.11.1-rc.2 > > > > --pulsar_binary_host_mirror=https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/; > > > > > > > > > > > > The vote will be open for at least 72 hours. It is adopted by majority > > > > approval, with at least 3 PMC affirmative votes. > > > > > > > > Source files: > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.1-rc.2/ > > > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > > https://downloads.apache.org/pulsar/KEYS > > > > > > > > SHA-512 checksum: > > > > 2c6a73502cb96e7e9bae958dac14ec98eed9131e3ec9796c07e4095f269f6c33df0fef32aa2bea810f321a708e5184c7526e6bbf803a2f954823ad55612623d2 > > > > ./apache-pulsar-client-node-1.11.1.tar.gz > > > > > > > > > > > > The tag to be voted upon: > > > > v1.11.1-rc.2 > > > > https://github.com/apache/pulsar-client-node/releases/tag/v1.11.1-rc.2 > > > > > > > > Please review and vote on the release candidate #1 for the version > > > > 1.11.1, as follows: > > > > [ ] +1, Approve the release > > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > > > Thanks, > > > > Baodi Shi
Re: [VOTE] Pulsar Node.js Client Release 1.11.1 Candidate 2
+1(binding) - Verified checksum and signatures - Built from source and ran examples on macOS with Node.js v20.4.0 - Verify batch_receive API on ubuntu 22.04 Thanks, Baodi Shi Yunze Xu 于2024年7月5日周五 15:43写道： > > +1 (binding) > > - Verified checksum and signatures > - Built from source and ran examples on macOS with Node.js v20.4.0 > - Install the npm and ran examples on Rocky Linux 8 with Node.js v16.6.0 > > Thanks, > Yunze > > On Wed, Jul 3, 2024 at 10:01 AM Baodi Shi wrote: > > > > Hi everyone, > > > > This is the second release candidate for Apache Pulsar Node.js client, > > version 1.11.1. > > (Candidate 1 build failed, so skip voting for it.) > > > > It fixes the following issues: > > - > > https://github.com/apache/pulsar-client-node/compare/v1.11.0...v1.11.1-rc.2 > > > > Please download the source files and review this release candidate: > > - Download the source package, verify shasum and asc > > - Follow the README.md to build and run the Pulsar Node.js client. > > > > The release candidate package has been published to the npm registry: > > https://www.npmjs.com/package/pulsar-client/v/1.11.1-rc.2 > > > > You can install it and verify the package: > > "npm i pulsar-client@1.11.1-rc.2 > > --pulsar_binary_host_mirror=https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/; > > > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > Source files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.1-rc.2/ > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://downloads.apache.org/pulsar/KEYS > > > > SHA-512 checksum: > > 2c6a73502cb96e7e9bae958dac14ec98eed9131e3ec9796c07e4095f269f6c33df0fef32aa2bea810f321a708e5184c7526e6bbf803a2f954823ad55612623d2 > > ./apache-pulsar-client-node-1.11.1.tar.gz > > > > > > The tag to be voted upon: > > v1.11.1-rc.2 > > https://github.com/apache/pulsar-client-node/releases/tag/v1.11.1-rc.2 > > > > Please review and vote on the release candidate #1 for the version > > 1.11.1, as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > Thanks, > > Baodi Shi
[VOTE] Pulsar Node.js Client Release 1.11.1 Candidate 2
Hi everyone, This is the second release candidate for Apache Pulsar Node.js client, version 1.11.1. (Candidate 1 build failed, so skip voting for it.) It fixes the following issues: - https://github.com/apache/pulsar-client-node/compare/v1.11.0...v1.11.1-rc.2 Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.11.1-rc.2 You can install it and verify the package: "npm i pulsar-client@1.11.1-rc.2 --pulsar_binary_host_mirror=https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/; The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.1-rc.2/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/pulsar/KEYS SHA-512 checksum: 2c6a73502cb96e7e9bae958dac14ec98eed9131e3ec9796c07e4095f269f6c33df0fef32aa2bea810f321a708e5184c7526e6bbf803a2f954823ad55612623d2 ./apache-pulsar-client-node-1.11.1.tar.gz The tag to be voted upon: v1.11.1-rc.2 https://github.com/apache/pulsar-client-node/releases/tag/v1.11.1-rc.2 Please review and vote on the release candidate #1 for the version 1.11.1, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
[DISCUSS] Release Pulsar Node.js client v1.11.1
Hi all, I would like to propose releasing the Pulsar Node.js client v1.11.1 It fixed a compatibility issue with glibc-like Linux systems. Refer to this PR: https://github.com/apache/pulsar-client-node/pull/389 Please let me know if you have any fix that need to be included in 1.11.1 Thanks, Baodi Shi
Re: [DISCUSS] Cherry-pick PIP-344 Correct the behavior of the public API pulsarClient.getPartitionsForTopic
+1 Thanks, Baodi Shi Yubiao Feng 于2024年6月17日周一 23:49写道： > > Hi all > > I would like to start a discussion to cherry-pick PIP-344 into `branch-3.0` > - https://github.com/apache/pulsar/pull/22206 > - https://github.com/apache/pulsar/pull/22773 > - https://github.com/apache/pulsar/pull/22838 > > This PIP fixed the wrong behavior for a public API, the wrong behavior may > cause unexpected partitioned topic creation when users call > "pulsarClient.getPartitionsForTopic". > > So I want to cherry-pick it into the long-term support version `3.0.x` > > The thread will keep open for 48 hours. If there is no objections, > I will perform the cherry-picking. > > Thanks > Yubiao Feng
Re: [DISCUSS] Report an error when seeking a multi-topics consumer that subscribes no topics
+1 Thanks, Baodi Shi On May 29, 2024 at 14:50:12, Yunze Xu wrote: > Hi community, > > Recently I found the behavior of seeking a multi-topics consumer is > intuitive. If there are no internal consumers, the `seek` call will > just succeed silently. > > If a consumer subscribes with a regex and no topics are found, users > might think the seek operation succeeds while no topics are sought. > > I suggest throwing an exception in this case to notify users that the > consumer to seek is a multi-topics consumer that contains no topics. > It's a breaking change so I'd like to hear more voices in the mail > list. > > For now, I report an error for the C++ client [1], which might also > affect the Python and Node.js clients. But the behavior of the Java > client does not change. > > [1] https://github.com/apache/pulsar-client-cpp/pull/426 > > Thanks, > Yunze >
Re: [VOTE] Release Apache Pulsar 3.3.0 based on 3.3.0-candidate-3
+1 (binding) - Build from the source code - Checked the signatures - Start the standalone - Run Node.js client unit test with image: czcoder/pulsar:3.3.0-0771f81 - https://github.com/shibd/pulsar-client-node/pull/38 Thanks, Baodi Shi On May 27, 2024 at 11:33:14, Cong Zhao wrote: > Thanks Yong, > > Yes, we can continue to release 3.3 and fix this issue in later versions. > > On 2024/05/27 03:10:18 Yong Zhang wrote: > > If the snappy in zookeeper is not used very commonly, this might not be a > > blocker for this release. > > > So I would be -0. > > > Thanks, > > Yong > > On Fri, 24 May 2024 at 15:17, Yong Zhang > wrote: > > > > -1 > > > > > > There is an issue with the snappy usage in the amd64-based image. > > > > > > It will get the error > > > > > > java.lang.UnsatisfiedLinkError: /tmp/ > > > snappy-1.1.10-b0757287-8557-44b9-9499-afca52f102ec-libsnappyjava.so: > > > Error relocating /lib/ld-linux-x86-64.so.2: unsupported relocation type > 37. > > > > > > Reproduce steps: > > > 1. docker run -it -u root --platform=linux/amd64 > > > czcoder/pulsar:3.3.0-0771f81 bash > > > 2. export > > > PULSAR_EXTRA_OPTS="-Dzookeeper.snapshot.compression.method=snappy" > > > 3. export PULSAR_STANDALONE_USE_ZOOKEEPER=true > > > 4. bin/pulsar standalone -nss -nfw > > > > > > Then you will get the error. More information: > > > https://github.com/sgerrand/alpine-pkg-glibc/issues/194 > > > > > > we need to resolve it before publishing the new release. > > > > > > Yong > > > > > > On Fri, 24 May 2024 at 13:00, guo jiwei wrote: > > > > > >> +1 (binding) > > >> > > >> - Built from source > > >> - Checked the signatures > > >> - Run standalone > > >> - Checked producer and consumer > > >> - Verified the Cassandra connector > > >> - Verified the Stateful function > > >> > > >> > > >> Regards > > >> Jiwei Guo (Tboy) > > >> > > >> > > >> On Fri, May 24, 2024 at 10:28 AM Cong Zhao wrote: > > >> > > >> > Hello Apache Pulsar Community, > > >> > > > >> > This is a call for the vote to release the Apache Pulsar version 3.3.0 > > >> > based on 3.3.0-candidate-3. > > >> > > > >> > Included changes since the previous release: > > >> > https://github.com/apache/pulsar/milestone/38?closed=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.3.0-candidate-3/ > > >> > > > >> > SHA-512 checksums: > > >> > > > >> > > > >> > 59fcf6e77ef47ea88696bc1a0f67dc09f0d3f2d791d23e09ff721678beb5512f58bbfb328bbb2980981243aff1aeda686c332b4d8c57dc0c4bffc0ec0a4dbb4d > > >> > > > >> > > > >> > b35fb4d9d20111f55b7d9c7016871daab0fe8edb2f09220e013fc51b2d828c482a05a7b19b3b1cd39bd2072162f77c3279722c9fdf3e876f22e90e2aea10c9e3 > > >> > > > >> > Maven staging repo: > > >> > > https://repository.apache.org/content/repositories/orgapachepulsar-1297 > > >> > > > >> > The tag to be voted upon: > > >> > v3.3.0-candidate-3 (commit 0771f818ba74f94b95cd0987997079d0f3e73f94) > > >> > https://github.com/apache/pulsar/releases/tag/v3.3.0-candidate-3 > > >> > > > >> > Pulsar's KEYS file containing PGP keys you use to sign the release: > > >> > https://downloads.apache.org/pulsar/KEYS > > >> > > > >> > Docker images: > > >> > docker pull czcoder/pulsar:3.3.0-0771f81 > > >> > > > >> > > > >> > https://hub.docker.com/layers/czcoder/pulsar/3.3.0-0771f81/images/sha256-e34f1e83bb2a1e8233a3429847bb8fc2cdac0f558a0e5c13658c28773287b07c?context=explore > > >> > docker pull czcoder/pulsar-all:3.3.0-0771f81 > > >> > > > >> > > > >> > https://hub.docker.com/layers/czcoder/pulsar-all/3.3.0-0771f81/images/sha256-49cf20acab7e71c8916cf594690c86eaaaf8426c8a13013a8c25944338d7be7c?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, > > >> > Cong Zhao > > >> > > > >> > > > > > >
Re: [VOTE] PIP-353: Improve transaction message visibility for peek-messages
Hi, all. >From this comment: https://github.com/apache/pulsar/pull/22762#discussion_r1615383124 I will use `---transaction-isolation-level` to instead of `--show-txn-uncommitted` and `--show-txn-aborted`. This way, we can maintain consistency with the interface behavior of the consume mentioned here in the PIP: https://github.com/apache/pulsar/pull/21114 If you have any concerns, please post a comment. Thanks, Baodi Shi On May 24, 2024 at 16:57:39, Baodi Shi wrote: > Close this vote passed by 3 +1 binding: > - zike > - yubiao > - jiwei > > > Thanks, > Baodi Shi > > > On May 24, 2024 at 16:41:07, guo jiwei wrote: > >> +1 (binding) >> >> >> Regards >> Jiwei Guo (Tboy) >> >> >> On Fri, May 24, 2024 at 8:29 AM Yubiao Feng >> wrote: >> >> +1 (binding) >> >> >> Thanks >> >> Yubiao Feng >> >> >> On Wed, May 22, 2024 at 9:55 PM Baodi Shi wrote: >> >> >> > Hi, all >> >> > >> >> > I would like to start the voting thread for PIP-353. >> >> > https://github.com/apache/pulsar/pull/22746 >> >> > >> >> > The implementation PR is: >> >> > https://github.com/apache/pulsar/pull/22762 >> >> > >> >> > Discuss thread: >> >> > https://lists.apache.org/thread/dc7f64jtvg987ydztxpffqx88bp44lwv >> >> > >> >> > Thanks, >> >> > Baodi Shi >> >> > >> >> >>
Re: [VOTE] PIP-353: Improve transaction message visibility for peek-messages
Close this vote passed by 3 +1 binding: - zike - yubiao - jiwei Thanks, Baodi Shi On May 24, 2024 at 16:41:07, guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Fri, May 24, 2024 at 8:29 AM Yubiao Feng > wrote: > > +1 (binding) > > > Thanks > > Yubiao Feng > > > On Wed, May 22, 2024 at 9:55 PM Baodi Shi wrote: > > > > Hi, all > > > > > > I would like to start the voting thread for PIP-353. > > > https://github.com/apache/pulsar/pull/22746 > > > > > > The implementation PR is: > > > https://github.com/apache/pulsar/pull/22762 > > > > > > Discuss thread: > > > https://lists.apache.org/thread/dc7f64jtvg987ydztxpffqx88bp44lwv > > > > > > Thanks, > > > Baodi Shi > > > > > >
[VOTE] PIP-353: Improve transaction message visibility for peek-messages
Hi, all I would like to start the voting thread for PIP-353. https://github.com/apache/pulsar/pull/22746 The implementation PR is: https://github.com/apache/pulsar/pull/22762 Discuss thread: https://lists.apache.org/thread/dc7f64jtvg987ydztxpffqx88bp44lwv Thanks, Baodi Shi
Re: [VOTE] Release Apache Pulsar 3.3.0 based on 3.3.0-candidate-2
+1 (binding) - Build from the source code - Checked the signatures - Start the standalone - Run Node.js client unit test with image: czcoder/pulsar:3.3.0-55ed823 - https://github.com/shibd/pulsar-client-node/actions/runs/9187138034/job/25264192973?pr=38 On 2024/05/20 04:25:10 Cong Zhao wrote: > Hello Apache Pulsar Community, > > This is a call for the vote to release the Apache Pulsar version 3.3.0 based > on 3.3.0-candidate-2. > > Included changes since the previous release: > https://github.com/apache/pulsar/milestone/38?closed=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.3.0-candidate-2/ > > SHA-512 checksums: > 88a0e66f164308613f0d6d0f5fe84e6b98a901dc3a8a5bf932b385f66548e5de6d39b2fe65bca5c661ca141e024450f0d85f9d7e2f8c2e21508fb95e7c09129a > a6b473d63b673ef9818ac62a6a98fa1ac9c11c084a4c713d7659a489dedb8a1126f3c9bd18b7250ea8943e51392d116c4bb398bf60cd52f7c871c67a00992d31 > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1296 > > The tag to be voted upon: > v3.3.0-candidate-2 (commit 55ed82346b804f24a0aa2185618bafa73f5a394b) > https://github.com/apache/pulsar/releases/tag/v3.3.0-candidate-2 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Docker images: > docker pull czcoder/pulsar:3.3.0-55ed823 > https://hub.docker.com/layers/czcoder/pulsar/3.3.0-55ed823/images/sha256-12928b392d55c19eca547b27fddbe8f1f90fc89cca3f3a5bf99d5bfa27239964?context=explore > docker pull czcoder/pulsar-all:3.3.0-55ed823 > https://hub.docker.com/layers/czcoder/pulsar-all/3.3.0-55ed823/images/sha256-2bb78e60e88d5fabc5956b5aa07b6f62724c548be7cdfdc35eccad7ac0cc2f9b?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, > > Cong Zhao >
[DISCUSS] PIP-353: Improve transaction message visibility for peek-messages
Hi all, I push a pip to improve transaction message visibility for the peek-messages command. https://github.com/apache/pulsar/pull/22746 Please feel free to leave your ideas. Thanks, Baodi Shi
Re: [DISCUSS] PIP-347 Extend LTS release process to client SDKs
+1 In the future, I think we should maintain the client LTS version page here: https://pulsar.apache.org/docs/next/client-libraries/ The original page is so hard to find that I guess users won't find it easily: https://pulsar.apache.org/contribute/release-policy/ Thanks, Baodi Shi On Apr 25, 2024 at 01:40:30, Matteo Merli wrote: > https://github.com/apache/pulsar/pull/22578 > > --- > > > # PIP-347: Extend LTS release process to client SDKs > > ## Motivation > > PIP-175 [1] has introduced the concept of LTS releases in Pulsar, with a > defined cadence of feature and LTS release and setting a clear expectation > in terms of support window for each release. > > The first Pulsar LTS release to follow this model was 3.0 in April 2023 > and it will be followed by 4.0 release in October 2024. > > Users have been very appreciative of these models and it has simplified the > work of maintainers, now that there are less active versions to support. > > While for the Pulsar Java client SDK, we are implicitly adopting the LTS > model, that > is not true for any other Pulsar client SDK, officially supported by the > Pulsar > PMC. > > This leaves all the non-Java client SDKs with different release cadences, > versioning and there is no support policy stated. > > > ## Goal > > The goal of this proposal is to align the support window for non-Java > client > SDKs to the same LTS model introduced in PIP-175. > > The interested clients are: > * C++ https://github.com/apache/pulsar-client-cpp > * Python https://github.com/apache/pulsar-client-python > * Go https://github.com/apache/pulsar-client-go > * NodeJS https://github.com/apache/pulsar-client-node > * .NET https://github.com/apache/pulsar-dotpulsar > * Reactive https://github.com/apache/pulsar-client-reactive > > All the above client libraries should switch to the 4.0 version now, to > mark the > first LTS release, then they will do 5.0 18 months after. > > Users of these client SDK should be expecting bug fixes for 24 months and > security for 36 months on the LTS release branches. > > This will set a clear expectation for users when deciding on a Pulsar SDK > version to use. > > > ## Changes > > All non-Java client SDKs managed by Pulsar PMC, will be starting to follow > the > same LTS release cadence established by Pulsar server releases. > > The alignment will be done only in terms of LTS releases. Feature releases > will > be done independently, with no requirement for quarterly feature releases. > Each > client SDK maintainer team (even though there is no formal team, there is > typically a smaller group of committers/PMCs closely following each > language SDK) > will do feature and patch releases as needed. > > The only new requirement will be to perform LTS releases every 18 months. > > There will be no additional requirement or additional explicit support > window > for client SDKs feature releases. > > > ## Note > > Similarly as for Pulsar server LTS releases, the major version digit bump > does > not signify any breaking changes and does not necessarily imply any "big" > new > features are introduced in a release. > > The compatibility between client and brokers running in different major > versions > will always be guaranteed, when using the lowest common denominator of > supported features. > > > --- > > [1]: PIP-175 https://github.com/apache/pulsar/issues/15966 > > > -- > Matteo Merli > >
[ANNOUNCE] Apache Pulsar Node.js client 1.11.0 released
The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.11.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 Node.js client release details and downloads, visit: https://www.npmjs.com/package/pulsar-client Release Notes are at: https://github.com/apache/pulsar-client-node/releases We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 4
Close this vote with 3 binding +1s - zike - baodi - Masahiro Sakamoto And 1 non-binding +1: - Shusuke Tsuda Thanks, Baodi Shi On Apr 17, 2024 at 11:52:47, Zike Yang wrote: > +1 (binding) > > - Verified checksum and signature > - Built from source on macOS arm64 and run the example > - Installed from the npm registry using node 12,14,16,18,20 on ubuntu > - Installed from the npm registry on macos > - Ran the example > > BR, > Zike Yang > > On Tue, Apr 16, 2024 at 8:38 AM 津田秀介 > wrote: > > > +1 (non-binding) > > > - verified checksums and signatures > > - confirmed that the build was successful > > - ran producer/consumer > > > Thanks, > > Shusuke Tsuda > > > -Original Message- > > From: "坂本雅宏" > > To: ; > > Cc: > > Sent: 2024/04/15(月) 17:25 (GMT+09:00) > > Subject: Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 4 > > > +1 (binding) > > > - verified checksums and signatures > > - confirmed that the build was successful > > - ran producer/consumer > > > Regards, > > > > Masahiro Sakamoto > > > LY Corporation > > Email massa...@lycorp.co.jp > > > > > -Original Message- > > From: "Baodi Shi" > > To: ; > > Cc: > > Sent: 2024/04/13(土) 18:32 (GMT+09:00) > > Subject: Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 4 > > > +1(binding) > > > - Verified sign and checksum > > - Build from source on macOS arm64 (Node 18) > > - Install from npm registry on Windows x64 (Node 18) > > - Run ProducerSample and ConsumerSample on macOS (Node 18) > > - Installed from the npm registry on Ubuntu using Node v12, v13, v14 ~ v20 > > > Thanks, > > Baodi Shi > > > > On Apr 13, 2024 at 17:30:23, Baodi Shi wrote: > > > > Hi everyone, > > > > > > This is the first release candidate for Apache Pulsar Node.js client, > > > version 1.11.0. > > > > > > It fixes the following issues: > > > - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 > > > - Related cpp client issue: > > > https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 > > > > > > Please download the source files and review this release candidate: > > > - Download the source package, verify shasum and asc > > > - Follow the README.md to build and run the Pulsar Node.js client. > > > > > > The release candidate package has been published to the npm registry: > > > https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.4 > > > You can install it by `npm i pulsar-client@1.11.0-rc.4 > > > --pulsar_binary_host_mirror= > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and > > > verify the package. > > > > > > The vote will be open for at least 72 hours. It is adopted by majority > > > approval, with at least 3 PMC affirmative votes. > > > > > > Source files: > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.4/ > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > https://downloads.apache.org/pulsar/KEYS > > > > > > SHA-512 checksum: > > > > 52cd6949e08d773ac11d315765278feb0165b65cabe654fb5d270acf17dffa77442ca4d42ad40b5ff7be92140a84ec98c1c94c616db84aff416641e43599bf5b > > > ./apache-pulsar-client-node-1.11.0.tar.gz > > > > > > The tag to be voted upon: > > > v1.11.0-rc.4 > > > https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.4 > > > > > > Please review and vote on the release candidate #1 for the version > 1.11.0, > > > as follows: > > > [ ] +1, Approve the release > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > > > > Thanks, > > > Baodi Shi > > > > > >
Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 4
+1(binding) - Verified sign and checksum - Build from source on macOS arm64 (Node 18) - Install from npm registry on Windows x64 (Node 18) - Run ProducerSample and ConsumerSample on macOS (Node 18) - Installed from the npm registry on Ubuntu using Node v12, v13, v14 ~ v20 Thanks, Baodi Shi On Apr 13, 2024 at 17:30:23, Baodi Shi wrote: > Hi everyone, > > This is the first release candidate for Apache Pulsar Node.js client, > version 1.11.0. > > It fixes the following issues: > - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 > - Related cpp client issue: > https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 > > Please download the source files and review this release candidate: > - Download the source package, verify shasum and asc > - Follow the README.md to build and run the Pulsar Node.js client. > > The release candidate package has been published to the npm registry: > https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.4 > You can install it by `npm i pulsar-client@1.11.0-rc.4 > --pulsar_binary_host_mirror= > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and > verify the package. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Source files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.4/ > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > SHA-512 checksum: > 52cd6949e08d773ac11d315765278feb0165b65cabe654fb5d270acf17dffa77442ca4d42ad40b5ff7be92140a84ec98c1c94c616db84aff416641e43599bf5b > ./apache-pulsar-client-node-1.11.0.tar.gz > > The tag to be voted upon: > v1.11.0-rc.4 > https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.4 > > Please review and vote on the release candidate #1 for the version 1.11.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > > Thanks, > Baodi Shi >
[VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 4
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.11.0. It fixes the following issues: - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 - Related cpp client issue: https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.4 You can install it by `npm i pulsar-client@1.11.0-rc.4 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.4/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/pulsar/KEYS SHA-512 checksum: 52cd6949e08d773ac11d315765278feb0165b65cabe654fb5d270acf17dffa77442ca4d42ad40b5ff7be92140a84ec98c1c94c616db84aff416641e43599bf5b ./apache-pulsar-client-node-1.11.0.tar.gz The tag to be voted upon: v1.11.0-rc.4 https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.4 Please review and vote on the release candidate #1 for the version 1.11.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 3
Thanks reminder, it related this
https://github.com/apache/pulsar-client-node/pull/301 pr, let me research
it.
I will cancel this vote
Thanks,
Baodi Shi
On Apr 12, 2024 at 10:46:57, Zike Yang wrote:
> - Verified checksum and signature
> - Built from source on macOS arm64 and run the example
> - Installed from the npm registry and run the example
> - Installed from the npm registry on Ubuntu using Node v14, v16, v18
> and run the example
>
> Installed from the npm registry using node v10, v11, v12, v13 but if
> failed with the following errors:
> ```
>
> pulsar-client@1.11.0-rc.3 install
> /data/verify/node1-11/node_modules/pulsar-client
>
> node-pre-gyp install --fallback-to-build && node GenCertFile.js
>
>
> [pulsar-client] Success:
> "/data/verify/node1-11/node_modules/pulsar-client/lib/binding/pulsar.node"
> is installed via remote
> /data/verify/node1-11/node_modules/pulsar-client/src/Client.js:60
>fs.rmSync(certsFilePath, { force: true });
> ^
>
> TypeError: fs.rmSync is not a function
>at Function.genCertFile
> (/data/verify/node1-11/node_modules/pulsar-client/src/Client.js:60:8)
>at Object.
> (/data/verify/node1-11/node_modules/pulsar-client/GenCertFile.js:22:8)
>at Module._compile (internal/modules/cjs/loader.js:1118:30)
>at Object.Module._extensions..js
> (internal/modules/cjs/loader.js:1138:10)
>at Module.load (internal/modules/cjs/loader.js:982:32)
>at Function.Module._load (internal/modules/cjs/loader.js:875:14)
>at Function.executeUserEntryPoint [as runMain]
> (internal/modules/run_main.js:71:12)
>at internal/main/run_main_module.js:17:47
> npm WARN node1-11@1.0.0 No description
> npm WARN node1-11@1.0.0 No repository field.
>
> npm ERR! code ELIFECYCLE
> npm ERR! errno 1
> npm ERR! pulsar-client@1.11.0-rc.3 install: `node-pre-gyp install
> --fallback-to-build && node GenCertFile.js`
> npm ERR! Exit status 1
> npm ERR!
> npm ERR! Failed at the pulsar-client@1.11.0-rc.3 install script.
> npm ERR! This is probably not a problem with npm. There is likely
> additional logging output above.
>
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/zike/.npm/_logs/2024-04-12T02_40_33_159Z-debug.log
> ```
>
> However the README states that the client is compatible with Nodejs 10
> or later:
> https://github.com/apache/pulsar-client-node/blob/e3bf582ea450e68379ff685598257ed6e69fb1aa/README.md?plain=1#L26
> Perhaps we should update our version compatibility strategy in the
> README.
>
> BR,
> Zike Yang
>
> On Fri, Apr 12, 2024 at 8:13 AM Baodi Shi wrote:
>
>
> +1(binding)
>
>
> - verified sign and checksum
>
> - Build from source and install from npm registry on macOS arm64
>
> - Install from npm registry on Windows x64
>
> - Run ProducerSample and ConsumerSample on macOS
>
>
>
> Thanks,
>
> Baodi Shi
>
>
>
> On Apr 11, 2024 at 18:43:51, Yunze Xu wrote:
>
>
> > +1 (binding)
>
> >
>
> > - Verified signature and checksums
>
> > - Built from source on macOS
>
> > - Run e2e tests against a local standalone
>
> > - Run e2e tests with OAuth2 authentication against an online cluster
>
> >
>
> > Thanks,
>
> > Yunze
>
> >
>
> > On Tue, Apr 9, 2024 at 6:26 PM Baodi Shi wrote:
>
> >
>
> >
>
> > Hi everyone,
>
> >
>
> >
>
> > This is the first release candidate for Apache Pulsar Node.js client,
>
> >
>
> > version 1.11.0.
>
> >
>
> >
>
> > It fixes the following issues:
>
> >
>
> > - https://github.com/apache/pulsar-client-node/milestone/16?closed=1
>
> >
>
> > - Related cpp client issue:
>
> >
>
> > https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1
>
> >
>
> >
>
> > Please download the source files and review this release candidate:
>
> >
>
> > - Download the source package, verify shasum and asc
>
> >
>
> > - Follow the README.md to build and run the Pulsar Node.js client.
>
> >
>
> >
>
> > The release candidate package has been published to the npm registry:
>
> >
>
> > https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.3
>
> >
>
> > You can install it by `npm i pulsar-client@1.11.0-rc.3
>
> >
>
> > --pulsar_binary_host_mirror=
>
> >
>
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and
>
> >
>
> > verify the package.
>
> >
>
> >
>
> > The vote will be open for at
Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 3
+1(binding) - verified sign and checksum - Build from source and install from npm registry on macOS arm64 - Install from npm registry on Windows x64 - Run ProducerSample and ConsumerSample on macOS Thanks, Baodi Shi On Apr 11, 2024 at 18:43:51, Yunze Xu wrote: > +1 (binding) > > - Verified signature and checksums > - Built from source on macOS > - Run e2e tests against a local standalone > - Run e2e tests with OAuth2 authentication against an online cluster > > Thanks, > Yunze > > On Tue, Apr 9, 2024 at 6:26 PM Baodi Shi wrote: > > > Hi everyone, > > > This is the first release candidate for Apache Pulsar Node.js client, > > version 1.11.0. > > > It fixes the following issues: > > - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 > > - Related cpp client issue: > > https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 > > > Please download the source files and review this release candidate: > > - Download the source package, verify shasum and asc > > - Follow the README.md to build and run the Pulsar Node.js client. > > > The release candidate package has been published to the npm registry: > > https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.3 > > You can install it by `npm i pulsar-client@1.11.0-rc.3 > > --pulsar_binary_host_mirror= > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and > > verify the package. > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > Source files: > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.3/ > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://downloads.apache.org/pulsar/KEYS > > > SHA-512 checksum: > > > 74196c05f80a0c2569c1d19d7e21ea18babb5fe75fc5936c6eef47574ee7a9abc0f4a7e4db3b740de760d477cb2dfc51c9fd5b2dd343ee54389d78b1e24849e7 > > ./apache-pulsar-client-node-1.11.0.tar.gz > > > The tag to be voted upon: > > v1.11.0-rc.3 > > https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.3 > > > Please review and vote on the release candidate #1 for the version 1.11.0, > > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > Thanks, > > Baodi Shi > >
Re: [DISCUSS] cherry-pick #22034 Create new ledger after the current ledger is closed
Hi, xiangying. I agree with cherry-picking the historical branch. This change in behavior is as expected, and it can indeed be understood as a bug. We can cherry-pick them all together after fixing all unstable tests. Currently, the only test I see is this one: - https://github.com/apache/pulsar/issues/22351 Thanks, Baodi Shi On Apr 7, 2024 at 19:12:59, Xiangying Meng wrote: > Hi all, > > I want to start a discussion to cherry-pick #22034 [0] to release branches. > The PR creates a new ledger after the current one is full. This is a > bug fix to resolve the issue where the last ledger could not be > deleted after expiration. Moreover, since there is no need to create a > new ledger only when messages are sent, it can reduce the send > latency. > > However, it could be a behavior change and introduce some flaky tests > we have fixed in the master. So I think it may be necessary to have a > discussion before cherry-picking. > > The target branches: > > - branch-3.0 > - branch-3.1 > - branch-3.2 > > [0] https://github.com/apache/pulsar/pull/22034 > > I will keep the discussion open for at least 48 hours. > If there is no objections, I will perform the cherry-picking. > > BR, > Xiangying >
[VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 3
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.11.0. It fixes the following issues: - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 - Related cpp client issue: https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.3 You can install it by `npm i pulsar-client@1.11.0-rc.3 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.3/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/pulsar/KEYS SHA-512 checksum: 74196c05f80a0c2569c1d19d7e21ea18babb5fe75fc5936c6eef47574ee7a9abc0f4a7e4db3b740de760d477cb2dfc51c9fd5b2dd343ee54389d78b1e24849e7 ./apache-pulsar-client-node-1.11.0.tar.gz The tag to be voted upon: v1.11.0-rc.3 https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.3 Please review and vote on the release candidate #1 for the version 1.11.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 2
Cancel this vote, as I will include this bug fix in the new release. - https://github.com/apache/pulsar-client-node/issues/374 Thanks, Baodi Shi On Apr 7, 2024 at 09:31:07, Baodi Shi wrote: > Hi everyone, > > This is the first release candidate for Apache Pulsar Node.js client, > version 1.11.0. > > It fixes the following issues: > - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 > - Related cpp client issue: > https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 > > Please download the source files and review this release candidate: > - Download the source package, verify shasum and asc > - Follow the README.md to build and run the Pulsar Node.js client. > > The release candidate package has been published to the npm registry: > https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.2 > You can install it by `npm i pulsar-client@1.11.0-rc.2 > --pulsar_binary_host_mirror= > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and > verify the package. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Source files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.2/ > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > SHA-512 checksum: > db443a415478aeba23fe7930fa4420bc6e40b10ac5b4b042b3c042c2c20f2fd1d3864f59df00eaf17acdfdf39e560ea406d0efa2e1bab4bfb79d2f1c31a6ae4e > ./apache-pulsar-client-node-1.11.0.tar.gz > > The tag to be voted upon: > v1.11.0-rc.2 > https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.2 > > Please review and vote on the release candidate #1 for the version 1.11.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > > Thanks, > Baodi Shi >
[VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 2
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.11.0. It fixes the following issues: - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 - Related cpp client issue: https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.2 You can install it by `npm i pulsar-client@1.11.0-rc.2 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.2/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/pulsar/KEYS SHA-512 checksum: db443a415478aeba23fe7930fa4420bc6e40b10ac5b4b042b3c042c2c20f2fd1d3864f59df00eaf17acdfdf39e560ea406d0efa2e1bab4bfb79d2f1c31a6ae4e ./apache-pulsar-client-node-1.11.0.tar.gz The tag to be voted upon: v1.11.0-rc.2 https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.2 Please review and vote on the release candidate #1 for the version 1.11.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 1
Cancel this vote, as I will include this feature in the new release. - https://github.com/apache/pulsar-client-node/pull/375 Thanks, Baodi Shi On Apr 4, 2024 at 09:42:12, Baodi Shi wrote: > Hi everyone, > > This is the first release candidate for Apache Pulsar Node.js client, > version 1.11.0. > > It fixes the following issues: > - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 > - Related cpp client issue: > https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 > > Please download the source files and review this release candidate: > - Download the source package, verify shasum and asc > - Follow the README.md to build and run the Pulsar Node.js client. > > The release candidate package has been published to the npm registry: > https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.1 > You can install it by `npm i pulsar-client@1.11.0-rc.1 > --pulsar_binary_host_mirror= > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and > verify the package. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Source files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.1/ > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > SHA-512 checksum: > 4bc83240b7d2886813d8fa26f92813f6c3ed4c75983f57bfb92b7c58d4d9db0d6d97fe747fbcd07c11f09ed262a42155e9391e836ea659ee54d763776de86084 > ./apache-pulsar-client-node-1.11.0.tar.gz > > The tag to be voted upon: > v1.11.0-rc.1 > https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.1 > > Please review and vote on the release candidate #1 for the version 1.11.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > > Thanks, > Baodi Shi >
[VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 1
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.11.0. It fixes the following issues: - https://github.com/apache/pulsar-client-node/milestone/16?closed=1 - Related cpp client issue: https://github.com/apache/pulsar-client-cpp/compare/v3.4.2...v3.5.1 Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.11.0-rc.1 You can install it by `npm i pulsar-client@1.11.0-rc.1 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.11.0-rc.1/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/pulsar/KEYS SHA-512 checksum: 4bc83240b7d2886813d8fa26f92813f6c3ed4c75983f57bfb92b7c58d4d9db0d6d97fe747fbcd07c11f09ed262a42155e9391e836ea659ee54d763776de86084 ./apache-pulsar-client-node-1.11.0.tar.gz The tag to be voted upon: v1.11.0-rc.1 https://github.com/apache/pulsar-client-node/releases/tag/v1.11.0-rc.1 Please review and vote on the release candidate #1 for the version 1.11.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: [VOTE] Pulsar Client C++ Release 3.5.1 Candidate 1
+1(non-binding) - Verified signature and checksums - build from macOS m1 local and run SampleProducer and SampleConsumer Thanks, Baodi Shi On Mar 28, 2024 at 20:44:33, Yunze Xu wrote: > +1 (binding) > > - Verified signature and checksums > - Built from source on macOS m1 with vcpkg > - Verified basic e2e case with a Pulsar standalone 3.2.0 > - Verified Python client with this dependency: > https://github.com/apache/pulsar-client-python/pull/209 > - Verified Node.js client with this dependency: > https://github.com/apache/pulsar-client-node/pull/370 > > Thanks, > Yunze > > On Thu, Mar 28, 2024 at 4:42 PM Yunze Xu wrote: > > > This is the first release candidate for Apache Pulsar Client C++, version > 3.5.1. > > > It fixes the following issues: > > https://github.com/apache/pulsar-client-cpp/labels/release%2F3.5.1 > > > *** 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-client-cpp/pulsar-client-cpp-3.5.1-candidate-1/ > > > SHA-512 checksums: > > > d01ebd64292fb1e55b889f1e2c90821c5f7c04a84e109caccd442cb0b15e79701fe10adfcd33a28046db48e10598bb1405a9bb64c063f18378a6ee64b80da847 > > apache-pulsar-client-cpp-3.5.1.tar.gz > > > The tag to be voted upon: > > v3.5.1-candidate-1 (21f4a4cffefaa9391b79d79a7849da9c539af834) > > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.5.1-candidate-1 > > > Pulsar's KEYS file containing PGP keys you use to sign the release: > > https://downloads.apache.org/pulsar/KEYS > > > Please download the source package, and follow > > > https://github.com/apache/pulsar-client-cpp/wiki/Verify-the-candidate-release-in-your-local-env > > to compile and test. > > > Note: If you're going to run the unit tests locally, please make sure > > the proxy is disabled. > >
Re: [DISCUSS] Release Pulsar C++ Client 3.5.1 and upgrade the verify process
+1 Thank you for push this discussion. We can modify the release process: we'll require the release manager to attach the PR for Python and Node.js upgrades when initiating a candidate vote, and ensure it CI can pass. Once the CPP client release is successful, we can remove the candidate, and then push for its merge. Thanks, Baodi Shi On Mar 25, 2024 at 18:29:23, Yunze Xu wrote: > Hi all, > > Recently I found a regression [1] for the C++ client 3.5.0 (thanks to > the reminder from @shibd). So I will push a fix and then release the > C++ client 3.5.1. > > However, this is not the 1st time that a regression was introduced, > see [2] for example. So I suggest when verifying the C++ client, we > can verify the Python and Node.js clients by upgrading the > dependencies as well. See the updated release process in [3]. > > [1] https://github.com/apache/pulsar-client-cpp/issues/420 > [2] https://lists.apache.org/thread/rjolgrlp4x1lmfj678k3hjco80kcb73c > [3] > https://github.com/apache/pulsar-client-cpp/wiki/Verify-the-candidate-release-in-your-local-env#verify-the-3rd-party-projects-that-depend-on-pulsar-c-client > > Thanks, > Yunze >
[DISCUSS] Release Pulsar Node.js client v1.11.0
Hi all, I would like to propose releasing the Pulsar Node.js client v1.11.0 Due to Node.js's dependency on the CPP client, and considering that CPP client version 3.5.0 has introduced many features and fixed numerous bugs, I would upgrade the CPP version that Node.js depends on to 3.5.0 and launch a new version. - https://github.com/apache/pulsar-client-cpp/releases/tag/v3.5.0 Please let me know if you have any PRs that need to be included in 1.11.0. Thanks, Baodi Shi
Re: [DISCUSS] Release Pulsar Python Client 3.5.0
+1 Thanks, Baodi Shi On Mar 19, 2024 at 20:04:52, Zike Yang wrote: > +1 > > Thanks, > Zike Yang > > On Tue, Mar 19, 2024 at 8:00 PM Yunze Xu wrote: > > > Hi all, > > > I would like to propose releasing the Pulsar Python client 3.5.0. > > > It's over two months since the release of 3.4.0, and there are 16 new > > commits: > https://github.com/apache/pulsar-client-python/compare/v3.4.0...main. > > The dependent C++ client was upgraded to 3.5.0 in > > https://github.com/apache/pulsar-client-python/pull/202, which also > > fixes some bugs. It's time to cut a new release. > > > Please let me know if you have any important fixes that need to be > > included in Pulsar Python client 3.5.0. > > > Thanks, > > Yunze > >
Re: [VOTE] Pulsar Client C++ Release 3.5.0 Candidate 2
Hi, yunze https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-cpp/pulsar-client-cpp-3.5.0-candidate-2/apache-pulsar-client-cpp-3.5.0.tar.gz This source code not include vcpkg, If we unzip it and run the command cmake -B build -DINTEGRATE_VCPKG=ON, it throws an error. Do we need to include vcpkg in the source code? Other passed verify: - Checked the sign and checksum - Use macOS arm64 pre-built binaries to build node.js client Thanks, Baodi Shi On Mar 12, 2024 at 10:25:56, Yunze Xu wrote: > This is the second release candidate for Apache Pulsar Client C++, > version 3.5.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/6?closed=1 > > *** 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-client-cpp/pulsar-client-cpp-3.5.0-candidate-2/ > > SHA-512 checksums: > > > b590c7128a0110812e3a2f3b94f81078a3ff254709aab175265838fa45c4022f0fab83d4817c1d31883a68e49454c698d0ea7b858c4b7e8d756aa1f7f703fe12 > apache-pulsar-client-cpp-3.5.0.tar.gz > > > The tag to be voted upon: > v3.5.0-candidate-2 (916af95dda4d06162f9ea4e4180f9fd726c25a4e) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.5.0-candidate-2 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Please download the source package, and follow > > https://github.com/apache/pulsar-client-cpp/wiki/Verify-the-candidate-release-in-your-local-env > to compile and test. > > Note: If you're going to run the unit tests locally, please make sure > the proxy is disabled. >
Re: [VOTE] PIP-339: Introducing the --log-topic Option for Pulsar Sinks and Sources
+1(non-binding) Thanks, Baodi Shi On Feb 27, 2024 at 15:57:07, Hang Chen wrote: > +1(binding) > > Regards, > Hang > > guo jiwei 于2024年2月27日周二 15:54写道： > > > +1 (binding) > > > Regards > > Jiwei Guo (Tboy) > > > > On Tue, Feb 27, 2024 at 10:18 AM Zike Yang wrote: > > > > +1 (no-binding) > > > > > > BR, > > > Zike Yang > > > > > > On Tue, Feb 27, 2024 at 8:56 AM PengHui Li wrote: > > > > > > > > +1 (binding) > > > > > > > > Regards, > > > > Penghui > > > > > > > > On Mon, Feb 26, 2024 at 5:44 PM Pengcheng Jiang > > > > wrote: > > > > > > > > > Hi, community > > > > > > > > > > I'm starting the vote for PIP-339: Introducing the --log-topic Option > > > for > > > > > Pulsar Sinks and Sources > > > > > PIP link: https://github.com/apache/pulsar/pull/22071 > > > > > > > > > > Thanks, > > > > > Pengcheng Jiang > > > > > > > > > >
Re: [ANNOUNCE] New Committer: Asaf Mesika
Congrats! Asaf Thanks, Baodi Shi On Feb 22, 2024 at 15:12:50, Haiting Jiang wrote: > Congratulations! > > Thanks, > Haiting > > On Wed, Feb 21, 2024 at 9:35 PM Yubiao Feng > wrote: > > > Congratulations! > > > Thanks > > Yubiao Feng > > > On Wed, Feb 21, 2024 at 12:50 AM Lari Hotari wrote: > > > > The Apache Pulsar Project Management Committee (PMC) has invited > > > Asaf Mesika https://github.com/asafm to become a committer and we > > > are pleased to announce that he has accepted. > > > > > > Welcome and Congratulations, Asaf Mesika! > > > > > > Please join us in congratulating and welcoming Asaf onboard! > > > > > > Best Regards, > > > > > > Lari Hotari > > > on behalf of the Pulsar PMC > > > > >
[ANNOUNCE] Apache Pulsar Node.js client 1.10.0 released
The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.10.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 Node.js client release details and downloads, visit: https://www.npmjs.com/package/pulsar-client Release Notes are at: https://github.com/apache/pulsar-client-node/releases We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
Re: [VOTE] Pulsar Node.js Client Release 1.10.0 Candidate 1
Closing this vote by 3 binding +1s - Yunze - Yubiao - Massahiro Thanks Baodi Shi On Feb 6, 2024 at 10:13:41, Yubiao Feng wrote: > +1 (binding) > > - verified checksums and signatures > - confirmed that the build was successful > - ran producer/consumer > > Thanks > Yubaio Feng > > On Mon, Jan 29, 2024 at 6:11 PM Baodi Shi wrote: > > Hi everyone, > > > This is the first release candidate for Apache Pulsar Node.js client, > > version 1.10.0. > > > It fixes the following issues: > > https://github.com/apache/pulsar-client-node/milestone/15?closed=1 > > > Please download the source files and review this release candidate: > > - Download the source package, verify shasum and asc > > - Follow the README.md to build and run the Pulsar Node.js client. > > > The release candidate package has been published to the npm registry: > > https://www.npmjs.com/package/pulsar-client/v/1.10.0-rc.1 > > You can install it by `npm i pulsar-client@1.10.0-rc.1 > > --pulsar_binary_host_mirror= > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` > > <https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/> and > > verify the package. > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > Source files: > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.10.0-rc.1/ > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://downloads.apache.org/pulsar/KEYS > > > SHA-512 checksum: > > > > 3e2c76ff8340597129eec1ab2a9cdbdd48fb162257426c474bd637bb02a45b49011e6b31e08679022f18d700e73f49cbb8adc59f75e345db9220a2b755eccac4 > > ./apache-pulsar-client-node-1.10.0.tar.gz > > > The tag to be voted upon: > > v1.10.0-rc.1 > > https://github.com/apache/pulsar-client-node/releases/tag/v1.10.0-rc.1 > > > Please review and vote on the release candidate #1 for the version 1.10.0, > > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > >
[VOTE] Pulsar Node.js Client Release 1.10.0 Candidate 1
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.10.0. It fixes the following issues: https://github.com/apache/pulsar-client-node/milestone/15?closed=1 Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.10.0-rc.1 You can install it by `npm i pulsar-client@1.10.0-rc.1 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.10.0-rc.1/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/pulsar/KEYS SHA-512 checksum: 3e2c76ff8340597129eec1ab2a9cdbdd48fb162257426c474bd637bb02a45b49011e6b31e08679022f18d700e73f49cbb8adc59f75e345db9220a2b755eccac4 ./apache-pulsar-client-node-1.10.0.tar.gz The tag to be voted upon: v1.10.0-rc.1 https://github.com/apache/pulsar-client-node/releases/tag/v1.10.0-rc.1 Please review and vote on the release candidate #1 for the version 1.10.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments)
[DISCUSS] Release Pulsar Node.js client v1.10.0
Hi all, I would like to propose releasing the Pulsar Node.js client v1.10.0 It has been over 5 months since the last release (1.9.0). There have been many new features and bug fixes since then. It's time to release a new version. - https://github.com/apache/pulsar-client-node/milestone/15?closed=1 Please let me know if you have any PRs that need to be included in 1.10.0. Thanks, Baodi Shi
[ANNOUNCE] Apache Pulsar 2.11.3 released
The Apache Pulsar team is proud to announce Apache Pulsar version 2.11.3. 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://pulsar.apache.org/download Release Notes are at: https://pulsar.apache.org/release-notes We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
Re: [VOTE] Pulsar Release 2.11.3 Candidate 2
Close this vote, and vote pass with 3 +1 binding. - jiwei - penghui - yubiao Thanks, Baodi Shi On Jan 2, 2024 at 15:18:31, Yubiao Feng wrote: > +1(binding) > > - Checked the signatures > - Run standalone and check the produce, consume > - Verified Cassandra connector > - Verified stateful function > > Thanks > Yubiao Feng > > On Thu, Dec 28, 2023 at 5:03 PM PengHui Li wrote: > > +1 (binding) > > > - Built from source > > - Checked the signatures > > - Run standalone > > - Checked producer and consumer > > - Verified the Cassandra connector > > - Verified the Stateful function > > > Regards, > > Penghui > > > On Mon, Dec 25, 2023 at 9:19 PM guo jiwei wrote: > > > > +1 (binding) > > > > > > > > > - Checked the signatures > > > - Built from source > > > - Run standalone and check the produce, consume > > > - Verified Cassandra connector > > > - Verified stateful function > > > > > > Regards > > > Jiwei Guo (Tboy) > > > > > > > > > On Thu, Dec 21, 2023 at 9:32 AM Baodi Shi wrote: > > > > > > > This is the second release candidate for Apache Pulsar, version 2.11.3. > > > > > > > > It fixes the following issues: > > > > > > > > > > > > > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed > > > > > > > > *** 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.11.3-candidate-2/ > > > > > > > > SHA-512 checksums: > > > > > > > > > > > > > > > > > > 521316ea9f01b54f0fb3981dc017d3529de4019360c57c38c72c1ecfa53030927b93608acd71d0eb58f3e7eb6b4a2583a94796462d577d7dca0ba935a2f68fcf > > > > ./apache-pulsar-2.11.3-bin.tar.gz > > > > > > > > > > > > > > > > > > 4510c16d6ec90847eb8dff0246bd09190f99bc10a30702ab5f521971b13b6cffe0f9d1de9637b85340154ee38764a39551fd871bd1132d7760fb3a7e931a20e3 > > > > ./apache-pulsar-2.11.3-src.tar.gz > > > > > > > > > > > > Maven staging repo: > > > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1258/ > > > > > > > > The tag to be voted upon: > > > > v2.11.3-candidate-2 (c7ac62c > > > > < > > > > > > > > > > https://github.com/apache/pulsar/commit/c7ac62ca9eb718e15c3e3e4a460167643ef3f48b > > > > > > > > > ) > > > > https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-2 > > > > > > > > Pulsar’s KEYS file containing PGP keys you use to sign the release: > > > > https://downloads.apache.org/pulsar/KEYS > > > > > > > > Docker images: > > > > docker pull wudixiaobaozi/pulsar-all:2.11.3 > > > > docker pull wudixiaobaozi/pulsar:2.11.3 > > > > > > > > Please download the source package, and follow the README to build > > > > and run the Pulsar standalone service. > > > > > > > > Thanks, > > > > Baodi Shi > > > > > > > > > >
[VOTE] Pulsar Release 2.11.3 Candidate 2
This is the second release candidate for Apache Pulsar, version 2.11.3. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed *** 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.11.3-candidate-2/ SHA-512 checksums: 521316ea9f01b54f0fb3981dc017d3529de4019360c57c38c72c1ecfa53030927b93608acd71d0eb58f3e7eb6b4a2583a94796462d577d7dca0ba935a2f68fcf ./apache-pulsar-2.11.3-bin.tar.gz 4510c16d6ec90847eb8dff0246bd09190f99bc10a30702ab5f521971b13b6cffe0f9d1de9637b85340154ee38764a39551fd871bd1132d7760fb3a7e931a20e3 ./apache-pulsar-2.11.3-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1258/ The tag to be voted upon: v2.11.3-candidate-2 (c7ac62c <https://github.com/apache/pulsar/commit/c7ac62ca9eb718e15c3e3e4a460167643ef3f48b> ) https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-2 Pulsar’s KEYS file containing PGP keys you use to sign the release: https://downloads.apache.org/pulsar/KEYS Docker images: docker pull wudixiaobaozi/pulsar-all:2.11.3 docker pull wudixiaobaozi/pulsar:2.11.3 Please download the source package, and follow the README to build and run the Pulsar standalone service. Thanks, Baodi Shi
Re: [VOTE] Pulsar Release 2.11.3 Candidate 1
Hi, yubiao. Thanks for your feedback. After discussing with Penghui, we need to wait for the Bookkeeper 4.15.5 release and then upgrade it on Pulsar. So, close this Vote first. Thanks, Baodi Shi On Nov 29, 2023 at 12:09:00, Yubiao Feng wrote: > Hi Penghui, Baodi > > - Run standalone and check the produce, consume > - Verified Cassandra connector > - Verified stateful function > > But the result of `unzip -t > ./lib/org.apache.bookkeeper-circe-checksum-*.jar | grep lib` is not > expected. I only got the logs below > > ``` > > unzip -t ./lib/org.apache.bookkeeper-circe-checksum-*.jar | grep lib > > > > Archive: ./lib/org.apache.bookkeeper-circe-checksum-4.15.4.jar > > No errors detected in compressed data of > ./lib/org.apache.bookkeeper-circe-checksum-4.15.4.jar. > ``` > > I can not find `testing: lib/libcirce-checksum.so OK` in the logs. > > By the way, the check above is newly added to the document by > https://github.com/apache/pulsar-site/pull/740 > > Thanks > Yubiao Feng > > On Tue, Nov 21, 2023 at 9:25 PM Baodi Shi wrote: > > This is the first release candidate for Apache Pulsar, version 2.11.3. > > > It fixes the following issues: > > > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed > > > *** 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.11.3-candidate-1/ > > > SHA-512 checksums: > > > > > 1104ce10ee55f99f162f71487922d9883201516754936feab07a631b25b8f76bc2443735b4bdff17d821d62ca20f605d386ce9ca2e0450ce8d2555ca07fd8dd > > ./apache-pulsar-2.11.3-bin.tar.gz > > > > > bdf2579d718d25def297538def0c237974c856f63aea00db30e61b10683eec29a52a354b61daa6eda5ffe5bdfda78e6a83d473f8d7f44104fc5d715ffb1892fc > > ./apache-pulsar-2.11.3-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1251 > > > The tag to be voted upon: > > v2.11.3-candidate-1 (aa7082efcafb58b1fc4b7bb1bc68c6e22f7bc2d3) > > https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-1 > > > Pulsar’s KEYS file containing PGP keys you use to sign the release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > Docker images: > > docker pull wudixiaobaozi/pulsar-all:2.11.3 > > docker pull wudixiaobaozi/pulsar > > > Please download the source package, and follow the README to build > > and run the Pulsar standalone service. > > > Thanks, > > Baodi Shi > > >
Re: [VOTE] Pulsar Release 2.11.3 Candidate 1
Tips: Pulsar’s KEYS file address: https://dist.apache.org/repos/dist/release/pulsar/KEYS Thanks, Baodi Shi On Nov 23, 2023 at 15:16:30, guo jiwei wrote: > +1 (binding) > > - Checked the signatures > - Built from source > - Run standalone and check the produce, consume > - Verified Cassandra connector > - Verified stateful function > > Regards > Jiwei Guo (Tboy) > > > On Tue, Nov 21, 2023 at 9:47 PM Baodi Shi wrote: > > Patch: > > > Docker images: > > docker pull wudixiaobaozi/pulsar-all:2.11.3 > > docker pull wudixiaobaozi/pulsar:2.11.3 > > > Thanks, > > Baodi Shi > > > > On Nov 21, 2023 at 21:23:41, Baodi Shi wrote: > > > > This is the first release candidate for Apache Pulsar, version 2.11.3. > > > > > > It fixes the following issues: > > > > > > > > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed > > > > > > *** 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.11.3-candidate-1/ > > > > > > SHA-512 checksums: > > > > > > > > > 1104ce10ee55f99f162f71487922d9883201516754936feab07a631b25b8f76bc2443735b4bdff17d821d62ca20f605d386ce9ca2e0450ce8d2555ca07fd8dd > > ./apache-pulsar-2.11.3-bin.tar.gz > > > > > > > > > bdf2579d718d25def297538def0c237974c856f63aea00db30e61b10683eec29a52a354b61daa6eda5ffe5bdfda78e6a83d473f8d7f44104fc5d715ffb1892fc > > ./apache-pulsar-2.11.3-src.tar.gz > > > > > > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/orgapachepulsar-1251 > > > > > > The tag to be voted upon: > > > v2.11.3-candidate-1 (aa7082efcafb58b1fc4b7bb1bc68c6e22f7bc2d3) > > > https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-1 > > > > > > Pulsar’s KEYS file containing PGP keys you use to sign the release: > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > Docker images: > > > docker pull wudixiaobaozi/pulsar-all:2.11.3 > > > docker pull wudixiaobaozi/pulsar > > > > > > Please download the source package, and follow the README to build > > > and run the Pulsar standalone service. > > > > > > Thanks, > > > Baodi Shi > > > > > >
Re: [VOTE] Pulsar Client C++ Release 3.4.1 Candidate 2
+1(non-binding) - Checked the signature - Verify for MacOS arm64 pre-built binaries and run producer and consumer passed. - Verify for Node.js client use this release to run unit test passed. Thanks, Baodi Shi On Nov 21, 2023 at 23:40:43, Yunze Xu wrote: > This is the second release candidate for Apache Pulsar Client C++, > version 3.4.1. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/7?closed=1 > > *** 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-client-cpp/pulsar-client-cpp-3.4.1-candidate-2/ > > SHA-512 checksums: > > 2f8e88b7ead8f18065a51fe1c2df2c39f83334618bf664af5051391c6356e616626a5b7eed30813fe97dfa3408f93ffd5daaefc39470855df7b0bab4e80e4d76 > apache-pulsar-client-cpp-3.4.1.tar.gz > > The tag to be voted upon: > v3.4.0-candidate-2 (1c725b421c672549f2a34222b8cb740294e75ff1) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.4.1-candidate-2 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Please download the source package, and follow > > https://github.com/apache/pulsar-client-cpp/wiki/Verify-the-candidate-release-in-your-local-env > to compile and test. > > Note: If you're going to run the unit tests locally, please make sure > the proxy is disabled. >
Re: [VOTE] Pulsar Release 2.11.3 Candidate 1
Patch: Docker images: docker pull wudixiaobaozi/pulsar-all:2.11.3 docker pull wudixiaobaozi/pulsar:2.11.3 Thanks, Baodi Shi On Nov 21, 2023 at 21:23:41, Baodi Shi wrote: > This is the first release candidate for Apache Pulsar, version 2.11.3. > > It fixes the following issues: > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed > > *** 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.11.3-candidate-1/ > > SHA-512 checksums: > > 1104ce10ee55f99f162f71487922d9883201516754936feab07a631b25b8f76bc2443735b4bdff17d821d62ca20f605d386ce9ca2e0450ce8d2555ca07fd8dd > ./apache-pulsar-2.11.3-bin.tar.gz > > bdf2579d718d25def297538def0c237974c856f63aea00db30e61b10683eec29a52a354b61daa6eda5ffe5bdfda78e6a83d473f8d7f44104fc5d715ffb1892fc > ./apache-pulsar-2.11.3-src.tar.gz > > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1251 > > The tag to be voted upon: > v2.11.3-candidate-1 (aa7082efcafb58b1fc4b7bb1bc68c6e22f7bc2d3) > https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-1 > > Pulsar’s KEYS file containing PGP keys you use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Docker images: > docker pull wudixiaobaozi/pulsar-all:2.11.3 > docker pull wudixiaobaozi/pulsar > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > Thanks, > Baodi Shi >
[VOTE] Pulsar Release 2.11.3 Candidate 1
This is the first release candidate for Apache Pulsar, version 2.11.3. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed *** 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.11.3-candidate-1/ SHA-512 checksums: 1104ce10ee55f99f162f71487922d9883201516754936feab07a631b25b8f76bc2443735b4bdff17d821d62ca20f605d386ce9ca2e0450ce8d2555ca07fd8dd ./apache-pulsar-2.11.3-bin.tar.gz bdf2579d718d25def297538def0c237974c856f63aea00db30e61b10683eec29a52a354b61daa6eda5ffe5bdfda78e6a83d473f8d7f44104fc5d715ffb1892fc ./apache-pulsar-2.11.3-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1251 The tag to be voted upon: v2.11.3-candidate-1 (aa7082efcafb58b1fc4b7bb1bc68c6e22f7bc2d3) https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-1 Pulsar’s KEYS file containing PGP keys you use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Docker images: docker pull wudixiaobaozi/pulsar-all:2.11.3 docker pull wudixiaobaozi/pulsar Please download the source package, and follow the README to build and run the Pulsar standalone service. Thanks, Baodi Shi
Re: [VOTE] Pulsar Client C++ Release 3.4.1 Candidate 1
Hi, yunze. When I test producer flush method for C client. I get two callbacks. If the user releases the context in the callback method, they will encounter a segmentation fault. Refer to: https://github.com/apache/pulsar-client-cpp/issues/352 Thanks, Baodi Shi On Nov 18, 2023 at 00:02:55, Yunze Xu wrote: > This is the first release candidate for Apache Pulsar Client C++, version > 3.4.1. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/7?closed=1 > > *** 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-client-cpp/pulsar-client-cpp-3.4.1-candidate-1/ > > SHA-512 checksums: > > 74ff4bbc9126f30eb8c104342918b577d4cdf62a443593b7caf89ef8f8e9dec57c4c66bbcb3965186780b0fdf1a40172d8a941584ceb3db798773b119b0f2c72 > apache-pulsar-client-cpp-3.4.1.tar.gz > > The tag to be voted upon: > v3.4.1-candidate-1 (e6ec207cd857af149b21429530be0691bd26dbdb) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.4.1-candidate-1 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Please download the source package, and follow the README to compile and > test. > > Note: If you're going to run the unit tests locally, please make sure > the proxy is disabled. >
Re: [VOTE] PIP-312 Use StateStoreProvider to manage state in Pulsar Functions endpoints
+1(non-binding) Thanks, Baodi Shi On Nov 15, 2023 at 11:49:24, Neng Lu wrote: > +1 > > On 2023/11/15 03:39:42 Pengcheng Jiang wrote: > > Hi Pulsar Community, > > > This thread is to start a vote for PIP-312: Use StateStoreProvider to > > manage state in Pulsar Functions endpoints. > > > I start the voting process since there are some approves for the PIP PR. > > > PR: https://github.com/apache/pulsar/pull/21438 > > Discussion thread: > > https://lists.apache.org/thread/0rz29wotonmdck76pdscwbqo19t3rbds > > > Sincerely, > > Pengcheng Jiang > > >
Re: [ANNOUNCE] Yubiao Feng as new PMC member in Apache Pulsar
Congrats! Yubiao. Thanks, Baodi Shi On Nov 13, 2023 at 16:23:00, ZhangJian He wrote: > Congrats! > > Thanks > ZhangJian He > > > On Mon, 13 Nov 2023 at 16:22, 1060026287 <1060026...@qq.com.invalid> > wrote: > > Congratulations. Yubiao > > > > > > > > -- Original -- > > From: PengHui Li > Date: Mon, Nov 13, 2023 4:20 PM > > To: dev > Subject: Re: [ANNOUNCE] Yubiao Feng as new PMC member in Apache Pulsar > > > > > Congrats! Yubiao. > > > - Penghui > > > On Mon, Nov 13, 2023 at 3:36 PM mattison chao > > wrote: > > > Dear Community, > > > > We are thrilled to announce that Yubiao Feng > > https://github.com/poorbarcode has been invited and has accepted the > > role > > of a member of the Apache Pulsar Project Management Committee (PMC). > > > > Yubiao Feng has proven to be an invaluable asset to our community, > > consistently showcasing dedication and active engagement through > > substantial contributions. Beyond his noteworthy technical input, > > Yubiao > > plays a crucial role in meticulously reviewing pull requests, thereby > > ensuring the overall excellence of our project. We eagerly anticipate > > and > > appreciate his ongoing contributions. On behalf of the Pulsar PMC, we > > extend a heartfelt welcome and congratulations to Yubiao Feng. > > > > Sincerely, > > Mattison > >
Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 1
+1 (non-binding) - Checked the sign and checksum - Build the source - Test SampleProducer and SampleConsumer Thanks, Baodi Shi On Nov 1, 2023 at 18:18:21, Yunze Xu wrote: > This is the first release candidate for Apache Pulsar Client C++, version > 3.4.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/5?closed=1 > > *** 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-client-cpp/pulsar-client-cpp-3.4.0-candidate-1/ > > SHA-512 checksums: > > > 85c2ae95bb3abb7c13326e1205c4dc9e339387d13efab242e51c044c53d322a65a28d32928ebe53202ea59f2df46a74480c4ef675e25adc64c14025dc3e314aa > ./apache-pulsar-client-cpp-3.4.0.tar.gz > > The tag to be voted upon: > v3.4.0-candidate-1 (272e1a1c78fd72d80758ac56ce400c67ce54d167) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.4.0-candidate-1 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Please download the source package, and follow the README to compile and > test. >
Re: [Discuss] Release Pulsar C++ Client 3.4.0
+1 Thanks, Baodi Shi On Oct 23, 2023 at 14:00:48, Zike Yang wrote: > +1, > > BR, > Zike Yang > > On Mon, Oct 23, 2023 at 1:10 PM PengHui Li wrote: > > > Thanks for driving the release, > > > +1 > > > Penghui > > > On Mon, Oct 23, 2023 at 11:00 AM Yunze Xu wrote: > > > > I would like to propose releasing the Pulsar C++ Client 3.4.0. It has > > > been about 3 months since the last release. There have been many new > > > features and bug fixes since then. > > > > > > Besides, from my own perspective, it's better to let Python and > > > Node.js clients depend on this new version of C++ client. Especially I > > > observed that the topic name was not shown correctly many times > > > recently, which are fixed by > > > https://github.com/apache/pulsar-client-cpp/pull/331 and > > > https://github.com/apache/pulsar-client-cpp/pull/329. > > > > > > So it's time to release a new version. Please let me know if you have > > > any PRs that need to be included in 3.4.0 > > > > > > Thanks, > > > Yunze > > > > >
[DISCUSS] Release Apache Pulsar 2.11.3
Hi all I would like to propose releasing the Pulsar 2.11.3 It's over one month since the release of 2.11.3, and there are 87 new commits. in branch-2.11: https://github.com/apache/pulsar/compare/v2.11.2...branch-2.11 We need to cut a new release. Please let me know if you have any important fixes that need to be included in Pulsar 2.11.3 Thanks, Baodi Shi
Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView
+1 (no-binding) Thanks, Baodi Shi On Oct 7, 2023 at 21:06:35, Yubiao Feng wrote: > +1 (no-binding) > > And correct the link of PIP: > - https://github.com/apache/pulsar/pull/21271 > > Thanks > Yubiao Feng > > On Wed, Sep 27, 2023 at 3:04 PM Xiangying Meng > wrote: > > Hi dev, > >This thread is to start a vote for PIP-302 Add new API > > refreshAsync for TableView. > > Discuss thread: > > https://lists.apache.org/thread/o085y2314o0fymvx0x8pojmgjwcwn59q > > PIP: https://github.com/apache/pulsar/pull/21166 > > > BR, > > Xiangying > > >
Re: [Discuss] Release RPM packages with cxx11 ABI
> > +1 Thanks, Baodi Shi On Sep 5, 2023 at 09:13:12, PengHui Li wrote: > +1 > > And if we can have a README file under the cpp client distribution > directory. > It should be great. Users can find the explanation of what legacy means. > > Regards, > Penghui > > On Mon, Sep 4, 2023 at 7:54 PM Yunze Xu wrote: > > Hi all, > > > Currently the official released pre-built binaries for Linux include: > > - RPM packages for RedHat-based Linux distros > > - DEB packages for Debian-based Linux distros > > - APK packages for Alpine-based Linux distros > > > Though they are provided in different Linux distributions, they are > > all compiled with GCC. However, only the RPM package is built with GCC > > < 5. GCC 5 brings a breaking ABI change [1] to the std::string, which > > is widely used in the Pulsar C++ client interfaces as the byte array. > > In short, the impact is, if you're using GCC >= 5 > > 1. You have to add the -D_GLIBCXX_USE_CXX11_ABI=0 compile option to > > use the pre-built RPM package. > > 2. If your application depends on other 3rd party libraries that are > > built with GCC >= 5, the pre-built RPM package cannot be used > > together. > > > So for users that use GCC >= 5, the current RPM package is very > > unfriendly especially for the 2nd case. As a workaround, they have to > > build libraries by themselves, while installing dependencies might be > > complicated in C++ world. > > > However, CentOS 7, whose EOL is 2024-06-30 [2], is still widely used. > > In addition, if you're going to upgrade your GCC via devtoolset, the > > installed GCC still does not have the cxx11 ABI [3]. So I don't think > > it's good to drop the support for old ABIs for RedHat users. > > > In short, I suggest adding separated pre-built binaries with new ABIs > > for RPM packages. The hierarchy will be: > > > rpm-arm64/aarch64/ RPMs with new ABIs > > rpm-arm64/aarch64/legacy RPMs with old ABIs > > rpm-x86_64/x86_64/ RPMs with new ABIs > > rpm-x86_64/x86_64/legacy RPMs with old ABIs > > > See [4] for the current hierarchy. > > > After that, we should document the difference here [5]. > > > [1] https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html > > [2] https://wiki.centos.org/About/Product > > [3] https://bugzilla.redhat.com/show_bug.cgi?id=1546704 > > [4] https://archive.apache.org/dist/pulsar/pulsar-client-cpp-3.3.0/ > > [5] https://pulsar.apache.org/docs/3.1.x/client-libraries-cpp-setup/ > > > Thanks, > > Yunze > > >
Re: [VOTE] PIP-297: Support terminating Function & Connector with the fatal exception
+1(non-binding) Thanks, Baodi Shi On Sep 5, 2023 at 05:23:38, Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il giorno lun 4 set 2023 alle ore 12:32 Zike Yang ha > scritto: > > > Hi, all > > > Since there are no other concerns in the discussion, I'm delighted to > > start the voting process for the PIP-297. > > > Here is the link to the PIP: https://github.com/apache/pulsar/pull/21079 > > > BR, > > Zike Yang > >
[ANNOUNCE] Apache Pulsar Client Python 3.3.0 released
The Apache Pulsar team is proud to announce Apache Pulsar Client Python version 3.3.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. You can download the source code and the Python wheels in: https://archive.apache.org/dist/pulsar/pulsar-client-python-3.3.0/ The Python wheels were uploaded to PyPI as well so that they can be installed by `pip install pulsar-client==3.3.0`. Release Notes are at: https://pulsar.apache.org/release-notes/versioned/client-python-3.3.0/ We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
Re: [VOTE] Pulsar Client Python Release 3.3.0 Candidate 1
Close this vote with 3(binding) - Matteo - Yunze - PengHui Thanks, Baodi Shi On Aug 29, 2023 at 01:50:25, Matteo Merli wrote: > +1 binding > > - Checked signatures > - Checked macos and linux wheel files. > > > -- > Matteo Merli > > > > On Sun, Aug 27, 2023 at 6:13 PM PengHui Li wrote: > > OS: macOS Ventura Version 13.4.1 (c) (22F770820d) > > Python: 3.11.4 > > > +1 (binding) > > > - Checked the signature > > - Build wheel from source > > - Run examples > > > Regards, > > Penghui > > > > On Mon, Aug 21, 2023 at 10:24 PM Yunze Xu wrote: > > > > +1 (binding) > > > > > > - Verified signature and checksums > > > - Build the wheel from source and run examples > > > - Run examples with the following wheels: > > > - Python 3.11 on macOS m1 > > > - Python 3.10 on Ubuntu 22.04 arm64 > > > > > > Thanks, > > > Yunze > > > > > > On Fri, Aug 18, 2023 at 10:25 AM Baodi Shi wrote: > > > > > > > > This is the Nth release candidate for Apache Pulsar Client Python, > > > > version 3.3.0. > > > > > > > > It fixes the following issues: > > > > https://github.com/apache/pulsar-client-python/milestone/4?closed=1 > > > > > > > > *** Please download, test and vote on this release. This vote will > > > > stay open for at least 72 hours *** > > > > > > > > Python wheels: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-python-3.3.0-candidate-1/ > > > > > > > > The supported python versions are 3.7, 3.8, 3.9, 3.10 and 3.11. The > > > > supported platforms and architectures are: > > > > - Windows x86_64 (windows/) > > > > - glibc-based Linux x86_64 (linux-glibc-x86_64/) > > > > - glibc-based Linux arm64 (linux-glibc-arm64/) > > > > - musl-based Linux x86_64 (linux-musl-x86_64/) > > > > - musl-based Linux arm64 (linux-musl-arm64/) > > > > - macOS universal 2 (macos/) > > > > > > > > You can download the wheel (the `.whl` file) according to your own OS > > and > > > > Python version > > > > and install the wheel: > > > > - Windows: `py -m pip install *.whl --force-reinstall` > > > > - Linux or macOS: `python3 -m pip install *.whl --force-reinstall` > > > > > > > > The tag to be voted upon: v3.3.0-candidate-1 > > > > (f445ceb) > > > > > > > > > > https://github.com/apache/pulsar-client-python/releases/tag/v3.3.0-candidate-1 > > > > > > > > Pulsar's KEYS file containing PGP keys you use to sign the release: > > > > https://downloads.apache.org/pulsar/KEYS > > > > > > > > Please download the Python wheels and follow the README to test. > > > > > > > > > > > > Thanks, > > > > Baodi Shi > > > > > >
[VOTE] Pulsar Client Python Release 3.3.0 Candidate 1
This is the Nth release candidate for Apache Pulsar Client Python, version 3.3.0. It fixes the following issues: https://github.com/apache/pulsar-client-python/milestone/4?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Python wheels: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-python-3.3.0-candidate-1/ The supported python versions are 3.7, 3.8, 3.9, 3.10 and 3.11. The supported platforms and architectures are: - Windows x86_64 (windows/) - glibc-based Linux x86_64 (linux-glibc-x86_64/) - glibc-based Linux arm64 (linux-glibc-arm64/) - musl-based Linux x86_64 (linux-musl-x86_64/) - musl-based Linux arm64 (linux-musl-arm64/) - macOS universal 2 (macos/) You can download the wheel (the `.whl` file) according to your own OS and Python version and install the wheel: - Windows: `py -m pip install *.whl --force-reinstall` - Linux or macOS: `python3 -m pip install *.whl --force-reinstall` The tag to be voted upon: v3.3.0-candidate-1 (f445ceb) https://github.com/apache/pulsar-client-python/releases/tag/v3.3.0-candidate-1 Pulsar's KEYS file containing PGP keys you use to sign the release: https://downloads.apache.org/pulsar/KEYS Please download the Python wheels and follow the README to test. Thanks, Baodi Shi
[Discuss] Release Pulsar Python Client 3.3.0
Hi all, I would like to propose releasing the Pulsar Python Client 3.3.0. It has been over 2 months since the last release (3.2.0). There have been some new features and bug fixes since then. It's time to release a new version. - https://github.com/apache/pulsar-client-python/milestone/4?closed=1 Please let me know if you have any PRs that need to be included in 3.3.0. Thanks, Baodi Shi
Re: [VOTE] PIP 289: Secure Pulsar Connector Configuration
+1(non-binding) Thanks, Baodi Shi On Aug 15, 2023 at 01:26:21, Enrico Olivelli wrote: > +1 (binding) > > Thanks > Enrico > > Il Gio 10 Ago 2023, 18:46 Michael Marshall ha > scritto: > > +1 (binding) > > > - Michael > > > On Thu, Aug 10, 2023 at 11:43 AM Michael Marshall > > wrote: > > > > > > Hi Pulsar Community, > > > > > > This is the vote thread for PIP 289: > > > https://github.com/apache/pulsar/pull/20903. > > > > > > This PIP will help improve Pulsar Connector Security by giving users > > > the ability to remove all plaintext secrets from their configurations. > > > > > > Thanks, > > > Michael > > >
Re: [DISCUSS] PIP 289: Secure Pulsar Connector Configuration
Hi, Sorry for the late reply. I think we can avoid adding a new config: interpolate_secrets_into_config_map. https://github.com/apache/pulsar/pull/20903#issuecomment-1674570878 Thanks, Baodi Shi On Aug 11, 2023 at 00:34:05, Michael Marshall wrote: > * Should we deprecate the old way of injecting secrets? It wasn't > > widely used, and it does not work in all cases. (See the PIP for the > > old mechanism.) > > > I propose we leave the old way of injecting secrets in place. This > will prevent unnecessary breaking changes. > > I'll add some new docs to make sure users understand what is available > to them for injecting secrets. > > * Should we enable environment variable interpolation by default? It > > carries some risk, but in a Kubernetes environment, that risk is > > limited. > > > Let's leave this disabled by default. We can revisit later if necessary. > > Thanks, > Michael > > On Fri, Jul 28, 2023 at 7:57 PM Michael Marshall > wrote: > > > Thanks for the question. I tried to find a way that would work using the > existing framework. Specifically, I looked into using the annotation that > is partially implemented in the connector code base. That annotation relies > on the getSecret method. > > > However, I don’t see a way to make this work for wrapped connectors, like > the Kafka Connect Adapter mentioned in the PIP. In that case, the wrapped > connector will have arbitrary secrets that we cannot know at compile time. > As such, I think we need a framework change that gives users arbitrarily > map in secrets at runtime. > > > Thanks, > > Michael > > > On Fri, Jul 28, 2023 at 7:42 PM Neng Lu wrote: > > > > > > Hi Michael, > > > > > > Thanks for writing the PIP for the connector secret issue. > > > > > > One question I have is why not reusing the `context.getSecret()` method > inside connectors to get sensitive values. > > > > > > In this way, no API/framework changes are needed and all we need to do > is update each connector to get the secret value with `context.getSecret()` > first. If nothing provided, then fall back to the plain text way. > > > > > > What do you think? > > > > > > On 2023/07/28 21:59:57 Michael Marshall wrote: > > > > Hi Pulsar Community, > > > > > > > > This is the discussion thread for PIP > > > > https://github.com/apache/pulsar/pull/20903. > > > > > > > > This PIP will help improve Pulsar Connector Security by giving users > > > > the ability to remove all plaintext secrets from their configurations. > > > > > > > > Thanks, > > > > Michael > > > > > >
Re: [DISCUSS] Generic Secret Injection for Sink/Source Configuration
Hi, Michael: I left some comments on the PR. if you could explain the implementation part in a little more detail. Thanks, Baodi Shi On Jul 29, 2023 at 05:57:40, Michael Marshall wrote: > * The PIP is https://github.com/apache/pulsar/pull/20903 > > - Michael > > On Fri, Jul 28, 2023 at 4:56 PM Michael Marshall > wrote: > > > After looking a bit closer at the requirements for this feature, I > > determined the above solution does not work because it won't work for > > nested configurations. > > > My new solution required a PIP: > https://github.com/apache/pulsar/issues/20862. > > > I'll start a new discussion thread. > > > Thanks, > > Michael > > > On Mon, Jul 24, 2023 at 5:33 PM Michael Marshall > wrote: > > > > > > Hi Pulsar Community, > > > > > > I would like to find a generic way to inject secrets into connector > > > configuration without needing to rewrite existing connectors. I > > > created this issue [0] to describe the current state of connector > > > secret management and to discuss potential solutions. I created [1] to > > > show my preferred solution. > > > > > > I don't think this change requires a PIP, but since it introduces a > > > new configuration, I am mentioning it on the mailing list. > > > > > > Thanks, > > > Michael > > > > > > [0] https://github.com/apache/pulsar/issues/20862 > > > [1] https://github.com/apache/pulsar/issues/20863 > >
Re: [VOTE] PIP-281: Add notifyError method on PushSource
Close this vote by 3 binding +1s - Penghui - Yunze - Jiwei And 2 non-binding +1s - Zike - Rui Thanks, Baodi Shi On Aug 2, 2023 at 10:47:32, guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Tue, Aug 1, 2023 at 10:24 AM Rui Fu wrote: > > +1 > > > Best, > > > Rui Fu > > On Jul 25, 2023 at 18:10 +0800, Baodi Shi , wrote: > > > Hello, > > > > > > This is the vote thread for PIP 281. > > > > > > PR: https://github.com/apache/pulsar/pull/20807 > > > Discussion: > > https://lists.apache.org/thread/dnmvcb5drvwhw4bpyq6x572hcdtyydfg > > > > > > The vote will be open for at least 48 hours. > > > > > > > > > Thanks, > > > Baodi Shi > > >
[VOTE] PIP-281: Add notifyError method on PushSource
Hello, This is the vote thread for PIP 281. PR: https://github.com/apache/pulsar/pull/20807 Discussion: https://lists.apache.org/thread/dnmvcb5drvwhw4bpyq6x572hcdtyydfg The vote will be open for at least 48 hours. Thanks, Baodi Shi
Re: [DISCUSS] PIP-281: Add notifyError method on PushSource
Hi, Penghui. Could you please help add a section to explain the compatibility guarantee? > Others look good to me. Added it, PTAL. Thanks, Baodi Shi On Jul 14, 2023 at 18:27:34, PengHui Li wrote: > Could you please help add a section to explain the compatibility guarantee? > Others look good to me. > > Regards, > Penghui > > On Fri, Jul 14, 2023 at 6:07 PM Baodi Shi wrote: > > Hi, All > > > I opened a new PIP design PR. > > I am looking forward to your feedback. > > > https://github.com/apache/pulsar/pull/20807 > > <https://github.com/apache/pulsar/pull/20776> > > > > > This is a very simple change and is forward-compatible. Sorry, I didn't > > notice that this change required PIP before, so the related PRs have been > > merged. > > > https://github.com/apache/pulsar/pull/20791 > > > If this PIP vote does not pass, I revert this PR afterward. > > > > > Thanks, > > Baodi Shi > > >
[DISCUSS] PIP-281: Add notifyError method on PushSource
Hi, All I opened a new PIP design PR. I am looking forward to your feedback. https://github.com/apache/pulsar/pull/20807 <https://github.com/apache/pulsar/pull/20776> This is a very simple change and is forward-compatible. Sorry, I didn't notice that this change required PIP before, so the related PRs have been merged. https://github.com/apache/pulsar/pull/20791 If this PIP vote does not pass, I revert this PR afterward. Thanks, Baodi Shi
[ANNOUNCE] Apache Pulsar Node.js client 1.9.0 released
The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.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 Node.js client release details and downloads, visit: https://www.npmjs.com/package/pulsar-client Release Notes are at: https://github.com/apache/pulsar-client-node/releases We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
Re: [VOTE] Pulsar Node.js Client Release 1.9.0 Candidate 1
Close the vote with 3(+1 binding) 1(+1 non-binding) 0(-1) binding: - Masahiro - Yunze - Penghui non-binding - Hideaki Thanks, Baodi Shi On Jul 10, 2023 at 09:34:21, PengHui Li wrote: > +1(binding) > > - Install from npm > - Run the produce and consume example [1] > > Regards, > Penghui > > [1] > > https://github.com/apache/pulsar-client-node/tree/v1.9.0-rc.1#getting-started > > On Fri, Jul 7, 2023 at 7:32 PM Yunze Xu wrote: > > +1 (binding) > > > - Verified checksum and signature > > - Build from source on macOS m1 with Node.js v20.4.0 > > - Run basic e2e examples > > > Two additional notes: > > 1. You should use https://downloads.apache.org/pulsar/KEYS instead of > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > 2. When building from the TAR source, you need to modify > > `pkg/mac/common.sh`. Change `ROOT_DIR=$(git rev-parse > > --show-toplevel)` to `ROOT_DIR=$PWD`. > > > Thanks, > > Yunze > > > On Fri, Jul 7, 2023 at 10:28 AM Masahiro Sakamoto > > wrote: > > > > > > +1 (binding) > > > > > > - verified checksum and signature > > > - confirmed that the build was successful > > > - ran produce/consume > > > > > > Regards, > > > > > > Masahiro Sakamoto > > > Yahoo Japan Corp. > > > E-mail: massa...@yahoo-corp.jp > > >
Re: [DISCUSS] Pluggable Pulsar Functions runtime to support new runtimes
Hi, Lari. Thanks for your proposal. Sounds good to me. Supporting function pluggable essentially decouples the scheduling layer and the computing layer. This can not only extend the function runtime in more languages but even use this feature to implement a new non-function runtime plugin, such as the EventSouring development model. Although pipelining (processing multiple in-flight messages) is possible > in current Pulsar Functions and Sinks, it often leads to complex and > error-prone solutions, especially when there's a need to combine > key-based ordered processing with retry and backoff implementations. At present, the scheduling logic of the function will not be related to the key of the message, I understand that it belongs to the internal feature of the runtime, and this can also be enhanced based on the current runtime? I don't quite understand what this has to do with runtime pluginization. Can you explain? In addition, the Pulsar Functions have a missing piece in how functions are > mapped to instances. It's not very efficient to even run each and every > function as a separate deployable entity. The cost of each independent JVMs > is high. It would be also better to have a model where where could be a > group of functions that are provided by one instance and always run > together. Having this option could bring down the cost and also improve the > developer experience. The framework shouldn't require the developer that > each individual function is deployed in a separate .jar file which gets run > in a separate JVM. This means that we need to enhance the function interface to that the user tells the runtime layer which topic the function subscription cares about. In addition, if we want to implement concurrent sequential processing based on keys, we can also let the function register the key of interest. These can be implemented in the current runtime, which has nothing to do with plug-in runtime, right? I wonder what are the future plans after plugging in the runtime? Do you want to develop a new runtime that implements many of the benefits you enumerate, or will you continue to enhance it on the original runtime (Java). Thanks, Baodi Shi On Jun 20, 2023 at 15:33:22, Lari Hotari wrote: > Dear Pulsar Community Members, > > I would like to initiate a discussion on making the Pulsar Functions > runtime "pluggable". In doing so, we can ensure that the addition of new > runtime types becomes more straightforward. > > This use case will allow us to add support for Pulsar Functions based on > various platforms such as: > > * Pulsar Client Reactive > * Node.js / JavaScript > * WebAssembly (WASM) > * Spring Pulsar & Reactive Spring > > One of the weak points in the current Pulsar Functions runtime is the > default handling of messages individually. Individual message processing > can be slow and inefficient in cases where the main function of the > Pulsar Function (or Sink) is to do backend API calls. > > Although pipelining (processing multiple in-flight messages) is possible > in current Pulsar Functions and Sinks, it often leads to complex and > error-prone solutions, especially when there's a need to combine > key-based ordered processing with retry and backoff implementations. > > The Reactive Pulsar Client provides an inbuilt solution for implementing > pipelining. With its ReactiveMessagePipelineBuilder, we can configure > concurrency levels with key-ordered processing support. This capability > could potentially eliminate the need to use key-shared subscriptions to > scale Pulsar processing. If a reactive Pulsar Function were primarily to > serve as a router for API calls, we could adjust the concurrency level > to hundreds or even thousands, provided the backend could handle the > load. > > With a pluggable Pulsar Functions runtime, we could introduce new > runtime types without the need for implementing each type in the > upstream project. This strategy could likely lead to new opportunities > for innovative ideas and contributions in this field. > > I am interested to know your thoughts on making the Pulsar Functions > runtime pluggable so that we can add new runtime types. > > Best Regards, > > -Lari >
[VOTE] Pulsar Node.js Client Release 1.9.0 Candidate 1
Hi everyone, This is the first release candidate for the Apache Pulsar Node.js client, version 1.9.0. It fixes the following issues: https://github.com/apache/pulsar-client-node/milestone/14?closed=1 Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md <https://readme.md/> to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.9.0-rc.1 <https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.1> You can install it by `npm i pulsar-client@1.9.0-rc.1 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.9.0-rc.1/ <https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.1-rc.2/> Pulsar's KEYS file containing the PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS SHA-512 checksum: 0cdf1d003061721565f27db19056843001d1153b79e4d7d907fff1eee53d8124e73a4174ed4d27466f59f52ae2ecbf1b9d6a3abe1b0465afeabc0022ee81b306 ./apache-pulsar-client-node-1.9.0.tar.gz The tag to be voted upon: v1.9.0-rc.1(affba83) https://github.com/apache/pulsar-client-node/releases/tag/v1.9.0-rc.1 <https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.1> Please review and vote on the release candidate #1 for the version 1.9.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: Change workflows run rule for outside collaborators of Go client
Hi,@tison, @Jarek Potiuk Thanks for your explanation, I got it. Thanks, Baodi Shi On Jun 29, 2023 at 18:17:24, Jarek Potiuk wrote: > There is this policy in place that handles it: > https://infra.apache.org/github-actions-policy.html > > It was announced a few months ago and several projects that saw that > "approve all" policy as unsustainable for their community got the policy > changed. > > Example ticket from Airflow: > https://issues.apache.org/jira/projects/INFRA/issues/INFRA-24200 with > justifications why we needed to reverse it and confirmation that we are > aware of the dangers mentioned in the policy and monitor if there is no > abuse happening. > > Projects that have a strong desire to use the “only require approval > > first time” option should communicate that, explaining their reasons, in a > Jira ticket for Infra. > > > On Thu, Jun 29, 2023 at 11:55 AM tison wrote: > > I remember it's an apache org-wise configuration. cc users@infra.a.o. > > > For now, non-committers can use personal CI tech like[1] to unblock CI > > verifications. And if anyone continues contributing and meets trouble with > > this inconvenience, I suggest we should nominate the contributor as > > committer to help he/she make contributions. > > > Best, > > tison. > > > [1] https://pulsar.apache.org/contribute/personal-ci/ > > > > Baodi Shi 于2023年6月29日周四 17:45写道： > > > > Hi, all. > > > > > > For now, non-committer PRs for Go clients do not run CI automatically and > > > require to committer approval every time. > > > > > > Can we modify this rule? Only first-time contributors need committer > > > approval. > > > > > > Who has permission to modify it? > > > > > > Thanks, > > > Baodi Shi > > > > > >
Change workflows run rule for outside collaborators of Go client
Hi, all. For now, non-committer PRs for Go clients do not run CI automatically and require to committer approval every time. Can we modify this rule? Only first-time contributors need committer approval. Who has permission to modify it? Thanks, Baodi Shi
[DISCUSS] Release Pulsar Node.js client v1.9.0
Hi all, I would like to propose releasing the Pulsar Node.js client v1.9.0 It has been over 2 months since the last release (1.8.2). There have been many new features and bug fixes since then. It's time to release a new version. - https://github.com/apache/pulsar-client-node/milestone/14?closed=1 Please let me know if you have any PRs that need to be included in 1.9.0. Thanks, Baodi Shi
Re: [VOTE] Pulsar Client C++ Release 3.2.0 Candidate 3
+1(non-binding) Verify: - SHA512 for source code. - Compilation on MacOS M1(13.2.1) - Run SampleProducer and SampleConsumer Thanks, Baodi Shi On May 7, 2023 at 10:53:32, Yunze Xu wrote: > This is the third release candidate for Apache Pulsar Client C++, version > 3.2.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/3?closed=1 > > *** 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-client-cpp/pulsar-client-cpp-3.2.0-candidate-3/ > > SHA-512 checksums: > > 4422088c9d16e91caf90f6991a0ca0e3a5f50328c3503acf90641b100fe72b1fef7bec782cc693b947d53841d61470a56175a29d27fb609b937a6f79486b > apache-pulsar-client-cpp-3.2.0.tar.gz > > The tag to be voted upon: > v3.2.0-candidate-3 (1dad87bb3b804d2aa8542ac48e4c35228ac2f1bf) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.2.0-candidate-3 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Please download the source package, and follow the README to compile and > test. >
Re: [VOTE] Pulsar Client C++ Release 3.2.0 Candidate 2
+1(non-binding) Verify: - SHA512 for source code. - Compilation on MacOS M1(13.2.1) - Run SampleProducer and SampleConsumer Thanks, Baodi Shi On May 5, 2023 at 15:27:44, Yunze Xu wrote: > This is the second release candidate for Apache Pulsar Client C++, > version 3.2.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/3?closed=1 > > *** 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-client-cpp/pulsar-client-cpp-3.2.0-candidate-2/ > > SHA-512 checksums: > > 0eebe4778f058cc350106f0be11ba0e0aed0769487ef6e870c7544872da0b34c57b3e711ad6ee3b05dd7352991508c9514f72940d74055ec96622b11d628a7bf > apache-pulsar-client-cpp-3.2.0.tar.gz > > The tag to be voted upon: > v3.2.0-candidate-2 (7127bef0974ac6d31c45d5aca10dd1ffe5ce7924) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.2.0-candidate-2 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Please download the source package, and follow the README to compile and > test. >
Re: [VOTE] Pulsar Client C++ Release 3.2.0 Candidate 1
Hi, yunze. I try to compile lib on MacOS by README[1], After compiling success, I not found `perf/perfProducer and `perf/perfConsumer`. Is it a documentation error? - [1] https://github.com/apache/pulsar-client-cpp#checks-1 Thanks, Baodi Shi On Apr 28, 2023 at 15:37:03, Yunze Xu wrote: > This is the first release candidate for Apache Pulsar Client C++, version > 3.2.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/3?closed=1 > > *** 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-client-cpp/pulsar-client-cpp-3.2.0-candidate-1/ > > SHA-512 checksums: > > ab3d676a6c95ddf09fcd09797ea913921c595d21a83594e3ee2c1432a8ab6190ddfcafd36c684e6e1a16737a52426a5ed74d887fa883781972b1536dc9580b5c > apache-pulsar-client-cpp-3.2.0.tar.gz > > The tag to be voted upon: > v3.2.0-candidate-1 (f3a037a49b8ba24270209e0830a7ce98a759c7c1) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.2.0-candidate-1 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Please download the source package, and follow the README to compile and > test. >
[ANNOUNCE] Apache Pulsar Node.js client 1.8.2 released
The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.8.2. 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 Node.js client release details and downloads, visit: https://www.npmjs.com/package/pulsar-client Release Notes are at: https://github.com/apache/pulsar-client-node/releases We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
[VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 4
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.8.2. It fixes the following issues: https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.4 You can install it by `npm i pulsar-client@1.8.2-rc.4 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. You can refer to this repository to verify tls related features: https://github.com/shibd/pulsar-client-tls-test The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.4/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/pulsar/KEYS SHA-512 checksum: 2bcfd0155abe653924d974839307c2bc980c982252e83c6442b1a368262057d4401eef186ec2b962ec973deedd81a899469ecee6afc61bd5718fa548c7c510ad ./apache-pulsar-client-node-1.8.2.tar.gz The tag to be voted upon: v1.8.2-rc.4(7b3de1f) https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.4 Please review and vote on the release candidate #1 for the version 1.8.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 3
Hi, @Oguni Hideaki Thanks for your feedback. How about cherry-picking this PR to address the high severity > vulnerabilities? > Sure, I’ll push 1.8.2-rc.4 latter. Let's wait another day and see if there is any other feedback. Thanks, Baodi Shi On Apr 13, 2023 at 17:46:23, Oguni Hideaki wrote: > Hi Baodi, > > I ran npm audit and it has detected the following vulnerabilities: > > ``` > $ npm audit > # npm audit report > > json5 <1.0.2 || >=2.0.0 <2.2.2 > Severity: high > Prototype Pollution in JSON5 via Parse Method - > https://github.com/advisories/GHSA-9c47-m6qq-7p4h > Prototype Pollution in JSON5 via Parse Method - > https://github.com/advisories/GHSA-9c47-m6qq-7p4h > fix available via `npm audit fix` > node_modules/@babel/core/node_modules/json5 > node_modules/json5 > > request * > Severity: moderate > Server-Side Request Forgery in Request - > https://github.com/advisories/GHSA-p8p7-x288-28g6 > fix available via `npm audit fix --force` > Will install dtslint@3.6.4, which is a breaking change > node_modules/request > @qiwi/npm-registry-client * > Depends on vulnerable versions of request > node_modules/@qiwi/npm-registry-client >@definitelytyped/utils >=0.0.88 >Depends on vulnerable versions of @qiwi/npm-registry-client >node_modules/@definitelytyped/utils > dtslint >=3.6.6 > Depends on vulnerable versions of @definitelytyped/utils > node_modules/dtslint > > 5 vulnerabilities (4 moderate, 1 high) > > To address issues that do not require attention, run: > npm audit fix > > To address all issues (including breaking changes), run: > npm audit fix --force > ``` > > How about cherry-picking this PR to address the high severity > vulnerabilities? > https://github.com/apache/pulsar-client-node/pull/270 > > Hideaki Oguni > Yahoo Japan Corp. > > -Original Message- > From: Hiroyuki Sakai > Reply-To: "dev@pulsar.apache.org" > Date: Thursday, April 13, 2023 16:09 > To: "dev@pulsar.apache.org" > Subject: Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 3 > >+1 (binding) > >* check the license headers >* build the source >* run producer/consumer with message listener (source/npm package) >* verify checksum and signatures > >== >Hiroyuki Sakai >Yahoo Japan Corp. >E-mail: hsa...@yahoo-corp.jp > > >From: Baodi Shi >Sent: Wednesday, April 12, 2023 18:12 >To: dev@pulsar.apache.org >Subject: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 3 > >Hi everyone, > >This is the first release candidate for Apache Pulsar Node.js client, >version 1.8.2. > >It fixes the following issues: > > https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed > >Please download the source files and review this release candidate: >- Download the source package, verify shasum and asc >- Follow the README.md <https://readme.md/<https://readme.md/>> to > build and run the Pulsar >Node.js client. > >The release candidate package has been published to the npm registry: > >https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.3< > https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.3> > >You can install it by `npm i pulsar-client@1.8.2-rc.3 >--pulsar_binary_host_mirror= >https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/%60< > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/%60> >and verify the package. > >You can refer to this repository to verify tls related features: > >https://github.com/shibd/pulsar-client-tls-test > >The vote will be open for at least 72 hours. It is adopted by majority >approval, with at least 3 PMC affirmative votes. > >Source files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.3/ > < > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.3/ > > > >Pulsar's KEYS file containing PGP keys we use to sign the release: >https://dist.apache.org/repos/dist/dev/pulsar/KEYS< > https://dist.apache.org/repos/dist/dev/pulsar/KEYS> > >SHA-512 checksum: > > > 98ff08092d3cd768a39499acac332cdec076a53b5521dad92c00810e8549165ede35eb3e2b1b6184265600e4e6a92356a2f142b1a1fa81d9c1461ac3c1e008f4 >./apache-pulsar-client-node-1.8.2.tar.gz > >The tag to be voted upon: >v1.8.2-rc.3(c8e7c41 >< > https://github.com/apache/pulsar-client-node/commit/c8e7c41ee72c8a8f33cf1599ab87d0eabf45753c > > >) >https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc. ><https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.2 > >3 > >Please review and vote on the release candidate #1 for the version >1.8.2, as follows: >[ ] +1, Approve the release >[ ] -1, Do not approve the release (please provide specific comments) > > >Thanks, >Baodi Shi > >
[VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 3
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.8.2. It fixes the following issues: https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md <https://readme.md/> to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.3 You can install it by `npm i pulsar-client@1.8.2-rc.3 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. You can refer to this repository to verify tls related features: https://github.com/shibd/pulsar-client-tls-test The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.3/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS SHA-512 checksum: 98ff08092d3cd768a39499acac332cdec076a53b5521dad92c00810e8549165ede35eb3e2b1b6184265600e4e6a92356a2f142b1a1fa81d9c1461ac3c1e008f4 ./apache-pulsar-client-node-1.8.2.tar.gz The tag to be voted upon: v1.8.2-rc.3(c8e7c41 <https://github.com/apache/pulsar-client-node/commit/c8e7c41ee72c8a8f33cf1599ab87d0eabf45753c> ) https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc. <https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.2>3 Please review and vote on the release candidate #1 for the version 1.8.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 2
Hi, tison. Thanks for your feedback. I noticed that the master branch also doesn't have NOTICE files. I'll add it first and then launch release 1.8.2-rc.3 Thanks, Baodi Shi On Apr 12, 2023 at 10:14:20, tison wrote: > Thank you! I can successfully run the example. > > However, -1 because the source release doesn't contain a NOTICE file. > > Other check items including LICENSE, license headers, checksum and GPG sign > should be fine. > > Best, > tison. > > > Baodi Shi 于2023年4月12日周三 09:48写道： > > This example connects test env. Maybe it's network latency or server > > instability. > > > You can try again. > > > BTW: The token expires in tls-token.js . I updated it, you can pull the > > main branch and try it. > > > Thanks, > > Baodi Shi > > > > On Apr 12, 2023 at 00:22:53, Zili Chen wrote: > > > > Hi Baodi, > > > > > > When running the tls test you provided, I encountered this error: > > > > > > $ node tls-oauth2.js > > > > > > [INFO][ClientConnection:190] [ -> pulsar+ssl:// > > > > > > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651 > > ] > > > Create ClientConnection, timeout=1 > > > [INFO][ConnectionPool:97] Created connection for pulsar+ssl:// > > > > > > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651 > > > [INFO][ClientConnection:388] [198.18.0.6:63458 -> 198.19.146.80:6651] > > > Connected to broker > > > [ERROR][ClientConnection:488] [198.18.0.6:63458 -> 198.19.146.80:6651] > > > Handshake failed: stream truncated > > > [INFO][ClientConnection:1600] [198.18.0.6:63458 -> 198.19.146.80:6651] > > > Connection closed with ConnectError > > > [ERROR][ClientImpl:184] Error Checking/Getting Partition Metadata while > > > creating producer on persistent://public/default/test-tls10 -- > > > ConnectError > > > [INFO][ClientConnection:269] [198.18.0.6:63458 -> 198.19.146.80:6651] > > > Destroyed connection > > > node:internal/process/promises:289 > > >triggerUncaughtException(err, true /* fromPromise */); > > >^ > > > > > > [Error: Failed to create producer: ConnectError] > > > > > > Node.js v19.8.1 > > > > > > $ node tls-token.js > > > > > > [INFO][ClientConnection:190] [ -> pulsar+ssl:// > > > > > > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651 > > ] > > > Create ClientConnection, timeout=1 > > > [INFO][ConnectionPool:97] Created connection for pulsar+ssl:// > > > > > > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651 > > > [INFO][ClientConnection:388] [198.18.0.6:63459 -> 198.19.146.80:6651] > > > Connected to broker > > > [ERROR][ClientConnection:488] [198.18.0.6:63459 -> 198.19.146.80:6651] > > > Handshake failed: stream truncated > > > [INFO][ClientConnection:1600] [198.18.0.6:63459 -> 198.19.146.80:6651] > > > Connection closed with ConnectError > > > [ERROR][ClientImpl:184] Error Checking/Getting Partition Metadata while > > > creating producer on persistent://public/default/test-tls10 -- > > > ConnectError > > > [INFO][ClientConnection:269] [198.18.0.6:63459 -> 198.19.146.80:6651] > > > Destroyed connection > > > node:internal/process/promises:289 > > >triggerUncaughtException(err, true /* fromPromise */); > > >^ > > > > > > [Error: Failed to create producer: ConnectError] > > > > > > Node.js v19.8.1 > > > > > > I don't know if it's because the Pulsar URL isn't public or other issues. > > > > > > Best, > > > tison. > > > > > > On 2023/04/11 15:21:37 Baodi Shi wrote: > > > > > > Hi everyone, > > > > > > > > > This is the first release candidate for Apache Pulsar Node.js client, > > > > > > version 1.8.2. > > > > > > > > > It fixes the following issues: > > > > > > > > > > > > https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed > > > > > > > > > Please download the source files and review this release candidate: > > > > > > - Download the source package, verify shasum and asc > > > > > > - Follow the README.md to build and run the Pu
Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 2
This example connects test env. Maybe it's network latency or server instability. You can try again. BTW: The token expires in tls-token.js . I updated it, you can pull the main branch and try it. Thanks, Baodi Shi On Apr 12, 2023 at 00:22:53, Zili Chen wrote: > Hi Baodi, > > When running the tls test you provided, I encountered this error: > > $ node tls-oauth2.js > > [INFO][ClientConnection:190] [ -> pulsar+ssl:// > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651] > Create ClientConnection, timeout=1 > [INFO][ConnectionPool:97] Created connection for pulsar+ssl:// > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651 > [INFO][ClientConnection:388] [198.18.0.6:63458 -> 198.19.146.80:6651] > Connected to broker > [ERROR][ClientConnection:488] [198.18.0.6:63458 -> 198.19.146.80:6651] > Handshake failed: stream truncated > [INFO][ClientConnection:1600] [198.18.0.6:63458 -> 198.19.146.80:6651] > Connection closed with ConnectError > [ERROR][ClientImpl:184] Error Checking/Getting Partition Metadata while > creating producer on persistent://public/default/test-tls10 -- > ConnectError > [INFO][ClientConnection:269] [198.18.0.6:63458 -> 198.19.146.80:6651] > Destroyed connection > node:internal/process/promises:289 >triggerUncaughtException(err, true /* fromPromise */); >^ > > [Error: Failed to create producer: ConnectError] > > Node.js v19.8.1 > > $ node tls-token.js > > [INFO][ClientConnection:190] [ -> pulsar+ssl:// > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651] > Create ClientConnection, timeout=1 > [INFO][ConnectionPool:97] Created connection for pulsar+ssl:// > baodi-test-7407d844-b456-49e1-987c-24f1a5c162cb.usce1-whale.test.g.sn2.dev:6651 > [INFO][ClientConnection:388] [198.18.0.6:63459 -> 198.19.146.80:6651] > Connected to broker > [ERROR][ClientConnection:488] [198.18.0.6:63459 -> 198.19.146.80:6651] > Handshake failed: stream truncated > [INFO][ClientConnection:1600] [198.18.0.6:63459 -> 198.19.146.80:6651] > Connection closed with ConnectError > [ERROR][ClientImpl:184] Error Checking/Getting Partition Metadata while > creating producer on persistent://public/default/test-tls10 -- > ConnectError > [INFO][ClientConnection:269] [198.18.0.6:63459 -> 198.19.146.80:6651] > Destroyed connection > node:internal/process/promises:289 >triggerUncaughtException(err, true /* fromPromise */); >^ > > [Error: Failed to create producer: ConnectError] > > Node.js v19.8.1 > > I don't know if it's because the Pulsar URL isn't public or other issues. > > Best, > tison. > > On 2023/04/11 15:21:37 Baodi Shi wrote: > > Hi everyone, > > > This is the first release candidate for Apache Pulsar Node.js client, > > version 1.8.2. > > > It fixes the following issues: > > > https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed > > > Please download the source files and review this release candidate: > > - Download the source package, verify shasum and asc > > - Follow the README.md to build and run the Pulsar Node.js client. > > > The release candidate package has been published to the npm registry: > > > https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.2 > > > You can install it by `npm i pulsar-client@1.8.2-rc.2 > > --pulsar_binary_host_mirror= > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` > > and verify the package. > > > You can refer to this repository to verify tls related features: > > > https://github.com/shibd/pulsar-client-tls-test > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > Source files: > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.2/ > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > SHA-512 checksum: > > > > 300cc86ab2fe0c433e818aa163f9646f7d23a6d26fd9dd8bcd61d375cfb69e9195eb4b13e37272f9c72a9e426a93f028c516e96546d60b0498f69bc4f9bb7276 > > ./apache-pulsar-client-node-1.8.2.tar.gz > > > The tag to be voted upon: > > v1.8.2-rc.2(c5fccfc) > > https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.2 > > > Please review and vote on the release candidate #1 for the version > > 1.8.2, as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > Thanks, > > Baodi Shi > > >
Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1
Hi, all The 1.8.2-rc.2 has been released. Please help verify it. It contains the following two PRs: - https://github.com/apache/pulsar-client-node/pull/316 - https://github.com/apache/pulsar-client-node/pull/309 https://lists.apache.org/thread/72240tgq5bct78rdslzc689w6h9nb8z0 Thanks, Baodi Shi On Apr 11, 2023 at 18:04:39, Zike Yang wrote: > Hi, all > > I have created a PR > https://github.com/apache/pulsar-client-node/pull/316 for that issue. > PTAL and help review. > > Thanks, > Zike Yang > > On Tue, Apr 11, 2023 at 5:57 PM Baodi Shi wrote: > > > Hi, @Nozomi Kurihara > > > Ok, We can wait for this issue fixed > > https://github.com/apache/pulsar-client-node/issues/315. > > > > Thanks, > > Baodi Shi > > > > On Apr 11, 2023 at 17:54:56, Nozomi Kurihara wrote: > > > > Hi Baodi, Zike, > > > > > > Thank you for clarifying the issue status. > > > Although this is not a regression bug, I prefer including the fix to the > > > current 1.8.2 release since it is easily reproducible and causes > unlimited > > > memory usage increase. > > > > > > Thanks, > > > Nozomi > > > > > > 2023年4月11日(火) 18:01 Zike Yang : > > > > > > Hi, > > > > > > > > > https://github.com/apache/pulsar-client-node/issues/308 is not a > > > > > > regression bug. I don't think we need to block this RC. > > > > > > > > > > May you share the link to the issue? There seems no such reference in > > > > > > PR-309. > > > > > > > > > I have created an issue to track it: > > > > > > https://github.com/apache/pulsar-client-node/issues/315 > > > > > > > > > But if you all want to include that fix, I can push a PR soon. > > > > > > > > > Thanks, > > > > > > Zike Yang > > > > > > > > > On Tue, Apr 11, 2023 at 4:29 PM tison wrote: > > > > > > > > > > > > > > Hi Baodi, > > > > > > > > > > > > > > > there is one Reader related issue > > > > > > > > > > > > > > May you share the link to the issue? There seems no such reference in > > > > > > > PR-309. > > > > > > > > > > > > > > Best, > > > > > > > tison. > > > > > > > > > > > > > > > > > > > > > Baodi Shi 于2023年4月11日周二 16:17写道： > > > > > > > > > > > > > > > Hi, > > > > > > > > I noticed that there is one Reader related issue for this that needs > > > > > > to be > > > > > > > > fixed, so I guess it could be included in 1.8.3. > > > > > > > > > > > > > > > > Thanks > > > > > > > > Baodi Shi > > > > > > > > > > > > > > > > On Tue, Apr 11, 2023 at 15:39 Nozomi Kurihara > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Baodi, > > > > > > > > > > > > > > > > > > Thank you for starting the release process. > > > > > > > > > > > > > > > > > > I think https://github.com/apache/pulsar-client-node/pull/309 > seems > > > > > > an > > > > > > > > > important fix. > > > > > > > > > Should we include it in the 1.8.2 release or postpone it to the > next > > > > > > > > > release? > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Nozomi > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > Thanks > > > > > > > > Baodi Shi > > > > > > > > > > > > > > > > > > >
[VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 2
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.8.2. It fixes the following issues: https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.2 You can install it by `npm i pulsar-client@1.8.2-rc.2 --pulsar_binary_host_mirror=https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. You can refer to this repository to verify tls related features: https://github.com/shibd/pulsar-client-tls-test The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.2/ Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS SHA-512 checksum: 300cc86ab2fe0c433e818aa163f9646f7d23a6d26fd9dd8bcd61d375cfb69e9195eb4b13e37272f9c72a9e426a93f028c516e96546d60b0498f69bc4f9bb7276 ./apache-pulsar-client-node-1.8.2.tar.gz The tag to be voted upon: v1.8.2-rc.2(c5fccfc) https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.2 Please review and vote on the release candidate #1 for the version 1.8.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1
Hi, @Nozomi Kurihara Ok, We can wait for this issue fixed https://github.com/apache/pulsar-client-node/issues/315. Thanks, Baodi Shi On Apr 11, 2023 at 17:54:56, Nozomi Kurihara wrote: > Hi Baodi, Zike, > > Thank you for clarifying the issue status. > Although this is not a regression bug, I prefer including the fix to the > current 1.8.2 release since it is easily reproducible and causes unlimited > memory usage increase. > > Thanks, > Nozomi > > 2023年4月11日(火) 18:01 Zike Yang : > > Hi, > > > https://github.com/apache/pulsar-client-node/issues/308 is not a > > regression bug. I don't think we need to block this RC. > > > > May you share the link to the issue? There seems no such reference in > > PR-309. > > > I have created an issue to track it: > > https://github.com/apache/pulsar-client-node/issues/315 > > > But if you all want to include that fix, I can push a PR soon. > > > Thanks, > > Zike Yang > > > On Tue, Apr 11, 2023 at 4:29 PM tison wrote: > > > > > > Hi Baodi, > > > > > > > there is one Reader related issue > > > > > > May you share the link to the issue? There seems no such reference in > > > PR-309. > > > > > > Best, > > > tison. > > > > > > > > > Baodi Shi 于2023年4月11日周二 16:17写道： > > > > > > > Hi, > > > > I noticed that there is one Reader related issue for this that needs > > to be > > > > fixed, so I guess it could be included in 1.8.3. > > > > > > > > Thanks > > > > Baodi Shi > > > > > > > > On Tue, Apr 11, 2023 at 15:39 Nozomi Kurihara > > wrote: > > > > > > > > > Hi Baodi, > > > > > > > > > > Thank you for starting the release process. > > > > > > > > > > I think https://github.com/apache/pulsar-client-node/pull/309 seems > > an > > > > > important fix. > > > > > Should we include it in the 1.8.2 release or postpone it to the next > > > > > release? > > > > > > > > > > Thanks, > > > > > Nozomi > > > > > > > > > -- > > > > > > > > Thanks > > > > Baodi Shi > > > > > > >
Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1
Hi, I noticed that there is one Reader related issue for this that needs to be fixed, so I guess it could be included in 1.8.3. Thanks Baodi Shi On Tue, Apr 11, 2023 at 15:39 Nozomi Kurihara wrote: > Hi Baodi, > > Thank you for starting the release process. > > I think https://github.com/apache/pulsar-client-node/pull/309 seems an > important fix. > Should we include it in the 1.8.2 release or postpone it to the next > release? > > Thanks, > Nozomi > -- Thanks Baodi Shi
[VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 1
Hi everyone, This is the first release candidate for Apache Pulsar Node.js client, version 1.8.2. It fixes the following issues: https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed <https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.1+is%3Aclosed> Please download the source files and review this release candidate: - Download the source package, verify shasum and asc - Follow the README.md <https://readme.md/> to build and run the Pulsar Node.js client. The release candidate package has been published to the npm registry: https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.1 You can install it by `npm i pulsar-client@1.8.2-rc.1 --pulsar_binary_host_mirror= https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and verify the package. You can refer to this repository to verify tls related features: - https://github.com/shibd/pulsar-client-tls-test The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.1/ <https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.1-rc.2/> Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS SHA-512 checksum: 2181fb2ebe22c806b8aaf4d3700c61bd2c6a8d240462bf5f870c16a882d1ca9fc3f164e3c139900145934e68f14f21cbaaeb232157f76f6c92e627dced3e861e ./apache-pulsar-client-node-1.8.2.tar.gz The tag to be voted upon: v1.8.2-rc.1(769d7cc) https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.1 Please review and vote on the release candidate #1 for the version 1.8.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Thanks, Baodi Shi
[DISCUSS] Release Pulsar Node.js Client 1.8.2
Hi everyone, I would like to propose releasing the Pulsar Node.js Client v1.8.2. The current latest version (v1.8.1) has a serious problem - It does not run in Node.js version greater than 16 (Linux environment)[0]. - Also, it's not compatible with Alpine 3.15[1]. [0] https://github.com/apache/pulsar-client-node/pull/310 [1] https://github.com/apache/pulsar-client-node/issues/299 Thanks, Baodi Shi
Re: [ANNOUNCE] Qiang Zhao as new PMC member in Apache Pulsar
Congrats! Qiang. Thanks, Baodi Shi 在 2023年3月29日 11:27:58 上，Horizon <1060026...@qq.com.invalid> 写道： > Congrats! > > 2023年3月29日 11:24，tison 写道： > > > Congrats! > > >
Re: [VOTE] Pulsar Client Go Release 0.10.0 Candidate 1
+1(non-binding) - Checked the signature - Verify producer, consumer, and reader examples on README. Thanks, Baodi Shi 在 2023年3月27日 20:23:28 上，Zike Yang 写道： > Hi everyone, > Please review and vote on the release candidate #1 for the version > 0.10.0, as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This is the first release candidate for Apache Pulsar Go client, version > 0.10.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-go/milestone/12?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/997 > - 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.10.0-candidate-1/ > > The tag to be voted upon: > v0.10.0 > https://github.com/apache/pulsar-client-go/tree/v0.10.0-candidate-1 > > SHA-512 checksums: > > 5f26d95061eb535595043ffc23424d9913f11d1b80ca815bdd20577453f6e08c2a5dd8b729d82494c4f5d0260905b231218c6a437995d893c4c25efdb0bb > apache-pulsar-client-go-0.10.0-src.tar.gz > > Zike Yang >
Re: [DISCUSS] PIP-258: Deprecation of the consumer subscribeTopicMode configuration
>
> I think we don't need to do such changes. Instead, we should fix the
> documentation of `ConsumerBuilder#topicsPattern`. From the
> implementation here [1], the prefix before "://" in the topic pattern
> should be ignored.
>
Agree, We can also add the warn log when the user-configured pattern
contains a domain(‘persistent://public/default/topic
.*')
We can close that PIP and discuss.
Thanks,
Baodi Shi
在 2023年3月24日 19:40:15 上，Yunze Xu 写道：
> I think we don't need to do such changes. Instead, we should fix the
> documentation of `ConsumerBuilder#topicsPattern`. From the
> implementation here [1], the prefix before "://" in the topic pattern
> should be ignored.
>
> [1]
> https://github.com/apache/pulsar/blob/f1f8dab972b098be69ad35ab3d307f19284c4e48/pulsar-common/src/main/java/org/apache/pulsar/common/topics/TopicList.java#L56
>
> Thanks,
> Yunze
>
> On Mon, Mar 20, 2023 at 9:32 AM Baodi Shi wrote:
>
>
> >
>
> > Should we state in the PIP which version it will be removed?
>
> >
>
>
> I think adding is best, but I'm not quite sure which version we should be
>
> specific to. How about v3.2.0? Wait for 2 major versions (3.0.0 and 3.1.0)
>
>
> Thanks,
>
> Baodi Shi
>
>
>
> 在 2023年3月17日 15:16:19 上，Zike Yang 写道：
>
>
> > LGTM. +1
>
> > It will make the API clearer without bringing breaking changes.
>
> >
>
> > After the configuration is removed in subsequent versions, it will be
>
> > clearer
>
> >
>
> >
>
> > Should we state in the PIP which version it will be removed?
>
> >
>
> > Thanks,
>
> > Zike Yang
>
> >
>
> > On Fri, Mar 17, 2023 at 8:50 AM Baodi Shi wrote:
>
> >
>
> >
>
> > Hi, Any ideas please discuss, thanks.
>
> >
>
> >
>
> > Thanks,
>
> >
>
> > Baodi Shi
>
> >
>
> >
>
> >
>
> > 在 2023年3月13日 22:24:09 上，Baodi Shi 写道：
>
> >
>
> >
>
> > > Hi all,
>
> >
>
> > >
>
> >
>
> > > I've started a PIP to discuss: PIP-258: Deprecation of the consumer
>
> >
>
> > > subscribeTopicMode configuration
>
> >
>
> > >
>
> >
>
> > > ### Motivation
>
> >
>
> > >
>
> >
>
> > > About pattern subscribes of consumers, the `topicsPattern` and
>
> >
>
> > > `subscribeTopicMode` configurations are contradictory.
>
> >
>
> > >
>
> >
>
> > > For example, the `topicsPattern` represents only subscription to
>
> >
>
> > > `persistent topic`, but the `subscriptionTopicsMode` represents
>
> >
>
> > > subscription to `all topic`.
>
> >
>
> > >
>
> >
>
> > > ``` java
>
> >
>
> > > Pattern pattern =
>
> >
>
> > > Pattern.compile("persistent://my-property/my-ns/pattern-topic.*");
>
> >
>
> > > Consumer consumer = pulsarClient.newConsumer()
>
> >
>
> > > .topicsPattern(pattern)
>
> >
>
> > > .subscriptionTopicsMode(RegexSubscriptionMode.AllTopics)
>
> >
>
> > > .build();
>
> >
>
> > > ```
>
> >
>
> > >
>
> >
>
> > > Finally, `all topics` are subscribed. It's very confusing.
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > For more details, please read the PIP at
>
> >
>
> > > https://github.com/apache/pulsar/issues/19798
>
> >
>
> > > <https://github.com/apache/pulsar/issues/19601>
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Thanks,
>
> >
>
> > > Baodi Shi
>
> >
>
> > >
>
> >
>
> >
>
>
Re: [DISCUSS] PIP-258: Deprecation of the consumer subscribeTopicMode configuration
>
> Should we state in the PIP which version it will be removed?
>
I think adding is best, but I'm not quite sure which version we should be
specific to. How about v3.2.0? Wait for 2 major versions (3.0.0 and 3.1.0)
Thanks,
Baodi Shi
在 2023年3月17日 15:16:19 上，Zike Yang 写道：
> LGTM. +1
> It will make the API clearer without bringing breaking changes.
>
> After the configuration is removed in subsequent versions, it will be
> clearer
>
>
> Should we state in the PIP which version it will be removed?
>
> Thanks,
> Zike Yang
>
> On Fri, Mar 17, 2023 at 8:50 AM Baodi Shi wrote:
>
>
> Hi, Any ideas please discuss, thanks.
>
>
> Thanks,
>
> Baodi Shi
>
>
>
> 在 2023年3月13日 22:24:09 上，Baodi Shi 写道：
>
>
> > Hi all,
>
> >
>
> > I've started a PIP to discuss: PIP-258: Deprecation of the consumer
>
> > subscribeTopicMode configuration
>
> >
>
> > ### Motivation
>
> >
>
> > About pattern subscribes of consumers, the `topicsPattern` and
>
> > `subscribeTopicMode` configurations are contradictory.
>
> >
>
> > For example, the `topicsPattern` represents only subscription to
>
> > `persistent topic`, but the `subscriptionTopicsMode` represents
>
> > subscription to `all topic`.
>
> >
>
> > ``` java
>
> > Pattern pattern =
>
> > Pattern.compile("persistent://my-property/my-ns/pattern-topic.*");
>
> > Consumer consumer = pulsarClient.newConsumer()
>
> > .topicsPattern(pattern)
>
> > .subscriptionTopicsMode(RegexSubscriptionMode.AllTopics)
>
> > .build();
>
> > ```
>
> >
>
> > Finally, `all topics` are subscribed. It's very confusing.
>
> >
>
> >
>
> > For more details, please read the PIP at
>
> > https://github.com/apache/pulsar/issues/19798
>
> > <https://github.com/apache/pulsar/issues/19601>
>
> >
>
> >
>
> > Thanks,
>
> > Baodi Shi
>
> >
>
>
Re: [DISCUSS] PIP-258: Deprecation of the consumer subscribeTopicMode configuration
Hi, Any ideas please discuss, thanks.
Thanks,
Baodi Shi
在 2023年3月13日 22:24:09 上，Baodi Shi 写道：
> Hi all,
>
> I've started a PIP to discuss: PIP-258: Deprecation of the consumer
> subscribeTopicMode configuration
>
> ### Motivation
>
> About pattern subscribes of consumers, the `topicsPattern` and
> `subscribeTopicMode` configurations are contradictory.
>
> For example, the `topicsPattern` represents only subscription to
> `persistent topic`, but the `subscriptionTopicsMode` represents
> subscription to `all topic`.
>
> ``` java
> Pattern pattern =
> Pattern.compile("persistent://my-property/my-ns/pattern-topic.*");
> Consumer consumer = pulsarClient.newConsumer()
> .topicsPattern(pattern)
> .subscriptionTopicsMode(RegexSubscriptionMode.AllTopics)
> .build();
> ```
>
> Finally, `all topics` are subscribed. It's very confusing.
>
>
> For more details, please read the PIP at
> https://github.com/apache/pulsar/issues/19798
> <https://github.com/apache/pulsar/issues/19601>
>
>
> Thanks,
> Baodi Shi
>
[DISCUSS] PIP-258: Deprecation of the consumer subscribeTopicMode configuration
Hi all,
I've started a PIP to discuss: PIP-258: Deprecation of the consumer
subscribeTopicMode configuration
### Motivation
About pattern subscribes of consumers, the `topicsPattern` and
`subscribeTopicMode` configurations are contradictory.
For example, the `topicsPattern` represents only subscription to
`persistent topic`, but the `subscriptionTopicsMode` represents
subscription to `all topic`.
``` java
Pattern pattern =
Pattern.compile("persistent://my-property/my-ns/pattern-topic.*");
Consumer consumer = pulsarClient.newConsumer()
.topicsPattern(pattern)
.subscriptionTopicsMode(RegexSubscriptionMode.AllTopics)
.build();
```
Finally, `all topics` are subscribed. It's very confusing.
For more details, please read the PIP at
https://github.com/apache/pulsar/issues/19798
<https://github.com/apache/pulsar/issues/19601>
Thanks,
Baodi Shi
Re: [DISCUSS] PIP 194 : Pulsar client: seek command add epoch
Any updates on this? On 2022/09/11 04:18:07 Qiang Huang wrote: > Hi Asaf, thank you for the very detailed reply. > > > The problem we have today is that while we have sent a request to reset > the subscription position, the broker decides to: > > 1. Close the TCP connection which in turn causes the client to clear any > pending messages it has in the queue. > > 2. Continue to send messages from the previous position, up to a certain > point where the broker "shifts gear" and starts sending messages from the > new position. > > > Since Pulsar doesn't follow a request-response model but has a > bi-directional protocol, the client can send a command to fetch messages > using a new session > > sequence number, while the server can still send messages using the old > session number. Using the Session Sequence Number the client can't tell the > > difference between the messages being pushed from the server to it. > I totally agree with you. I am aware of something wrong in the pip when I > re-read this part of the code. > > > > # What are the issues with this PIP? > > 1. The PIP decides to solve the problem listed above *only* for exclusive > > and failover subscriptions where you have only a single consumer. The > > problem still remains at large with Shared or Key Shared subscriptions. > > 2. The cost of solving a small portion of the problem is high: > > Added Complexity - Adding another field to the protocol, and another > > thing to check. I believe we should aim to reduce the cognitive load of > the > > developers of Pulsar. > > 3. There are no rejected solutions - We always need to examine all > > available options and list why we decided against them. > > 4. Lack of background knowledge (context) - it's super hard IMO to grasp > > the idea without so much context missing: The client-server protocol > > pertaining to this PIP, including its async nature, what is an epoch and > > why it was introduced, what are flow permits. I'm not saying explain all > > pulsar in this doc, but just include a brief explanation of that > terminology. > > > > # What We Suggest > > > > Rethink the solution. > > 1. The consumer (one of many) will send a seek command to the broker, and > > at the same time clear its internal queue and wait for a response from the > > broker. > > 2. The broker upon receiving the seek command, will > > a. Stop sending dispatching messages to consumers. > > b. Notify all consumers via a command (new) that the subscription > > position was asked to be reset. Consumers receiving this command will > clear > > their internal queue. The broker will no longer close the TCP connection > > (with its adverse effects on other consumers and produces "riding" on that > > connection) > > c. Reset the cursor to the newly requested position. > > d. Continue dispatching messages from newly requested positions to > consumers. > > > > Good suggestions. I'll look into these issues and rethink the solution. I > will rewrite this pip according to your suggestions. > Thanks again for your review. > > Asaf Mesika 于2022年9月7日周三 23:12写道： > > > Hi Qiang, > > > > We have a brainstorming session on this PIP over Zoom with Penghui, Hang, > > and more people, and I'm jotting down here our feedback. > > > > Before I do that, I just want to write my own understanding of the > > document, for other readers: > > > > # Context > > Pulsar, as opposed to other distributed / streaming systems, took the > > approach of a push model. The client (consumer that is) asks for 1000 > > messages (that's the consumer's remaining capacity in its internal queue) > > from the broker (that process is named flow permits). The broker was now > > given permission to send 1000 messages to the client, hence utilizing the > > TCP connection to send those 1000 messages as they were ready to be sent. > > > > The consumer has the ability to request the subscription to reset its > > position to the requested new position. > > The problem we have today is that while we have sent a request to reset the > > subscription position, the broker decides to: > > 1. Close the TCP connection which in turn causes the client to clear any > > pending messages it has in the queue. > > 2. Continue to send messages from the previous position, up to a certain > > point where the broker "shifts gear" and starts sending messages from the > > new position. > > > > So the problem is that you would expect that after the connection was > > reset, only messages from the new position will be sent to the consumer, > > but that doesn't happen. > > > > We have to keep in mind, that we have effectively two scenarios here from > > the point of view of the consumer: > > 1. Single consumer - It can be due to using an Exclusive subscription, or > > being a consumer attached to a single topic since the subscription is of > > type Failover. > > 2. Multiple consumers - In a Shared or Key Shared subscription types. In > > this case, one of those consumers can
[ANNOUNCE] Apache Pulsar Node.js client 1.8.1 released
The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.8.1. 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 Node.js client release details and downloads, visit: https://www.npmjs.com/package/pulsar-client Release Notes are at: https://github.com/apache/pulsar-client-node/releases We would like to thank the contributors that made the release possible. Regards, The Pulsar Team Thanks, Baodi Shi
Re: [DISCUSS] Release Pulsar Go Client 0.10.0
Hi, zike. The current pulsar-client-go master branch has some flay-test. There may be some internal bugs, I think we need to wait for them to be fixed. - https://github.com/apache/pulsar-client-go/issues/971 Thanks, Baodi Shi 在 2023年3月1日 20:26:10 上，Zike Yang 写道： > I will include this PR > https://github.com/apache/pulsar-client-go/pull/968 to this release > since it's an important performance improvement. > > BR, > Zike Yang > > On Wed, Mar 1, 2023 at 8:25 PM Zike Yang wrote: > > > Hi everyone, > > > I would like to propose releasing the Pulsar Go Client 0.10.0. > > > It has been several months since the last release. And there are > > several new features and bug fixes in the master branch[0]. It’s time > > to release a new version. > > > Please let me know if you have any PRs that need to be included in 0.10.0 > > > [0] https://github.com/apache/pulsar-client-go/compare/v0.9.0...master > > > BR, > > Zike Yang > >
Re: [DISCUSS] The GET_TOPICS_OF_NAMESPACE command should filter out system topics
Have another problem: If the transaction is enabled, the transaction-related system topic will return by the client(__transaction_buffer_snapshot, __transaction_buffer_snapshot_segments, __transaction_buffer_snapshot_indexes). I see this PR[1] filters some transaction-related topics, but these are missing. Is there a reason? /cc @丛搏 - https://github.com/apache/pulsar/pull/16533/files#r1120225388 Thanks, Baodi Shi 在 2023年2月28日 22:37:42 上，Baodi Shi 写道： > Yes, we can wait for the v2.11.1 release. > > > Thanks, > Baodi Shi > > > 在 2023年2月28日 22:25:39 上，Yunze Xu 写道： > >> I agree with Enrico that we should revert this change in 2.11. BTW, I >> see https://github.com/apache/pulsar-client-go/pull/969 tried to >> upgrade the Pulsar version to 2.11 for Go client. I think we'd better >> skip this version. There is no need to upgrade the server version >> unless we have to add a new feature that depends on the new version of >> Pulsar. >> >> Thanks, >> Yunze >> >> On Tue, Feb 28, 2023 at 9:38 PM Enrico Olivelli >> wrote: >> >> >> Baodi, >> >> >> Il giorno mar 28 feb 2023 alle ore 05:58 Baodi Shi >> >> ha scritto: >> >> > >> >> > Hi, >> >> > >> >> > In v2.11.0, the system topic enables by default [1]. This causes the >> >> > `GET_TOPICS_OF_NAMESPACE ` command to redundantly return the system >> topic. >> >> > >> >> > This causes some incompatibility issues: If consumers use pattern >> subscribe >> >> > and the pattern is `/tenant/namespace/.*`, it will subscribe >> >> > `__change_events` topic. >> >> > >> >> > I suggest that GET_TOPICS_OF_NAMESPACE should filter out system >> topics(or >> >> > add include-system-topic param, like the HTTP interface[2]) to maintain >> >> > consistent behavior with versions before 2.11.0 >> >> >> I agree that the behaviour must be consistent with previous versions. >> >> >> This is a fix that we should do on 2.11.1, otherwise users upgrading >> >> from 2.10 will have a >> >> bad surprise. >> >> >> Enrico >> >> >> > >> >> > >> >> > Refer: >> >> > - [1] https://github.com/apache/pulsar/pull/15619 >> >> > - [2] https://github.com/apache/pulsar/pull/15410 >> >> > >> >> > >> >> > Thanks, >> >> > Baodi Shi >> >>
Re: [DISCUSS] The GET_TOPICS_OF_NAMESPACE command should filter out system topics
Yes, we can wait for the v2.11.1 release. Thanks, Baodi Shi 在 2023年2月28日 22:25:39 上，Yunze Xu 写道： > I agree with Enrico that we should revert this change in 2.11. BTW, I > see https://github.com/apache/pulsar-client-go/pull/969 tried to > upgrade the Pulsar version to 2.11 for Go client. I think we'd better > skip this version. There is no need to upgrade the server version > unless we have to add a new feature that depends on the new version of > Pulsar. > > Thanks, > Yunze > > On Tue, Feb 28, 2023 at 9:38 PM Enrico Olivelli > wrote: > > > Baodi, > > > Il giorno mar 28 feb 2023 alle ore 05:58 Baodi Shi > > ha scritto: > > > > > > Hi, > > > > > > In v2.11.0, the system topic enables by default [1]. This causes the > > > `GET_TOPICS_OF_NAMESPACE ` command to redundantly return the system > topic. > > > > > > This causes some incompatibility issues: If consumers use pattern > subscribe > > > and the pattern is `/tenant/namespace/.*`, it will subscribe > > > `__change_events` topic. > > > > > > I suggest that GET_TOPICS_OF_NAMESPACE should filter out system topics(or > > > add include-system-topic param, like the HTTP interface[2]) to maintain > > > consistent behavior with versions before 2.11.0 > > > I agree that the behaviour must be consistent with previous versions. > > > This is a fix that we should do on 2.11.1, otherwise users upgrading > > from 2.10 will have a > > bad surprise. > > > Enrico > > > > > > > > > > Refer: > > > - [1] https://github.com/apache/pulsar/pull/15619 > > > - [2] https://github.com/apache/pulsar/pull/15410 > > > > > > > > > Thanks, > > > Baodi Shi > >
[DISCUSS] The GET_TOPICS_OF_NAMESPACE command should filter out system topics
Hi, In v2.11.0, the system topic enables by default [1]. This causes the `GET_TOPICS_OF_NAMESPACE ` command to redundantly return the system topic. This causes some incompatibility issues: If consumers use pattern subscribe and the pattern is `/tenant/namespace/.*`, it will subscribe `__change_events` topic. I suggest that GET_TOPICS_OF_NAMESPACE should filter out system topics(or add include-system-topic param, like the HTTP interface[2]) to maintain consistent behavior with versions before 2.11.0 Refer: - [1] https://github.com/apache/pulsar/pull/15619 - [2] https://github.com/apache/pulsar/pull/15410 Thanks, Baodi Shi
