[
https://issues.apache.org/jira/browse/METRON-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432852#comment-16432852
]
ASF GitHub Bot commented on METRON-1421:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/970
@mmiklavc I think that's a good insight. The original intention of
metaalerts was to basically wrap and augment the functionality of the index
alerts. I think a portion of that problem we've hit is that wrapping that is
both specific in implementation and general in purpose and it blurs that line
between data store and domain model object.
I definitely agree that a discuss thread on our access patterns is a good
outcome of this. Doing an second implementation is always revealing for things
like this, and taking that insight and improving things for the future would be
good.
> Create a SolrMetaAlertDao
> -------------------------
>
> Key: METRON-1421
> URL: https://issues.apache.org/jira/browse/METRON-1421
> Project: Metron
> Issue Type: Sub-task
> Reporter: Justin Leet
> Assignee: Justin Leet
> Priority: Major
>
> Create an implementation of the MetaAlertDao for Solr. This will involve
> implementing the various MetaAlertDao methods using the SolrJ library and
> also providing a SolrMetaAlertIntegrationTest (similar to
> ElasticsearchMetaAlertIntegrationTest).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
