[
https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414995#comment-15414995
]
Magnus Edenhill commented on KAFKA-1588:
----------------------------------------
Thanks [~ijuma].
But I dont see how the bug fix changes the protocol (the behaviour is
undocumented and non-intuitive), or breaks any clients (how can a client rely
or make use of undefined ordering, silent ignore of duplicate topics, etc?).
For the greater good of the community and eco-system I feel it is important
that the protocol specification is considered authoritative rather than the
broker implementation, and any discrepencies between the two should be fixed in
the corresponding implementation(s) rather than the protocol spec unless the
protocol spec is clearly wrong (which would affect all protocol implementations
(clients)) .
> 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)
