Re: [VOTE] PIP-359: Support custom message listener executor for specific subscription

[guo jiwei]

+1 binding


Regards
Jiwei Guo (Tboy)


On Fri, Jul 5, 2024 at 6:05 PM Haiting Jiang  wrote:

> +1 binding
>
> Thanks,
> Haiting
>
> On Wed, Jun 19, 2024 at 9:45 PM Yubiao Feng
>  wrote:
> >
> > +1 (binding)
> >
> > Thanks
> > Yubiao Feng
> >
> > On Wed, Jun 19, 2024 at 12:45 AM Aurora Twinkle <
> foreverlove...@gmail.com>
> > wrote:
> >
> > > Hi, Pulsar Community: I would like to start the voting thread for
> > > PIP-359: Support
> > > custom message listener executor for specific subscription.
> > > PIP: https://github.com/apache/pulsar/pull/22902
> > >
> > > Please review and vote on the PIP-359, as follows: [ ] +1, Approve the
> > > PIP-359 [ ] -1, Do not approve the PIP-539 (please provide specific
> > > comments)
> > > Thanks, Linlin Duan(AuroraTwinkle)
> > >
>

Re: [VOTE] PIP-358: let resource weight work for OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl.

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Fri, Jun 14, 2024 at 11:04 AM Yubiao Feng
 wrote:

> +1 (binding)
>
> Thanks
> Yubiao Feng
>
> On Fri, Jun 14, 2024 at 10:09 AM thetumbled  wrote:
>
> > Hi, Pulsar Community.
> >  I would like to start the voting thread for PIP-358: let resource
> > weight work for OverloadShedder, LeastLongTermMessageRate,
> > ModularLoadManagerImpl.
> >  Proposal PR: https://github.com/apache/pulsar/pull/22889
> >  ; Implementation
> > PR: https://github.com/apache/pulsar/pull/22888
> >  ;
> > Thanks,
> > Wenzhi Feng(thetumbled).
>

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.6 Candidate 1

[guo jiwei]

+1 (binding)

- validate the checksum and signature
- validate the binaries


Regards
Jiwei Guo (Tboy)


On Thu, Jun 13, 2024 at 3:20 AM Chris Bono  wrote:

> Following PIP-205: Reactive Java client for Apache Pulsar (
> https://github.com/apache/pulsar/issues/17335), this is release
> candidate 1 for the Reactive Java client for Apache Pulsar, version 0.5.6.
>
> *** 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 in the Maven
> repository
> are provided for convenience.
>
> Source package:
>
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.6-candidate-1/
>
> SHA-512 checksums:
>
> 0572aab3f35ad2b246894366ddeb0e32cf26dde67e7edde0adeb274be9384ec88fc8691d23c97add86b47b88118d32831b585f445d1f7216eb592d1244b2ec40
>  pulsar-client-reactive-0.5.6-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1301/
>
> The tag to be voted upon:
> v0.5.6-candidate-1 (59fea26f7a5a505098ddd110bd88167622871c73)
>
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.6-candidate-1
>
> Please download the source package, and follow detailed instructions
> for pulsar-client-reactive release validation at
>
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> .
>
> Best regards
>
> Chris
>

Re: [VOTE] PIP-355: Enhancing Broker-Level Metrics for Pulsar

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Tue, Jun 11, 2024 at 8:35 AM PengHui Li  wrote:

> +1 (binding)
>
> Regards,
> Penghui
>
> On Sat, Jun 1, 2024 at 5:05 AM Dragos Misca
>  wrote:
>
> > +1 non-binding
> >
> > Thank you,
> > Dragos
> >
> > > On May 30, 2024, at 5:47 PM, Hang Chen  wrote:
> > >
> > > Hi, all
> > >
> > > I would like to start the voting thread for PIP-355: Enhancing
> > > Broker-Level Metrics for Pulsar
> > >
> > > PIP: https://github.com/apache/pulsar/pull/22778
> > >
> > > Thanks
> > > Hang
> >
> >
>

Re: [VOTE] PIP-351: Additional options for Pulsar-Test client to support KeyStore based TLS

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Wed, May 22, 2024 at 2:25 PM Lari Hotari  wrote:

> +1 (binding)
>
> -Lari
>
> On 2024/05/16 19:20:19 Shasank Sekhar Pandey wrote:
> > Hello,
> >
> > I would like to start a voting thread for PIP-351: [improve][pip]
> PIP-351: Additional options for Pulsar-Test client to support KeyStore
> based TLS by shasank112001 · Pull Request #22694 · apache/pulsar (
> github.com)
> >
> > Its implementation PR can be found here:  [improve][misc] KeyStores can
> now be utilised for performance testing by shasank112001 · Pull Request
> #22692 · apache/pulsar (github.com)<
> https://github.com/apache/pulsar/pull/22692>
> >
> > The original Issue I created for this can be found here: Add parameters
> for KeyStore TLS in Pulsar test client · Issue #22678 · apache/pulsar (
> github.com)
> >
> > The discussion thread for this can be found here : [DISCUSS] PIP-351:
> Additional options for Pulsar-Test client to support KeyStore based
> TLS-Apache Mail Archives<
> https://lists.apache.org/thread/rlyjkyvmdkjors0oq63k7gwb33prw4hv>
> >
> > Regards,
> > Shasank
> >
>

Re: [VOTE] PIP-357: Correct the conf name in load balance module.

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, Jun 6, 2024 at 3:05 PM Yunze Xu  wrote:

> +1 (binding)
>
> Thanks,
> Yunze
>
> On Wed, Jun 5, 2024 at 6:25 PM thetumbled  wrote:
> >
> > Hi PengHui,
> > The current design is not to remove the old one directly, but deprecate
> it. We are still comptible with the old cluster in following way:
> > - If a configuration is not the default configuration, use that
> configuration.
> > - If both the new and the old are configured different from the default
> value, use the new one.
> > So user upgrading to the new version without doing any change will not
> meet any problem.
> >
> > Regards,
> > Wenzhi Feng.
> >
> > On 2024/06/05 09:37:43 PengHui Li wrote:
> >  Hi Wenzhi,
> > 
> >  Thanks for driving the proposal.
> > 
> >  The old configuration name should not be removed directly.
> >  It might break users when they upgrade to the new cluster.
> >  Instead, we can move it to the `Deprecated settings` section
> >  and use `-1` as the default value. If the user sets it to a
> positive number,
> >  we should use the old configuration to ensure compatibility.
> > 
> >  If the existing user wants to move to the new configuration name,
> they
> >  should
> >  set the old one to -1 or just delete it.
> > 
> >  Regards,
> >  Penghui
> > 
> >  On Wed, Jun 5, 2024 at 11:15 AM Kai Wang  wrote:
> > 
> >   +1 non-binding
> >  
> >   Thank you,
> >   Kai
> >  
> >   On 2024/06/05 02:32:51 thetumbled wrote:
> >Hi, Pulsar Community.
> >  I would like to start the voting thread for PIP-357:
> Correct the conf
> >   name in load balance module.
> >  Proposal PR:
> https://github.com/apache/pulsar/pull/22823
> >  Implementation PR:
> https://github.com/apache/pulsar/pull/22824
> >   
> >Thanks,
> >Wenzhi Feng(thetumbled).
> >  
> > 
>

Re: [VOTE] Release Apache Pulsar 3.3.0 based on 3.3.0-candidate-4

[guo jiwei]

+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 Mon, Jun 3, 2024 at 6:51 PM 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-4.
>
> 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-4/
>
> SHA-512 checksums:
>
> a19f80caa7dcc92d6df235af9f71e90d9ab52739e2d7d1ddc59944ed11be8f5f6a083db4792cafd87802d68ef9edce88e1ed91ee43cac2a98c3782b8925f07f6
>
> 03692f2b6d574ce523418850d47391b9aa9f71a2bde0b593d6e1eaaf34eb6ebe080e598231d6faf2902a9f071192c0a6982403095a9374d4357b7bebb18e5e93
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1300
>
> The tag to be voted upon:
> v3.3.0-candidate-4 (commit c0aab493aafa5386dbf93c0b58a66a666aeba17a)
> https://github.com/apache/pulsar/releases/tag/v3.3.0-candidate-4
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Docker images:
> docker pull czcoder/pulsar3.3.0-c0aab49
>
> https://hub.docker.com/layers/czcoder/pulsar/3.3.0-c0aab49/images/sha256-996c6babec1f887cf2f43cac0692e06f879364fe87372fcb6c8b9d3ac779c7d6?context=explore
> docker pull czcoder/pulsar-all:3.3.0-c0aab49
>
> https://hub.docker.com/layers/czcoder/pulsar-all/3.3.0-c0aab49/images/sha256-dd781dfcc72dfb3db6c0053c656dfdb750c8d36e4c57f4bbad87aee4a9cdce28?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-356: Support Geo-Replication starts at earliest position

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, May 30, 2024 at 5:01 PM Zike Yang  wrote:

> +1 (binding)
>
> Thanks,
> Zike Yang
>
> On Thu, May 30, 2024 at 3:29 PM Yubiao Feng
>  wrote:
> >
> > Hi, all
> >
> > I would like to start the voting thread for PIP-356: Support
> > Geo-Replication at the earliest position.
> >
> > https://github.com/apache/pulsar/pull/22806
> >
> > Thanks
> > Yubiao Feng
>

Re: [VOTE] PIP-354: apply topK mechanism to ModularLoadManagerImpl

[guo jiwei]

+1 (binding)



Regards
Jiwei Guo (Tboy)


On Mon, May 27, 2024 at 11:35 AM PengHui Li  wrote:

> +1 (binding)
>
> Regards,
> Penghui
>
> On Mon, May 27, 2024 at 10:24 AM Kai Wang  wrote:
>
> > +1 (non-binding)
> >
> > Thanks,
> > Kai
> >
>

Re: [VOTE] PIP-353: Improve transaction message visibility for peek-messages

[guo jiwei]

+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] Release Apache Pulsar 3.3.0 based on 3.3.0-candidate-3

[guo jiwei]

+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] Release Apache Pulsar 3.3.0 based on 3.3.0-candidate-2

[Guo Jiwei]

-1 (binding)

When verifying the `Functions` parts, it can't get the functions even if 
created them.
The broker logs show that creating fn using the `default` namespace, but geting 
fn using the `test-namespace`. Then find the related fix in 
https://github.com/apache/pulsar/pull/22209, it adds the default tenant and 
namespace.




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
> 

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.5 Candidate 1

[guo jiwei]

+1 (binding)

- checked sha512 checksum
- checked signature
- validate the binary with the script and the sample test application

Regards
Jiwei Guo (Tboy)


On Thu, May 16, 2024 at 2:55 PM Lari Hotari  wrote:

> +1 (binding)
>
> Validated source artifacts
> - checked sha512 checksum
> - checked signature
>
> Validated binaries
> - ran sample app
>
> -Lari
>
> On 2024/05/15 18:37:48 Chris Bono wrote:
> > Following PIP-205: Reactive Java client for Apache Pulsar (
> > https://github.com/apache/pulsar/issues/17335), this is release
> > candidate 1 for the Reactive Java client for Apache Pulsar, version
> 0.5.5.
> >
> > *** 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 in the Maven
> repository
> > are provided for convenience.
> >
> > Source package:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.5-candidate-1/
> >
> > SHA-512 checksums:
> >
> bbbf8cbd52044579eeff80755899f332c642b1cbcb7ce265b782e605623f174371735e5988b2cdaf59eac39a6eb9c59ce2eb49a4fcac4b511efa86f72a4a51fc
> >  pulsar-client-reactive-0.5.5-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1291/
> >
> > The tag to be voted upon:
> > v0.5.5-candidate-1 (a813593ffbe8781ef4028a2831822a6922bffacd)
> >
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.5-candidate-1
> >
> > Please download the source package, and follow detailed instructions
> > for pulsar-client-reactive release validation at
> >
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > .
> >
> > Best regards
> >
> > Chris Bono
> >
>

Re: [VOTE] Release Apache Pulsar 3.2.3 based on 3.2.3-candidate-1

[guo jiwei]

+1 (binding)

- Build from source
- Checked the signatures
- Start standalone
- Verified producers and consumers
- Verified Cassandra connect
- Verified Stateful function


Regards
Jiwei Guo (Tboy)


On Wed, May 15, 2024 at 12:35 AM Lari Hotari  wrote:

> Hello Apache Pulsar Community,
>
> This is a call for the vote to release the Apache Pulsar version 3.2.3
> based on 3.2.3-candidate-1.
>
> Included changes since the previous release:
> https://github.com/apache/pulsar/compare/v3.2.2...v3.2.3-candidate-1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> The release candidate is available at:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.3-candidate-1/
>
> SHA-512 checksums:
> 76b1075ec13608eed70b735d2c807d22134f3b28b578efc4fef05b6e740d84c9e00173ec8a2b60fa597d66bedc0ac4c9565e9acf817af26bd88adc095b3e6af4
> apache-pulsar-3.2.3-src.tar.gz
> eaec1feac417949794a6a14c8ab7908235e36a34e644fe1c61fcc1cf39d621d8746492c2d5c8c6ae03c45de4c402e5baa0b1fc7c78b2368fccfff69d2abd9990
> apache-pulsar-3.2.3-bin.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1290
>
> The tag to be voted upon:
> v3.2.3-candidate-1 (commit 2f8a2bd5fd5b258dbe44c772b824f06c540975ea)
> https://github.com/apache/pulsar/releases/tag/v3.2.3-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Docker images:
> docker pull lhotari/pulsar:3.2.3-2f8a2bd
>
> https://hub.docker.com/layers/lhotari/pulsar/3.2.3-2f8a2bd/images/sha256-23c45434fe7955ff3aba124609ab965132a6304e96441e668c5bd9507d1e4284?context=explore
> docker pull lhotari/pulsar-all:3.2.3-2f8a2bd
>
> https://hub.docker.com/layers/lhotari/pulsar-all/3.2.3-2f8a2bd/images/sha256-443831e5c40005756219f0840b9609d6ba27ecd0eb07df1afe17e8a1a1ed69c9?context=explore
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
> More advanced release validation instructions can be found at
> https://pulsar.apache.org/contribute/validate-release-candidate/
>
> Thanks,
>
> Lari Hotari
>

Re: [VOTE] Release Apache Pulsar 3.0.5 based on 3.0.5-candidate-1

[guo jiwei]

+1 (binding)

- Build from source
- Checked the signatures
- Start standalone
- Verified producers and consumers
- Verified Cassandra connect
- Verified Stateful function

Regards
Jiwei Guo (Tboy)


On Tue, May 14, 2024 at 8:57 PM Lari Hotari  wrote:

> Hello Apache Pulsar Community,
>
> This is a call for the vote to release the Apache Pulsar version 3.0.5
> based on 3.0.5-candidate-1.
>
> Included changes since the previous release:
> https://github.com/apache/pulsar/compare/v3.0.4...v3.0.5-candidate-1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> The release candidate is available at:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.0.5-candidate-1/
>
> SHA-512 checksums:
> a6940adc7237636ef2e9eac833feca18900b2a76658a3c8314cd074a258c580f8c8b01d7eadaa9c8936e0df97cf2d8850e60c9c7144f1b8b154825aa05ecb934
> apache-pulsar-3.0.5-src.tar.gz
> e2cc1e60e41514dd60ccdc06d0ac51301ec2a6cf18dab5ce4e87c350340d50aa509e2e70b0ae337716bb8fb163397cc978ae9c224dc454803f63fd25bd644930
> apache-pulsar-3.0.5-bin.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1288
>
> The tag to be voted upon:
> v3.0.5-candidate-1 (commit 2da571eb2dc97bec413d70d3800bb150fcec9507)
> https://github.com/apache/pulsar/releases/tag/v3.0.5-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Docker images:
> docker pull lhotari/pulsar:3.0.5-2da571e
>
> https://hub.docker.com/layers/lhotari/pulsar/3.0.5-2da571e/images/sha256-66c92070acc750def529bd9c104649cc6e28d3dd4df623a0dff17290aa61cc24?context=explore
> docker pull lhotari/pulsar-all:3.0.5-2da571e
>
> https://hub.docker.com/layers/lhotari/pulsar-all/3.0.5-2da571e/images/sha256-16060c85aae05d610b3ca6e5ed578e570de0debfc3fb2854288263f741e77750?context=explore
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
> More advanced release validation instructions can be found at
> https://pulsar.apache.org/contribute/validate-release-candidate/
>
> Thanks,
>
> Lari Hotari
>

Re: [VOTE] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Tue, May 14, 2024 at 12:05 PM Zike Yang  wrote:

> +1 (binding)
>
> Thanks,
> Zike Yang
>
> On Mon, May 13, 2024 at 3:08 PM ZhangJian He  wrote:
> >
> > +1(nonbinding)
> >
> > Thanks
> > ZhangJian He
> > Twitter: shoothzj
> > Wechat: shoothzj
> >
> >
> > On Mon, May 13, 2024 at 2:35 PM Hang Chen  wrote:
> >
> > > +1 (binding)
> > >
> > > Thanks,
> > > Hang
> > >
> > > 太上玄元道君  于2024年5月13日周一 11:30写道：
> > > >
> > > > +1 nonbinding
> > > >
> > > > Thanks,
> > > > Tao Jiuming
> > > >
> > > > Yong Zhang  于2024年5月13日周一 10:57写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > I would like to start voting thread for PIP-350.
> > > > > https://github.com/apache/pulsar/pull/22688
> > > > >
> > > > > The implementation PR is:
> > > > > https://github.com/apache/pulsar/pull/22689
> > > > >
> > > > > Discuss thread:
> > > > > https://lists.apache.org/thread/7tlpkcm2933ddg95kgrb42943r4gq3v9
> > > > >
> > > > > Thanks,
> > > > > Yong
> > > > >
> > >
>

Re: [VOTE] PIP-348: Trigger offload on topic load stage

[guo jiwei]

+1 (binding)

Regards
Jiwei Guo (Tboy)


On Wed, May 8, 2024 at 8:45 PM PengHui Li  wrote:

> +1 (binding)
>
> Penghui
>
> On Wed, May 8, 2024 at 8:27 PM Enrico Olivelli 
> wrote:
>
> > +1 (binding)
> >
> > Enrico
> >
> > Il giorno mer 8 mag 2024 alle ore 12:51 Zike Yang  ha
> > scritto:
> >
> > > +1 (binding)
> > >
> > > Thanks,
> > > Zike Yang
> > >
> > > On Wed, May 8, 2024 at 6:22 PM Yubiao Feng
> > >  wrote:
> > > >
> > > > +1 (binding)
> > > >
> > > > Thanks
> > > > Yubiao Feng
> > > >
> > > > On Tue, May 7, 2024 at 11:27 AM Hang Chen 
> wrote:
> > > >
> > > > > Hi guys,
> > > > >  I want to start voting for PIP-348.
> > > > >
> > > > > PIP: https://github.com/apache/pulsar/pull/22650
> > > > > PR: https://github.com/apache/pulsar/pull/22652
> > > > >
> > > > > DISCUSSION Thread:
> > > > > https://lists.apache.org/thread/2ndomp8v4wkcykzthhlyjqfmswor88kv
> > > > >
> > > > > Thanks,
> > > > > Hang
> > > > >
> > >
> >
>

Re: [DISCUSS] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis

[guo jiwei]

+1

Regards
Jiwei Guo (Tboy)


On Fri, May 10, 2024 at 4:00 PM Hang Chen  wrote:

> +1
>
> Best,
> Hang
>
> 太上玄元道君  于2024年5月10日周五 12:13写道：
> >
> > looks good
> >
> > Yong Zhang  于2024年5月10日周五 11:31写道：
> >
> > > Hi all,
> > >
> > > I pushed a new proposal to allow to use -1 to disable
> > > the managedLedgerOffloadDeletionLagInMillis to not delete the data from
> > > bookkeeper.
> > >
> > > Please take a look and share your thoughts. Thanks!
> > >
> > > PIP: https://github.com/apache/pulsar/pull/22688
> > >
> > > Best Regards,
> > > Yong
> > >
>

Re: [VOTE] PIP-349: Add systemCursorNames ignore list for TTL check

[guo jiwei]

+1 (binding)

Regards
Jiwei Guo (Tboy)


On Wed, May 8, 2024 at 8:45 PM PengHui Li  wrote:

> +1 (binding)
>
> Regards,
> Penghui
>
> On Wed, May 8, 2024 at 6:58 PM Zixuan Liu  wrote:
>
> > +1 (non-binding)
> >
> > Thanks,
> > Zixuan
> >
> > Yubiao Feng  于2024年5月8日周三 18:22写道：
> >
> > > +1 (binding)
> > >
> > > Thanks
> > > Yubiao Feng
> > >
> > > On Tue, May 7, 2024 at 11:25 AM Hang Chen  wrote:
> > >
> > > > Hi guys,
> > > >  I want to start voting for PIP-349.
> > > >
> > > > PIP: https://github.com/apache/pulsar/pull/22651
> > > > PR: https://github.com/apache/pulsar/pull/22614
> > > >
> > > > DISCUSSION Thread:
> > > > https://lists.apache.org/thread/xgcworz4j8rjlqwr476s7sqn9do43f1t
> > > >
> > > > Thanks,
> > > > Hang
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Pulsar Helm Chart 3.4.0 based on 3.4.0-candidate-1

[guo jiwei]

+1 (binding)

- verify the checksums
- verify the signature


Regards
Jiwei Guo (Tboy)


On Sat, Apr 20, 2024 at 12:51 AM David Jensen  wrote:

> +1 (binding)
>
> # verify checksums
> sha512sum -c *.sha512
>
> # signature OK
> gpg --verify-files *.asc
>
> Greetings
> David Jensen
>
> On 2024/04/02 13:34:38 Lari Hotari wrote:
> > Hello Apache Pulsar Community,
> >
> > This is a call for the vote to release the Apache Pulsar Helm Chart
> version 3.4.0.
> >
> > Release notes for 3.4.0-candidate-1:
> >
> https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.4.0-candidate-1
> >
> > The release candidate is available at:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/3.4.0-candidate-1/
> >
> > pulsar-chart-3.4.0-source.tar.gz - is the "main source release".
> > pulsar-3.4.0.tgz - is the binary Helm Chart release.
> >
> > Public keys are available at: https://www.apache.org/dist/pulsar/KEYS
> >
> > For convenience "index.yaml" has been uploaded (though excluded from
> voting), so you can also run the below commands.
> >
> > helm repo add --force-update apache-pulsar-dist-dev
> https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/3.4.0-candidate-1/
> > helm repo update
> > helm install pulsar apache-pulsar-dist-dev/pulsar --version 3.4.0 --set
> affinity.anti_affinity=false
> >
> > pulsar-3.4.0.tgz.prov - is also uploaded for verifying Chart Integrity,
> though it is not strictly required for releasing the artifact based on ASF
> Guidelines.
> >
> > You can optionally verify this file using this helm plugin
> https://github.com/technosophos/helm-gpg, or by using helm --verify (
> https://helm.sh/docs/helm/helm_verify/).
> >
> > helm fetch --prov apache-pulsar-dist-dev/pulsar
> > helm plugin install https://github.com/technosophos/helm-gpg
> > helm gpg verify pulsar-3.4.0.tgz
> >
> > The vote will be 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)".
> >
> > For license checks, the .rat-excludes files is included, so you can run
> the following to verify licenses (just update ):
> >
> > tar -xvf pulsar-chart-3.4.0-source.tar.gz
> > cd pulsar-chart-3.4.0
> > java -jar /apache-rat-0.15/apache-rat-0.15.jar . -E .rat-excludes
> >
> > Please note that the version number excludes the `-candidate-X` string,
> so it's now
> > simply 3.4.0. This will allow us to rename the artifact without modifying
> > the artifact checksums when we actually release it.
> >
> > Thanks,
> >
> > Lari
> >
>

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.4 Candidate 1

