[
https://issues.apache.org/jira/browse/EAGLE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438286#comment-15438286
]
ASF GitHub Bot commented on EAGLE-481:
--------------------------------------
GitHub user yonzhang opened a pull request:
https://github.com/apache/incubator-eagle/pull/391
Make alert engine topology to be one application so to be managed by Eagle
API
https://issues.apache.org/jira/browse/EAGLE-481
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yonzhang/incubator-eagle develop
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/391.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 #391
----
commit 050b2d52a05cecd3fc8987b90f107c25e63fad96
Author: yonzhang <[email protected]>
Date: 2016-08-25T19:49:33Z
create alert datasource/stream while installing application
commit 8d535797208611ceec0923497204f573a62bb544
Author: yonzhang <[email protected]>
Date: 2016-08-25T21:02:19Z
hook data source with stream
commit 00ab16b01d2ad4f2dcaed05db716c71daad0145d
Author: yonzhang <[email protected]>
Date: 2016-08-25T21:03:19Z
Merge remote-tracking branch 'upstream/develop' into develop
commit 36ca130043e018866b8cbbbcbd59db1cb40ddb4b
Author: yonzhang <[email protected]>
Date: 2016-08-26T01:25:05Z
wrapper alert engine with one application of Eagle
commit e811f1fb7d1aa4e195a3dea34005617d82200a74
Author: yonzhang <[email protected]>
Date: 2016-08-26T01:26:33Z
fix merge issue
commit 7cf760f80e7d6656834f3b84df21a12e7055b507
Author: yonzhang <[email protected]>
Date: 2016-08-26T01:35:25Z
add license header
----
> Make alert engine topology to be one application so to be managed by Eagle API
> ------------------------------------------------------------------------------
>
> Key: EAGLE-481
> URL: https://issues.apache.org/jira/browse/EAGLE-481
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Edward Zhang
> Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Eagle alert engine as of 0.5 is multiple separate storm topologies. Instead
> of running alert engine manually, we can leverage Eagle 0.5 application API
> to manage alert engine.
> Options:
> 1. Wrapper alert engine topology to be one Eagle application
> 2. Define a new service API to directly start/stop alert engine
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
