[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086228#comment-15086228
]
ASF GitHub Bot commented on STORM-822:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/986#issuecomment-169452092
CI seems to be failing with a trident kafka test hanging.
The code appears to provide a best effort replay, but that is neither at
least once nor at most once, so it is likely to cause issues for some
topologies that don't expect this a-typical behavior. I am not an expert on
the kafka API, but it looks like auto.commit.enable is inherently incompatible
with what storm wants from a well behaved spout.
> As a storm developer I’d like to use the new kafka consumer API (0.8.3) to
> reduce dependencies and use long term supported kafka apis
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: STORM-822
> URL: https://issues.apache.org/jira/browse/STORM-822
> Project: Apache Storm
> Issue Type: Story
> Components: storm-kafka
> Reporter: Thomas Becker
> Assignee: Hugo Louro
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
