This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Elasticsearch version 8.16.4 Elasticsearch version 8.16.2 »
Elastic Docs ›Elasticsearch Guide [8.x] ›Release notes

Elasticsearch version 8.16.3

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

Elasticsearch version 8.16.3

edit

Also see Breaking changes in 8.16.

Bug fixes

edit
CCS
  • Resolve/cluster should mark remotes as not connected when a security exception is thrown #119793
Data streams
  • Add missing traces ilm policy for OTel traces data streams #119449
ES|QL
ILM+SLM
  • Add missing timeouts to rest-api-spec ILM APIs #118837
  • Add missing timeouts to rest-api-spec SLM APIs #118958
Ingest Node
  • Add missing timeouts to rest-api-spec ingest APIs #118844
  • Expose BwC enrich cache setting in plugin #119131
  • Fixing GetDatabaseConfigurationAction response serialization #119233
Machine Learning
  • Fix loss of context in the inference API for streaming APIs #118999 (issue: #119000)
  • Fix spike detection for short spikes at the tail of the data #119637
  • Fix timeout ingesting an empty string into a semantic_text field #117840
Search
  • Fix: do not let _resolve/cluster hang if remote is unresponsive #119516
  • Handle exceptions in query phase can match #117469 (issue: #104994)

Enhancements

edit
Authorization
  • Improve handling of nested fields in index reader wrappers #118757
Packaging
  • In this release we’ve introduced an image based on the hardened Wolfi image to provide secure containers to our self-managed customers, help with compliance regulations, and improve our supply chain security posture. #118684

Upgrades

edit
Security
  • Upgrade Bouncy Castle FIPS dependencies #112989

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.4 Elasticsearch version 8.16.2 »