[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425899#comment-15425899
]
ASF GitHub Bot commented on STORM-822:
--------------------------------------
Github user jianbzhou commented on the issue:
https://github.com/apache/storm/pull/1131
@hmcl and all, the new spout is fit for the at least once semantics and
works fine for us, thanks a lot! Very recently one of our key customers asked
to use a at most once implementation. Do we have any plan to have a
at-most-once implementation? They set the topology.acker.executors=0 and found
the spout is not working. Could you please help to evaluate - 1, will we
implement this? 2. roughly how long time needed? Thanks
**Requirement from customer** - “topology.acker.executors” is a Storm
parameter, which refers to at-least-once when it’s not 0, and at-most-once if
it’s 0. We want to know do we have a at-most-once implementation?
> Kafka Spout New Consumer API
> ----------------------------
>
> 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
> Fix For: 1.0.0, 2.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
