[
https://issues.apache.org/jira/browse/METRON-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518189#comment-16518189
]
ASF GitHub Bot commented on METRON-1626:
----------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1068
+1 Spun this up in dev and it worked like a charm. Thanks for the fix.
@sardell mentioned that this is covered in the e2e tests, which is how he
discovered the problem.
This regression was caused by #1049, but since the e2e are not running
reliably we probably did not attempt to run those before merging that one in.
Once we get #1004 merged, we should hopefully avoid regressions like this.
> Alerts UI: An empty result is returned when searching for a single alert
> contained in a metaalert
> -------------------------------------------------------------------------------------------------
>
> Key: METRON-1626
> URL: https://issues.apache.org/jira/browse/METRON-1626
> Project: Metron
> Issue Type: Bug
> Reporter: Shane Ardell
> Priority: Major
> Attachments: Screen Shot 2018-06-19 at 3.18.43 PM.png, Screen Shot
> 2018-06-19 at 3.19.09 PM.png
>
>
> When a user tries to searc for a single alert contained within a metaalert,
> an empty result set is returned from the API. Upon further inspection, it
> looks like this is because the query string is not updated to use
> metron_alert in place of alert. [This change happend in
> METRON-1601|https://github.com/apache/metron/pull/1049].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
