You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Justin Leet (JIRA)" <ji...@apache.org> on 2018/09/05 15:35:00 UTC

[jira] [Updated] (METRON-1616) Changing alert status fails if no metaalerts have been created yet

     [ https://issues.apache.org/jira/browse/METRON-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Leet updated METRON-1616:
--------------------------------
    Fix Version/s: 0.6.0

> Changing alert status fails if no metaalerts have been created yet
> ------------------------------------------------------------------
>
>                 Key: METRON-1616
>                 URL: https://issues.apache.org/jira/browse/METRON-1616
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Ryan Merriman
>            Assignee: Ryan Merriman
>            Priority: Major
>             Fix For: 0.6.0
>
>
> Patching an alert will fail with a IndexNotFoundException if a metaalert hasn't been created yet and the metaalert index doesn't exist.  This is because the ElasticsearchMetaAlertDao tries to lookup and update any metaalerts that contain the alert.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)