From 258e950f17cc5d8ba277470a7a25f3d383e6eabf Mon Sep 17 00:00:00 2001 From: George Wallace Date: Tue, 13 May 2025 22:32:01 -0700 Subject: [PATCH 1/3] Update release-notes-elasticsearch-rc1.asciidoc --- .../release-notes-elasticsearch-rc1.asciidoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc index 7e9f06153..ceef19296 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc @@ -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 skip_unavailable setting for nonmatching indices errors at planning time. +*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 +==== + [discrete] [[deprecated-9.0-rc1]] === Deprecations From 343ffc67c477c3e82c14aeadffa18d6c5d9d66e1 Mon Sep 17 00:00:00 2001 From: George Wallace Date: Wed, 14 May 2025 07:17:44 -0700 Subject: [PATCH 2/3] Update release-notes-elasticsearch-rc1.asciidoc --- .../release-notes/release-notes-elasticsearch-rc1.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc index ceef19296..1a5ba7046 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc @@ -37,9 +37,9 @@ The dropped ciphers are `TLS_RSA_WITH_AES_256_GCM_SHA384`, `TLS_RSA_WITH_AES_128 [%collapsible] ==== *Details* + -Before this change, ES|QL would honor skip_unavailable setting for nonmatching indices errors at planning time. +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 +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] From c7c2d73871eb4d66ce1ba80ac4fdca35962497ea Mon Sep 17 00:00:00 2001 From: George Wallace Date: Wed, 14 May 2025 09:20:48 -0700 Subject: [PATCH 3/3] Update release-notes-elasticsearch-rc1.asciidoc --- .../release-notes/release-notes-elasticsearch-rc1.asciidoc | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc index 1a5ba7046..50b8f4235 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch-rc1.asciidoc @@ -38,6 +38,7 @@ The dropped ciphers are `TLS_RSA_WITH_AES_256_GCM_SHA384`, `TLS_RSA_WITH_AES_128 ==== *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. ====