ElasticSearch version compatibility

[dwanedebonocatena]

Hi @verkurkie , is there a limit to which version of ElasticSearch can Timings be used with? I am trying to use it with ES 7.0.1 but on initializing the Timings API I am getting some issues:

timings | (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): [mapper_parsing_exception] Root mapping definition has unsupported parameters ....

timings | (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): [illegal_argument_exception] Setting index.mapper.dynamic was removed after version 6.0.0 ....

timings | [2019-06-02T08:07:40.387Z][error] - Elasticsearch - UTILS - [ERROR] message: [illegal_argument_exception] Rejecting mapping update to [.kibana_1] as the final mapping would have more than 1 type: [_doc, doc] in path [/.kibana/doc/index-pattern%3Acicd-resource*]

[mverkerk-godaddy]

Hey @dwanedebonocatena - i have not tested Timings with ES7+ yet as i have been swamped by another project for quite some time now :-( ... i hope to get back into it again pretty soon and will definitely tests the code on ES7! I know there are a few impacting changes when going 6->7 but shouldn't be too bad ...

[mverkerk-godaddy]

one question: are you upgrading an existing installation of Timings? i.e. you have existing ES/Kibana indices?

[dwanedebonocatena]

I had started in the default Kibana 5.6.2 that is in your docker-compose and up till 6.8.0 all is fine. However, I do not really need to upgrade/reindex the existing data to 7 cos the plan is that I would eventually hook to the company's ELK rather than my own setup, and they have moved to version 7 recently. So I am looking at just starting a fresh index on version 7.

Thanks for getting back to me!

[mverkerk-godaddy]

Got it! I am also planning on first running a fresh copy on ES7 first and make the necessary changes + then work on the upgrade path 5->6->7 to also support that scenario but it will take me a bit of time. Thx for the extra info!

[dwanedebonocatena]

Upgrade path 6>7 might be a bit tricky unless ELK provides some endpoint/functionality to perform it in bulk, because I tried to do it from the UI (when you're on version 6, there is a 7.0 Upgrade Assistant under the Management section) but it will only allow you to reindex one by one. For each index it requires you to tick a box which says that Boolean data in _source might change as fields with values outside of true and false might contain incorrect data after this process.