[
https://issues.apache.org/jira/browse/KAFKA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288035#comment-15288035
]
Jiangjie Qin commented on KAFKA-3721:
-------------------------------------
I am fine either way. My understanding of the original intention was to just
let "0.10.0" pointing to the latest IV object so it is always ready for
release.
KIP-35 would be useful, although arguably there are some cases that people want
to specify the version instead of doing auto negotiation.
> UpdateMetadataRequest V2 should be in API version 0.10.0-IV1
> ------------------------------------------------------------
>
> Key: KAFKA-3721
> URL: https://issues.apache.org/jira/browse/KAFKA-3721
> Project: Kafka
> Issue Type: Bug
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Priority: Blocker
> Fix For: 0.10.0.0
>
>
> When we introduce UpdateMetadataRequest V2 in KAFKA-1215, we did not
> introduce a new API Version 0.10.0-IV1 but reused 0.10.0-IV0. This causes
> problem for people who are running off the trunk and using message format
> 0.10.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
