[
https://issues.apache.org/jira/browse/METRON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209378#comment-16209378
]
ASF GitHub Bot commented on METRON-1255:
----------------------------------------
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/802#discussion_r145424998
--- Diff:
metron-platform/metron-elasticsearch/src/test/java/org/apache/metron/elasticsearch/integration/ElasticsearchMetaAlertIntegrationTest.java
---
@@ -83,6 +90,7 @@ public static void setup() throws Exception {
put("es.date.format", DATE_FORMAT);
}
};
+ accessConfig.setMaxSearchResults(1000);
--- End diff --
Makes sense. Do you know if there's a reason we don't default there if it's
not set? It's outside the scope of this, so if you don't know I'm not worried,
but it seems like it's an opportunity.
> MetaAlert search is not filtering on status
> -------------------------------------------
>
> Key: METRON-1255
> URL: https://issues.apache.org/jira/browse/METRON-1255
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
>
> Currently both active and inactive metaAlerts are being returned in a search.
> Only active metaAlerts should be returned.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
