[
https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112989#comment-14112989
]
Guozhang Wang commented on KAFKA-1588:
--------------------------------------
Thanks [~sriharsha] for the investigation, I looked through the code again and
I agree with you. Since the requestInfo of the OffsetRequest today is a Map, it
would simply override the old info with the new one when it was pointing to the
same partition. To really solve this issue we need to make requestInfo a List
instead of a Map, which would require a protocol change. Given its benefit
being just allowing two requests in one with the same topic / partition combo I
think this is not worth doing it.
> 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
> 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.2#6252)
