[
https://issues.apache.org/jira/browse/EAGLE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605187#comment-15605187
]
ASF GitHub Bot commented on EAGLE-684:
--------------------------------------
GitHub user RalphSu opened a pull request:
https://github.com/apache/incubator-eagle/pull/561
EAGLE-684: AlertEngine : PolicyDefinition.Defintion should not be cha…
…nged.
When introduced stated policy definition in one policy, there is a logic to
set the PolicyDefinition.Defintion's input and output stream while create the
policy handler.
This behavior change the policy definition itself, thus cause the metadata
reload incorrectly close and recreate policy evaluation handler.
Author: ralphsu
This closes #
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/561.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 #561
----
commit b2910f4d470c0047419ba79b0d20e059f122f36d
Author: Ralph, Su <[email protected]>
Date: 2016-10-25T12:25:08Z
EAGLE-684: AlertEngine : PolicyDefinition.Defintion should not be changed.
When introduced stated policy definition in one policy, there is a logic to
set the PolicyDefinition.Defintion's input and output stream while create the
policy handler.
This behavior change the policy definition itself, thus cause the metadata
reload incorrectly close and recreate policy evaluation handler.
Author: ralphsu
This closes #
----
> AlertEngine : PolicyDefinition.Defintion should not be changed.
> ---------------------------------------------------------------
>
> Key: EAGLE-684
> URL: https://issues.apache.org/jira/browse/EAGLE-684
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Su Ralph
> Assignee: Su Ralph
> Priority: Critical
> Fix For: v0.5.0
>
>
> When introduced stated policy definition in one policy, there is a logic to
> set the PolicyDefinition.Defintion's input and output stream while create the
> policy handler.
> This behavior change the policy definition itself, thus cause the metadata
> reload incorrectly close and recreate policy evaluation handler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
