Skip to content

Update 9.0 rc release notes with esql breaking change #3022

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: 9.0
Choose a base branch
from
+15 −0
Open

Update 9.0 rc release notes with esql breaking change #3022

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
258e950
Update release-notes-elasticsearch-rc1.asciidoc
georgewallace May 14, 2025
343ffc6
Update release-notes-elasticsearch-rc1.asciidoc
georgewallace May 14, 2025
c7c2d73
Update release-notes-elasticsearch-rc1.asciidoc
georgewallace May 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,20 @@ The dropped ciphers are `TLS_RSA_WITH_AES_256_GCM_SHA384`, `TLS_RSA_WITH_AES_128
// TLS::
// * Drop `TLS_RSA` cipher support for JDK 24 {es-pull}123600[#123600]

[discrete]
[[breaking_90_esql_changes]]
==== ES|QL changes

[[limit_scope_skip_unavailable_setting_remote_clusters]]
.Limit the scope of the skip_unavailable setting for remote clusters
[%collapsible]
====
*Details* +
Before this change, ES|QL would honor the skip_unavailable setting for nonmatching indices errors at planning time, meaning that when a query with a concrete (non-wildcarded) index was issued to a cluster where skip_unavailable=true, the index would be skipped, allowing the query to proceed on any other specified clusters rather than returning an error.
*Impact* +
Remote clusters, regardless of their skip_unavailable setting, will now use the same logic as the local cluster for index expression analysis at plan time. As a result, any missing concrete index in your index expression will return an error rather than partial results.
====

[discrete]
[[deprecated-9.0-rc1]]
=== Deprecations
Expand Down