Re: [VOTE] Pulsar Release 2.3.1 Candidate 1

2019-04-04 Thread Matteo Merli
Thanks for pointing out! Updated the issue target for 2.3.2 -- Matteo Merli On Thu, Apr 4, 2019 at 4:58 PM Ezequiel Lovelle wrote: > > Hi! > Great work! > > Just a little observation, issue 3935 > has 2.3.1 milestone tag but > the fix in pull 3946 <

Re: [VOTE] Pulsar Release 2.3.1 Candidate 1

2019-04-04 Thread Ezequiel Lovelle
Hi! Great work! Just a little observation, issue 3935 has 2.3.1 milestone tag but the fix in pull 3946 wasn't merged in 2.3.1. Thanks. -- *Ezequiel Lovelle* On Thu, 4 Apr 2019 at 20:09, Matteo Merli wro

[VOTE] Pulsar Release 2.3.1 Candidate 1

2019-04-04 Thread Matteo Merli
This is the first release candidate for Apache Pulsar, version 2.3.1. It fixes the following issues: https://github.com/apache/pulsar/milestone/21?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 sour

Re: [DISCUSS] PIP 34: Add new subscribe type -- Key_Failover

2019-04-04 Thread Sijie Guo
Penguin, Thank you for your clarification! That makes sense to me then. Sijie On Thu, Apr 4, 2019 at 2:21 AM PengHui Li wrote: > @Sijie Guo > > Sorry, I may not have described my point in the previous email. > I try to describe it again. :) > > User can use key to achieve business logic(e.g.

Re: [DISCUSS] PIP 34: Add new subscribe type -- Key_Failover

2019-04-04 Thread PengHui Li
@Sijie Guo Sorry, I may not have described my point in the previous email. I try to describe it again. :) User can use key to achieve business logic(e.g. use user_id as message key) At the same time, want to use another identifier as the basis for the order. As the message key has many uses, av

Slack digest for #dev - 2019-04-04

2019-04-04 Thread Apache Pulsar Slack
2019-04-03 21:31:28 UTC - FG: @FG has joined the channel

Re: [DISCUSS] PIP 34: Add new subscribe type -- Key_Failover

2019-04-04 Thread Sijie Guo
Jia thank you for raising this up. A couple of comments here 1. technically you don't need a consistent hashing mechanism for dividing hash ranges for consumers. Any hash mechanism that can map a key to a consumer should work here. The only advantage of consistent hashing mechanism is to reduce t