[
https://issues.apache.org/jira/browse/METRON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266590#comment-16266590
]
ASF GitHub Bot commented on METRON-939:
---------------------------------------
Github user mraliagha commented on the issue:
https://github.com/apache/metron/pull/840
One of the issues that we had with the previous mpack was the lack of
config segregation for Elasticsearch Master Nodes and Data Nodes. Hence, we
have ended up hardcoding specific configuration outside Ambari. With ES 5 it
will be even more complex due to the existence of Ingestion Nodes and ML Nodes.
Therefore, it would be really nice if we can have multiple tabs in Ambari ES
service. For example, one tab for generic configurations and another tab per
each node type to segregate specific configurations from generic ones.
> Upgrade ElasticSearch and Kibana
> --------------------------------
>
> Key: METRON-939
> URL: https://issues.apache.org/jira/browse/METRON-939
> Project: Metron
> Issue Type: Improvement
> Reporter: Jon Zeolla
> Assignee: Michael Miklavcic
>
> Upgrade ElasticSearch and Kibana (latest is 5.4 as of writing this). Among
> other benefits, this allows us to use periods in field names
> (https://github.com/elastic/elasticsearch/pull/19937/files), which has been
> available as of 5.0 and 2.4, and the ability to index an IPv6 address
> properly
> (https://www.elastic.co/blog/indexing-ipv6-addresses-in-elasticsearch).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
