Skip to content
Discussion options

You must be logged in to vote

Hi, thanks for the detailed comparison — you've read the spec correctly, and I verified the two points that decide your questions. The short answer is: no, v5 has no way for a consumer to declare the hash ranges it owns — and yes, for your use case, staying on v4 Key_Shared STICKY over persistent topics is the intended pattern for now.

What the spec actually says (spec/scalable-topics/key-shared.md):

  1. Assignment is controller-driven, not client-declared. "The controller only decides which consumers share a segment; the bucket→consumer spread is computed broker-side from the live membership of the subscription." Every sharer declares the segment's full boundary list (identical for every sh…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by chrisdrobison-fbg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants