feat: protocol support for V11 fetch w/ rackID #1605
Conversation
These are the initial protocol beginnings to add support for follower fetching (KIP-392). This commit simply adds configuration support for a consumer to specify its rack identifier and to flow it in a V11 FetchRequest and correctly decode the "preferredReplica" field in the response. Currently no further action is taken. A future PR will be required to act upon this response. Signed-off-by: Dominic Evans <dominic.evans@uk.ibm.com>
|
ooh, this is super exciting! |
|
👋 @dnwe you should have received an invite to join this repo as a collaborator so you could merge this PR and others that you see fit. Thank you so much for continued contributions. |
|
@bai thanks 😀 As an aside, I have also been experimenting with generating the protocol Go code from the upstream .json-based format descriptions, which I thought might be interesting for Sarama v2.x — once I have something reasonable around that I'll push up a branch to collaborate over |
|
@dnwe when you do decide to work on the followup to read |
|
@lizthegrey @dnwe I took a shot at that #1696 |
These are the initial protocol beginnings to add support for follower
fetching (KIP-392). This commit simply adds configuration support for a
consumer to specify its rack identifier and to flow it in a V11
FetchRequest and correctly decode the "preferredReplica" field in the
response. Currently no further action is taken. A future PR will be
required to act upon this response.