Elasticsearch version 8.15.1
editElasticsearch version 8.15.1
editAlso 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).
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.
Bug fixes
edit- Aggregations
- Authorization
- ES|QL
- Geo
- Indices APIs
-
- Fix template alias parsing livelock #112217
- Infra/Core
- Ingest Node
- Logs
- 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)
-
Check for valid
- Ranking
-
-
Properly handle filters on
TextSimilarityRank
retriever #111673
-
Properly handle filters on
- Relevance
- Search
-
- Explain Function Score Query #111807
- Security
- Vector Search