metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (METRON-1465) X-pack support for Elasticsearch
Date Mon, 02 Apr 2018 16:46:00 GMT


ASF GitHub Bot commented on METRON-1465:

Github user mmiklavc commented on a diff in the pull request:
    --- Diff: metron-interface/metron-rest/src/main/scripts/ ---
    @@ -36,6 +36,7 @@ METRON_SYSCONFIG="${METRON_SYSCONFIG:-/etc/default/metron}"
    --- End diff --
    @nickwallen This is consistent with what we've done for the parsers (see line 38 immediately
above). We could possibly refactor, but I wouldn't advise it as part of this PR. Not defining
a default would mean the responsibility is now on the end user for indexing, but not for parsers.
I think that is going to be more confusing to a user in the current state. I do agree that
these could probably be moved to the defaults script as a follow-on refactoring PR.

> X-pack support for Elasticsearch
> --------------------------------
>                 Key: METRON-1465
>                 URL:
>             Project: Metron
>          Issue Type: Bug
>    Affects Versions: 0.4.2
>            Reporter: Ward Bekker
>            Priority: Major
>             Fix For: 0.4.3
> Provide support for X-pack secured Elasticsearch clusters for the Elasticsearch writer
and the DAO used by the rest service.

This message was sent by Atlassian JIRA

View raw message