[
https://issues.apache.org/jira/browse/STORM-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311925#comment-15311925
]
ASF GitHub Bot commented on STORM-1755:
---------------------------------------
Github user harshach commented on the issue:
https://github.com/apache/storm/pull/1386
@abhishekagarwal87 didn't see this merged in. Instead of overriding the
kafka.version for storm-kafka lets add another param to pom.xml and keep it at
0.8.2.1 and use that as kafka version for storm-kafka. This way distributors
can override the kafka version for both storm-kafka and storm-kafka-client by
passing kafka.version and new param for storm-kafka instead of keep building it
0.8.2.1 and for apache it will work as this patch intended.
> 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
> Fix For: 2.0.0, 1.0.2, 1.1.0
>
>
> 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)
