Elasticsearch version 7.9.1edit
Also see Breaking changes in 7.9.
Known issuesedit
-
SQL: If a
WHERE
clause contains at least two relational operators joined byAND
, of which one is a comparison (<=
,<
,>=
,>
) and another one is an inequality (!=
,<>
), both against literals or foldable expressions, the inequality will be ignored. The workaround is to substitute the inequality with aNOT IN
operator.We have fixed this issue in Elasticsearch 7.10.1 and later versions. For more details, see #65488.
New featuresedit
Enhancementsedit
Bug fixesedit
- Authentication
-
- Call ActionListener.onResponse exactly once #61584
- Authorization
-
- Relax the index access control check for scroll searches #61446
- CCR
- Cluster Coordination
- EQL
- Features/Data streams
- Features/ILM+SLM
-
- Fix race in SLM master/cluster state listeners #59801
- Features/Ingest
-
- Fix handling of final pipelines when destination is changed #59522 (issue: #57968)
- Fix wrong pipeline name in debug log #58817 (issue: #58478)
- Fix wrong result when executing bulk requests with and without pipeline #60818 (issue: #60437)
- Update regex file for es user agent node processor #59697 (issue: #59694)
- IdentityProvider
- Machine Learning
-
- Always write prediction_probability and prediction_score for classification inference #60335
- Ensure .ml-config index is updated before clearing anomaly job’s finished_time #61064 (issue: #61157)
- Ensure annotations index mappings are up to date #61107 (issue: #74935)
- Handle node closed exception in ML result processing #60238 (issue: #60130)
- Recover data frame extraction search from latest sort key #61544
- SQL
- Search
- Snapshot/Restore