Upgrade to ElasticSearch 8.14 client doesn't work with previous versions of Elasticsearch server 8.X or 7.X

[josegar74]

Describe the bug

After the upgrade to Elasticsearch 8.14 client in #8161, the application doesn't work with previous versions of Elasticsearch server 8.X or 7.X as with the previous client version.

Probably needs some update the records.json for the fields definition. But it's unclear yet.

Until this issue is fixed to work fine or reverted the client version to the previous version, 4.4.6 can't be released.

To Reproduce
Steps to reproduce the behavior:

1. Start ElasticSearch 8.13
2. Start GeoNetwork main branch
3. Login as administrator and try to load the sample metadata
4. See error in the application log

Expected behavior
It works fine with previous versions of Elasticsearch server 8.X or 7.X as with the previous client version.

[fxprunayre]

Error is

[2024-09-02T17:45:30,923][INFO ][o.e.c.m.MetadataCreateIndexService] [icho]
 failed on parsing mappings on index creation [sextant-records]
org.elasticsearch.index.mapper.MapperParsingException: Failed to parse mapping: 
No field type matched on [[object]], 
possible values are [object, string, long, double, boolean, date, binary]
	at [email protected]/org.elasticsearch.index.mapper.MapperService.parseMapping(MapperService.java:555)
	at [email protected]/org.elasticsearch.index.mapper.MapperService.doMerge(MapperService.java:517)
	at [email protected]/org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:404)
	at [email protected]/org.elasticsearch.cluster.metadata.MetadataCreateIndexService.updateIndexMappingsAndBuildSortOrder(MetadataCreateIndexService.java:1340)
	at [email protected]/org.elasticsearch.cluster.metadata.MetadataCreateIndexService.lambda$applyCreateIndexWithTemporaryService$2(MetadataCreateIndexService.java:472)

[fxprunayre]

It is related to https://github.com/geonetwork/core-geonetwork/blob/main/web/src/main/webResources/WEB-INF/data/config/index/records.json#L1364

Removing match_mapping_type make index creation to work. Do you remember why we added it ?
Can't find any similar issue and error message is not that much explicit - I don't see why it could be an array of object.

[josegar74]

I don't remember, but it probably matched other types of data in some cases and I added that to force the match.

Indeed it's really bizarre that tries to match an array of objects, have you check with Kibana the content of the field?

[fxprunayre]

I've been testing on large index (28k records) without issue so far. You can give a try on NGR and see if the issue happens?

[josegar74]

I'll do some additional checks locally, thanks.