to be
in order.
Thanks all for the help.
Haseeb
From: Javed, Haseeb
Sent: Sunday, October 1, 2017 6:39:13 AM
To: dev@kafka.apache.org
Subject: Re: How is CorrelationId used for matching request and response
Thanks all for reaching out.
Ted - I am looking
ds.
> <https://github.com/apache/kafka/blob/0.11.0/clients/src/
> main/java/org/apache/kafka/common/requests/AbstractResponse.java>
>
>
> Haseeb
>
>
> From: Jay Kreps
> Sent: Saturday, September 30, 2017 11:43:30 PM
> To: dev@
43:30 PM
To: dev@kafka.apache.org
Subject: Re: How is CorrelationId used for matching request and response
Yes the idea of the correlation id is to make it easier for the client to
match a particular response to the request it answers. Kafka’s protocol
allows sending multiple requests without wait
Yes the idea of the correlation id is to make it easier for the client to
match a particular response to the request it answers. Kafka’s protocol
allows sending multiple requests without waiting for the response. In
theory you can just rely on ordering, but that can be a bit fragile if the
client h
Which release / version are you looking at ?
In trunk branch, I only see one toSend():
protected Send toSend(String destination, ResponseHeader header, short
apiVersion) {
return new NetworkSend(destination, serialize(apiVersion, header));
On Fri, Sep 29, 2017 at 4:49 PM, Javed, Hase
The Kafka protocol guide mentions that each request and response contains a
correlationId which is a user-supplied integer to match requests and
corresponding responses. However, when I look at the code in the class
AbstractResponse, we have a method defined as following:
public Send toSend(St
