Re: [VOTE] DotPulsar Release 3.1.2-rc.1 (reupload)

[Daniel Blankensteiner]

+1 (binding)

Tested on Windows 10 with .NET 8(.0.100).

Best regards

Daniel Blankensteiner

tison skrev den 2024-01-27 08:51:

+1 (binding)

+ Download link valid
+ LICENSE and NOTICE exist
+ Signature and checksum matches

pulsar-dotpulsar-3.1.2-src.tar.gz
gpg: Signature made 五  1/26 16:51:33 2024 CST
gpg:using RSA key 
04DA66C9F3CCF13E714EFCA6906E6E0723D4C215

gpg: Good signature from "David Jensen (CODE SIGNING KEY)
" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the 
owner.
Primary key fingerprint: 04DA 66C9 F3CC F13E 714E  FCA6 906E 6E07 23D4 
C215


+ Can compile from source
+ No unexpected binary files

Two suggestions:

1. The NOTICE year can be updated.
2. When we "rerun" a vote on a new release candidate, you can use a
new rc number. That is, you may upload to a rc.2 and start a vote for
rc.2.

These are not release blockers, though.

Best,
tison.

David Jensen  于2024年1月26日周五 17:00写道：


 Hi everyone,

Please review and vote on the release candidate 1 for the version 
3.1.2, as

follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

DotPulsar's KEYS file contains the PGP keys we used to sign this 
release:

https://downloads.apache.org/pulsar/KEYS

Please download these packages and review this release candidate:
- Review release notes
- Download the source package (verify shasum, and asc) and follow the
README.md to build and run DotPulsar.

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Source file:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-dotpulsar-3.1.2-rc.1/

Nuget package:
https://www.nuget.org/packages/DotPulsar/3.1.2-rc.1

The tag to be voted upon:
https://github.com/apache/pulsar-dotpulsar/tree/3.1.2-rc.1

SHA-512 checksums:
6a09978eddc1822f7d9b2887be25d295d673f9264b47305c77202390b84292eb9d21c2b88cf5f40af262cb305802a0edd790d351960d5e56318dd40464fca95b
 pulsar-dotpulsar-3.1.2-src.tar.gz

Re: [VOTE] DotPulsar Release 3.1.2-rc.1 (reupload)

[Lari Hotari]

+1 (binding)

- verified source release file hash and signature
- ran build
- validated the Nuget package using a simple Pulsar app

Using dotnet sdk 8.0.101 on MacOS arm64.

I documented how the validation can be done on MacOS:
https://gist.github.com/lhotari/270cc2c3db5b05c2b0d05611f97c6d45 .
Hopefully this makes it easier for others on MacOS to run the
validation process and vote.

-Lari

On Fri, 26 Jan 2024 at 11:00, David Jensen  wrote:
>
>  Hi everyone,
>
> Please review and vote on the release candidate 1 for the version 3.1.2, as
> follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> DotPulsar's KEYS file contains the PGP keys we used to sign this release:
> https://downloads.apache.org/pulsar/KEYS
>
> Please download these packages and review this release candidate:
> - Review release notes
> - Download the source package (verify shasum, and asc) and follow the
> README.md to build and run DotPulsar.
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Source file:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-dotpulsar-3.1.2-rc.1/
>
> Nuget package:
> https://www.nuget.org/packages/DotPulsar/3.1.2-rc.1
>
> The tag to be voted upon:
> https://github.com/apache/pulsar-dotpulsar/tree/3.1.2-rc.1
>
> SHA-512 checksums:
> 6a09978eddc1822f7d9b2887be25d295d673f9264b47305c77202390b84292eb9d21c2b88cf5f40af262cb305802a0edd790d351960d5e56318dd40464fca95b
>  pulsar-dotpulsar-3.1.2-src.tar.gz

[VOTE] Pulsar Node.js Client Release 1.10.0 Candidate 1

[Baodi Shi]

Hi everyone,

This is the first release candidate for Apache Pulsar Node.js client,
version 1.10.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-node/milestone/15?closed=1

Please download the source files and review this release candidate:
- Download the source package, verify shasum and asc
- Follow the README.md to build and run the Pulsar Node.js client.