[guo jiwei]

+1 (binding)

- validate checksum
- validate signature
- validate binaries with the script and manually(produce/consume)



Regards
Jiwei Guo (Tboy)


On Thu, Apr 11, 2024 at 2:16 PM Lari Hotari  wrote:

> +1 (binding)
>
> Validated source artifacts
> - checked sha512 checksum
> - checked signature
>
> Validated binaries
> - ran sample app
>
> -Lari
>
> On 2024/04/10 18:32:06 Chris Bono wrote:
> > Following PIP-205: Reactive Java client for Apache Pulsar (
> > https://github.com/apache/pulsar/issues/17335), this is release
> > candidate 1 for the Reactive Java client for Apache Pulsar, version
> 0.5.4.
> >
> > *** 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 in the Maven
> repository
> > are provided for convenience.
> >
> > Source package:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.4-candidate-1/
> >
> > SHA-512 checksums:
> >
> f1640fa49571df0bf449f05cf106f417e1f4609020d6c11a54a9e5d601d62b4db7aaa8a59a1ce9e5026a410b2a7bb351b8d0415e1c1e7a3b2487c167a4c8dd5c
> >  pulsar-client-reactive-0.5.4-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1287/
> >
> > The tag to be voted upon:
> > v0.5.4-candidate-1 (1139dd84138be1758f078b160b986307af714b10)
> >
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.4-candidate-1
> >
> > Please download the source package, and follow detailed instructions
> > for pulsar-client-reactive release validation at
> >
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > .
> >
> > Best regards
> >
> > Chris Bono
> >
>

Re: [VOTE] Pulsar Client Python Release 3.5.0 Candidate 3

[guo jiwei]

+1 (binding)

- Checked the signature and checksums
- Install the pulsar_client-3.5.0-cp310-cp310-macosx_10_15_universal2.whl
- Run Pulsar standalone
- Run the Python examples producer and consumer


Regards
Jiwei Guo (Tboy)


On Tue, Apr 2, 2024 at 5:49 PM Yunze Xu  wrote:

> This is the 3rd release candidate for Apache Pulsar Client Python,
> version 3.5.0.
>
> It fixes the following issues:
> https://github.com/apache/pulsar-client-python/milestone/6?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.5.0-candidate-3/
>
> The supported python versions are 3.8, 3.9, 3.10, 3.11 and 3.12. 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.5.0-candidate-3
> (38737a24f6ba77fe4efc5321980513ae317920e4)
>
> https://github.com/apache/pulsar-client-python/releases/tag/v3.5.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 Python wheels and follow the README to test.
>

Re: [VOTE] Release Apache Pulsar 3.2.2 based on 3.2.2-candidate-1

[guo jiwei]

+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, Mar 29, 2024 at 5:25 AM Lari Hotari  wrote:

> Hello Apache Pulsar Community,
>
> This is a call for the vote to release the Apache Pulsar version 3.2.2
> based on 3.2.2-candidate-1.
>
> Included changes since the previous release:
> https://github.com/apache/pulsar/compare/v3.2.1...v3.2.2-candidate-1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> The release candidate is available at:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.2-candidate-1/
>
> SHA-512 checksums:
> 04e723bd926751ca2638d7926ccc0c18d876e5017f8116df44a9c11b9dc82bca867ed9e4cdd6ff27cd998cb9279218db9e6ab41c0d38a27609d44abaa706ad05
> apache-pulsar-3.2.2-src.tar.gz
> 0610b0c33b456f2fd48ad07ea19eb5c0ff985497f63bd99174e6521bcd314cc79a855982204ebbce40ef3e88927fc2dd45cd728444fcaf8baaf927b7cf14058f
> apache-pulsar-3.2.2-bin.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1286
>
> The tag to be voted upon:
> v3.2.2-candidate-1 (commit bacedb5bd6b27e53cb3036976bec27340089b179)
> https://github.com/apache/pulsar/releases/tag/v3.2.2-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Docker images:
> docker pull lhotari/pulsar:3.2.2-bacedb5
>
> https://hub.docker.com/layers/lhotari/pulsar/3.2.2-bacedb5/images/sha256-6f71f6bbefcc98fe1a818ca6188fcbdfddd26b0a9244470f090bc8c4f82566ee?context=explore
> docker pull lhotari/pulsar-all:3.2.2-bacedb5
>
> https://hub.docker.com/layers/lhotari/pulsar-all/3.2.2-bacedb5/images/sha256-947d9a5cc52e4a528007b9d6a5d4371cea93ffc527748b263d1eaa0891dd634f?context=explore
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
> More advanced release validation instructions can be found at
> https://pulsar.apache.org/contribute/validate-release-candidate/
>
> Thanks,
>
> Lari Hotari
>

Re: [VOTE] Release Apache Pulsar 3.0.4 based on 3.0.4-candidate-1

[guo jiwei]

+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 Mon, Apr 1, 2024 at 2:16 PM Yike Xiao  wrote:

> +1 (non-binding)
>
> - Checked the signatures and checksums
> - Built from source
>   ```
>   Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
>   Maven home: /usr/local/maven
>   Java version: 17.0.3.1, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-17.0.3.1.jdk/Contents/Home
>   Default locale: en_CN, platform encoding: UTF-8
>   OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
>   ```
> - Run standalone and checked produce and consume
> - Run a cluster with 2 brokers and 3 bookies by docker image
> (`lhotari/pulsar:3.0.4-5a1fa0c`)
>
> Regards,
> Yike
> 
> From: Lari Hotari 
> Sent: Friday, March 29, 2024 3:21
> To: dev@pulsar.apache.org 
> Subject: [VOTE] Release Apache Pulsar 3.0.4 based on 3.0.4-candidate-1
>
> Hello Apache Pulsar Community,
>
> This is a call for the vote to release the Apache Pulsar version 3.0.4
> based on 3.0.4-candidate-1.
>
> Included changes since the previous release:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fcompare%2Fv3.0.3...v3.0.4-candidate-1=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351021679%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=Ncq6ioCrn8CWhdJ6PFt%2BeOKb%2Bom3B2HamUwXoxYp35s%3D=0
> 
>
> *** 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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.4-candidate-1%2F=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351031981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=jxrBE37mapskOznzp4IEBgveROh5%2FzI%2Bz%2Fopg3KlVG0%3D=0
> 
>
> SHA-512 checksums:
> 9ba5d46f57c06f4c401664ed1ac2e31f7e0d93a09cda4c82ca05e3854422528e8fe6ab7c7003fed10c854f4bfda70376acb95f49df85d3cd2ed1e020e40886b2
> apache-pulsar-3.0.4-src.tar.gz
> 6167eada33c4c7b744c18b0b4c62a41282f42f302869f21dda2d0ea480389f7e5325007d1f13675bd7e3ee67f83a5c72940a28c968e53f7b741ea016d8c987fe
> apache-pulsar-3.0.4-bin.tar.gz
>
> Maven staging repo:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1285=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351039515%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=Rp%2B0octSdDm7HjySkSpLE9HXl6uH0C51U3LICCt0NrQ%3D=0
> 
>
> The tag to be voted upon:
> v3.0.4-candidate-1 (commit 5a1fa0c5c6709bdb7b003ce12d00abf52da293e1)
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Freleases%2Ftag%2Fv3.0.4-candidate-1=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351045597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=UW6pXZKj5dapTsVu55OH28l8aUQXHiOFwy7R%2B%2BXQsxc%3D=0
> 
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownloads.apache.org%2Fpulsar%2FKEYS=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351050849%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=ze0qjM6Bpf%2FfbTg4ZI%2BcF1VP6YbCOzFEgXcPgJjvTC4%3D=0
> 
>
> Docker images:
> docker pull lhotari/pulsar:3.0.4-5a1fa0c
>
> 

Re: [VOTE] Pulsar Client C++ Release 3.5.1 Candidate 1

[guo jiwei]

+1 (binding)

- Verified checksum and signatures
- Built from source on macOS m1
- Ran the tests

Regards
Jiwei Guo (Tboy)


On Thu, Mar 28, 2024 at 10:38 PM Baodi Shi  wrote:

> +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: [VOTE] PIP-344: Correct the behavior of the public API pulsarClient.getPartitionsForTopic(topicName)

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Fri, Mar 22, 2024 at 2:23 PM Aloys Zhang  wrote:

> +1(no-binding)
>
> Zike Yang  于2024年3月21日周四 18:09写道：
>
> > +1 (no-binding)
> >
> > Thanks,
> > Zike Yang
> >
> > On Thu, Mar 21, 2024 at 11:42 AM Yunze Xu  wrote:
> > >
> > > +1 (binding)
> > >
> > > Thanks,
> > > Yunze
> > >
> > > On Wed, Mar 20, 2024 at 9:19 PM PengHui Li  wrote:
> > > >
> > > > +1 (binding)
> > > >
> > > > Regards.
> > > > Penghui
> > > >
> > > > On Sat, Mar 16, 2024 at 6:28 AM Yubiao Feng
> > > >  wrote:
> > > >
> > > > > Hi All
> > > > >
> > > > > This thread is to start a vote for PIP-344.
> > > > >
> > > > > PIP: https://github.com/apache/pulsar/pull/22182
> > > > > Discussion thread:
> > > > > https://lists.apache.org/thread/z693blcxoqk0mj0rzyt1k7nvy72j18t5
> > > > >
> > > > > Thanks
> > > > > Yubiao Feng
> > > > >
> >
>

Re: [VOTE] Pulsar Client C++ Release 3.5.0 Candidate 2

[guo jiwei]

+1 (binding)

- Verified checksum and signatures
- Built from source on macOS m1
- Ran the tests

Regards
Jiwei Guo (Tboy)


On Thu, Mar 14, 2024 at 9:12 PM Yunze Xu  wrote:

> +1 (binding)
>
> - Verified checksum and signatures
> - Built from source on macOS m1
> - Upgrade the dependency of the python client and verified the issues
> are fixed (https://github.com/apache/pulsar-client-python/pull/202)
>
> Thanks,
> Yunze
>
> On Thu, Mar 14, 2024 at 6:13 PM Yunze Xu  wrote:
> >
> > The vcpkg submodule is just convenient for development. You can just
> > run `git clone https://github.com/microsoft/vcpkg.git`
>  in the source
> > directory instead of fetching the submodule.
> >
> > BTW, I just found that when INTEGRATE_VCPKG is ON, we cannot customize
> > the CMAKE_TOOLCHAIN_FILE. So I opened a PR to fix it.
> > https://github.com/apache/pulsar-client-cpp/pull/417
> >
> > Thanks,
> > Yunze
> >
> > On Thu, Mar 14, 2024 at 3:47 PM Baodi Shi  wrote:
> > >
> > > 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.
> > > >
>

[ANNOUNCE] Apache Pulsar 3.2.1 released

[guo jiwei]

The Apache Pulsar team is proud to announce Apache Pulsar version 3.2.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 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
Jiwei Guo (Tboy)

Re: [VOTE] Pulsar Release 3.2.1 Candidate 2

[guo jiwei]

Close this vote with 3 bindings


Regards
Jiwei Guo (Tboy)


On Fri, Mar 8, 2024 at 3:21 PM 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, Mar 8, 2024 at 2:59 PM PengHui Li  wrote:
>
>> +1 (binding)
>>
>> - Checked the signatures
>> - Build from the source
>> - Checked the bookkeeper JNI libs
>> org.apache.bookkeeper-circe-checksum-*.jar and
>> org.apache.bookkeeper-cpu-affinity-*.jar
>> - Verified the Cassandra connector
>> - Verified the Stateful Function
>> - Verified the Trino connector
>> - Tested performance with 100 topics
>>
>> Regards,
>> Penghui
>>
>> On Fri, Mar 8, 2024 at 5:13 AM Lari Hotari  wrote:
>>
>> > +1 (binding)
>> >
>> > - Built from source
>> > - Checked the signatures of the source and binary release artifacts
>> > - Run standalone
>> > - Checked producer and consumer
>> > - Verified the Cassandra connector
>> > - Verified the Stateful function
>> >
>> > -Lari
>> >
>> > On 2024/03/07 07:16:37 guo jiwei wrote:
>> > > This is the second release candidate for Apache Pulsar version 3.2.1.
>> > >
>> > > It fixes the following issues:
>> > >
>> >
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.2.1+label%3Acherry-picked%2Fbranch-3.2+
>> > >
>> > > *** Please download, test and verify on this release. This vote will
>> stay
>> > > open for at least 72 hours ***
>> > >
>> > > Note that we are verifying upon the source (tag), binaries are
>> provided
>> > for
>> > > convenience.
>> > >
>> > > Source and binary files:
>> > >
>> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.1-candidate-2/
>> > >
>> > > SHA-512 checksums:
>> > >
>> > >
>> >
>> bc66d777977aaa06a6e30c291e4e400e8ec4a3f619a3fc046ade6c9d9a711610099be3578f5dd1eee4eeab8afdd67963cfef49521219107ca829465762689494
>> > >
>> > > apache-pulsar-3.2.1-bin.tar.gz
>> > >
>> > >
>> >
>> dc09d5246075f56456f00875a3b9654b3a31d69a3e502a61db4481e493c2d20babb46b48e47ff95b66ad60d0e6e3455b13e1f01259366ab6b982b07b00aabda6
>> > >
>> > > apache-pulsar-3.2.1-src.tar.gz
>> > >
>> > > Maven staging repo:
>> > >
>> https://repository.apache.org/content/repositories/orgapachepulsar-1271/
>> > >
>> > > The tag to verify:
>> > > v3.2.1-candidate-2 (da98b8d8d0bc0c2bdd2d14d3e2e8058fb4c5dfd2)
>> > > https://github.com/apache/pulsar/commits/v3.2.1-candidate-2/
>> > >
>> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
>> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>> > >
>> > > Docker images:
>> > >
>> > > pulsar images:
>> > >
>> >
>> https://hub.docker.com/layers/technoboy8/pulsar/3.2.1-da98b8d/images/sha256-e3ae82ff5504470878f8c871e8737d71be8a58507937be3c2d6b4d31e7480f42?context=repo
>> > > <
>> >
>> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
>> > >
>> > > pulsar-all images:
>> > >
>> >
>> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.1-da98b8d/images/sha256-be975933560b0bff3ae5f1d72b9be1b150c049eff7692a7e14308648c4103f0e?context=repo
>> > >
>> > > Please download the source package, and follow the README to build
>> > > and run the Pulsar standalone service.
>> > >
>> > >
>> > > Regards
>> > > Jiwei Guo (Tboy)
>> > >
>> >
>>
>

Re: [VOTE] Pulsar Release 2.11.4 Candidate 1

[guo jiwei]

+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, Mar 8, 2024 at 3:52 PM PengHui Li  wrote:

> +1 (binding)
>
> - Checked the signatures
> - Build from the source
> - Checked the bookkeeper JNI libs
> org.apache.bookkeeper-circe-checksum-*.jar and
> org.apache.bookkeeper-cpu-affinity-*.jar
> - Verified the Cassandra connector
> - Verified the Stateful Function
> - Verified the Trino connector
> - Tested performance with 100 topics
>
> Regards,
> Penghui
>
> On Fri, Mar 8, 2024 at 5:26 AM Lari Hotari  wrote:
>
> > +1 (binding)
> >
> > - Built from source
> > - Checked the signatures of the source and binary release artifacts
> > - Run standalone
> > - Checked producer and consumer
> > - Verified the Cassandra connector
> > - Verified the Stateful function
> >
> > -Lari
> >
> > On 2024/03/07 17:44:32 Lari Hotari wrote:
> > > This is the first release candidate for Apache Pulsar, version 2.11.4.
> > >
> > > It fixes the following issues:
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F2.11.4+label%3Acherry-picked%2Fbranch-2.11+sort%3Acreated-asc
> > >
> > > *** Please download, test and vote on this release. This vote will stay
> > open
> > > for at least 24 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.4-candidate-1/
> > >
> > > SHA-512 checksums:
> > >
> >
> 365b75767e16f0475d8b986e4503773630d1d9af2a37add0cb417df5822000889d105f192cc0b4023c44426b096204d03be1277723d3e5ed88f66a378b9848f5
> > apache-pulsar-2.11.4-bin.tar.gz
> > >
> >
> 173635e73f6a8d1a2a1c7255f9dd337408cfbef4f59fa662e1d16c33347e1eb15d97e19ec82c8f62a6236b80d7bb9ddde1039bc374074676923acff8ad8a2211
> > apache-pulsar-2.11.4-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1276
> > >
> > > The tag to be voted upon:
> > > v2.11.4-candidate-1 (b61587216f9d9ea8f6468edbbf6078658d2c0bc2)
> > > https://github.com/apache/pulsar/releases/tag/v2.11.4-candidate-1
> > >
> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > https://downloads.apache.org/pulsar/KEYS
> > >
> > > Docker images:
> > >
> > > lhotari/pulsar:2.11.4
> >
> https://hub.docker.com/layers/lhotari/pulsar/2.11.4/images/sha256-bb31af23830234770ed1468aef41f63f68daa59f090154d80c7ae1b9b72c4163?context=explore
> > > lhotari/pulsar-all:2.11.4
> >
> https://hub.docker.com/layers/lhotari/pulsar-all/2.11.4/images/sha256-8c00a6c232d2185907daf01a7392aac70f771ffbed7d4ecd3f91d983a35926a4?context=explore
> > >
> > > Please download the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> > > You can find release candidate validation instructions at
> > https://pulsar.apache.org/contribute/validate-release-candidate/
> > >
> > > Regards,
> > >
> > > -Lari
> > >
> >
>

Re: [VOTE] Pulsar Release 2.10.6 Candidate 2

[guo jiwei]

+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, Mar 8, 2024 at 3:48 PM Lari Hotari  wrote:

> +1 (binding)
>
> - Built from source
> - Checked the signatures of the source and binary release artifacts
> - Run standalone
> - Checked producer and consumer
> - Verified the Cassandra connector
> - Verified the Stateful function
>
> -Lari
>
> On 2024/03/08 02:08:34 Xiangying Meng wrote:
> > This is the first release candidate for Apache Pulsar, version 2.10.6.
> >
> > It fixes the following issues:
> >
> https://github.com/apache/pulsar/pulls?q=is:pr+label:cherry-picked/branch-2.10+label:release/2.10.6+is:closed
> >
> > *** Please download, test and vote on this release. This vote will stay
> open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.6-candidate-2/
> >
> > SHA-512 checksums:
> >
> 699a18b25828dc1274debb4d20cb22e9700935849243ea1892a15ad7b40c67d42ba46574e96356c39f4963183f080fb154fb42002559469eb1d240ceadf7a76c
> >  apache-pulsar-2.10.6-bin.tar.gz
> >
> fe7230e6c939b4da8da7c80b41611fd05336f83caeea981d16a749988cf4cb10cce64703c2c62aaec9f7ed1a4b353b1f68f8800b5befafe3264a5504750a2b6a
> >  apache-pulsar-2.10.6-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1274
> >
> > The tag to be voted upon:
> > v2.10.6-candidate-2 (a76ddbe5af523b4aa541a2272c58f685ef05859f)
> > https://github.com/apache/pulsar/releases/tag/v2.10.6-candidate-2
> >
> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > https://downloads.apache.org/pulsar/KEYS
> >
> > Docker images:
> >
> > 
> >
> https://hub.docker.com/layers/xiangyingmeng/pulsar/2.10.6/images/sha256-743a4b5d79708b7e87d99008882c4d7321433616d7ee3b9a32063c398238decf?context=repo
> >
> > 
> >
> https://hub.docker.com/layers/xiangyingmeng/pulsar-all/2.10.6/images/sha256-14013a1307c0c44ccb35526866c0775e5978fcb10beae5d5ffbdf4e73a029dc1?context=repo
> >
> > Please download the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
>

Re: [VOTE] Pulsar Release 3.1.3 Candidate 2

[guo jiwei]

+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, Mar 8, 2024 at 2:15 PM PengHui Li  wrote:

> +1 (binding)
>
> - Checked the signatures
> - Build from the source
> - Checked the bookkeeper JNI libs
> org.apache.bookkeeper-circe-checksum-*.jar and
> org.apache.bookkeeper-cpu-affinity-*.jar
> - Verified the Cassandra connector
> - Verified the Stateful Function
> - Verified the Trino connector
> - Tested performance with 100 topics
>
> Regards,
> Penghui
>
> On Fri, Mar 8, 2024 at 4:49 AM Lari Hotari  wrote:
>
> > +1 (binding)
> >
> > - Built from source
> > - Checked the signatures of the source and binary release artifacts
> > - Run standalone
> > - Checked producer and consumer
> > - Verified the Cassandra connector
> > - Verified the Stateful function
> >
> > -Lari
> >
> > On 2024/03/07 18:00:26 Ran Gao wrote:
> > > This is the second release candidate for Apache Pulsar version 3.1.3.
> > >
> > > It fixes the following issues:
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.3+label%3Acherry-picked%2Fbranch-3.1+
> > >
> > > *** Please download, test and verify on this release. This vote will
> stay
> > > open for at least 24 hours ***
> > >
> > > Note that we are verifying upon the source (tag), binaries are provided
> > for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.3-candidate-2/
> > >
> > > SHA-512 checksums:
> > >
> > >
> >
> 057cc9dd391aab98e0607a7f240f96c191a3c195ab404572530dec0045725d11ffdeb491c55db6ad87e36cdb72748ad70160f2b768a9f2e94e7ba515f8c0a5ff
> > >  apache-pulsar-3.1.3-bin.tar.gz
> > >
> >
> b657fc45e385ffd8b73372ec21616ea181d9bb04221864104ce9b507f993a2c6f69e3e2f617535473d5032815a564a7a472fd2f2187764ad9acd1eac1ffcdab4
> > >  apache-pulsar-3.1.3-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1277
> > >
> > > The tag to verify:
> > > v3.1.3-candidate-2 (dcaf508f8e381107125e98722f4ddab76f9303ad)
> > > https://github.com/apache/pulsar/commits/v3.1.3-candidate-2
> > >
> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > https://downloads.apache.org/pulsar/KEYS
> > >
> > > Docker images:
> > >
> > >
> >
> https://hub.docker.com/layers/gaoran10/pulsar/3.1.3-dcaf508/images/sha256-ef03162480a2710d8fc83dd22635ad401cc48c0ba8ebefa413bdfd794ae3af4f?context=repo
> > >
> > >
> >
> https://hub.docker.com/layers/gaoran10/pulsar-all/3.1.3-dcaf508/images/sha256-091214bca4985694a2e95d6e8432d3790c64e83af1ef0e4f2423833e66073685?context=repo
> > >
> > >
> > > Please download the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> > >
> > >
> > > Regards
> > > Ran Gao (gaoran10)
> > >
> >
>

Re: [VOTE] Pulsar Release 3.2.1 Candidate 2

[guo jiwei]

+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, Mar 8, 2024 at 2:59 PM PengHui Li  wrote:

> +1 (binding)
>
> - Checked the signatures
> - Build from the source
> - Checked the bookkeeper JNI libs
> org.apache.bookkeeper-circe-checksum-*.jar and
> org.apache.bookkeeper-cpu-affinity-*.jar
> - Verified the Cassandra connector
> - Verified the Stateful Function
> - Verified the Trino connector
> - Tested performance with 100 topics
>
> Regards,
> Penghui
>
> On Fri, Mar 8, 2024 at 5:13 AM Lari Hotari  wrote:
>
> > +1 (binding)
> >
> > - Built from source
> > - Checked the signatures of the source and binary release artifacts
> > - Run standalone
> > - Checked producer and consumer
> > - Verified the Cassandra connector
> > - Verified the Stateful function
> >
> > -Lari
> >
> > On 2024/03/07 07:16:37 guo jiwei wrote:
> > > This is the second release candidate for Apache Pulsar version 3.2.1.
> > >
> > > It fixes the following issues:
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.2.1+label%3Acherry-picked%2Fbranch-3.2+
> > >
> > > *** Please download, test and verify on this release. This vote will
> stay
> > > open for at least 72 hours ***
> > >
> > > Note that we are verifying upon the source (tag), binaries are provided
> > for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.1-candidate-2/
> > >
> > > SHA-512 checksums:
> > >
> > >
> >
> bc66d777977aaa06a6e30c291e4e400e8ec4a3f619a3fc046ade6c9d9a711610099be3578f5dd1eee4eeab8afdd67963cfef49521219107ca829465762689494
> > >
> > > apache-pulsar-3.2.1-bin.tar.gz
> > >
> > >
> >
> dc09d5246075f56456f00875a3b9654b3a31d69a3e502a61db4481e493c2d20babb46b48e47ff95b66ad60d0e6e3455b13e1f01259366ab6b982b07b00aabda6
> > >
> > > apache-pulsar-3.2.1-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1271/
> > >
> > > The tag to verify:
> > > v3.2.1-candidate-2 (da98b8d8d0bc0c2bdd2d14d3e2e8058fb4c5dfd2)
> > > https://github.com/apache/pulsar/commits/v3.2.1-candidate-2/
> > >
> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > >
> > > Docker images:
> > >
> > > pulsar images:
> > >
> >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.1-da98b8d/images/sha256-e3ae82ff5504470878f8c871e8737d71be8a58507937be3c2d6b4d31e7480f42?context=repo
> > > <
> >
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> > >
> > > pulsar-all images:
> > >
> >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.1-da98b8d/images/sha256-be975933560b0bff3ae5f1d72b9be1b150c049eff7692a7e14308648c4103f0e?context=repo
> > >
> > > Please download the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
> >
>

Re: [VOTE] PIP-343: Use picocli instead of jcommander

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, Mar 7, 2024 at 1:14 AM 太上玄元道君  wrote:

> +1 nonbinding
>
> Zixuan Liu 于2024年3月6日 周三23:04写道：
>
> > Hello,
> >
> > A new proposal to improve the CLI user experience.
> >
> > PIP: https://github.com/apache/pulsar/pull/22181
> > Discussion thread:
> > https://lists.apache.org/thread/ydg1q064cd11pxwz693frtk4by74q32f
> >
> > PR: https://github.com/apache/pulsar/pull/22209
> >
> > Thanks,
> > Zixuan
> >
>

[VOTE] Pulsar Release 3.2.1 Candidate 2

[guo jiwei]

This is the second release candidate for Apache Pulsar version 3.2.1.

It fixes the following issues:
https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.2.1+label%3Acherry-picked%2Fbranch-3.2+

*** Please download, test and verify on this release. This vote will stay
open for at least 72 hours ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.1-candidate-2/

SHA-512 checksums:

bc66d777977aaa06a6e30c291e4e400e8ec4a3f619a3fc046ade6c9d9a711610099be3578f5dd1eee4eeab8afdd67963cfef49521219107ca829465762689494

apache-pulsar-3.2.1-bin.tar.gz

dc09d5246075f56456f00875a3b9654b3a31d69a3e502a61db4481e493c2d20babb46b48e47ff95b66ad60d0e6e3455b13e1f01259366ab6b982b07b00aabda6

apache-pulsar-3.2.1-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1271/

The tag to verify:
v3.2.1-candidate-2 (da98b8d8d0bc0c2bdd2d14d3e2e8058fb4c5dfd2)
https://github.com/apache/pulsar/commits/v3.2.1-candidate-2/

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.1-da98b8d/images/sha256-e3ae82ff5504470878f8c871e8737d71be8a58507937be3c2d6b4d31e7480f42?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.1-da98b8d/images/sha256-be975933560b0bff3ae5f1d72b9be1b150c049eff7692a7e14308648c4103f0e?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] Pulsar Release 3.2.1 Candidate 1

[guo jiwei]

Close this candidate, as we have a new fix, #22202, that needs to be
contained in the release.  I will raise a new candidate soon.


Regards
Jiwei Guo (Tboy)


On Wed, Mar 6, 2024 at 7:08 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 Wed, Mar 6, 2024 at 3:38 PM 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 Wed, Mar 6, 2024 at 2:33 AM Ran Gao  wrote:
> >
> > > +1(non-binding)
> > >
> > > 1. verify the GPG signature for the below files
> > > - apache-pulsar-3.2.1-bin.tar.gz.asc
> > > - apache-pulsar-3.2.1-src.tar.gz.asc
> > > 2. build the source code
> > > 3. test following the release verifying doc.
> > >
> > > Regards,
> > > Ran Gao
> > >
> > > On 2024/03/05 07:05:05 guo jiwei wrote:
> > > > This is the first release candidate for Apache Pulsar version 3.2.1.
> > > >
> > > > It fixes the following issues:
> > > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.2.1+label%3Acherry-picked%2Fbranch-3.2+
> > > >
> > > > *** Please download, test and verify on this release. This vote will
> > stay
> > > > open for at least 72 hours ***
> > > >
> > > > Note that we are verifying upon the source (tag), binaries are
> provided
> > > for
> > > > convenience.
> > > >
> > > > Source and binary files:
> > > >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.1-candidate-1/
> > > >
> > > > SHA-512 checksums:
> > > >
> > > >
> > >
> >
> d500ba21305d56b0f7b4355e1270e50ae5f60e5632b6632d66fec6d1178bb9fdf3f24caa709b6b36ea8273e5a2c094868cf30e389154bc8bb6397e7de4f1bf1d
> > > >
> > > > apache-pulsar-3.2.1-bin.tar.gz
> > > >
> > > >
> > >
> >
> 7aee1623db6dc95058cd0e7a4f108f8a3f43163d798a8eeeaecf5f335225c04f5a0518ce2dfb2d4fa29b7b5e54d27ba24af82fbb3542eb3ffc9e3602cb577878
> > > >
> > > > apache-pulsar-3.2.1-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1267/
> > > >
> > > > The tag to verify:
> > > > v3.2.1-candidate-1 (158d5eb670c9fd7b123c204533ac6cf8cb439ccd)
> > > > https://github.com/apache/pulsar/commits/v3.2.1-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:
> > > >
> > > > pulsar images:
> > > >
> > >
> >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.1-158d5eb/images/sha256-23f0cbd54b1fb504dcab16dfcce562ed735ab94db1c5f6fabbe9145f3a2d0fa8?context=repo
> > > > <
> > >
> >
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> > > >
> > > > pulsar-all images:
> > > >
> > >
> >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.1-158d5eb/images/sha256-80ab1d748eff18655a9c247beba74aa107624b9d3e7cc3a2f22e1246f0d3de83?context=repo
> > > >
> > > > Please download the source package, and follow the README to build
> > > > and run the Pulsar standalone service.
> > > >
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > >
> >
>

Re: [VOTE] Pulsar Release 3.2.1 Candidate 1

[guo jiwei]

+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 Wed, Mar 6, 2024 at 2:33 AM Ran Gao  wrote:

> +1(non-binding)
>
> 1. verify the GPG signature for the below files
> - apache-pulsar-3.2.1-bin.tar.gz.asc
> - apache-pulsar-3.2.1-src.tar.gz.asc
> 2. build the source code
> 3. test following the release verifying doc.
>
> Regards,
> Ran Gao
>
> On 2024/03/05 07:05:05 guo jiwei wrote:
> > This is the first release candidate for Apache Pulsar version 3.2.1.
> >
> > It fixes the following issues:
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.2.1+label%3Acherry-picked%2Fbranch-3.2+
> >
> > *** Please download, test and verify on this release. This vote will stay
> > open for at least 72 hours ***
> >
> > Note that we are verifying upon the source (tag), binaries are provided
> for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.1-candidate-1/
> >
> > SHA-512 checksums:
> >
> >
> d500ba21305d56b0f7b4355e1270e50ae5f60e5632b6632d66fec6d1178bb9fdf3f24caa709b6b36ea8273e5a2c094868cf30e389154bc8bb6397e7de4f1bf1d
> >
> > apache-pulsar-3.2.1-bin.tar.gz
> >
> >
> 7aee1623db6dc95058cd0e7a4f108f8a3f43163d798a8eeeaecf5f335225c04f5a0518ce2dfb2d4fa29b7b5e54d27ba24af82fbb3542eb3ffc9e3602cb577878
> >
> > apache-pulsar-3.2.1-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1267/
> >
> > The tag to verify:
> > v3.2.1-candidate-1 (158d5eb670c9fd7b123c204533ac6cf8cb439ccd)
> > https://github.com/apache/pulsar/commits/v3.2.1-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:
> >
> > pulsar images:
> >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.1-158d5eb/images/sha256-23f0cbd54b1fb504dcab16dfcce562ed735ab94db1c5f6fabbe9145f3a2d0fa8?context=repo
> > <
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> >
> > pulsar-all images:
> >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.1-158d5eb/images/sha256-80ab1d748eff18655a9c247beba74aa107624b9d3e7cc3a2f22e1246f0d3de83?context=repo
> >
> > Please download the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
>

Re: [VOTE] Pulsar Release 2.10.6 Candidate 1

[guo jiwei]

+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 Wed, Mar 6, 2024 at 11:15 AM Xiangying Meng  wrote:

> This is the first release candidate for Apache Pulsar, version 2.10.6.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is:pr+label:cherry-picked/branch-2.10+label:release/2.10.6+is:closed
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.6-candidate-1/
>
> SHA-512 checksums:
>
> 09f29265f8173331d4c05b470c4e77a31146172b27ef333f45d8c8a19074ef25061cb1e80872fc45c323c9ce8e2e17989c6df5d991ef84c4d245197303d9e6d7
>  apache-pulsar-2.10.6-bin.tar.gz
>
> 49c8836882818c6f38748dae26b51c598f163606c16993a3287ab1ce9f853a4aaa43c6729c1b6f6957738b4dead3818cd12026da68b328eb2d4ac0d0214957bb
>  apache-pulsar-2.10.6-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1270
>
> The tag to be voted upon:
> v2.10.6-candidate-1 (9c29b76ff2be865429ad44df8683aec80deacfba)
> https://github.com/apache/pulsar/releases/tag/v2.10.6-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Docker images:
>
> 
>
> https://hub.docker.com/layers/xiangyingmeng/pulsar/2.10.6/images/sha256-bf8f36e49ff44ef810ab2c76742121205e51d3a04c79afdb5d288c7d8a06443f?context=repo
>
> 
>
> https://hub.docker.com/layers/xiangyingmeng/pulsar-all/2.10.6/images/sha256-1b3a10db12f6d5a0acd2d4ed73eb11864b6b598294bb905b6ede34aef1157f23?context=repo
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>

Re: [VOTE] Pulsar Release 3.1.3 Candidate 1

[guo jiwei]

+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 Wed, Mar 6, 2024 at 2:25 AM Ran Gao  wrote:

> This is the first release candidate for Apache Pulsar version 3.1.3.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.3+label%3Acherry-picked%2Fbranch-3.1+
>
> *** Please download, test and verify on this release. This vote will stay
> open for at least 72 hours ***
>
> Note that we are verifying upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.3-candidate-1/
>
> SHA-512 checksums:
>
>
> 66e2cdbc28af2c1bc5aafa8f0a9c726c2d3bb33128f81632dadbb49d51397c9295d82c797094988eda80494ad217053e609e135fca3506e135f198f7d3ce18ed
>  apache-pulsar-3.1.3-bin.tar.gz
>
> ca4ffeeb13b77b1d36f2e8e121a7698f2b989f73f88d1f708745cf45875daf033a8395bb2941f43b5e0f014ee482dfdc01ad805938456511ddfa9777a07c
>  apache-pulsar-3.1.3-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1268
>
> The tag to verify:
> v3.1.3-candidate-1 (7e28e8404f50d065ed37a590c188b8934cae4a75)
> https://github.com/apache/pulsar/commits/v3.1.3-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Docker images:
>
>
> https://hub.docker.com/layers/gaoran10/pulsar/3.1.3-7e28e84/images/sha256-fe637cca3c98137f70237568f12d589b62d00483b5563ac8c63ac0a6a5d33b5c?context=repo
>
>
> https://hub.docker.com/layers/gaoran10/pulsar-all/3.1.3-7e28e84/images/sha256-219cf93ea289254de127bb52e0c0f1d324a6891fda583ec2ade02c0b0b5a508f?context=repo
>
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>
> Regards
> Ran Gao (gaoran10)
>

[VOTE] Pulsar Release 3.2.1 Candidate 1

[guo jiwei]

This is the first release candidate for Apache Pulsar version 3.2.1.

It fixes the following issues:
https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.2.1+label%3Acherry-picked%2Fbranch-3.2+

*** Please download, test and verify on this release. This vote will stay
open for at least 72 hours ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.1-candidate-1/

SHA-512 checksums:

d500ba21305d56b0f7b4355e1270e50ae5f60e5632b6632d66fec6d1178bb9fdf3f24caa709b6b36ea8273e5a2c094868cf30e389154bc8bb6397e7de4f1bf1d

apache-pulsar-3.2.1-bin.tar.gz

7aee1623db6dc95058cd0e7a4f108f8a3f43163d798a8eeeaecf5f335225c04f5a0518ce2dfb2d4fa29b7b5e54d27ba24af82fbb3542eb3ffc9e3602cb577878

apache-pulsar-3.2.1-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1267/

The tag to verify:
v3.2.1-candidate-1 (158d5eb670c9fd7b123c204533ac6cf8cb439ccd)
https://github.com/apache/pulsar/commits/v3.2.1-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:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.1-158d5eb/images/sha256-23f0cbd54b1fb504dcab16dfcce562ed735ab94db1c5f6fabbe9145f3a2d0fa8?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.1-158d5eb/images/sha256-80ab1d748eff18655a9c247beba74aa107624b9d3e7cc3a2f22e1246f0d3de83?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.



Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-339: Introducing the --log-topic Option for Pulsar Sinks and Sources

[guo jiwei]

+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: [VOTE] Reactive Java client for Apache Pulsar 0.5.3 Candidate 1

[guo jiwei]

+1 binding

- Validated checksum and signature
- Compared source tarballs with the git tag ones
- Ran build and tests with JDK17


Regards
Jiwei Guo (Tboy)


On Tue, Feb 20, 2024 at 4:10 PM Nicolò Boschi  wrote:

> +1 binding
>
> - Validated checksum and signature
> - Compared source tarballs with the git tag ones
> - Ran build and tests with JDK21 - all green
>
> Thanks,
> Nicolò Boschi
>
>
> Il giorno lun 19 feb 2024 alle ore 18:06 Enrico Olivelli <
> eolive...@gmail.com> ha scritto:
>
> > +1 (binding)
> >
> > Validated checksum and signature
> > All tests passed on Ubuntu, JDK1
> >
> > Thanks for running the release
> >
> > Enrico
> >
> > Il giorno ven 16 feb 2024 alle ore 19:01 Lari Hotari
> >  ha scritto:
> > >
> > > +1 (binding)
> > >
> > > Validated source artifacts
> > > - checked sha512 checksum
> > > - checked signature
> > >
> > > Validated binaries
> > > - ran sample app
> > >
> > > -Lari
> > >
> > > On Fri, 16 Feb 2024 at 17:42, Chris Bono  wrote:
> > > >
> > > > Following PIP-205: Reactive Java client for Apache Pulsar (
> > > > https://github.com/apache/pulsar/issues/17335), this is release
> > > > candidate 1 for the Reactive Java client for Apache Pulsar, version
> > 0.5.3.
> > > >
> > > > *** 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 in the Maven
> > repository
> > > > are provided for convenience.
> > > >
> > > > Source package:
> > > >
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.3-candidate-1/
> > > >
> > > > SHA-512 checksums:
> > > >
> >
> 3ba5c623d11329c3336657b3e081ae80a2ee581b1a206d4d5e1e84642ad143cab8462ef325cfa1082b89c18dae65b9bf51f063c97bd970fecb0d8b943bb28535
> > > >  pulsar-client-reactive-0.5.3-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1266/
> > > >
> > > > The tag to be voted upon:
> > > > v0.5.3-candidate-1 (8c8d087abaa04c413150d6931451996e9fad8c2c)
> > > >
> >
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.3-candidate-1
> > > >
> > > > Please download the source package, and follow detailed instructions
> > > > for pulsar-client-reactive release validation at
> > > >
> >
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > > > .
> > > >
> > > > Best regards
> > > >
> > > > Chris
> >
>

[ANNOUNCE] Apache Pulsar 3.2.0 released

[guo jiwei]

The Apache Pulsar team is proud to announce Apache Pulsar version 3.2.0.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management
for
subscribers, and cross-datacenter replication.

For Pulsar release details and downloads, visit:

https://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
Jiwei Guo (Tboy)

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

[guo jiwei]

Thanks.
Close this vote, and vote pass with 3(+1) binding

Penghui.
Jiwei
Yubiao

 and 1 (+0) binding
 yunze


Regards
Jiwei Guo (Tboy)


On Mon, Feb 5, 2024 at 12:08 AM Yubiao Feng
 wrote:

> +1 (binding)
>
> - Run standalone
> - Checked producer and consumer
> - Verified the Cassandra connector
> - Verified the Stateful function
>
> Thanks
> Yubiao Feng
>
> On Wed, Jan 31, 2024 at 11:40 PM guo jiwei  wrote:
>
> > This is the fifth release candidate for Apache Pulsar version 3.2.0.
> >
> > It fixes the following issues:
> > https://github.com/apache/pulsar/milestone/36?closed=1
> >
> > *** Please download, test and verify on this release. This vote will stay
> > open for at least 72 hours ***
> >
> > Note that we are verifying upon the source (tag), binaries are provided
> for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/
> >
> > SHA-512 checksums:
> >
> >
> >
> 194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c
> >
> > apache-pulsar-3.2.0-bin.tar.gz
> >
> >
> >
> 7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93
> >
> > apache-pulsar-3.2.0-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1265/
> >
> > The tag to verify:
> > v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
> > https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/
> >
> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> >
> > Docker images:
> >
> > pulsar images:
> >
> >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo
> > <
> >
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> > >
> > pulsar-all images:
> >
> >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo
> >
> > Please download the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
>

Re: [VOTE] Pulsar Release 3.2.0 Candidate 5

[guo jiwei]

+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 Sun, Feb 4, 2024 at 3:42 PM Yunze Xu  wrote:

> I changed my binding -1 to +0 now.
>
> This behavior change is implicit but acceptable. The previous way of
> setting up standalone should be wrong but it just accidentally works.
> When system topic policy is enabled, the `brokerClientXxx` arguments
> must be configured correctly to ensure the system topic policies can
> be loaded or updated. To disable this limitation, we should disable
> the system topic policy, while it's enabled by default since 2.11 [1].
>
> [1] https://github.com/apache/pulsar/pull/15619
>
> Thanks,
> Yunze
>
> On Fri, Feb 2, 2024 at 9:45 PM Yunze Xu  wrote:
> >
> > I pushed a fix: https://github.com/apache/pulsar/pull/22014
> >
> > Thanks,
> > Yunze
> >
> > On Fri, Feb 2, 2024 at 9:15 PM Yunze Xu  wrote:
> > >
> > > Yes. I wrote a unit test in Java [1]. This breaking change is
> > > introduced by #21445 [2], which requires the topic policies to be
> > > available in `BrokerTopic#getTopic`.
> > >
> > > However, when the built-in client is not configured correctly, e.g.
> > > `brokerClientXxx` authentication arguments are not configured
> > > correctly, `BrokerService#getTopicPoliciesBypassSystemTopic` will
> > > always fail, which makes `BrokerService#getTopic` fail.
> > >
> > > [1]
> https://github.com/BewareMyPower/pulsar/commit/eab7002299764765ef43f7d6d63a4bd993bba9c0
> > > [2] https://github.com/apache/pulsar/pull/21445
> > >
> > > Thanks,
> > > Yunze
> > >
> > > On Fri, Feb 2, 2024 at 8:41 PM PengHui Li  wrote:
> > > >
> > > > It looks like some tests are missed in the Java client?
> > > > Otherwise, the java client detected this break change.
> > > >
> > > > Thanks,
> > > > Penghui
> > > >
> > > > On Fri, Feb 2, 2024 at 11:40 AM Yunze Xu  wrote:
> > > >
> > > > > -1 (binding)
> > > > >
> > > > > I observed a regression for Pulsar 3.1.2 recently because the
> latest
> > > > > image was just updated yesterday [1]. It seems related to the SSL
> > > > > hostname verification because the failed tests come from
> > > > > https://github.com/apache/pulsar-client-cpp/pull/126. I tested the
> > > > > `technoboy8/pulsar:3.2.0-8025763` image locally and found the tests
> > > > > still failed. You can also check the CI test result [2].
> > > > >
> > > > > Currently, I'm debugging locally to see why the tests failed.
> Before
> > > > > figuring it out, we should prevent this release.
> > > > >
> > > > > [1]
> > > > >
> https://github.com/apache/pulsar-client-cpp/pull/392#issuecomment-1922698516
> > > > > [2] https://github.com/apache/pulsar-client-cpp/pull/394
> > > > >
> > > > > Thanks,
> > > > > Yunze
> > > > >
> > > > > On Thu, Feb 1, 2024 at 8:57 AM 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 Wed, Jan 31, 2024 at 11:40 PM guo jiwei 
> wrote:
> > > > > >
> > > > > > > This is the fifth release candidate for Apache Pulsar version
> 3.2.0.
> > > > > > >
> > > > > > > It fixes the following issues:
> > > > > > > https://github.com/apache/pulsar/milestone/36?closed=1
> > > > > > >
> > > > > > > *** Please download, test and verify on this release. This
> vote will
> > > > > stay
> > > > > > > open for at least 72 hours ***
> > > > > > >
> > > > > > > Note that we are verifying upon the source (tag), binaries are
> > > > > provided for
> > > > > >

[VOTE] Pulsar Release 3.2.0 Candidate 5

[guo jiwei]

This is the fifth release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This vote will stay
open for at least 72 hours ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/

SHA-512 checksums:

194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c

apache-pulsar-3.2.0-bin.tar.gz

7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1265/

The tag to verify:
v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.



Regards
Jiwei Guo (Tboy)

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5

[guo jiwei]

> I think we need to state the release deadline before each feature
release. What’s the deadline of 3.2.0? @Jiwei Maybe we could start the vote
now?

Yes, I will raise the `VOTE` thread soon.


Regards
Jiwei Guo (Tboy)


On Tue, Jan 30, 2024 at 9:55 AM Zike Yang  wrote:

> Based on the release
> policy(https://pulsar.apache.org/contribute/release-policy/), for each
> feature release, there would be three weeks to verify the release
> candidate before the release deadline. And the first two weeks are
> only for verification.
>
> I think we need to state the release deadline before each feature
> release. What’s the deadline of 3.2.0? @Jiwei Maybe we could start the
> vote now?
>
> > We don't have that in our release process documented at
> https://pulsar.apache.org/contribute/release-process/ .
>
> Indeed, we need to add this guidance into the release process to align
> it with the release policy.
>
> Thanks,
> Zike Yang
>
> On Mon, Jan 29, 2024 at 11:25 PM Lari Hotari  wrote:
> >
> > Is this a release VOTE thread? I think that the subject of the thread
> should state that explicitly.
> >
> > What does a VERIFY thread mean? We don't have that in our release
> process documented at
> https://pulsar.apache.org/contribute/release-process/ .
> >
> > Thanks,
> >
> > -Lari
> >
> > On 2024/01/27 15:14:27 guo jiwei wrote:
> > > This is the fifth release candidate for Apache Pulsar version 3.2.0.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar/milestone/36?closed=1
> > >
> > > *** Please download, test and verify on this release. This release
> > > candidate verification will stay open until Feb 2 ***
> > >
> > > Note that we are verifying upon the source (tag), binaries are
> provided for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/
> > >
> > > SHA-512 checksums:
> > >
> > >
> 194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c
> > >
> > > apache-pulsar-3.2.0-bin.tar.gz
> > >
> > >
> 7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93
> > >
> > > apache-pulsar-3.2.0-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1265/
> > >
> > > The tag to verify:
> > > v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
> > > https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/
> > >
> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > >
> > > Docker images:
> > >
> > > pulsar images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo
> > > <
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> >
> > > pulsar-all images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo
> > >
> > > Please download the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> > > Note that this RC doesn't require a formal vote, but we would also
> > > appreciate your feedback with +1/-1. And please provide specific
> > > comments if your feedback is not +1.
> > >
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
>

[VERIFY] Pulsar Release 3.2.0 Candidate 5

[guo jiwei]

This is the fifth release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This release
candidate verification will stay open until Feb 2 ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/

SHA-512 checksums:

194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c

apache-pulsar-3.2.0-bin.tar.gz

7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1265/

The tag to verify:
v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.

Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.



Regards
Jiwei Guo (Tboy)

Re: [VOTE] Release Apache Pulsar Helm Chart 3.2.0 based on 3.2.0-candidate-3

[guo jiwei]

+1 (binding)

- Checked the license
- Verify the signature
- Deploy pulsar cluster on local docker-desktop


Regards
Jiwei Guo (Tboy)


On Thu, Jan 25, 2024 at 12:17 AM Lari Hotari  wrote:

> +1 (binding)
>
> -Lari
>
> On 2024/01/21 08:45:04 Lari Hotari wrote:
> > Hello Apache Pulsar Community,
> >
> > This is a call for the vote to release the Apache Pulsar Helm Chart
> version 3.2.0.
> >
> > Release notes for 3.2.0-candidate-3:
> >
> https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.2.0-candidate-3
> >
> > The release candidate is available at:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/3.2.0-candidate-3/
> >
> > pulsar-chart-3.2.0-source.tar.gz - is the "main source release".
> > pulsar-3.2.0.tgz - is the binary Helm Chart release.
> >
> > Public keys are available at: https://www.apache.org/dist/pulsar/KEYS
> >
> > For convenience "index.yaml" has been uploaded (though excluded from
> voting), so you can also run the below commands.
> >
> > helm repo add --force-update apache-pulsar-dist-dev
> https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/3.2.0-candidate-3/
> > helm repo update
> > helm install pulsar apache-pulsar-dist-dev/pulsar --version 3.2.0 --set
> affinity.anti_affinity=false
> >
> > pulsar-3.2.0.tgz.prov - is also uploaded for verifying Chart Integrity,
> though it is not strictly required for releasing the artifact based on ASF
> Guidelines.
> >
> > You can optionally verify this file using this helm plugin
> https://github.com/technosophos/helm-gpg, or by using helm --verify (
> https://helm.sh/docs/helm/helm_verify/).
> >
> > helm fetch --prov apache-pulsar-dist-dev/pulsar
> > helm plugin install https://github.com/technosophos/helm-gpg
> > helm gpg verify pulsar-3.2.0.tgz
> >
> > The vote will be 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)".
> >
> > For license checks, the .rat-excludes files is included, so you can run
> the following to verify licenses (just update ):
> >
> > tar -xvf pulsar-chart-3.2.0-source.tar.gz
> > cd pulsar-chart-3.2.0
> > java -jar /apache-rat-0.15/apache-rat-0.15.jar . -E .rat-excludes
> >
> > Please note that the version number excludes the `-candidate-X` string,
> so it's now
> > simply 3.2.0. This will allow us to rename the artifact without modifying
> > the artifact checksums when we actually release it.
> >
> > Thanks,
> > Lari
> >
>

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 4

[guo jiwei]

Thanks Lari.
We have confirmed there is a break change from the function part.
Before, the output of querystate was

  "key": "hello",
  "numberValue": 20,
  "version": 19

And now, it was changed to

{
  "key": "hello",
  "stringValue": "\u\u\u\u\u\u\u\n",
  "numberValue": 10
}


We need to drop this candidate, I will raise a new one when it is fixed.


Regards
Jiwei Guo (Tboy)


On Thu, Jan 25, 2024 at 12:17 AM Lari Hotari  wrote:

> +1 (binding)
>
> - checked the source and binary files
>   - checksums matched
>   - signatures were ok
> - ran validation steps in
> https://pulsar.apache.org/contribute/validate-release-candidate/
>
> -Lari
>
>
>
> On 2024/01/22 14:43:14 guo jiwei wrote:
> > This is the fourth release candidate for Apache Pulsar version 3.2.0.
> >
> > It fixes the following issues:
> > https://github.com/apache/pulsar/milestone/36?closed=1
> >
> > *** Please download, test and verify on this release. This release
> > candidate verification will stay open until Jan 28 ***
> >
> > Note that we are verifying upon the source (tag), binaries are provided
> for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-4/
> >
> > SHA-512 checksums:
> >
> >
> de4beeb266dea2bdce0b6a3cf213bd36235f89003ed42cb212eb2eab2c784255ca8d82a4c8ed7d02f1ae7598dae114f7717f0828af41ce15573ab2606b0205f9
> >
> > apache-pulsar-3.2.0-bin.tar.gz
> >
> >
> 0e7d0f3043b85d54a3b346d5b702db358437ee178596967f02d79472ce2797d46a4af4692463c349187afed2ea8f084b071e5711b311fd332d23ac4f84a3d895
> >
> > apache-pulsar-3.2.0-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1264/
> >
> > The tag to verify:
> > v3.2.0-candidate-4 (bca08d98ab742d241d31b2e8d7673273605b2e16)
> > https://github.com/apache/pulsar/commits/v3.2.0-candidate-4/
> >
> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> >
> > Docker images:
> >
> > pulsar images:
> >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-bca08d9/images/sha256-714e977706b44a2ed9376a8d7328ab1bf72217553e9c127ef9f7a33c0f3d8e4b?context=repo
> > <
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> >
> > pulsar-all images:
> >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-bca08d9/images/sha256-668ab662d6506bc154a12da5359b944d8115596e8d09035c7213fe073fbf5078?context=repo
> >
> > Please download the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
> > Note that this RC doesn't require a formal vote, but we would also
> > appreciate your feedback with +1/-1. And please provide specific
> > comments if your feedback is not +1.
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
>

[VERIFY] Pulsar Release 3.2.0 Candidate 4

[guo jiwei]

This is the fourth release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This release
candidate verification will stay open until Jan 28 ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-4/

SHA-512 checksums:

de4beeb266dea2bdce0b6a3cf213bd36235f89003ed42cb212eb2eab2c784255ca8d82a4c8ed7d02f1ae7598dae114f7717f0828af41ce15573ab2606b0205f9

apache-pulsar-3.2.0-bin.tar.gz

0e7d0f3043b85d54a3b346d5b702db358437ee178596967f02d79472ce2797d46a4af4692463c349187afed2ea8f084b071e5711b311fd332d23ac4f84a3d895

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1264/

The tag to verify:
v3.2.0-candidate-4 (bca08d98ab742d241d31b2e8d7673273605b2e16)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-4/

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-bca08d9/images/sha256-714e977706b44a2ed9376a8d7328ab1bf72217553e9c127ef9f7a33c0f3d8e4b?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-bca08d9/images/sha256-668ab662d6506bc154a12da5359b944d8115596e8d09035c7213fe073fbf5078?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.

Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.


Regards
Jiwei Guo (Tboy)

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 3

[guo jiwei]

Hi Lari,
   I will build the new candidate-4 soon.

Regards
Jiwei Guo (Tboy)


On Mon, Jan 22, 2024 at 5:02 AM Lari Hotari  wrote:

> Thank you for reviewing and merging the PR #21937 (restoring the broker id
> format). I have cherry-picked that to branch-3.2 together with it's
> dependency PR #21894 (fixes leader broker election when advertised
> listeners is configured) and in addition #21871 (pulsar-bom).
>
> From my side we are ready for the next release candidate.
>
> Thank you, Jiwei Guo (Tboy), for driving the release and handling all of
> the extra work related to the multiple RCs.
>
> -Lari
>
> On 2024/01/20 16:46:23 Lari Hotari wrote:
> > As a follow up, I have created
> https://github.com/apache/pulsar/pull/21937 to restore the broker id
> (previously called "lookup service address") to match the format used in
> existing Pulsar releases.
> >
> > There was a misconception that PR #17136 would have changed the broker
> id ("lookup service address") format in Pulsar 2.11 release. That PR didn't
> change the format. It can be verified from the diff [1].
> >
> > Please review the PR https://github.com/apache/pulsar/pull/21937. After
> merging, I suggest that we cherry-pick it to branch-3.2 together with the
> fix for the advertised listeners bug related to broker id [2].
> >
> > Since we need yet another RC for 3.2.0, let's consider adding the BOM
> support (PIP-326) to 3.2.0 release as suggested by Chris Bono in another
> thread. [3]
> >
> > -Lari
> >
> > 1 - https://github.com/apache/pulsar/pull/17136/files
> > 2 - https://github.com/apache/pulsar/pull/21894
> > 3 - https://lists.apache.org/thread/9vqgwpqxjo04n1pyzg0s00nrb3sl8r07
> >
> > On 2024/01/19 19:55:10 Lari Hotari wrote:
> > > -1 from my side.
> > >
> > > Explanation: I didn't notice until now that the "lookup service
> address" (now brokerId ) was modified for 3.2.0 in this PR
> https://github.com/apache/pulsar/pull/21015 based on this issue report
> https://github.com/apache/pulsar/issues/21012 .
> > >
> > > I'm waiting for answers on the question in 21012 so that I could
> understand the reason why this was considered a problem in the first place.
> > >
> > > The "lookup service address" was never meant to be used as a "service
> address" for the broker and this confusion was addressed recently by
> https://github.com/apache/pulsar/pull/21894 . "lookup service address"
> was renamed to "broker id" which hopefully clarifies that it's just an
> unique runtime identifier for the broker (which is used in Pulsar load
> manager to as the broker's unique id).
> > >
> > > I'll follow-up asap on this after receiving answers.
> > >
> > > -Lari
> > >
> > >
> > > On 2024/01/19 07:49:11 guo jiwei wrote:
> > > > This is the third release candidate for Apache Pulsar version 3.2.0.
> > > >
> > > > It fixes the following issues:
> > > > https://github.com/apache/pulsar/milestone/36?closed=1
> > > >
> > > > *** Please download, test and verify on this release. This release
> > > > candidate verification will stay open until Jan 25 ***
> > > >
> > > > Note that we are verifying upon the source (tag), binaries are
> provided for
> > > > convenience.
> > > >
> > > > Source and binary files:
> > > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-3/
> > > >
> > > > SHA-512 checksums:
> > > >
> > > >
> 27e70dfa4e1fd6b300f92463c6ef3165dcf02ac2f933199bf9f1e29693d538a1012e950ad3a1195833275504b0924623d068d70e4eefca0cf2819dfc6b2cd698
> > > >
> > > > apache-pulsar-3.2.0-bin.tar.gz
> > > >
> > > >
> 9d4c889889a920a133a7a07035dbd2cfc61b63aa112b072ea6138aad228358cbbc04c71953839321cf9896458aed18965fb15b547e8890969e95bf3426134470
> > > >
> > > > apache-pulsar-3.2.0-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1263/
> > > >
> > > > The tag to verify:
> > > > v3.2.0-candidate-3 (9630608ff1fd726cbd124a2e65a1a50c3802b5dc)
> > > > https://github.com/apache/pulsar/commits/v3.2.0-candidate-3/
> > > >
> > > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > > >
> > > > Docker images:
> &g

[VERIFY] Pulsar Release 3.2.0 Candidate 3

[guo jiwei]

This is the third release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This release
candidate verification will stay open until Jan 25 ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-3/

SHA-512 checksums:

27e70dfa4e1fd6b300f92463c6ef3165dcf02ac2f933199bf9f1e29693d538a1012e950ad3a1195833275504b0924623d068d70e4eefca0cf2819dfc6b2cd698

apache-pulsar-3.2.0-bin.tar.gz

9d4c889889a920a133a7a07035dbd2cfc61b63aa112b072ea6138aad228358cbbc04c71953839321cf9896458aed18965fb15b547e8890969e95bf3426134470

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1263/

The tag to verify:
v3.2.0-candidate-3 (9630608ff1fd726cbd124a2e65a1a50c3802b5dc)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-3/

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-9630608/images/sha256-ab30ee3fcde4667072d864cb82d774fe90cdd1d8e4b8ed70b44a97aa292ea826?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-9630608/images/sha256-48fccc356637961402627ccbf900f8ea08cf1c325a32d2ea32660a3f4d7a365b?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.

Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.



Regards
Jiwei Guo (Tboy)

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 2

[guo jiwei]

Thanks Penghui and PengCheng, I will drop this candidate and raise a new
one after #21921 <https://github.com/apache/pulsar/pull/21921> get merged.


Regards
Jiwei Guo (Tboy)


On Thu, Jan 18, 2024 at 9:45 PM Pengcheng Jiang
 wrote:

> > 1. The querystate exit with `Reason: key 'hello' doesn't exist`, which
> the
> old version will not exit
>
> there is a bug for it, a 500 error is returned instead of a 404 error,
> there is the fix: https://github.com/apache/pulsar/pull/21921
>
> > The output missed the `version` field
>
> In PIP-312 <https://github.com/apache/pulsar/pull/21597>, I used the
> `StateStore` instead of bookkeeper's `StorageAdminClient` to manage state
> keys in `ComponentImpl`, this is to make functions support
> `StateStoreImpls` other than the bookkeeper
> but for now the `StateStore.get` method doesn't return `version` yet, so
> there is no `version` field in the output, we may expose the `version`
> field to the `StateStore.get` in the future
>
> Regards,
> Jiang Pengcheng
>
> PengHui Li  于2024年1月18日周四 11:29写道：
>
> > It looks like something broke the behavior of the querystate from Pulsar
> > Functions.
> >
> > 1. The querystate exit with `Reason: key 'hello' doesn't exist`, which
> the
> > old version will not exit
> >
> > ```
> > lipenghui@lipenghuis-MacBook-Pro apache-pulsar-3.2.0 % bin/pulsar-admin
> > functions querystate --tenant test --namespace test-namespace --name
> > word_count -k hello -w
> > key 'hello' doesn't exist.
> >
> > Reason: key 'hello' doesn't exist.
> > ```
> >
> > 2. The output missed the `version` field
> >
> > ```
> >   "key": "hello",
> >   "numberValue": 20,
> >   "version": 19
> > ```
> >
> > ```
> >   "key": "hello",
> >   "stringValue": "\u\u\u\u\u\u\u\n",
> >   "numberValue": 10
> > ```
> >
> > Regards,
> > Penghui
> >
> > On Tue, Jan 16, 2024 at 6:34 PM Zixuan Liu  wrote:
> >
> > > +1 (non-binding)
> > >
> > > - Checked the checksums and signatures
> > > - Built with Temurin-17.0.6+10
> > > - Run standalone
> > > - Checked producer and consumer
> > >
> > > Thanks,
> > > Zixuan
> > >
> > > guo jiwei  于2024年1月16日周二 15:57写道：
> > >
> > > > This is the second release candidate for Apache Pulsar version 3.2.0.
> > > >
> > > > It fixes the following issues:
> > > > https://github.com/apache/pulsar/milestone/36?closed=1
> > > >
> > > > *** Please download, test and verify on this release. This release
> > > > candidate verification will stay open until Jan 15 ***
> > > >
> > > > Note that we are verifying upon the source (tag), binaries are
> provided
> > > for
> > > > convenience.
> > > >
> > > > Source and binary files:
> > > >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-2/
> > > >
> > > > SHA-512 checksums:
> > > >
> > > >
> > > >
> > >
> >
> 57af4de0531baada79ff3eb5e51659ae3d2b6732840a27861636d3538d8cca2b3aeb77d3f5cecf37dc5d8a0de11a05d0775ae2d2ca9398f9747fbe662e1cdeae
> > > >
> > > > apache-pulsar-3.2.0-bin.tar.gz
> > > >
> > > >
> > > >
> > >
> >
> 7ddd8df261f4ffeed2e4f029aa475f523bb9505869870db681a57b7df25af01d5670ba00bc7e062ddae0b962eaed9ee828a4cd7f4744a965afd77e9ae1239d6a
> > > >
> > > > apache-pulsar-3.2.0-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1262/
> > > >
> > > > The tag to verify:
> > > > v3.2.0-candidate-2 (5348e1b9124052a454f66769ae3e9f54ee0a75d4)
> > > > https://github.com/apache/pulsar/commits/v3.2.0-candidate-2/
> > > >
> > > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > > >
> > > > Docker images:
> > > >
> > > > pulsar images:
> > > >
> > > >
> > >
> >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-5348e1b/images/sha256-cf02a08e588ca493d10dbe472b72f5e64e4f90b8b5ae01e91321f336776a5a4e?context=repo
> > > > <
> > > >
> > >
> >
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> > > > >
> > > > pulsar-all images:
> > > >
> > > >
> > >
> >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-5348e1b/images/sha256-801e395fc26257e2beb5ea0574fe27f5a4ff956c85cbcd6b362432d6dda28b95?context=repo
> > > >
> > > > Please download the source package, and follow the README to build
> > > > and run the Pulsar standalone service.
> > > >
> > > > Note that this RC doesn't require a formal vote, but we would also
> > > > appreciate your feedback with +1/-1. And please provide specific
> > > > comments if your feedback is not +1.
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > >
> >
>

Re: [VOTE] PIP-330: getMessagesById gets all messages

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Wed, Jan 17, 2024 at 5:39 PM 太上玄元道君  wrote:

> +1 nonbinding
>
>
> > 2024年1月17日 17:35，Asaf Mesika  写道：
> >
> > +1 (non-binding)
> >
> > On Tue, Jan 16, 2024 at 4:43 AM Dezhi Liu  wrote:
> >
> >> +1 (non-binding)
> >>
> >> Thanks,
> >> Dezhi Liu
> >>
> >> On 2024/01/15 09:33:48 Zixuan Liu wrote:
> >>> Hi Pulsar Community,
> >>>
> >>> Voting for PIP-330: getMessagesById gets all messages
> >>>
> >>> PIP: https://github.com/apache/pulsar/pull/21873
> >>> Discussion thread:
> >>> https://lists.apache.org/thread/vqyh3mvtvovd383sd8zxnlzsspdr863z
> >>>
> >>> Thanks,
> >>> Zixuan
> >>>
> >>
>
>

Re: [VOTE] PIP-329: Strategy for maintaining the latest tag to Pulsar docker images

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Jan 15, 2024 at 5:50 PM Zixuan Liu  wrote:

> +1(non-binding)
>
> Thanks,
> Zixuan
>
> Zike Yang  于2024年1月15日周一 16:14写道：
>
> > Hi, all
> >
> > I'm starting the vote for PIP-329: Strategy for maintaining the latest
> > tag to Pulsar docker images
> >
> > PIP link: https://github.com/apache/pulsar/pull/21872
> >
> > Thanks,
> > Zike Yang
> >
>

Re: [VOTE]PIP-321: Split the responsibilities of namespace replication-clusters

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Tue, Jan 16, 2024 at 2:41 PM Xiangying Meng  wrote:

> Dear Pulsar community,
>
> I am initiating a voting thread for "PIP-321: Split the responsibilities of
> namespace replication-clusters".
>
> Here is the pull request for PIP-321:
> https://github.com/apache/pulsar/pull/21648
>
> And the discussion thread:
> https://lists.apache.org/thread/87qfp8ht5s0fvw2y4t3j9yzgfmdzmcnz
>
> Highlight:
> This proposal introduces a new feature for topics, allowing a topic to be
> loaded across different clusters without data replication between these
> clusters. It also introduces more granular control over `allowed_clusters`
> at the namespace level.
>
> Please review the PIP document and cast your vote!
>
> Thank you,
>
> Xiangying
>

[VERIFY] Pulsar Release 3.2.0 Candidate 2

[guo jiwei]

This is the second release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This release
candidate verification will stay open until Jan 15 ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-2/

SHA-512 checksums:

57af4de0531baada79ff3eb5e51659ae3d2b6732840a27861636d3538d8cca2b3aeb77d3f5cecf37dc5d8a0de11a05d0775ae2d2ca9398f9747fbe662e1cdeae

apache-pulsar-3.2.0-bin.tar.gz

7ddd8df261f4ffeed2e4f029aa475f523bb9505869870db681a57b7df25af01d5670ba00bc7e062ddae0b962eaed9ee828a4cd7f4744a965afd77e9ae1239d6a

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1262/

The tag to verify:
v3.2.0-candidate-2 (5348e1b9124052a454f66769ae3e9f54ee0a75d4)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-2/

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-5348e1b/images/sha256-cf02a08e588ca493d10dbe472b72f5e64e4f90b8b5ae01e91321f336776a5a4e?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-5348e1b/images/sha256-801e395fc26257e2beb5ea0574fe27f5a4ff956c85cbcd6b362432d6dda28b95?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.

Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.2 Candidate 1

[guo jiwei]

+1 (binding)

- verified source package checksum and signature.
- verified binary `./scripts/validate_staging_repo.sh 0.5.2
https://repository.apache.org/content/repositories/orgapachepulsar-1261`
- verified the HelloPulsarClientReactive with maven artifacts


Regards
Jiwei Guo (Tboy)


On Mon, Jan 15, 2024 at 7:00 PM Lari Hotari  wrote:

> +1 (binding)
>
> - verified source package checksum and signature.
> - verified staged maven artifacts by running a test app built with Gradle.
>   - used "./scripts/validate_staging_repo.sh 0.5.2
> https://repository.apache.org/content/repositories/orgapachepulsar-1261;
> command for an automated check
>
> -Lari
>
> On 2024/01/12 20:24:36 Chris Bono wrote:
> > Following PIP-205: Reactive Java client for Apache Pulsar (
> > https://github.com/apache/pulsar/issues/17335), this is release
> > candidate 1 for the Reactive Java client for Apache Pulsar, version
> 0.5.2.
> >
> > *** 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 in the Maven
> repository
> > are provided for convenience.
> >
> > Source package:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.2-candidate-1/
> >
> > SHA-512 checksums:
> >
> 206a790ef54a20683a26e5c585676ca4a4c4410468cc5a9eec2a2331778f17bbd42b82a4d5b4440fa8aa7059e66c2227ad9e55588202e80b7ea72a589b6466ed
> >  pulsar-client-reactive-0.5.2-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1261/
> >
> > The tag to be voted upon:
> > v0.5.2-candidate-1 (0ec250d65868d61c64333f7f3b0c439b54257da7)
> >
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.2-candidate-1
> >
> > Please download the source package, and follow detailed instructions
> > for pulsar-client-reactive release validation at
> >
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > .
> >
> > Best regards
> >
> > Chris Bono
> >
>

Re: [VOTE] PIP-325: Add command to abort transaction

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Jan 15, 2024 at 9:36 AM PengHui Li  wrote:

> +1 (binding)
>
> Regards,
> Penghui
>
> On Mon, Jan 8, 2024 at 4:00 PM Enrico Olivelli 
> wrote:
>
> > +1 (binding)
> >
> >
> > Enrico
> >
> > Il Lun 8 Gen 2024, 03:55 ruihongzhou  ha
> > scritto:
> >
> > > Hi community,
> > >
> > > This thread is to start a vote for PIP-325: Add command to abort
> > > transaction.
> > >
> > > PIP: https://github.com/apache/pulsar/pull/21731
> > >
> > > Releted PR: https://github.com/apache/pulsar/pull/21630
> > >
> > >  Discussion thread:
> > > https://lists.apache.org/thread/ssgngyrlgx36zvygvsd5b2dm5q6krn0f
> > >
> > > Ruihong
> > >
> > >
> > >
> > > ruihongzhou
> > > ruihongz...@qq.com
> > >
> > >
> > >
> > > 
> >
>

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 1

[guo jiwei]

Hi Zike,
   Thanks for reporting this, drop this candidate, I will raise a new
candidate after the fix.


Regards
Jiwei Guo (Tboy)


On Fri, Jan 12, 2024 at 10:46 AM Zike Yang  wrote:

> There is a regression bug introduced in 3.2.0:
> https://github.com/apache/pulsar/issues/21888
> The producer name will be conflicted when multiple consumers in the
> same topic and subscription send messages to the same DLQ
> concurrently.
>
> I will provide a fix later.
>
> Best,
> Zike Yang
>
> On Tue, Jan 9, 2024 at 8:34 PM houxiaoyu  wrote:
> >
> > +1 (non-binding)
> >
> >
> > - Checksum and signatures
> > - Build on Mac, using JDK17.0.8
> > - Run Pulsar standalone and produce/consume case
> >
> > Thanks,
> > Xiaoyu Hou
> >
> > guo jiwei  于2024年1月9日周二 16:15写道：
> > >
> > > This is the first release candidate for Apache Pulsar version 3.2.0.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar/milestone/36?closed=1
> > >
> > > *** Please download, test and verify on this release. This release
> > > candidate verification will stay open until Jan 15 ***
> > >
> > > Note that we are verifying upon the source (tag), binaries are
> provided for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-1/
> > >
> > > SHA-512 checksums:
> > >
> > >
> cf4e661d78f4194f4cde88e102bc9a734e2777613c5315f09115d64236759fbc5ded868c7e0cc3d07813c3fd34b1b123ca6f06f4335d6c9c96393789c6eda5bc
> > >
> > > apache-pulsar-3.2.0-bin.tar.gz
> > >
> > >
> 6ebe72de801db9a3f51dde39587b93d947904856385a21020319edb6988776fd68ec079471bcce5db17ea1b79c58e22ebf89a854debb40437ad9dc2bc2350357
> > >
> > > apache-pulsar-3.2.0-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1259/
> > >
> > > The tag to verify:
> > > v3.2.0-candidate-1 (4ab09374ade3c1402812c3c6be0d07984ab373a4)
> > > https://github.com/apache/pulsar/commits/v3.2.0-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:
> > >
> > > pulsar images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-4ab0937/images/sha256-06d35d60f3bd4f954b8b1b6f4cc4f663556ace5da097173f41a61622e81a76b9?context=repo
> > > <
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> >
> > > pulsar-all images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-4ab0937/images/sha256-a6f87bc5fd8025f096f35f26d47303267452e35d92f9f974d8536b61543ddbeb?context=repo
> > >
> > > Please download the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> > > Note that this RC doesn't require a formal vote, but we would also
> > > appreciate your feedback with +1/-1. And please provide specific
> > > comments if your feedback is not +1.
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
>

[VERIFY] Pulsar Release 3.2.0 Candidate 1

[guo jiwei]

This is the first release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This release
candidate verification will stay open until Jan 15 ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-1/

SHA-512 checksums:

cf4e661d78f4194f4cde88e102bc9a734e2777613c5315f09115d64236759fbc5ded868c7e0cc3d07813c3fd34b1b123ca6f06f4335d6c9c96393789c6eda5bc

apache-pulsar-3.2.0-bin.tar.gz

6ebe72de801db9a3f51dde39587b93d947904856385a21020319edb6988776fd68ec079471bcce5db17ea1b79c58e22ebf89a854debb40437ad9dc2bc2350357

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1259/

The tag to verify:
v3.2.0-candidate-1 (4ab09374ade3c1402812c3c6be0d07984ab373a4)
https://github.com/apache/pulsar/commits/v3.2.0-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:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-4ab0937/images/sha256-06d35d60f3bd4f954b8b1b6f4cc4f663556ace5da097173f41a61622e81a76b9?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-4ab0937/images/sha256-a6f87bc5fd8025f096f35f26d47303267452e35d92f9f974d8536b61543ddbeb?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.

Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] Pulsar Client Python Release 3.4.0 Candidate 1

[guo jiwei]

+1 (binding)

- Checked the signature and checksums
- Install the pulsar_client-3.4.0-cp39-cp39-macosx_10_15_universal2.whl
- Run Pulsar standalone
- Run the Python examples producer and consumer


Regards
Jiwei Guo (Tboy)


On Fri, Dec 29, 2023 at 12:34 PM Yunze Xu  wrote:

> +1 (binding)
>
> For source code,
> * verified signatures and checksums
> * built from source on macOS (with C++ client 3.4.2)
>
> For the following wheels, verified end-to-end with OAuth2
> authentication on specific platforms.
> * the wheel built from source (macOS Ventura 13.6.3)
> * pulsar_client-3.4.0-cp312-cp312-macosx_10_15_universal2.whl (macOS
> Ventura 13.6.3)
> *
> pulsar_client-3.4.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
> (Rocky Linux 9)
> *
> pulsar_client-3.4.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
> (Ubuntu 22.04)
>
> Thanks,
> Yunze
>
> On Thu, Dec 28, 2023 at 5:13 PM PengHui Li  wrote:
> >
> > +1 (binding)
> >
> > - Checked the signature
> > - Install the pulsar_client-3.4.0-cp39-cp39-macosx_10_15_universal2.whl
> > - Run Pulsar standalone
> > - Run the Python examples `python3 ./examples/consumer.py` and `python3
> > ./examples/producer.py`
> >
> > Regards,
> > Penghui
> >
> > On Tue, Dec 26, 2023 at 4:54 PM Zike Yang  wrote:
> >
> > > This is the first release candidate for Apache Pulsar Client Python,
> > > version 3.4.0.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar-client-python/milestone/5?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.4.0-candidate-1/
> > >
> > > The supported python versions are 3.8, 3.9, 3.10, 3.11 and 3.12. 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.4.0-candidate-1
> > > (v3.4.0-candidate-1)
> > > https://github.com/apache/pulsar-client-python/tree/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 Python wheels and follow the README to test.
> > >
>

Re: [DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Hi
   https://lists.apache.org/thread/4f1cco12cycq36m7vtyjs2j5q5975666 has
been agreed upon, and the related patch has been merged. Now I have cut the
new branch-3.2.


Regards
Jiwei Guo (Tboy)


On Sat, Dec 23, 2023 at 4:34 PM guo jiwei  wrote:

> Thanks Lari.
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Sat, Dec 23, 2023 at 1:35 AM Lari Hotari  wrote:
>
>> There was a discussion yesterday in the community meeting to make the
>> proposed change
>> to drop Pulsar SQL (Trino/Presto), already in the 3.2.0 release.
>>
>> Matteo started the discussion thread:
>> https://lists.apache.org/thread/4f1cco12cycq36m7vtyjs2j5q5975666
>>
>> I deleted branch-3.2 for now so that we don't spend unnecessary time
>> backporting these changes from master to branch-3.2. Let's cut branch-3.2
>> when we have voted about the Pulsar SQL removal and made the changes in
>> master branch. I hope this makes sense.
>>
>> -Lari
>>
>> On 2023/12/22 03:14:01 guo jiwei wrote:
>> > Hi community
>> >   I have cut branch 3.2 and will freeze the code for the next two weeks.
>> >
>> > Regards
>> > Jiwei Guo (Tboy)
>> >
>> >
>> > On Thu, Dec 14, 2023 at 11:40 AM guo jiwei 
>> wrote:
>> >
>> > > Hi community,
>> > >It has been more than three months since the release of 3.1.0.  we
>> now
>> > > have more than 305 commits
>> > > <
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged>
>> and
>> > > 26 PIPs
>> > > <
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged+label%3APIP
>> >
>> > > merged.  We'd better prepare for the 3.2.0 release. I would like to
>> cut
>> > > branch-3.2 in the next week and freeze the code for two weeks.
>> > >Please leave any ideas or concerns.
>> > >
>> > >
>> > > Regards
>> > > Jiwei Guo (Tboy)
>> > >
>> >
>>
>

Re: [VOTE] Pulsar Release 2.11.3 Candidate 2

[guo jiwei]

+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
>

Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

[guo jiwei]

yes, +1 agree


Regards
Jiwei Guo (Tboy)


On Sat, Dec 23, 2023 at 11:37 AM Matteo Merli 
wrote:

> Good point. I have created a PR here:
> https://github.com/apache/pulsar/pull/21795
>
> We can always cherry-pick changes into the release branch, during the code
> freeze, with the appropriate precautions :)
>
> Matteo
>
>
> --
> Matteo Merli
> 
>
>
> On Fri, Dec 22, 2023 at 9:41 AM Lari Hotari  wrote:
>
> > Do we target release 3.2.0 if this change gets accepted?
> >
> > The code freeze for 3.2.0 was about to start today and I blocked that. I
> > removed the already started branch-3.2 (which didn't contain any changes)
> > until the decision has been made. I hope this makes sense. If not, we can
> > always cut the branch again, nothing has been lost.
> >
> > re: https://lists.apache.org/thread/0pl9by5c53nkjp7vld3x89c8nqjrx9on
> >
> > -Lari
> >
> > On 2023/12/22 17:09:19 Matteo Merli wrote:
> > > I want to start a discussion regarding the removal of all the code
> > related
> > > to the Trino (PrestoDB) plugin from the Pulsar main repository.
> > >
> > > This topic was already discussed and approved long time ago in PIP-62 (
> > >
> >
> https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories
> > > )
> > >
> > > The main reasons for not having Presto plugin as part of the main
> > > distribution of Pulsar were (and still are valid):
> > >
> > >  1. We need to ship the entire Presto runtime which is ~400 MB. This
> > makes
> > > our tgz and Docker images huge
> > >  3. There is no strict need for this component to be in the same
> > > distribution / image: it could easily be provided in a different
> release
> > > tgz or Docker image
> > >
> > > Though I think that since then it became more clear that the current
> > state
> > > of this plugin has been stagnating over the years.
> > >
> > > 1. There are not many active users of Pulsar-SQL component (I'd be very
> > > happy to be contradicted here)
> > > 2. The plugin code has not been improved in a long time
> > > 3. There are several open security issues (actually, almost the
> totality
> > of
> > > current dependencies issues are today coming from Trino).
> > >
> > > My suggestion would be that, if there is any volunteer willing to pick
> > this
> > > plugin up and maintain it in a separate repository (within the Apache
> > > Pulsar project) and with a separate release schedule, we should go
> ahead
> > > and move it.
> > > If there are no volunteers, we should just remove it as it is. If later
> > on
> > > we want to revive it, we can always import the code from the last
> commit.
> > >
> > > Thoughts?
> > >
> > >
> > > --
> > > Matteo Merli
> > > 
> > >
> >
>

Re: [DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Thanks Lari.


Regards
Jiwei Guo (Tboy)


On Sat, Dec 23, 2023 at 1:35 AM Lari Hotari  wrote:

> There was a discussion yesterday in the community meeting to make the
> proposed change
> to drop Pulsar SQL (Trino/Presto), already in the 3.2.0 release.
>
> Matteo started the discussion thread:
> https://lists.apache.org/thread/4f1cco12cycq36m7vtyjs2j5q5975666
>
> I deleted branch-3.2 for now so that we don't spend unnecessary time
> backporting these changes from master to branch-3.2. Let's cut branch-3.2
> when we have voted about the Pulsar SQL removal and made the changes in
> master branch. I hope this makes sense.
>
> -Lari
>
> On 2023/12/22 03:14:01 guo jiwei wrote:
> > Hi community
> >   I have cut branch 3.2 and will freeze the code for the next two weeks.
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Thu, Dec 14, 2023 at 11:40 AM guo jiwei  wrote:
> >
> > > Hi community,
> > >It has been more than three months since the release of 3.1.0.  we
> now
> > > have more than 305 commits
> > > <
> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged>
> and
> > > 26 PIPs
> > > <
> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged+label%3APIP
> >
> > > merged.  We'd better prepare for the 3.2.0 release. I would like to cut
> > > branch-3.2 in the next week and freeze the code for two weeks.
> > >Please leave any ideas or concerns.
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
> >
>

Re: [DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Hi community
  I have cut branch 3.2 and will freeze the code for the next two weeks.

Regards
Jiwei Guo (Tboy)


On Thu, Dec 14, 2023 at 11:40 AM guo jiwei  wrote:

> Hi community,
>It has been more than three months since the release of 3.1.0.  we now
> have more than 305 commits
> <https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged>
>  and
> 26 PIPs
> <https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged+label%3APIP>
> merged.  We'd better prepare for the 3.2.0 release. I would like to cut
> branch-3.2 in the next week and freeze the code for two weeks.
>Please leave any ideas or concerns.
>
>
> Regards
> Jiwei Guo (Tboy)
>

Re: [VOTE] PIP-313 Support force unsubscribe using consumer api

[guo jiwei]

We can close this vote with 4 (binding) and 1(non-binding).

Regards
Jiwei Guo (Tboy)


On Mon, Dec 11, 2023 at 9:09 PM Enrico Olivelli  wrote:

> +1 (binding)
>
> Enrico
>
> Il giorno lun 11 dic 2023 alle ore 12:56 Yunze Xu  ha
> scritto:
> >
> > +1 (binding)
> >
> > Thanks,
> > Yunze
> >
> > On Mon, Dec 11, 2023 at 2:18 PM Apurva Telang 
> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > On Sun, Dec 10, 2023 at 6:12 PM guo jiwei 
> wrote:
> > >
> > > > +1 (binding)
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > > >
> > > > On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia 
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I would like to start voting thread for PIP-313  which also
> addresses
> > > > issue
> > > > > # https://github.com/apache/pulsar/issues/21451
> > > > >
> > > > > PIP design PR:
> > > > > https://github.com/apache/pulsar/pull/21452
> > > > >
> > > > > Thread:
> > > > > https://lists.apache.org/thread/hptx8z9mktn94gvqtt4547wzcfcgdsrv
> > > > >
> > > > > Thanks,
> > > > > Rajan
> > > > >
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Apurva Telang.
>

Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

[guo jiwei]

Hi Xiangying,
   I think  we can rename this PIP to:   *Introduce `allowed-clusters` and
`topic-policy-synchronized-clusters` to fully support replication on
message and topic level*
   Currently, we can set replication clusters on the message and topic
level, but the replication clusters should be a subset of the namespace
replication clusters. which means :
   If we set namespace replication clusters: cluster1, cluster2, cluster3,
at most, these three or two clusters can be set on message or topic. If the
user wanna set cluster4 or others, the replication
   can't work as expected.
   It's easy to reproduce by this test:

>@Test

public void testEnableReplicationInTopicLevel() throws Exception {

// 1. Create namespace and topic

String namespace =
> BrokerTestUtil.newUniqueName("pulsar/testEnableReplicationInTopicLevel");

String topic1 = "persistent://" + namespace + "/topic-1";

admin1.namespaces().createNamespace(namespace);

admin1.topics().createNonPartitionedTopic(topic1);

// 2. Configure replication clusters for the topic.

admin1.topics().setReplicationClusters(topic1, List.of("r1", "r2"));

// 3. Check if the replicator connected successfully.

Awaitility.await().atMost(5, TimeUnit.MINUTES).untilAsserted(() -> {

List keys = pulsar1.getBrokerService()

.getTopic(topic1, false).get().get()

.getReplicators().keys();

assertEquals(keys.size(), 1);

assertTrue(pulsar1.getBrokerService()

.getTopic(topic1, false).get().get()

.getReplicators().get(keys.get(0)).isConnected());

});

}


  To fully support the replication, we find out an easy way to solve it.
Introduce `allowed-clusters` on namespace policies, which Xiangying
explains above.
  How could this work and solve the issue? The same example :
  If we set namespace replication clusters: cluster1, cluster2, cluster3,
and
   set topic1 replication clusters: cluster2, cluster4.
   set topic2 replication clusters: cluster1, cluster4.
  We must set `allowed-clusters` with cluster1, cluster2, cluster3, and
cluster4.  The broker side will validate the topic or message replication
clusters from the `allowed-cluster.`
  In this way,  we can simplify more codes and logic here.
  For *`topic-policy-synchronized-clusters` *we also add examples in the
PIP.

  Hope the explanation could help @Rajan @Girish




Regards
Jiwei Guo (Tboy)


On Thu, Dec 7, 2023 at 10:29 PM Xiangying Meng  wrote:

> Hi Girish,
>
> I'm very pleased that we have reached some consensus now. Pulsar already
> supports geo-replication at the topic level, but the existing
> implementation of this topic level replication does not match our
> expectations.
>
> At the moment, I can think of three directions to solve this problem:
>
> 1. Treat this issue as a bug and fix it so that Pulsar can truly support
> replication at the topic level.
> 2. Limit the replication topic policy, so that the replication clusters at
> the topic level must be included in the replication clusters configured at
> the namespace level. In this case, the topic level replication would serve
> as a supplement to the namespace replication, rather than a true topic
> level policy.
> 3. Remove topic level replication.
>
> I lean towards the first option, as it would make Pulsar's replication
> configuration more flexible and would not break the previous behavior
> logic.
>
> >Yes, that's my viewpoint. In case that's not your view point, then in your
> >use cases do you ever have more than one namespace inside a tenant?
> >With every property coming at topic level, it makes no sense for the
> >namespace hierarchy to exist anymore.
>
> I didn't propose this from the perspective of a user, but from the
> perspective of a Pulsar maintainer. The replication cluster at the topic
> level cannot function independently like other topic policies, and I
> attempted to fix it after finding the reason.
>
> From the user's perspective, I could modify my system to put topics with
> the same replication strategy under the same namespace. From the
> maintainer's perspective, if a feature can help users use Pulsar more
> flexibly and conveniently without introducing risks, then this feature
> should be implemented. Perhaps business systems do not want to maintain too
> many namespaces, as they would need to configure multiple namespace
> policies or it might make their business logic complex. The other
> configurations for topics under this namespace might be consistent, with
> only a few topics needing to enable replication. In this case, topic level
> replication becomes valuable. Therefore, I lean towards the first option,
> to solve this problem and make it a truly expected topic policy.
>
> On Thu, Dec 7, 2023 at 12:45 PM Girish Sharma 
> wrote:
>
> > Hello Xiangying,
> >
> >
> > On Thu, Dec 7, 2023 at 6:32 

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.1 Candidate 1

[guo jiwei]

+1 (binding)

- Verify the signature and checksum.
- Verified staged maven artifacts by running the test
HelloPulsarClientReactive

We can correct the commit in this thread to v0.5.1-candidate-1
(92a1e390e854876b54936bd0e6d21bf1e5071aeb)


Regards
Jiwei Guo (Tboy)


On Thu, Dec 14, 2023 at 7:39 PM Christophe Bornet 
wrote:

> +0
>
> The git commit is incorrect in the voting mail
> (d45c08827387bd8d2a0d6bdc542c2bf7e4ebcda8 instead of
> 92a1e390e854876b54936bd0e6d21bf1e5071aeb)
> I don't think it needs a new RC but I believe it needs a new voting
> mail with the correct commit.
>
> Regards
>
> Christophe
>
> Le mer. 13 déc. 2023 à 22:59, Chris Bo  a écrit :
> >
> > Following PIP-205: Reactive Java client for Apache Pulsar (
> > https://github.com/apache/pulsar/issues/17335), this is release
> > candidate 1 for the Reactive Java client for Apache Pulsar, version
> 0.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 in the Maven
> > repository
> > are provided for convenience.
> >
> > Source package:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.1-candidate-1/
> >
> > SHA-512 checksums:
> >
> def9a9d97ac69ca27bed66f1a1ce15194f589aa95b68f0add75ffa4488efd9eac96bd9af0f278b3eba5872a7bd4c47394127a42b55f4a4a8140ab9f401641238
> >  pulsar-client-reactive-0.5.1-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1257/
> >
> > The tag to be voted upon:
> > v0.5.1-candidate-1 (d45c08827387bd8d2a0d6bdc542c2bf7e4ebcda8)
> >
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.1-candidate-1
> >
> > Please download the source package, and follow detailed instructions for
> > pulsar-client-reactive release validation at
> >
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > .
> >
> > Best regards
> >
> > Chris Bono
>

[DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Hi community,
   It has been more than three months since the release of 3.1.0.  we now
have more than 305 commits

and
26 PIPs

merged.  We'd better prepare for the 3.2.0 release. I would like to cut
branch-3.2 in the next week and freeze the code for two weeks.
   Please leave any ideas or concerns.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-323: Complete Backlog Quota Telemetry

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Wed, Dec 13, 2023 at 4:23 PM Asaf Mesika  wrote:

> Hi,
>
> I'm starting the vote for PIP-323, since it has been reviewed by several
> people and all comments have been resolved.
>
> Reminder:
>
> PIP-323 is introduced to fill the gap of backlog quota telemetry. It allows
> the user to know when a time-based backlog quota is about to exceed, and
> how many times it exceeded. It also adds backlog quota check duration
> metric allowing the user to configure the interval for that check based on
> data. Once this is implemented, the user can finally create an alert to
> know when a certain topic is about to exceed its defined backlog quota
> limit, alert on it, and use topic stats Admin API to grab the subscription
> name causing it.
>
> PIP link: https://github.com/apache/pulsar/pull/21709
>
>
> Thanks,
>
> Asaf
>

Re: [VOTE] Pulsar Release 3.1.2 Candidate 2

[guo jiwei]

+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 Sat, Dec 9, 2023 at 2:48 PM houxiaoyu  wrote:

> This is the second release candidate for Apache Pulsar version 3.1.2.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.2+label%3Acherry-picked%2Fbranch-3.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-3.1.2-candidate-2/
>
> SHA-512 checksums:
>
> apache-pulsar-3.1.2-bin.tar.gz
>
> 48e2d0069cd69c6f2bf5b5d5aa9fbc775436d3e160bd51645a6626fb86706ddba4901a5d6b87e29a57b9f19c0d0b8c22aef2dfa3d3525260ad55d0a39db6
>
> apache-pulsar-3.1.2-src.tar.gz
>
> 4d29b1f707047d1bd55d8cb8aacb488517fbd82903fef57c9924180b62454725bdbdc53adf7af5d5caa4d57522a10d6eb15028fd929325b9cadd088a6e3de20a
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1256/
>
> The tag to verify:
> v3.1.2-candidate-2 (c4196fba3ae107d74f9421d3f7ed11c0c245f10f)
> https://github.com/apache/pulsar/releases/tag/v3.1.2-candidate-2
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> Docker images:
>
> pulsar images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar
>
> pulsar-all images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar-all
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>
> Regards
> Xiaoyu Hou
>

Re: [VOTE] Pulsar Client C++ Release 3.4.2 Candidate 1

[guo jiwei]

+1 (binding)

- Verified the signature and checksum
- Build from the source
- Test SampleConsumer and SampleProducer

Regards
Jiwei Guo (Tboy)


On Tue, Dec 12, 2023 at 4:30 PM tison  wrote:

> +1 (binding)
>
> * Download URL valid
> * Checksum and sign match
> * Can build from source
> * LICENSE and NOTICE present
>
> nit: Years in NOTICE can be updated.
>
> Best,
> tison.
>
> Yunze Xu  于2023年12月6日周三 16:00写道：
> >
> > This is the first release candidate for Apache Pulsar Client C++,
> version 3.4.2.
> >
> > It fixes the following issues:
> >
> https://github.com/apache/pulsar-client-cpp/pulls?q=is%3Apr+is%3Aclosed+label%3Arelease%2F3.4.2
> >
> > *** 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.2-candidate-1/
> >
> > SHA-512 checksums:
> >
> d64a07c4f78071ae0607f1afac4ab0db15f9dc25cb1f2ceae7152e262b65e660719f1520f93933da6615691ea0de2f25a6fb2806369126c4a777c0a075af0f5e
> >  apache-pulsar-client-cpp-3.4.2.tar.gz
> >
> > The tag to be voted upon:
> > v3.4.2-candidate-1 (1cb1bf8ba1ca1033b4a36d35514f22fcf150973a)
> >
> https://github.com/apache/pulsar-client-cpp/releases/tag/v3.4.2-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: [VOTE] PIP-322: Pulsar Rate Limiting Refactoring

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Dec 11, 2023 at 2:20 PM Lari Hotari  wrote:

> Dear Pulsar community,
>
> I am starting a vote thread for "PIP-322: Pulsar Rate Limiting
> Refactoring".
>
> PIP-322 document:
> https://github.com/apache/pulsar/pull/21680
>
> Draft changes for "PIP-322: Pulsar Rate Limiting Refactoring":
> https://github.com/apache/pulsar/pull/21681
>
> Discussion thread:
> https://lists.apache.org/thread/xzrp2ypggp1oql437tvmkqgfw2b4ft33
>
> Please review the PIP document and vote!
>
> Thanks,
>
> Lari
>

Re: [VOTE] PIP-313 Support force unsubscribe using consumer api

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia  wrote:

> Hi,
>
> I would like to start voting thread for PIP-313  which also addresses issue
> # https://github.com/apache/pulsar/issues/21451
>
> PIP design PR:
> https://github.com/apache/pulsar/pull/21452
>
> Thread:
> https://lists.apache.org/thread/hptx8z9mktn94gvqtt4547wzcfcgdsrv
>
> Thanks,
> Rajan
>

Re: [VOTE] Pulsar Release 3.1.2 Candidate 1

[guo jiwei]

Hi
 We find a regression in 3.0,  Apache/Pulsar/#17512
 has fixed the data being
deleted when offload met Metastore exception, but Apache/Pulsar/#17915
 skip the logic, causing the
broker to delete the data from the tiered storage.
 I suggest dropping this vote and fix the issue then raise a new candidate.

Regards
Jiwei Guo (Tboy)


On Sat, Dec 2, 2023 at 4:56 PM houxiaoyu  wrote:

> This is the first release candidate for Apache Pulsar version 3.1.2.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.2+label%3Acherry-picked%2Fbranch-3.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-3.1.2-candidate-1/
>
> SHA-512 checksums:
>
>
> 47e487de57c4354ed07a1690197eed9057e67ee85055d11c098ae6cff642b20e4966d43c3d52f449a942547d417dd20b94c353c7485cbd599f6f059147826f5f
> apache-pulsar-3.1.2-bin.tar.gz
>
>
> 664a5811788817c302c1e2a943f959339832ef77417e2ca566696948e330172ada878e1487402e9aff6a0a81a89b44404c797114eb2f27922f58831adfaa0582
> apache-pulsar-3.1.2-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1255/
>
> The tag to verify:
> v3.1.2-candidate-1 (9f110390ebd3ccaeb67adec9c51631e735414ccd)
> https://github.com/apache/pulsar/releases/tag/v3.1.2-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:
>
> pulsar images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar
>
> pulsar-all images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar-all
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>
> Regards
> houxiaoyu
>

Re: [DISCUSS] Release Pulsar 3.1.2

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Mon, Nov 27, 2023 at 9:55 AM Yubiao Feng
 wrote:

> +1
>
> Thanks
> Yubiao Feng
>
> On Sun, Nov 26, 2023 at 4:10 PM houxiaoyu  wrote:
>
> > Hi all,
> >
> > I would like to propose releasing the Pulsar 3.1.2.
> >
> > It's over one month since the release of 3.1.1 and there are 56 new
> commits
> > in branch-3.1:
> > https://github.com/apache/pulsar/compare/v3.1.1...branch-3.1
> >
> > We need to cut a new release. Please let me know if you have any
> > important fixes that need to be included in Pulsar 3.1.2.
> >
> >
> > Regards
> > Xiaoyu Hou
> >
>

Re: [VOTE] Pulsar Release 3.0.2 Candidate 4

[guo jiwei]

+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 Sun, Nov 26, 2023 at 10:10 PM Yike Xiao  wrote:

> +1 (non-binding)
>
>   *   Checked the signatures and checksums
>   *   Built from source
> ```
> Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
> Maven home: /usr/local/maven
> Java version: 17.0.5, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-17.0.5.jdk/Contents/Home
> Default locale: en_CN, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1", arch: "aarch64", family: "mac"
> ```
>   *   Run standalone and checked produce and consume
>   *   Run a cluster with three nodes with docker image (pulsar)
>
> 
> From: Yubiao Feng 
> Sent: Monday, November 20, 2023 10:24
> To: dev@pulsar.apache.org 
> Subject: [VOTE] Pulsar Release 3.0.2 Candidate 4
>
> This is the first release candidate for Apache Pulsar version 3.0.4.
>
> It fixes the following issues:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpulls%3Fq%3Dis%253Apr%2Bis%253Amerged%2Blabel%253Arelease%252F3.0.2%2Blabel%253Acherry-picked%252Fbranch-3.0=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699813981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=O0t7XQ%2Fyl8E1jqomYW9ObingScQ3j0ynFvpgpmAdWkk%3D=0+
> <
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.0.2+label%3Acherry-picked%2Fbranch-3.0
> >
>
> *** 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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.2-candidate-4%2F=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=CEKQMg7XumWSg9OsK1iHTBNYDqtAFfnXOE52LfPZV8Y%3D=0
> 
>
> SHA-512 checksums:
>
>
> 9bd5b4030de47c10a906d6271731ca7bcfb8801984cdd625789bc0c5047138f0f2eb1aaceaec1c8941e2ccfa639bbb2458496518e87fb29abb9ebc518e2da60d
>
> apache-pulsar-3.0.2-bin.tar.gz
>
>
> 6854d1776de08c9079228a5a5d2f670f92b1b905f0d92c50ee35c5bc9c53be5225626a6d84fc3bbb209b8b12ff3b142685b5c9ea33609e1bb934e9679402e0b8
>
> apache-pulsar-3.0.2-src.tar.gz
>
> Maven staging repo:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1249=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oZ44u3rpSGhgdzvrWXlA3XTrLjjGIHiPlf2o9cFRvYE%3D=0
> 
>
> The tag to verify:
> v3.0.2-candidate-4 (12c92fed7847965e3bc3769a91c866b2f0ec2e44)
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Freleases%2Ftag%2Fv3.0.2-candidate-4=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=KOuCBWEIvtBkourwAuQJfx7NKFLrWWZVlAVd%2FChDpgk%3D=0
> 
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oX2GoSYu4ZSW997%2BTdJOC%2BJxyfbvMIPalRMAC09OHwU%3D=0
> 
>
> Docker images:
>
> pulsar images:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Frepository%2Fdocker%2F9947090%2Fpulsar-all=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=XWmZ9Ytz%2BW7Wryc1M6WcLzQMSLoP3YN6ZTallD15IJs%3D=0
> 
>
> pulsar-all images:
>
> 

Re: [VOTE] Pulsar Release 2.11.3 Candidate 1

[guo jiwei]

+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] PIP-303: Add optional parameters for getPartitionedStats

[guo jiwei]

+1 (binding)

Regards
Jiwei Guo (Tboy)


On Thu, Nov 16, 2023 at 12:46 PM Yunze Xu  wrote:

> +1 (binding)
>
> Thanks,
> Yunze
>
> On Thu, Nov 16, 2023 at 11:01 AM Jie crossover 
> wrote:
> >
> > Hi All, This thread is to start a vote for PIP-303. PIP:
> > https://github.com/apache/pulsar/pull/21228 Discussion thread:
> > https://lists.apache.org/thread/c92043zq6lyrsd5z1hnln48mx858n7vj
> > --
> > Best Regards！
> > crossoverJie
>

Re: [VOTE] PIP-312 Use StateStoreProvider to manage state in Pulsar Functions endpoints

[guo jiwei]

+1 binding


Regards
Jiwei Guo (Tboy)


On Sat, Nov 18, 2023 at 12:27 AM 太上玄元道君  wrote:

> +1 non binding
>
> Zili Chen 于2023年11月17日 周五17:56写道：
>
> > +1 binding
> >
> > Thanks for your proposal.
> >
> > 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: [VOTE] PIP-300: Add custom dynamic configuration for plugins

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Sun, Oct 8, 2023 at 2:13 PM 太上玄元道君  wrote:

> +1 (no-binding)
>
>
> Zixuan Liu 于2023年9月26日 周二10:54写道：
>
> > Hi Pulsar Community,
> >
> > Voting for PIP-300: https://github.com/apache/pulsar/pull/21127
> > Discussion thread:
> > https://lists.apache.org/thread/ysnsnollgy1b6w1dsvmx1t1y2rz1tyd6
> >
> > Thanks,
> > Zixuan
> >
>

Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Thanks @Tison

Close this vote first and then I will change the pip num.

Regards
Jiwei Guo (Tboy)


On Wed, Oct 25, 2023 at 3:02 AM tison  wrote:

> PIP number conflicts.
>
> May we keep using pip-xxx instead of pip_xxx so that Git can help detect
> number conflict..
>
> Best,
> tison.
>
>
> 太上玄元道君  于2023年10月24日周二 23:50写道：
>
> > +1(no-binding)
> >
> > Thanks,
> > Tao Jiuming
> >
> > Cong Zhao 于2023年10月24日 周二16:03写道：
> >
> > > +1(no-binding)
> > >
> > > Thanks,
> > > Cong Zhao
> > >
> > > On 2023/10/19 12:47:45 guo jiwei wrote:
> > > > Hi dev,
> > > >Currently WebSocket only supports the consumption of a single
> topic,
> > > > which cannot satisfy users' consumption scenarios of multiple topics.
> > So
> > > > in order to support consumption of multiple topics or pattern
> topics, I
> > > > would like to start a vote for PIP-307
> > > > <https://github.com/apache/pulsar/pull/21390>.
> > > >
> > > >
> > > > Ref:
> > > > • Discuss Mail:
> > > > https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
> > > > • PIP-307: https://github.com/apache/pulsar/pull/21390
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > >
> >
>

[ANNOUNCE] Apache Pulsar 3.1.1 released

[guo jiwei]

The Apache Pulsar team is proud to announce Apache Pulsar version 3.1.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 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
Jiwei Guo (Tboy)

Re: [VOTE] Pulsar Release 3.1.1 Candidate 1

[guo jiwei]

Close this vote by 3 binding +1:

- Penghui
- Mattison
- Yunze


Regards
Jiwei Guo (Tboy)


On Tue, Oct 24, 2023 at 6:27 PM PengHui Li  wrote:

> +1 (binding)
>
> - Checked the signatures
> - Built from source tarball
> - Run standalone and check the produce, consume
> - Verified Cassandra connector
> - Verified stateful function
>
> Regards,
> Penghui
>
> On Tue, Oct 24, 2023 at 12:34 PM Yunze Xu  wrote:
>
> > +1 (binding)
> >
> > - Verified checksum and signatures
> > - Built from source with Java 17.0.7 and Maven 3.9.3 on macOS m1
> > - Started standalone and verified produce and consume
> > - Ran it with StreamNative KoP and verified produce and consume with
> > Kafka clients 3.5.0
> >
> > Thanks,
> > Yunze
> >
> > On Thu, Oct 19, 2023 at 5:53 PM mattison chao 
> > wrote:
> > >
> > > +1 (binding)
> > >
> > >
> > > - Built from source code. (Java version: 17.0.8.1, Apache Maven 3.9.4,
> > OS name: "mac os x", version: "13.4.1", arch: "x86_64")
> > > - Checked binary license
> > > - Started Standalone
> > > - Ran a round of publish and consume
> > >
> > > Best,
> > > Mattison
> > >
> > > > On 7 Oct 2023, at 09:09, guo jiwei  wrote:
> > > >
> > > > This is the first release candidate for Apache Pulsar version 3.1.1.
> > > >
> > > > It fixes the following issues:
> > > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.1+label%3Acherry-picked%2Fbranch-3.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-3.1.1-candidate-1/
> > > >
> > > > SHA-512 checksums:
> > > >
> > > >
> >
> af79f970c8835320584faf58c85bfc5cd12261f5e366c2c16bce2f7628d769ef7374a3c0e383ff443519e484a35a23e86415e0156a0f35dd3bc1f606d2fa0421
> > > >
> > > > apache-pulsar-3.1.1-bin.tar.gz
> > > >
> > > >
> >
> a43306b8a08a330c721ca96501c0c4285e5c47cfab4a037034148401afc4dbd65e505da591ef9ca76ca5acf39d6fd9c96537a08956ad6fb37f7c70d8ab747510
> > > >
> > > > apache-pulsar-3.1.1-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1243/
> > > >
> > > > The tag to verify:
> > > > v3.1.1-candidate-1 (80fb39085b4e49ff31f2df17b10addcca5abdccb)
> > > > https://github.com/apache/pulsar/releases/tag/v3.1.1-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:
> > > >
> > > > pulsar images:
> > > >
> >
> https://hub.docker.com/layers/mattison/pulsar-all/3.1.1-80fb390/images/sha256-1088b07fd2448733db1d165676b82c1278f2940cb0861c704450ef2be5c2fa1c?context=explore
> > > >
> > > > pulsar-all images:
> > > >
> >
> https://hub.docker.com/layers/mattison/pulsar/3.1.1-80fb390/images/sha256-21e8bf1571e4ab559a51b3f6e524d725cffabe3c6836101f9d7ea7eb1e2bf62c?context=explore
> > > >
> > > > Please download the source package, and follow the README to build
> > > > and run the Pulsar standalone service.
> > > >
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > >
> >
>

Re: [VOTE] PIP-298 Consumer supports specifying consumption isolation level

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Oct 23, 2023 at 1:40 PM Yunze Xu  wrote:

> +1 (binding)
>
> Thanks,
> Yunze
>
> On Mon, Oct 23, 2023 at 1:08 PM PengHui Li  wrote:
> >
> > +1 (binding)
> >
> > Regards,
> > Penghui
> >
> > On Mon, Oct 23, 2023 at 10:37 AM hzh0425  wrote:
> >
> > > Dave previously mentioned in the discussion thread that he will
> continue
> > > to support this pip if the documentation is supplemented and improved.
> Due
> > > to inability to contact him, we apply to cancel his -1 binding.
> > >
> > >
> > >
> > >  Replied Message 
> > > | From | Dave Fisher |
> > > | Date | 09/26/2023 04:03 |
> > > | To | dev@pulsar.apache.org |
> > > | Cc | |
> > > | Subject | Re: [VOTE] PIP-298 Consumer supports specifying consumption
> > > isolation level |
> > > -1 (binding) I’m not convinced that breaking transaction isolation is
> the
> > > proper course of action.
> > >
> > > Regards,
> > > Dave
> > >
> > > > On Sep 25, 2023, at 6:46 AM, hzh0425  wrote:
> > > >
> > > > Hi dev,
> > > > This thread is to start a vote for PIP-298 Consumer supports
> specifying
> > > consumption isolation level
> > > > Discuss thread:
> > > > https://lists.apache.org/thread/8ny0qtp7m9qcdbvnfjdvpnkc4c5ssyld
> > > >
> > > > https://lists.apache.org/thread/2opqjof83425vry6gzszd5glqgryrv11
> > > >
> > > > PIP: https://github.com/apache/pulsar/pull/21114
> > > >
> > > > BR,
> > > > hzh
> > >
>

[VOTE] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Hi dev,
   Currently WebSocket only supports the consumption of a single topic,
which cannot satisfy users' consumption scenarios of multiple topics.  So
in order to support consumption of multiple topics or pattern topics, I
would like to start a vote for PIP-307
.


Ref:
• Discuss Mail:
https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
• PIP-307: https://github.com/apache/pulsar/pull/21390


Regards
Jiwei Guo (Tboy)

Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Thanks, I will send out the vote mail.


Regards
Jiwei Guo (Tboy)


On Thu, Oct 19, 2023 at 11:50 AM Zixuan Liu  wrote:

> +1
>
> Thanks,
> Zixuan
>
> guo jiwei  于2023年10月18日周三 20:45写道：
> >
> > Hi dev,
> >Currently WebSocket only supports the consumption of a single topic,
> > which cannot satisfy users' consumption scenarios of multiple topics.  So
> > in order to support consumption of multiple topics or pattern topics, I
> > start discussing PIP-307 <https://github.com/apache/pulsar/pull/21390>.
> >
> >
> > Ref:
> > • PIP-307: https://github.com/apache/pulsar/pull/21390
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
>

Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, Oct 19, 2023 at 10:11 AM Zili Chen  wrote:

> +1 binding
>
> On 2023/10/17 07:23:29 Diego Salvi wrote:
> > Hi Community,
> >
> > This thread is to start a vote for PIP-305.
> >
> > PIP: https://github.com/apache/pulsar/pull/21352
> > Discussion thread:
> > https://lists.apache.org/thread/p0870y7o6brv5y1ghn5tz9hvs24bl1k4
> >
> > Best regards
> > Diego Salvi
> >
>

[DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Hi dev,
   Currently WebSocket only supports the consumption of a single topic,
which cannot satisfy users' consumption scenarios of multiple topics.  So
in order to support consumption of multiple topics or pattern topics, I
start discussing PIP-307 .


Ref:
• PIP-307: https://github.com/apache/pulsar/pull/21390


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-299: Stop dispatch messages if the individual acks will be lost in the persistent storage

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Oct 9, 2023 at 8:14 AM PengHui Li  wrote:

> +1 (binding)
>
> Left to minor comments on the proposal, PTAL.
>
> Thanks,
> Penghui
>
> On Thu, Sep 21, 2023 at 2:53 PM Yubiao Feng
>  wrote:
>
> > Sorry.  The last email was sent by mistake. Just correct it by this one.
> >
> > I'd like to start a vote thread for the PIP-299.
> > https://github.com/apache/pulsar/pull/21118
> >
> > Discussion :
> > https://lists.apache.org/thread/2fzo1gnlyd1t5o80g1polbvbx4699r09
> >
> > Thanks
> > Yubiao Feng
> >
> > On Thu, Sep 21, 2023 at 2:49 PM Yubiao Feng  >
> > wrote:
> >
> > > Hi all
> > >
> > > I'd like to start a vote thread for the PIP-299.
> > >
> >
>

Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Sat, Oct 7, 2023 at 8:07 PM PengHui Li  wrote:

> +1
>
> Thanks,
> Penghui
>
> On Wed, Sep 27, 2023 at 3:09 PM Zike Yang  wrote:
>
> > +1
> >
> > BR,
> > Zike Yang
> >
> > On Wed, Sep 27, 2023 at 3:05 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
> >
>

[VOTE] Pulsar Release 3.1.1 Candidate 1

[guo jiwei]

This is the first release candidate for Apache Pulsar version 3.1.1.

It fixes the following issues:
https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.1+label%3Acherry-picked%2Fbranch-3.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-3.1.1-candidate-1/

SHA-512 checksums:

af79f970c8835320584faf58c85bfc5cd12261f5e366c2c16bce2f7628d769ef7374a3c0e383ff443519e484a35a23e86415e0156a0f35dd3bc1f606d2fa0421

apache-pulsar-3.1.1-bin.tar.gz

a43306b8a08a330c721ca96501c0c4285e5c47cfab4a037034148401afc4dbd65e505da591ef9ca76ca5acf39d6fd9c96537a08956ad6fb37f7c70d8ab747510

apache-pulsar-3.1.1-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1243/

The tag to verify:
v3.1.1-candidate-1 (80fb39085b4e49ff31f2df17b10addcca5abdccb)
https://github.com/apache/pulsar/releases/tag/v3.1.1-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:

pulsar images:
https://hub.docker.com/layers/mattison/pulsar-all/3.1.1-80fb390/images/sha256-1088b07fd2448733db1d165676b82c1278f2940cb0861c704450ef2be5c2fa1c?context=explore

pulsar-all images:
https://hub.docker.com/layers/mattison/pulsar/3.1.1-80fb390/images/sha256-21e8bf1571e4ab559a51b3f6e524d725cffabe3c6836101f9d7ea7eb1e2bf62c?context=explore

Please download the source package, and follow the README to build
and run the Pulsar standalone service.



Regards
Jiwei Guo (Tboy)

Re: [Vote] PIP-281: Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Wed, Sep 20, 2023 at 8:53 AM mattison chao 
wrote:

> +1 (binding)
>
> Best,
> Mattison
> On 20 Sep 2023 at 08:40 +0800, PengHui Li , wrote:
> > There are a lot of discussions that happened in the DISCUSS thread.
> > The proposal looks good to me.
> >
> > +1 (binding)
> >
> > Regards,
> > Penghui
> >
> > On Wed, Sep 6, 2023 at 1:51 PM Heesung Sohn
> >  wrote:
> >
> > > Yes, this was my last comment in the PIP.
> > > https://github.com/apache/pulsar/pull/20748#discussion_r1300733232
> > > I saw your comment,
> > > https://github.com/apache/pulsar/pull/20748#discussion_r1303801386.
> > >
> > > I am sorry. I probably didn't make it clear.
> > > I thought you would leave more comments to conclude the discussion,
> > > or we would discuss more during the community meeting.
> > >
> > >
> > >
> > > On Tue, Sep 5, 2023 at 6:19 PM Michael Marshall 
> > > wrote:
> > >
> > > > > > > In my last comment, I proposed a follow-up PIP if we want to
> add the
> > > > > > > "prepare" command(Michael’s idea) on top of this PIP.
> > > > > > > I have been waiting to hear from him since then.
> > > > >
> > > > > Out of curiosity, where was your proposal? If it was on the PIP
> PR, I
> > > > > already replied here:
> > > > > https://github.com/apache/pulsar/pull/20748#discussion_r1303801386
> > > > >
> > > > > On Tue, Sep 5, 2023 at 8:09 PM Matteo Merli <
> matteo.me...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > +1 (binding)
> > > > > > > --
> > > > > > > Matteo Merli
> > > > > > > 
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Aug 7, 2023 at 11:55 AM Heesung Sohn
> > > > > > >  wrote:
> > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I'd like to start a vote thread for the PIP-281.
> > > > > > > > > https://github.com/apache/pulsar/pull/20748
> > > > > > > > >
> > > > > > > > > Discussion :
> > > > > > > > >
> https://lists.apache.org/thread/bdmx4qhn6hkoxm0xbtf67tq4kt5r8jmy
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Heesung
> > > > > > > > >
> > > > >
> > >
>

Re: [VOTE] PIP-301: Introduce LoadBalanceResources to unify the load-date CRUD

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Sep 18, 2023 at 8:57 PM houxiaoyu  wrote:

> Hi dev,
>This thread is to start a vote for PIP-301: Introduce
> LoadBalanceResources to unify the load-date CRUD
>
>Discuss thread :
> https://lists.apache.org/thread/7ngw9dc62tj2c4c5484dgsnlwgtstpbj
>PIP: https://github.com/apache/pulsar/pull/21129
>
>
>
> Regards
> houxiaoyu
>

[DISCUSS] Release Pulsar 3.1.1

[guo jiwei]

Hi all,

I would like to propose releasing the Pulsar 3.1.1.

It's over one month since the release of 3.1.0 and there are 56 new commits
in branch-3.1:
https://github.com/apache/pulsar/compare/v3.1.0...branch-3.1

We need to cut a new release. Please let me know if you have any
important fixes that need to be included in Pulsar 3.1.1.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-286: Make the TopicCompactionService to support find entry based on publishTime or index

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Sep 18, 2023 at 11:01 AM Zike Yang  wrote:

> +1 (non-binding)
>
> BR,
> Zike Yang
>
> On Mon, Sep 18, 2023 at 9:35 AM mattison chao 
> wrote:
> >
> > +1 (binding)
> >
> > Best,
> > Mattison
> > On 18 Sep 2023 at 09:19 +0800, PengHui Li , wrote:
> > > +1 (binding)
> > >
> > > Thanks,
> > > Penghui
> > >
> > > On Thu, Sep 14, 2023 at 11:23 AM Cong Zhao 
> wrote:
> > >
> > > > Hi, all
> > > >
> > > > Since there are no other concerns in the discussion, I'm delighted to
> > > > start the voting process for the PIP-286.
> > > >
> > > > Here is the link to the PIP:
> https://github.com/apache/pulsar/pull/20867
> > > >
> > > > Thanks,
> > > > Cong Zhao
> > > >
>

Re: [VOTE] PIP-277: Add `current` option in the Clusters list cmd

[guo jiwei]

Thanks.
Close the vote with 3+ (binding):
Penghui
Mattison
tison

2+(non-binding):
Zike
Zixuan

Regards
Jiwei Guo (Tboy)


On Thu, Sep 7, 2023 at 12:48 AM Zixuan Liu  wrote:

> +1 (non-binding)
>
> Best,
> Zixuan
>
> Zike Yang  于2023年9月6日周三 23:56写道：
> >
> > +1 (non-binding)
> >
> > BR,
> > Zike Yang
> >
> > On Wed, Sep 6, 2023 at 11:47 PM tison  wrote:
> > >
> > > +1 (binding)
> > >
> > > Trivial with low risk.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > mattison chao  于2023年9月6日周三 22:50写道：
> > >
> > > > +1 (binding)
> > > >
> > > > Best,
> > > > Mattison
> > > > On 6 Sep 2023 at 22:37 +0800, PengHui Li ,
> wrote:
> > > > > +1 (binding)
> > > > >
> > > > > The proposal just added a new option to show which cluster is the
> current
> > > > > cluster accessed. It will not break any existing behavior.
> > > > >
> > > > > Regards,
> > > > > Penghui
> > > > >
> > > > > On Wed, Sep 6, 2023 at 4:21 PM guo jiwei 
> wrote:
> > > > >
> > > > > > Hi dev,
> > > > > > This thread is to start a vote for PIP-277: Add `current` option
> in the
> > > > > > Clusters list cmd
> > > > > >
> > > > > > Discuss thread :
> > > > > > https://lists.apache.org/thread/800r6ld5wg7bttbywmk38m1qx12hs6nl
> > > > > > PIP: https://github.com/apache/pulsar/pull/20614
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > > Jiwei Guo (Tboy)
> > > > > >
> > > >
>