[
https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414868#comment-15414868
]
Magnus Edenhill commented on KAFKA-1588:
----------------------------------------
[~guozhang] Why would this fix require a protocol change? It is already an
array of Topics+partitions in the OffsetRequest and all the broker needs to do
is honour the contents and order of that list and respond accordingly, which
should be a broker implementation detail only and not affect the protocol
definition, right?
> Offset response does not support two requests for the same topic/partition
> combo
> --------------------------------------------------------------------------------
>
> Key: KAFKA-1588
> URL: https://issues.apache.org/jira/browse/KAFKA-1588
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.0
> Reporter: Todd Palino
> Assignee: Sriharsha Chintalapani
> Labels: newbie
>
> When performing an OffsetRequest, if you request the same topic and partition
> combination in a single request more than once (for example, if you want to
> get both the head and tail offsets for a partition in the same request), you
> will get a response for both, but they will be the same offset.
> We identified that the problem is that when the offset response is assembled,
> a map is used to store the offset info before it is converted to the response
> format and sent to the client. Therefore, the second request for a
> topic/partition combination will overwrite the offset from the first request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