The release candidate package has been published to the npm registry:
https://www.npmjs.com/package/pulsar-client/v/1.10.0-rc.1
You can install it by `npm i pulsar-client@1.10.0-rc.1
--pulsar_binary_host_mirror=
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/` and
verify the package.

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Source files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.10.0-rc.1/

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://downloads.apache.org/pulsar/KEYS

SHA-512 checksum:
3e2c76ff8340597129eec1ab2a9cdbdd48fb162257426c474bd637bb02a45b49011e6b31e08679022f18d700e73f49cbb8adc59f75e345db9220a2b755eccac4
./apache-pulsar-client-node-1.10.0.tar.gz

The tag to be voted upon:
v1.10.0-rc.1
https://github.com/apache/pulsar-client-node/releases/tag/v1.10.0-rc.1

Please review and vote on the release candidate #1 for the version 1.10.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

[RESULT][VOTE] Apache Pulsar DotPulsar 3.1.2 released

[David Jensen]

[RESULT][VOTE] Release Apache DotPulsar 3.1.2

The vote to release Apache DotPulsar 3.1.2 has passed.

The vote PASSED with 3 binding +1 and 0 -1 votes:

Binding votes:
- tison
- Daniel Blankensteiner
- Lari Hotar

Vote thread:
https://lists.apache.org/thread/ktq6tt61btlx93tdc3kw2pw5skyo35h7

Thank you to all the above members for helping us to verify and vote for
the 3.1.2 release.

Thanks

[ANNOUNCE] Apache Pulsar C# Client DotPulsar 3.1.2 released

[David Jensen]

The Apache Pulsar team is proud to announce DotPulsar version 3.1.2

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

For Pulsar release details and downloads, visit:
https://github.com/apache/pulsar-dotpulsar/releases/tag/3.1.2

Nuget package:
https://www.nuget.org/packages/DotPulsar/3.1.2

Release Notes are at:
https://github.com/apache/pulsar-dotpulsar/blob/master/CHANGELOG.md

We would like to thank the contributors who made the release possible.

Regards,

The Pulsar Team

Re: [ANNOUNCE] Apache Pulsar C# Client DotPulsar 3.1.2 released

[tison]

Congrats and thanks for everyone making this release happen :D

Best,
tison.

David Jensen  于2024年1月29日周一 19:56写道：
>
> The Apache Pulsar team is proud to announce DotPulsar version 3.1.2
>
> Pulsar is a highly scalable, low-latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at least once delivery of messages, automatic cursor management for
> subscribers, and cross-datacenter replication.
>
> For Pulsar release details and downloads, visit:
> https://github.com/apache/pulsar-dotpulsar/releases/tag/3.1.2
>
> Nuget package:
> https://www.nuget.org/packages/DotPulsar/3.1.2
>
> Release Notes are at:
> https://github.com/apache/pulsar-dotpulsar/blob/master/CHANGELOG.md
>
> We would like to thank the contributors who made the release possible.
>
> Regards,
>
> The Pulsar Team

Re: [ANNOUNCE] Apache Pulsar C# Client DotPulsar 3.1.2 released

[David Jensen]

Thanks for helping with advice and guidance tison :)
Greetings
David

On 2024/01/29 12:00:21 tison wrote:
> Congrats and thanks for everyone making this release happen :D
> 
> Best,
> tison.
> 
> David Jensen  于2024年1月29日周一 19:56写道：
> >
> > The Apache Pulsar team is proud to announce DotPulsar version 3.1.2
> >
> > Pulsar is a highly scalable, low-latency messaging platform running on
> > commodity hardware. It provides simple pub-sub semantics over topics,
> > guaranteed at least once delivery of messages, automatic cursor management 
> > for
> > subscribers, and cross-datacenter replication.
> >
> > For Pulsar release details and downloads, visit:
> > https://github.com/apache/pulsar-dotpulsar/releases/tag/3.1.2
> >
> > Nuget package:
> > https://www.nuget.org/packages/DotPulsar/3.1.2
> >
> > Release Notes are at:
> > https://github.com/apache/pulsar-dotpulsar/blob/master/CHANGELOG.md
> >
> > We would like to thank the contributors who made the release possible.
> >
> > Regards,
> >
> > The Pulsar Team
> 

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5

[PengHui Li]

+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 Sat, Jan 27, 2024 at 11:15 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 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)
>

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5

