Documentation recommends Elasticsearch 8.14, which is no longer maintained

[paul-hoeller]

The docs state that the minimum required Elasticsearch version is 8.14.x and that 8.14.3 is recommended. However, the 8.14 minor release is no longer maintained. (According to Elastic's EOL policy, for older-than-current major releases, only the latest minor release is maintained. 8 is not current because we have 9, and 8.14 is not 8's latest minor because we have 8.19.)

Does Geonetwork officially support any currently-maintained Elasticsearch versions (as of now: 8.19, 9.1, 9.2)? The table in the docs gives a minimum required version; the latest version that was tested and is known to work would also be useful information.

Related: #6855

[chesselphilippe]

We have the same exact concern with Geonetwork.

We as the GIS team want to implement Geonetwork on premises , but our IT infra and architecture team , for standards, support and security concerns are requiring to use ElasticSearch 9.x.

Is ElasticSearch 9.x supported with Geonetwork 4.4.x

Which version of ElasticSearch will be supported by Geonetwork 5.x : 8x or/and 9.x ?

Thanks

[jodygarnett]

I always check what is supported here:

• https://github.com/geonetwork/core-geonetwork/blob/main/es/docker-compose.yml
• https://github.com/geonetwork/core-geonetwork/blob/main/pom.xml#L1601

And then if I need to update I make a pull request changing the number. The automated builds check if works or not, and then a developer will review.

So in this case I would change from 8.14.3 to 8.19.10:

• Update es.version to 8.19.10 #9175

If it fails it will be due to some incompatibility, but at least a discussion would be started.

[jodygarnett]

@chesselphilippe to answer your question, as an infrastructure project we tend to follow the mosts stable supported branch. And depend on community members (including oursevles) to update when needed.

If you have some technical ability please go ahead with the update in future.

I understand my co-worker @josegar74 is working on it (and found one api change resulting in a compile error). One thing we can both do to help is review the pull-request for @josegar74 allowing it to be merged.

[josegar74]

I have open this draft pull request, with the upgrade to 8.19.11: #9176, any help to do additional testing is really welcome.

I'll check also the feasibility to upgrade to Elasticsearch 9.

[josegar74]

About the upgrade to Elasticsearch 9.x, it requires Java 17 at least. But GeoNetwork 4.4 uses Java 11.

It can be an option to upgrade it in GeoNetwork 5 when that version is released in the future.

[chesselphilippe]

@josegar74 , Thanks a lot for your quick response.

It looks like it is a must have to upgrade/implement ElasticSearch 9.x for the Geonetwork 5.x

In big administration (Geneva City) like ours, for new applications, obsolescence and security is very much prioritized these days , when it comes to validate usage of new framworks.

So ElasticSearch 9.x looks mandatory for Geonetwork 5.x because 8.x is EOL 07.2027.

And OpenJDK 17 is EOL 10.2027 (Temurin) or 09.2029 (Azul Zulu)