You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/05 20:50:20 UTC
[jira] [Commented] (EAGLE-590) AlertEngine: the kafka_spout might
be dropped by metadata update when system ack a tupe
[ https://issues.apache.org/jira/browse/EAGLE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549902#comment-15549902 ]
ASF GitHub Bot commented on EAGLE-590:
--------------------------------------
GitHub user RalphSu opened a pull request:
https://github.com/apache/incubator-eagle/pull/475
[EAGLE-590]: AlertEngine: the kafka_spout might be dropped by metadat…
Fix the kafka_spout metadata missing caused npe issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RalphSu/incubator-eagle master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/475.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 #475
----
commit c100d84cd75cfd0d5c382ecdeedfa1d23e4d5568
Author: Ralph, Su <su...@gmail.com>
Date: 2016-10-05T18:13:56Z
[EAGLE-590]: AlertEngine: the kafka_spout might be dropped by metadata update when system ack a tupe
----
> AlertEngine: the kafka_spout might be dropped by metadata update when system ack a tupe
> ---------------------------------------------------------------------------------------
>
> Key: EAGLE-590
> URL: https://issues.apache.org/jira/browse/EAGLE-590
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Su Ralph
> Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> In correlationSpout's ack/failure method, given a messageId, a spout might be not available when there is a metadata update. Thus cause an NPE in spout ack/failure, this would cause spout error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)