[
https://issues.apache.org/jira/browse/KAFKA-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262593#comment-15262593
]
Gwen Shapira commented on KAFKA-3633:
-------------------------------------
I completely understand the pain that this change will cause the Storm
community (and probably few others). However, I have concerns regarding this
change:
The API is marked as unstable, so we expected the Storm community to understand
it is subject to incompatible changes (I'm sure you are working with other
communities that do the same).
The new API, as is, was voted in at KIP-45
(https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61337336)
It was discussed in a KIP meeting and passed with 5 committer votes and 9
overall votes.
Changing it again is a change to a public API and would require another
community discussion and vote. Do you mind raising the issue in the mailing
list?
> Kafka Consumer API breaking backward compatibility
> --------------------------------------------------
>
> Key: KAFKA-3633
> URL: https://issues.apache.org/jira/browse/KAFKA-3633
> Project: Kafka
> Issue Type: Bug
> Reporter: Sriharsha Chintalapani
> Assignee: Sriharsha Chintalapani
> Priority: Blocker
> Fix For: 0.10.0.0
>
>
> KAFKA-2991 and KAFKA-3006 broke the backward compatibility. In storm we
> already using 0.9.0.1 consumer api for the KafkaSpout. We should atleast kept
> the older methods and shouldn't be breaking backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
