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

[ https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li resolved EAGLE-947. -- Resolution: Fixed fixed by PR - https://github.com/apache/eagle/pull/864 > Publishers with same policy b

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

[ https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-947: - Summary: Publishers with same policy but different schema could produce duplicate alerts (was: Publishers

[jira] [Updated] (EAGLE-947) Publishers with different schema could produce duplicate alerts

[ https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-947: - Description: Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and another i

[jira] [Created] (EAGLE-947) Publishers with different schema could produce duplicate alerts

Garrett Li created EAGLE-947: Summary: Publishers with different schema could produce duplicate alerts Key: EAGLE-947 URL: https://issues.apache.org/jira/browse/EAGLE-947 Project: Eagle Issue Ty