Hi everyone, Is there any reason for using elasticsearch version=5.6.8 ? Can we use a newer version of elasticsearch? The reason why I am asking is due to permission restrictions in our servers, we have to get the Dockerfile from the docker github repository and update the entrypoint.sh script to build the image. But it seems the Dockerfile for version 5.6.8 is not present in the github.

Internally we're limited to this old version of ES. The code might work as-is with a newer version (e.g. 6.x) so please give it a try and let us know.

Sure Mars. Thank you!

In the last townhall @nutritious-bird-77396 gave a demo that mentioned that the ExpediaGroup had moved to ElasticSearch 7.x, iirc. You two may want to sync up

No..it was not….It was mainly changing some of the incompatibilities introduced by the version upgrade…Notable few are : • Changing

DOC TYPE

as

_doc

instead of doc -> In

MetadataAuditEventsProcessor

and also in Test json’s • Few changes in

ESBrowseDAO

due to deprecated methods like using

BuckerOrder.key

instead of deprecated

Terms.Order.term

• Also changes due to packages being migrated for ex: like

tophits.ParsedTopHits

moved up a level. Overall it wasn’t a huge effort. Let me know if you need more info.

Thanks for getting back. 🙂 So more or less a trial and error to get it to work with ES7. Sounds doable and not too complicated indeed.

I wonder if we can't abstract ES a little and then have two implementations, one for 7.x and 5.x. That way open source builds can use whatever version they want. Probably the easiest way to enable that without breaking LI / other existing users that are using 5.x. I think it'd be really nice if we provided a 7.x option in open source 🙂

Agree. Alternatively we can try to migrate to ES 7.x internally since 5.x is kind of ancient already anyway.

Yeah, it's just more work to do that since we have live services running that would need upgrading. Just updating code in a non breaking way is much easier lol

Hopefully 🙂

Hi @bumpy-keyboard-50565 -- just to check is there further progress in supporting ES 7.x

Sorry not yet. We're trying to migrate to ES 7.x internally but it'd take some time for us to get there. We'd appreciate PRs from the community on this front.