[
https://issues.apache.org/jira/browse/EAGLE-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986671#comment-15986671
]
ASF GitHub Bot commented on EAGLE-993:
--------------------------------------
Github user qingwen220 commented on a diff in the pull request:
https://github.com/apache/eagle/pull/926#discussion_r113703970
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/impl/AlertPublisherImpl.java
---
@@ -73,11 +76,11 @@ public void nextEvent(PublishPartition partition,
AlertStreamEvent event) {
private void notifyAlert(PublishPartition partition, AlertStreamEvent
event) {
// remove the column values for publish plugin match
partition.getColumnValues().clear();
- if (!publishPluginMapping.containsKey(partition)) {
+ if (!publishPluginMapping.containsKey(partition.getPublishId())) {
--- End diff --
Sorry for the late reply.
For the alert dropping off of unwanted stream is handled in
AlertBoltOutputCollectorWrapper, which are kept as it is.
In this class, i just simplify the coding, which should keeps the original
logic. How do you think? @garrettlish
> add duplicate removal settings in policy definition
> ---------------------------------------------------
>
> Key: EAGLE-993
> URL: https://issues.apache.org/jira/browse/EAGLE-993
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Zhao, Qingwen
> Assignee: Zhao, Qingwen
>
> customize duplicate fields & interval in each policy
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
