Re: [DISCUSS] KeyShared routing additions/configuration

2023-01-17 Thread Tim Corbett
To start, sorry if this breaks threading and/or ends up looking hideous, I am new to using these mailing lists and was not subscribed so can't seem to resume the thread from the latest message. > > The proposal is two-fold: first, we would like to implement a new KeyShared > > routing mechanism wh

Re: [DISCUSS] KeyShared routing additions/configuration

2023-01-15 Thread PengHui Li
Hi Tim, > The proposal is two-fold: first, we would like to implement a new KeyShared routing mechanism which tracks outstanding messages and their consumers, routing messages with outstanding keys to the current consumer handling that key, and any messages with new keys to any arbitrary consumer

Re: [DISCUSS] KeyShared routing additions/configuration

2023-01-13 Thread Enrico Olivelli
Tim, Il giorno gio 12 gen 2023 alle ore 04:31 Tim Corbett ha scritto: > > Greetings, > > I was informed to ask this here but was unclear yet if this should be a PIP > or not. Please advise if I should follow a different process. Thanks in > advance. > > The motivation is as follows: today we ha

[DISCUSS] KeyShared routing additions/configuration

2023-01-11 Thread Tim Corbett
Greetings, I was informed to ask this here but was unclear yet if this should be a PIP or not. Please advise if I should follow a different process. Thanks in advance. The motivation is as follows: today we have KeyShared subscriptions in which the consumers are rapidly autoscaling up and down