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.2 Elasticsearch version 8.16.0 »

› ›

Elasticsearch version 8.16.1

edit

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

Elasticsearch version 8.16.1

edit

Also see Breaking changes in 8.16.

Bug fixes

edit

Data streams

Add missing header in put_data_lifecycle rest-api-spec #116292

Mapping

Ignore conflicting fields during dynamic mapping update #114227 (issue: #114228)

Ranking

Propagating nested inner_hits to the parent compound retriever #116408 (issue: #116397)

Relevance

Fix handling of bulk requests with semantic text fields and delete ops #116942

Search

Fix handling of time exceeded exception in fetch phase #116676
Semantic text simple partial update #116478
Validate missing shards after the coordinator rewrite #116382

Vector Search

Update Semantic Query To Handle Zero Size Responses #116277 (issue: #116083)

Enhancements

edit

Data streams

Apm-data: disable date_detection for all apm data streams #116995

Ingest Node

Add postal_code support to the City and Enterprise databases #114193
Add support for registered country fields for maxmind geoip databases #114521
Support IPinfo database configurations #114548
Support more maxmind fields in the geoip processor #114268

Relevance

Add tracking for query rule types #116357

Snapshot/Restore

Improve message about insecure S3 settings #116915
Split searchable snapshot into multiple repo operations #116918

Known issues

edit

ES|QL

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.2 Elasticsearch version 8.16.0 »