[
https://issues.apache.org/jira/browse/METRON-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253528#comment-16253528
]
ASF GitHub Bot commented on METRON-1289:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/824
@merrimanr I'm okay with excluding metaalerts (although I need to review
what you did there). I wouldn't expect it to go down by two though.
Say I have two matches, I put one in a metaalert (so it should be hidden).
I make the query again. I would still expect to get the remaining, standalone
match. The metaalert should never have showed up and the child alert should be
hidden. So one result.
> Alert fields are lost when a MetaAlert is created
> -------------------------------------------------
>
> Key: METRON-1289
> URL: https://issues.apache.org/jira/browse/METRON-1289
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> When a MetaAlert is created, the included results are being updated
> incorrectly with only the "metaalert" field. This causes subsequent findOne
> operations to only return the "metaalert field for that alert. All fields
> should continue to be present.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
