From d2dd1b483564f380d22c24b3c4a5ebc364f6624e Mon Sep 17 00:00:00 2001 From: elasticsearchmachine Date: Tue, 6 May 2025 15:59:52 +0000 Subject: [PATCH 1/5] Forward port release notes for v8.17.6 --- docs/reference/release-notes.asciidoc | 4 + docs/reference/release-notes/8.17.6.asciidoc | 44 ++++++++ .../release-notes/highlights.asciidoc | 101 ++++++++++++++++-- 3 files changed, 143 insertions(+), 6 deletions(-) create mode 100644 docs/reference/release-notes/8.17.6.asciidoc diff --git a/docs/reference/release-notes.asciidoc b/docs/reference/release-notes.asciidoc index 72efd09da5947..3622d65546850 100644 --- a/docs/reference/release-notes.asciidoc +++ b/docs/reference/release-notes.asciidoc @@ -7,7 +7,9 @@ This section summarizes the changes in each release. * <> +* <> * <> +* <> * <> * <> * <> @@ -91,7 +93,9 @@ This section summarizes the changes in each release. -- include::release-notes/8.19.0.asciidoc[] +include::release-notes/8.18.1.asciidoc[] include::release-notes/8.18.0.asciidoc[] +include::release-notes/8.17.6.asciidoc[] include::release-notes/8.17.5.asciidoc[] include::release-notes/8.17.4.asciidoc[] include::release-notes/8.17.3.asciidoc[] diff --git a/docs/reference/release-notes/8.17.6.asciidoc b/docs/reference/release-notes/8.17.6.asciidoc new file mode 100644 index 0000000000000..4682d540c6fa7 --- /dev/null +++ b/docs/reference/release-notes/8.17.6.asciidoc @@ -0,0 +1,44 @@ +[[release-notes-8.17.6]] +== {es} version 8.17.6 + +Also see <>. + +[[bug-8.17.6]] +[float] +=== Bug fixes + +CCS:: +* Cancel expired async search task when a remote returns its results {es-pull}126583[#126583] + +Data streams:: +* [otel-data] Bump plugin version to release _metric_names_hash changes {es-pull}126850[#126850] + +ES|QL:: +* Fix count optimization with pushable union types {es-pull}127225[#127225] (issue: {es-issue}127200[#127200]) + +Infra/Core:: +* Rework uniquify to not use iterators {es-pull}126889[#126889] (issue: {es-issue}126883[#126883]) +* Workaround max name limit imposed by Jackson 2.17 {es-pull}126806[#126806] + +Machine Learning:: +* Adding missing `onFailure` call for Inference API start model request {es-pull}126930[#126930] +* Fix text structure NPE when fields in list have null value {es-pull}125922[#125922] +* Leverage threadpool schedule for inference api to avoid long running thread {es-pull}126858[#126858] (issue: {es-issue}126853[#126853]) + +Ranking:: +* Fix LTR rescorer with model alias {es-pull}126273[#126273] + +Task Management:: +* Fix race condition in `RestCancellableNodeClient` {es-pull}126686[#126686] (issue: {es-issue}88201[#88201]) + +Vector Search:: +* Fix `vec_caps` to test for OS support too (on x64) {es-pull}126911[#126911] (issue: {es-issue}126809[#126809]) + +[[enhancement-8.17.6]] +[float] +=== Enhancements + +Security:: +* Add Issuer to failed SAML Signature validation logs when available {es-pull}126310[#126310] (issue: {es-issue}111022[#111022]) + + diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc index 84af80343b528..615e5c1a4d3d0 100644 --- a/docs/reference/release-notes/highlights.asciidoc +++ b/docs/reference/release-notes/highlights.asciidoc @@ -33,13 +33,102 @@ Other versions: endif::[] -// The notable-highlights tag marks entries that -// should be featured in the Stack Installation and Upgrade Guide: // tag::notable-highlights[] -// [discrete] -// === Heading -// -// Description. + +[discrete] +[[upgrade_repository_s3_to_aws_sdk_v2]] +=== Upgrade `repository-s3` to AWS SDK v2 +In earlier versions of {es} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {es} {minor-version} so we have migrated this plugin to the newer AWS SDK v2. +The two SDKs are not quite compatible, so please check the breaking changes documentation and test the new version thoroughly before upgrading any production workloads. + +{es-pull}126843[#126843] + +[discrete] +[[add_ability_to_redirect_ingestion_failures_on_data_streams_to_failure_store]] +=== Add ability to redirect ingestion failures on data streams to a failure store +Documents that encountered ingest pipeline failures or mapping conflicts +would previously be returned to the client as errors in the bulk and +index operations. Many client applications are not equipped to respond +to these failures. This leads to the failed documents often being +dropped by the client which cannot hold the broken documents +indefinitely. In many end user workloads, these failed documents +represent events that could be critical signals for observability or +security use cases. + +To help mitigate this problem, data streams can now maintain a "failure +store" which is used to accept and hold documents that fail to be +ingested due to preventable configuration errors. The data stream's +failure store operates like a separate set of backing indices with their +own mappings and access patterns that allow Elasticsearch to accept +documents that would otherwise be rejected due to unhandled ingest +pipeline exceptions or mapping conflicts. + +Users can enable redirection of ingest failures to the failure store on +new data streams by specifying it in the new `data_stream_options` field +inside of a component or index template: + +[source,yaml] +---- +PUT _index_template/my-template +{ + "index_patterns": ["logs-test-*"], + "data_stream": {}, + "template": { + "data_stream_options": { + "failure_store": { + "enabled": true + } + } + } +}' +---- + +Existing data streams can be configured with the new data stream +`_options` endpoint: + +[source,yaml] +---- +PUT _data_stream/logs-test-apache/_options +{ + "failure_store": { + "enabled": "true" + } +} +---- + +When redirection is enabled, any ingestion related failures will be +captured in the failure store if the cluster is able to, along with the +timestamp that the failure occurred, details about the error +encountered, and the document that could not be ingested. Since failure +stores are a kind of Elasticsearch index, we can search the data stream +for the failures that it has collected. The failures are not shown by +default as they are stored in different indices than the normal data +stream data. In order to retrieve the failures, we use the `_search` API +along with a new bit of index pattern syntax, the `::` selector. + +[source,yaml] +---- +POST logs-test-apache::failures/_search +---- + +This index syntax informs the search operation to target the indices in +its failure store instead of its backing indices. It can be mixed in a +number of ways with other index patterns to include their failure store +indices in the search operation: + +[source,yaml] +---- +POST logs-*::failures/_search +POST logs-*,logs-*::failures/_search +POST *::failures/_search +POST _query +{ + "query": "FROM my_data_stream*::failures" +} +---- + +{es-pull}126973[#126973] + // end::notable-highlights[] From fbd6288fc657c69fe1d4c6a3a257dcaa6a73d771 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 7 May 2025 11:33:53 +0200 Subject: [PATCH 2/5] delete erroneous highlights update --- .../release-notes/highlights.asciidoc | 94 ------------------- 1 file changed, 94 deletions(-) diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc index 615e5c1a4d3d0..bc083a52df9b8 100644 --- a/docs/reference/release-notes/highlights.asciidoc +++ b/docs/reference/release-notes/highlights.asciidoc @@ -35,100 +35,6 @@ endif::[] // tag::notable-highlights[] -[discrete] -[[upgrade_repository_s3_to_aws_sdk_v2]] -=== Upgrade `repository-s3` to AWS SDK v2 -In earlier versions of {es} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {es} {minor-version} so we have migrated this plugin to the newer AWS SDK v2. -The two SDKs are not quite compatible, so please check the breaking changes documentation and test the new version thoroughly before upgrading any production workloads. - -{es-pull}126843[#126843] - -[discrete] -[[add_ability_to_redirect_ingestion_failures_on_data_streams_to_failure_store]] -=== Add ability to redirect ingestion failures on data streams to a failure store -Documents that encountered ingest pipeline failures or mapping conflicts -would previously be returned to the client as errors in the bulk and -index operations. Many client applications are not equipped to respond -to these failures. This leads to the failed documents often being -dropped by the client which cannot hold the broken documents -indefinitely. In many end user workloads, these failed documents -represent events that could be critical signals for observability or -security use cases. - -To help mitigate this problem, data streams can now maintain a "failure -store" which is used to accept and hold documents that fail to be -ingested due to preventable configuration errors. The data stream's -failure store operates like a separate set of backing indices with their -own mappings and access patterns that allow Elasticsearch to accept -documents that would otherwise be rejected due to unhandled ingest -pipeline exceptions or mapping conflicts. - -Users can enable redirection of ingest failures to the failure store on -new data streams by specifying it in the new `data_stream_options` field -inside of a component or index template: - -[source,yaml] ----- -PUT _index_template/my-template -{ - "index_patterns": ["logs-test-*"], - "data_stream": {}, - "template": { - "data_stream_options": { - "failure_store": { - "enabled": true - } - } - } -}' ----- - -Existing data streams can be configured with the new data stream -`_options` endpoint: - -[source,yaml] ----- -PUT _data_stream/logs-test-apache/_options -{ - "failure_store": { - "enabled": "true" - } -} ----- - -When redirection is enabled, any ingestion related failures will be -captured in the failure store if the cluster is able to, along with the -timestamp that the failure occurred, details about the error -encountered, and the document that could not be ingested. Since failure -stores are a kind of Elasticsearch index, we can search the data stream -for the failures that it has collected. The failures are not shown by -default as they are stored in different indices than the normal data -stream data. In order to retrieve the failures, we use the `_search` API -along with a new bit of index pattern syntax, the `::` selector. - -[source,yaml] ----- -POST logs-test-apache::failures/_search ----- - -This index syntax informs the search operation to target the indices in -its failure store instead of its backing indices. It can be mixed in a -number of ways with other index patterns to include their failure store -indices in the search operation: - -[source,yaml] ----- -POST logs-*::failures/_search -POST logs-*,logs-*::failures/_search -POST *::failures/_search -POST _query -{ - "query": "FROM my_data_stream*::failures" -} ----- - -{es-pull}126973[#126973] - // end::notable-highlights[] From 06d62a8058d7cb726903689e1cf90c0ea7ca0769 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 7 May 2025 11:34:36 +0200 Subject: [PATCH 3/5] restore comments to highlights --- docs/reference/release-notes/highlights.asciidoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc index bc083a52df9b8..2bade69388402 100644 --- a/docs/reference/release-notes/highlights.asciidoc +++ b/docs/reference/release-notes/highlights.asciidoc @@ -35,6 +35,14 @@ endif::[] // tag::notable-highlights[] +// The notable-highlights tag marks entries that +// should be featured in the Stack Installation and Upgrade Guide: +// tag::notable-highlights[] +// [discrete] +// === Heading +// +// Description. + // end::notable-highlights[] From 82beb0d549beeb32552cff170ae9de363758ce1f Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 7 May 2025 11:35:25 +0200 Subject: [PATCH 4/5] Update highlights.asciidoc --- docs/reference/release-notes/highlights.asciidoc | 5 ----- 1 file changed, 5 deletions(-) diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc index 2bade69388402..7a468c4baf405 100644 --- a/docs/reference/release-notes/highlights.asciidoc +++ b/docs/reference/release-notes/highlights.asciidoc @@ -33,8 +33,6 @@ Other versions: endif::[] -// tag::notable-highlights[] - // The notable-highlights tag marks entries that // should be featured in the Stack Installation and Upgrade Guide: // tag::notable-highlights[] @@ -42,7 +40,4 @@ endif::[] // === Heading // // Description. - // end::notable-highlights[] - - From 2b3df50eb9af6ce8b83a8a2c8b7d8a7ed3008211 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 7 May 2025 11:39:34 +0200 Subject: [PATCH 5/5] delete unincluded file --- docs/reference/release-notes.asciidoc | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/reference/release-notes.asciidoc b/docs/reference/release-notes.asciidoc index 3622d65546850..1d12676044604 100644 --- a/docs/reference/release-notes.asciidoc +++ b/docs/reference/release-notes.asciidoc @@ -7,7 +7,6 @@ This section summarizes the changes in each release. * <> -* <> * <> * <> * <> @@ -93,7 +92,6 @@ This section summarizes the changes in each release. -- include::release-notes/8.19.0.asciidoc[] -include::release-notes/8.18.1.asciidoc[] include::release-notes/8.18.0.asciidoc[] include::release-notes/8.17.6.asciidoc[] include::release-notes/8.17.5.asciidoc[]