[
https://issues.apache.org/jira/browse/STORM-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463749#comment-16463749
]
Stig Rohde Døssing commented on STORM-2974:
-------------------------------------------
[~aniket.alhat]
{quote}
Do you know someone with whom may be I can confirm this?
{quote}
You can either try it out yourself (e.g. set up a test topology against Kafka
0.11 and try using storm-kafka to consume from it), or try asking on the
kafka-user mailing list whether the SimpleConsumer class I linked still works
for newer Kafka versions, even though it's deprecated. As long as
SimpleConsumer works, storm-kafka should also work. We put the note you quoted
in the documentation because we weren't sure when SimpleConsumer would be
removed, and we'd prefer people use storm-kafka-client for new code.
{quote}
Do you have any timeline in mind for backporting the bugfixes to 1.0.x?
{quote}
I'm a little unsure what you mean by bugfixes? Like I said, I'm not planning on
backporting the transactional spout to 1.x (including 1.2.x) at all. If we
start releasing storm-kafka-client independently, this should become a
non-issue, since you should be able to just use the newest spout with 1.x. If
we decide not to release storm-kafka-client independently, I might need to
reconsider depending on how far off 2.0.0 is.
Why do you need the transactional spout by the way? It was my impression that
the opaque (transactional) spout should be able to offer the same guarantees?
> Add a transactional non-opaque spout to storm-kafka-client
> ----------------------------------------------------------
>
> Key: STORM-2974
> URL: https://issues.apache.org/jira/browse/STORM-2974
> Project: Apache Storm
> Issue Type: Sub-task
> Components: storm-kafka-client
> Affects Versions: 2.0.0
> Reporter: Stig Rohde Døssing
> Assignee: Stig Rohde Døssing
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)