[
https://issues.apache.org/jira/browse/METRON-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242301#comment-16242301
]
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_r149423571
--- Diff:
metron-platform/metron-indexing/src/main/java/org/apache/metron/indexing/dao/IndexDao.java
---
@@ -65,6 +65,8 @@
*/
Document getLatest(String guid, String sensorType) throws IOException;
+ Iterable<Document> getAllLatest(Map<String, String> guidToIndices)
throws IOException;
--- End diff --
Actually, even a default implementation here that calls getLatest might be
useful.
> 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)
