[
https://issues.apache.org/jira/browse/STORM-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465490#comment-16465490
]
Stig Rohde Døssing commented on STORM-2974:
-------------------------------------------
[~aniket.alhat] Yes, you are right about the need for more state.
I would still hope for being able to release storm-kafka-client independently
soon. The issue with backporting the changes I mentioned to 1.x is that the
changes break a good bit of the configuration API for all the Kafka spouts
(Trident and non-Trident). If we decide not to release storm-kafka-client
independently, we'll probably just have to break the API in a minor version,
but I'd like to avoid doing that (again) if possible.
> 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)