[
https://issues.apache.org/jira/browse/STORM-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324664#comment-15324664
]
ASF GitHub Bot commented on STORM-1705:
---------------------------------------
GitHub user abhishekagarwal87 opened a pull request:
https://github.com/apache/storm/pull/1481
STORM-1705: Fix cap-retry bug
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/abhishekagarwal87/storm cap-retry
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1481.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1481
----
commit a59695e97953dc68b798f01df92c49b6df4b6abd
Author: Abhishek Agarwal <abhishek.agar...@inmobi.com>
Date: 2016-06-10T15:48:40Z
STORM-1705: Fix cap-retry bug
----
> Cap on number of retries for a failed message in kafka spout
> ------------------------------------------------------------
>
> Key: STORM-1705
> URL: https://issues.apache.org/jira/browse/STORM-1705
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-kafka
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
> Fix For: 2.0.0, 1.0.2, 1.1.0
>
>
> The kafka-spout module based on newer APIs has a cap on the number of times,
> a message is to be retried. It will be a good feature add in the older kafka
> spout code as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
