You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@senssoft.apache.org by "Joshua Poore (JIRA)" <ji...@apache.org> on 2019/03/25 02:14:00 UTC

[jira] [Closed] (SENSSOFT-332) Upgrade to Elastic 6.6

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

Joshua Poore closed SENSSOFT-332.
---------------------------------
    Resolution: Implemented

Updated via Senssoft 332 merge

> Upgrade to Elastic 6.6
> ----------------------
>
>                 Key: SENSSOFT-332
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-332
>             Project: SensSoft
>          Issue Type: New Feature
>          Components: builds
>    Affects Versions: SensSoft 1.0
>            Reporter: Joshua Poore
>            Assignee: Joshua Poore
>            Priority: Major
>             Fix For: SensSoft 1.0
>
>
> Should be an easy upgrade given we're currently running 6.5.4. New features are great!
> [https://www.elastic.co/blog/elastic-stack-6-6-0-released]
> Doesn't appear to be any breaking changes to current configs rel to 6.5.4:
> [https://www.elastic.co/guide/en/logstash/current/breaking-changes.html]
> [https://www.elastic.co/guide/en/elasticsearch/reference/6.7/breaking-changes-6.6.html]
> [https://www.elastic.co/guide/en/kibana/current/release-notes-6.6.0.html#breaking-6.6.0]
> [https://www.elastic.co/guide/en/beats/libbeat/6.6/breaking-changes.html]
>  



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