[Lari Hotari]

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

[DISCUSS] Add a policy to delivery messages to each consumers qually if message not contains key

[Yubiao Feng]

Hi all

### Background
Regarding Key_Shared mode, messages without message-key will default to
"NONE_KEY".

### Issue
In a topic, if half of the messages contain a message-key and the other
half do not. This will result in the consumer who occupies the key-range of
"NONE_KEY" consuming more much messages than others.

### What I want to do
I want to add a new config to switch the behavior when the message does
not contain a message-key:
- the policy exists: default the message-key to "NONE_KEY".
- the new policy: default the message-key to a random value when the
message does not contain a key.


Thanks
Yubiao Feng

Re: [E] Re: [DISCUSS] PIP-188(BlueGreenClusterMigration) Remove redirectedClusterURI in Pulsar Client

[Heesung Sohn]

Here is the sample code to clean this lookup/urlLookupMap access(by
following Option A-1).

https://github.com/heesung-sn/pulsar/pull/60

Plz let me know if this looks good. Then, I will raise a PR, and
accordingly, I will apply a similar change to other clients(cpp and golang)
when adding the blue-green migration logic.

Regards,
Heesung


On Sun, Jan 28, 2024 at 3:23 PM Heesung Sohn  wrote:

> I see. Thank you for clarifying this requirement.
>
> Then, I am wondering if we need to refactor the current
> `lookup/urlLookupMap` access code to avoid using `lookup` when the
> `redirectedClusterURI` is set at the consumers/producer layer. (it appears
> that we still use `lookup` in the following code at the PulsarClientImpl
> even when the consumers/producer might have migrated already(set
> redirectedClusterURI already). Maybe I missed some other logic here, and
> please also correct me if this behavior is fine.
>
> Some of the `lookup` access examples:
>
>
> https://github.com/apache/pulsar/blob/master/pulsar-client/src/main/java/org/apache/pulsar/client/impl/PulsarClientImpl.java#L574
>
>
> https://github.com/apache/pulsar/blob/master/pulsar-client/src/main/java/org/apache/pulsar/client/impl/PulsarClientImpl.java#L951
>
>
> https://github.com/apache/pulsar/blob/master/pulsar-client/src/main/java/org/apache/pulsar/client/impl/PulsarClientImpl.java#L989
>
>
> https://github.com/apache/pulsar/blob/master/pulsar-client/src/main/java/org/apache/pulsar/client/impl/PulsarClientImpl.java#L999
>
>
> If we need to make the clients use `urlLookupMap` after
> producers/customers are migrated, then I guess we may need to consider the
> following options.
>
> Option A-1:
> Pass `optional redirectedClusterURI` var to the above PulsarClientImpl
> funcs to select the lookup or urlLookupMap inside.
>
> Option A-2:
> - Remove urlLookupMap from PulsarClientImpl
> - Instead, add serviceNameResolverMap in LookupService
> - Pass `optional redirectedClusterURI` var to the above PulsarClientImpl
> funcs
> - Pass `optional redirectedClusterURI` var to the above LookupService funcs
>
>
> Regards,
> Heesung
>
>
>
> On Sat, Jan 27, 2024 at 10:33 AM Rajan Dhabalia
>  wrote:
>
>> Hi,
>>
>> Updating ServiceUrl in PulsarClient will make all producers and
>> consumers of all topics to use that new url which is incorrect because
>> redirection state can be different for each topic and even producer
>> and consumer of the same topic. So, we can not update main serviceUrl
>> but client should maintain redirection url for each producer and
>> consumer based on its state decided by the server.
>>
>>
>> Sent from my iPhone
>>
>> > On Jan 26, 2024, at 9:12 AM, Heesung Sohn  wrote:
>> >
>> > To add more context, I am trying to add this blue-green migration
>> logic in
>> > the cpp and golang client, and before copying the current logic, I am
>> > wondering if we can simplify it.
>> >
>> > Again, since all of the producers and consumers from the same client and
>> > topic need to migrate eventually,
>> > I think directly updating the lookup service of that shared client to
>> the
>> > new cluster seems harmless.
>> > I might be missing some other requirements here, so please correct me.
>> > If we conclude keeping this redirectedClusterURI in HandlerState here, I
>> > will go ahead and copy the current java client logic to other clients.
>> >
>> > Also, I updated the sample code for better synchronization and dedup.
>> >
>> https://urldefense.com/v3/__https://github.com/heesung-sn/pulsar/pull/59/__;!!Op6eflyXZCqGR5I!GOoO9eJK-kfDowteNFB-KOZpNcOrlY32vOe5Z86oxNS9wuxZjjqfwunkBYgxHjtBLEpnjga7rArkuM1fbw$
>> >
>> > Thanks,
>> > Heesung
>> >
>> >
>> >
>> >> On Thu, Jan 25, 2024 at 10:51 PM Heesung Sohn 
>> wrote:
>> >>
>> >> I am sorry, but the current implementation of blue-green migration is
>> for
>> >> all topics (producers and customers), not topic-specific. Could you
>> correct
>> >> me if I am wrong here?
>> >> So, for the current requirement(all topics migration), can't we just
>> >> update the original lookup service for that client because all of the
>> >> topics (of consumers and producers) will eventually migrate to the new
>> >> cluster?
>> >> Having said this, having redirectedClusterURI in HandlerState appears
>> to
>> >> be futuristic.
>> >>
>> >> Heesung
>> >>
>> >>
>> >>
>> >> On Thu, Jan 25, 2024 at 10:36 PM Heesung Sohn 
>> wrote:
>> >>
>>  This might not work because same PulsarClient can be used to create
>> >>> multiple topics and producer/consumer and migration state can be
>> different
>> >>> per topic and even for produce/consumer (of same topic) so, changing
>> >>> service url will not work for blue-green migration redirection for all
>> >>> topics served by that PulsarClient.
>> >>>
>> >>> Good point on this topic (and producer and consumer) level migration
>> >>> requirement. I was under the impression that the migration happens
>> for all
>> >>> topics from the old to the new cluster.
>> >>>
>> >>> For this requirement, I 

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 5

[Zike Yang]

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
> > 
> > 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: [DISCUSS] Add a policy to delivery messages to each consumers qually if message not contains key

[PengHui Li]

+1

BTW, instead of having a random key, can we just dispatch the messages
without a key
in the round-robin fashion? It just works like the Shared subscription.

Regards,
Penghui

On Tue, Jan 30, 2024 at 2:32 AM Yubiao Feng
 wrote:

> Hi all
>
> ### Background
> Regarding Key_Shared mode, messages without message-key will default to
> "NONE_KEY".
>
> ### Issue
> In a topic, if half of the messages contain a message-key and the other
> half do not. This will result in the consumer who occupies the key-range of
> "NONE_KEY" consuming more much messages than others.
>
> ### What I want to do
> I want to add a new config to switch the behavior when the message does
> not contain a message-key:
> - the policy exists: default the message-key to "NONE_KEY".
> - the new policy: default the message-key to a random value when the
> message does not contain a key.
>
>
> Thanks
> Yubiao Feng
>

Re: [DISCUSS] Add a policy to delivery messages to each consumers qually if message not contains key

[Yubiao Feng]

Hi Penghui

> BTW, instead of having a random key, can we just dispatch the
> messages without a key in the round-robin fashion?
> It just works like the Shared subscription.

Sure, good suggestion.

Thanks
Yubiao Feng

On Tue, Jan 30, 2024 at 10:50 AM PengHui Li  wrote:

> +1
>
> BTW, instead of having a random key, can we just dispatch the messages
> without a key
> in the round-robin fashion? It just works like the Shared subscription.
>
> Regards,
> Penghui
>
> On Tue, Jan 30, 2024 at 2:32 AM Yubiao Feng
>  wrote:
>
> > Hi all
> >
> > ### Background
> > Regarding Key_Shared mode, messages without message-key will default to
> > "NONE_KEY".
> >
> > ### Issue
> > In a topic, if half of the messages contain a message-key and the other
> > half do not. This will result in the consumer who occupies the key-range
> of
> > "NONE_KEY" consuming more much messages than others.
> >
> > ### What I want to do
> > I want to add a new config to switch the behavior when the message does
> > not contain a message-key:
> > - the policy exists: default the message-key to "NONE_KEY".
> > - the new policy: default the message-key to a random value when the
> > message does not contain a key.
> >
> >
> > Thanks
> > Yubiao Feng
> >
>

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