You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Justin Leet (JIRA)" <ji...@apache.org> on 2018/12/11 16:24:00 UTC

[jira] [Updated] (METRON-1845) Correct Test Data Load in Elasticsearch Integration Tests

     [ https://issues.apache.org/jira/browse/METRON-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Leet updated METRON-1845:
--------------------------------
    Fix Version/s: 0.7.0

> Correct Test Data Load in Elasticsearch Integration Tests
> ---------------------------------------------------------
>
>                 Key: METRON-1845
>                 URL: https://issues.apache.org/jira/browse/METRON-1845
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>             Fix For: 0.7.0
>
>
> The Elasticsearch integration tests use the legacy Transport client to load test data into the search indexes before running the tests. Loading the test data like this does not accurately reflect how the indices will appear in a production environment.
> This should be changed to use our existing ElasticsearchUpdateDao to write the test data.  This ensures that any changes made to the 'write' portion of our Elasticsearch code will function correctly with the 'read' portion. This ensures that telemetry written into Elasticsearch by 'Indexing' can be read correctly by the Alerts UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)