[
https://issues.apache.org/jira/browse/METRON-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250035#comment-16250035
]
ASF GitHub Bot commented on METRON-1289:
----------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/824#discussion_r150638251
--- Diff:
metron-platform/metron-indexing/src/test/java/org/apache/metron/indexing/dao/InMemoryMetaAlertDao.java
---
@@ -200,4 +207,23 @@ public MetaAlertCreateResponse
createMetaAlert(MetaAlertCreateRequest request)
createResponse.setCreated(true);
return createResponse;
}
+
+ @Override
+ public boolean addAlertsToMetaAlert(String metaAlertGuid,
Collection<String> alertGuids,
+ Collection<String> sensorTypes) throws IOException {
+ return true;
--- End diff --
Given the non-implementation of these, do we not have any integration tests
in metron-rest exercising the add/remove alerts calls?
> 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)
