[
https://issues.apache.org/jira/browse/STORM-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273934#comment-15273934
]
ASF GitHub Bot commented on STORM-1755:
---------------------------------------
Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1386#issuecomment-217418115
Going by the Kafka coding guidelines
(http://kafka.apache.org/coding-guide.html), it looks like client libraries can
only be assumed to support two major (0.x) releases (current and previous). I'm
wondering if it would be possible to spin off the components executing requests
against Kafka into separate projects, so users can declare dependency on the
newest storm-kafka-client while also retaining support for older brokers?
> Revert the kafka client version upgrade in storm-kafka module
> -------------------------------------------------------------
>
> Key: STORM-1755
> URL: https://issues.apache.org/jira/browse/STORM-1755
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-kafka
> Affects Versions: 1.0.1
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
>
> storm-kafka module does not use any feature of new API. The newer kafka
> client (0.9.x) is not backward compatible with 0.8.x brokers and upgrading
> storm-kafka version in topology could break the currently running topologies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
