9066920586174c2ba967fbd2434a21fa5b8353fa - eagle

commit	9066920586174c2ba967fbd2434a21fa5b8353fa	[log] [tgz]
author	Xiancheng Li <xiancheng.li@ebay.com>	Tue Mar 14 15:22:03 2017 +0800
committer	Zhao, Qingwen <qingwzhao@apache.org>	Tue Mar 14 15:22:03 2017 +0800
tree	dc3adfc2efaaeefd29d5df5af7a506eab1ab2856
parent	7e41ed0b9d9c6bcbd5fef156ae5ca1cdc7e16c28 [diff]

[EAGLE-947] Publishers with same policy but different schema could produce duplicate alerts

Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and another is stream2. If publisher1 is configured for policy1 and stream1, and publisher2 is configured for policy1 and stream2, current code will produce 2 alerts for either stream1 or stream2.

Author: Xiancheng Li <xiancheng.li@ebay.com>

Closes #864 from garrettlish/master.

eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/evaluator/impl/AlertBoltOutputCollectorWrapper.java[diff]
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/test/java/org/apache/eagle/alert/engine/evaluator/impl/AlertBoltOutputCollectorWrapperTest.java[Added - diff]
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/test/java/org/apache/eagle/alert/engine/router/CustomizedHandler.java[diff]
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/test/java/org/apache/eagle/alert/engine/router/TestAlertBolt.java[diff]
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/test/java/org/apache/eagle/alert/engine/statecheck/TestStateCheckPolicy.java[diff]

5 files changed

tree: dc3adfc2efaaeefd29d5df5af7a506eab1ab2856