IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Elasticsearch version 8.16.5 Elasticsearch version 8.16.3 »
Elastic Docs ›Elasticsearch Guide [8.16] ›Release notes

Elasticsearch version 8.16.4

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Elasticsearch version 8.16.4

edit

Also see Breaking changes in 8.16.

Bug fixes

edit
Aggregations
Data streams
  • Map scope.name as a dimension #120590
ES|QL
  • Use field_caps native nested fields filtering #117201 (issue: #117054)
Mapping
  • Fix synthetic source issue with deeply nested ignored source fields #121715
Ranking
  • Fix LTR rescorer throws local model reference is null on multi-shards index when explained is enabled #120717 (issue: #120739)
  • LTR sometines throw NullPointerException: Cannot read field "approximation" because "top" is null #120809
  • Normalize negative scores for text_similarity_reranker retriever #120930 (issue: #120201)
  • Update Text Similarity Reranker to Properly Handle Aliases #120062 (issue: #119617)
Search
  • Fix potential file leak in ES816BinaryQuantizedVectorsWriter #120014 (issue: #119981)
Snapshot/Restore
  • Cheaper snapshot-related toString() impls #121283
  • Issue S3 web identity token refresh call with sufficient permissions #119748 (issue: #119747)

Enhancements

edit
Ingest Node

Known issues

edit
ES|QL
  • The VALUES aggregate function can run for an extremely long time when collecting many groups. Processing hundreds of thousands of groups may take several minutes on a single thread, while processing millions of groups can take days. The function has O(n^2) complexity with respect to the number of groups. During execution, these operations will not respond to the tasks cancellation API. This issue has been fixed by #123073 and the fix is available in versions 8.16.5, 8.17.3, 8.18.0, and all releases after that.
  • Some valid queries using an ENRICH command can fail when a match field is used that is absent from some indices or shards, either with a 500 status code due to NullPointerException or ClassCastException or with a 400 status code and IllegalArgumentException. This is fixed in #126187.
« Elasticsearch version 8.16.5 Elasticsearch version 8.16.3 »