[
https://issues.apache.org/jira/browse/METRON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267214#comment-16267214
]
ASF GitHub Bot commented on METRON-939:
---------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/840
@mraliagha I do think we should consider revisiting the field name
conventions, but I'd push for that as a follow-on task. As discussed in other
points on this thread, e.g. going straight to ES 6.x, this PR is already
massive in scope, and adding further non-critical improvements will increase
the surface area of those changes.
Now that we have the meta alerts fixes in master, I strongly encourage the
community to stabilize around as minimal an ES upgrade as possible with
incremental improvements and feature enhancements once we've been able to
convince ourselves through the unit and integration test suites and functional
testing that we're in a healthy and stable place with minimal risk of adding
regressions.
> 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)
