elastic · elasticsearchmachine · Feb 12, 2025
diff --git a/docs/reference/migration/migrate_8_17.asciidoc b/docs/reference/migration/migrate_8_17.asciidoc
@@ -0,0 +1,68 @@
+[[migrating-8.17]]
+== Migrating to 8.17
+++++
+<titleabbrev>8.17</titleabbrev>
+++++
+
+This section discusses the changes that you need to be aware of when migrating
+your application to {es} 8.17.
+
+See also <<release-highlights>> and <<es-release-notes>>.
+
+[discrete]
+[[breaking-changes-8.17]]
+=== Breaking changes
+
+There are no breaking changes in {es} 8.17.
+
+
+[discrete]
+[[deprecated-8.17]]
+=== Deprecations
+
+The following functionality has been deprecated in {es} 8.17
+and will be removed in a future version.
+While this won't have an immediate impact on your applications,
+we strongly encourage you to take the described steps to update your code
+after upgrading to 8.17.
+
+To find out if you are using any deprecated functionality,
+enable <<deprecation-logging, deprecation logging>>.
+
+[discrete]
+[[deprecations_817_mapping]]
+==== Mapping deprecations
+
+[[deprecate_source_mode_in_mappings]]
+.Deprecate `_source.mode` in mappings
+[%collapsible]
+====
+*Details* +
+Configuring `_source.mode` in mappings is deprecated and will be removed in future versions. Use `index.mapping.source.mode` index setting instead.
+
+*Impact* +
+Use `index.mapping.source.mode` index setting instead
+====
+
+[discrete]
+[[deprecations_817_rest_api]]
+==== REST API deprecations
+
+[[format_of_non_detailed_error_responses_changing_in_v9]]
+.The format of non-detailed error responses is changing in v9
+[%collapsible]
+====
+*Details* +
+When an error occurs when processing a request, Elasticsearch returns information on that error in the REST response.
+If `http:detailed_errors.enabled: false` is specified in node settings with the v8 REST API and below,
+the format of this response changes significantly.
+Starting with the v9 REST API, the JSON structure of responses with errors when the `http.detailed_errors.enabled: false` option is set
+will be the same as when detailed errors are enabled (which is the default).
+To keep using the existing format for non-detailed error responses, use the v8 REST API.
+
+*Impact* +
+If you have set `http.detailed_errors.enabled: false` (the default is `true`)
+the structure of JSON when any exceptions occur will change with the v9 REST API.
+To keep using the existing format, use the v8 REST API.
+====
+
diff --git a/docs/reference/release-notes/8.17.2.asciidoc b/docs/reference/release-notes/8.17.2.asciidoc
@@ -0,0 +1,51 @@
+[[release-notes-8.17.2]]
+== {es} version 8.17.2
+
+Also see <<breaking-changes-8.17,Breaking changes in 8.17>>.
+
+[[bug-8.17.2]]
+[float]
+=== Bug fixes
+
+Authentication::
+* Fix NPE on disabled API auth key cache {es-pull}120483[#120483]
+
+Data streams::
+* Map `scope.name` as a dimension {es-pull}120590[#120590]
+
+ES|QL::
+* Use `field_caps` native nested fields filtering {es-pull}117201[#117201] (issue: {es-issue}117054[#117054])
+
+Machine Learning::
+* Fix infer on and elasticsearch service endpoint created with a deployment id {es-pull}121428[#121428]
+* Fix inference update API calls with `task_type` in body or `deployment_id` defined {es-pull}121231[#121231]
+* Skip Usage stats update when ML is disabled {es-pull}121559[#121559] (issue: {es-issue}121532[#121532])
+
+Mapping::
+* Fix synthetic source issue with deeply nested ignored source fields {es-pull}121715[#121715]
+* Lower `_source.mode` mapping attribute deprecation issue level {es-pull}120059[#120059]
+
+Ranking::
+* Fix LTR rescorer throws 'local model reference is null' on multi-shards index when explained is enabled {es-pull}120717[#120717] (issue: {es-issue}120739[#120739])
+* LTR sometines throw `NullPointerException:` Cannot read field "approximation" because "top" is null {es-pull}120809[#120809]
+* Normalize negative scores for `text_similarity_reranker` retriever {es-pull}120930[#120930] (issue: {es-issue}120201[#120201])
+* Update Text Similarity Reranker to Properly Handle Aliases {es-pull}120062[#120062] (issue: {es-issue}119617[#119617])
+
+Search::
+* Add back `keep_alive` to `async_search.submit` rest-api-spec {es-pull}120781[#120781]
+* Fix NPE caused by race condition in async search when minimise round trips is true {es-pull}117504[#117504]
+* Fix potential file leak in ES816BinaryQuantizedVectorsWriter {es-pull}120014[#120014] (issue: {es-issue}119981[#119981])
+* Use approximation to advance matched queries {es-pull}120133[#120133] (issue: {es-issue}120130[#120130])
+
+Snapshot/Restore::
+* Cheaper snapshot-related `toString()` impls {es-pull}121283[#121283]
+* Issue S3 web identity token refresh call with sufficient permissions {es-pull}119748[#119748] (issue: {es-issue}119747[#119747])
+
+[[enhancement-8.17.2]]
+[float]
+=== Enhancements
+
+Ingest Node::
+* Improve memory aspects of enrich cache {es-pull}120256[#120256] (issues: {es-issue}96050[#96050], {es-issue}120021[#120021])
+
+
diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc
@@ -15,13 +15,29 @@ 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]
+[[add_new_experimental_rank_vectors_mapping_for_late_interaction_second_order_ranking]]
+=== Add new experimental `rank_vectors` mapping for late-interaction second order ranking
+Late-interaction models are powerful rerankers. While their size and overall cost doesn't lend itself for HNSW indexing, utilizing them as second order reranking can provide excellent boosts in relevance. The new `rank_vectors` mapping allows for rescoring over new and novel multi-vector late-interaction models like ColBERT or ColPali.
+
+{es-pull}118804[#118804]
+
+[discrete]
+[[enable_lookup_join_in_non_snapshot_builds]]
+=== Enable LOOKUP JOIN in non-snapshot builds
+This effectively releases LOOKUP JOIN into tech preview. Docs will
+follow in a separate PR.
+
+- Enable the lexing/grammar for LOOKUP JOIN in non-snapshot builds.
+- Remove the grammar for the unsupported `| JOIN ...` command (without `LOOKUP` as first keyword). The way the lexer modes work, otherwise we'd also have to enable `| JOIN ...` syntax on non-snapshot builds and would have to add additional validation to provide appropriate error messages.
+- Remove grammar for `LOOKUP JOIN index AS ...` because qualifiers are not yet supported. Otherwise we'd have to put in additional validation as well to prevent such queries.
+
+Also fix https://github.com/elastic/elasticsearch/issues/121185
+
+{es-pull}121193[#121193]
+
 // end::notable-highlights[]