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.15.2 Elasticsearch version 8.15.0 »
Elastic Docs ›Elasticsearch Guide [8.16] ›Release notes

Elasticsearch version 8.15.1

edit

Elasticsearch version 8.15.1

edit

Also see Breaking changes in 8.15.

Known issues

edit
  • Elasticsearch will not start if custom role mappings are configured using the xpack.security.authc.realms.*.files.role_mapping configuration option. As a workaround, custom role mappings can be configured using the REST API (issue: #112503)

  • ES|QL queries can lead to node crashes due to Out Of Memory errors when:

    • Multiple indices match the query pattern
    • These indices have many conflicting field mappings

    • Many of those fields are included in the request These issues deplete heap memory, increasing the likelihood of OOM errors. (issue: #111964, #111358). In Kibana, you might indirectly execute these queries when using Discover, or adding a Field Statistics panel to a dashboard.

      To work around this issue, you have a number of options:

    • Downgrade to an earlier version
    • Upgrade to 8.15.2 upon release
    • Follow the instructions to disable ES|QL queries in Kibana
    • Change the default data view in Discover to a smaller set of indices and/or one with fewer mapping conflicts.

  • Index Stats, Node Stats and Cluster Stats API can return a null pointer exception if an index contains a dense_vector field but there is an index segment that does not contain any documents with a dense vector field (#112720). Workarounds:

    • If the affected index already contains documents with a dense vector field, force merge the index to a single segment.
    • If the affected index does not already contain documents with a dense vector field, index a document with a dense vector field and then force merge to a single segment.
    • If the affected index’s dense_vector fields are unused, reindex without the dense_vector fields.

  • Synthetic source bug. Synthetic source may fail generating the _source at runtime, causing failures in get APIs or partial failures in the search APIs. The result is that for the affected documents the _source can’t be retrieved. There is no workaround and the only option to is to upgrade to 8.15.2 when released.

    If you use synthetic source then you may be affected by this bug if the following is true: If you have more fields then the index.mapping.total_fields.limit setting allows. If you use dynamic mappings and the index.mapping.total_fields.ignore_dynamic_beyond_limit setting is enabled.

Bug fixes

edit
Aggregations
Authorization
ES|QL
  • Avoid losing error message in failure collector #111983 (issue: #111894)
  • Avoid wrapping rejection exception in exchange #112178 (issue: #112106)
  • ESQL: Fix for overzealous validation in case of invalid mapped fields #111475 (issue: #111452)
Geo
  • Add maximum nested depth check to WKT parser #111843
  • Always check crsType when folding spatial functions #112090 (issue: #112089)
  • Fix NPE when executing doc value queries over shape geometries with empty segments #112139
Indices APIs
  • Fix template alias parsing livelock #112217
Infra/Core
Ingest Node
  • Fixing incorrect bulk request took time #111863 (issue: #111854)
  • Improve performance of grok pattern cycle detection #111947
Logs
  • Merge multiple ignored source entires for the same field #111994 (issue: #111694)
Machine Learning
  • [Inference API] Move Delete inference checks to threadpool worker #111646
Mapping
  • Check for valid parentDoc before retrieving its previous #112005 (issue: #111990)
  • Fix calculation of parent offset for ignored source in some cases #112046
  • Fix synthetic source for empty nested objects #111943 (issue: #111811)
  • No error when store_array_source is used without synthetic source #111966
  • Prevent synthetic field loaders accessing stored fields from using stale data #112173 (issue: #112156)
Ranking
  • Properly handle filters on TextSimilarityRank retriever #111673
Relevance
  • Semantic reranking should fail whenever inference ID does not exist #112038 (issue: #111934)
  • [Bugfix] Add accessDeclaredMembers permission to allow search application templates to parse floats #111285
Search
  • Explain Function Score Query #111807
Security
  • Fix "unexpected field [remote_cluster]" for CCS (RCS 1.0) when using API key that references remote_cluster #112226
  • Fix connection timeout for OpenIdConnectAuthenticator get Userinfo #112230
Vector Search
  • Fix NullPointerException when doing knn search on empty index without dims #111756 (issue: #111733)
  • Speed up dense/sparse vector stats #111729 (issue: #111715)
« Elasticsearch version 8.15.2 Elasticsearch version 8.15.0 »