[
https://issues.apache.org/jira/browse/METRON-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240852#comment-16240852
]
ASF GitHub Bot commented on METRON-1290:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/825#discussion_r149196394
--- Diff:
metron-platform/metron-elasticsearch/src/test/java/org/apache/metron/elasticsearch/dao/ElasticsearchMetaAlertDaoTest.java
---
@@ -489,4 +505,54 @@ public void testHandleMetaUpdateAlert() throws
IOException {
verify(mockEsDao, times(1)).getLatest(guidAlert, null);
verify(mockEsDao, times(1)).batchUpdate(updates);
}
+
+ @Test
+ public void getAllAlertsForMetaAlertShouldReturnAllAlerts() throws
Exception {
--- End diff --
Are we able to replicate this defect in the integration tests? Personally,
I'd prefer to see the integration tests validate something like this, if at all
possible. That would also help our migration to ES 5.x over this mock driven
test.
> Only first 10 alerts are update when a MetaAlert status is changed to inactive
> ------------------------------------------------------------------------------
>
> Key: METRON-1290
> URL: https://issues.apache.org/jira/browse/METRON-1290
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Priority: Trivial
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
