elastic · elasticsearchmachine · Jan 22, 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.1.asciidoc b/docs/reference/release-notes/8.17.1.asciidoc
@@ -0,0 +1,77 @@
+[[release-notes-8.17.1]]
+== {es} version 8.17.1
+
+Also see <<breaking-changes-8.17,Breaking changes in 8.17>>.
+
+[[bug-8.17.1]]
+[float]
+=== Bug fixes
+
+Aggregations::
+* Fix moving function linear weighted avg {es-pull}118435[#118435] (issue: {es-issue}113751[#113751])
+
+CCS::
+* Resolve/cluster should mark remotes as not connected when a security exception is thrown {es-pull}119793[#119793]
+
+Data streams::
+* Add missing traces ilm policy for OTel traces data streams {es-pull}119449[#119449]
+
+Downsampling::
+* Handle `index.mapping.ignore_malformed` in downsampling {es-pull}119134[#119134] (issue: {es-issue}119075[#119075])
+* Support flattened field with downsampling {es-pull}118816[#118816] (issue: {es-issue}116319[#116319])
+
+ES|QL::
+* Allow DATE_PARSE to read the timezones {es-pull}118603[#118603] (issue: {es-issue}117680[#117680])
+* Fix ESQL async get while task is being cancelled {es-pull}119897[#119897]
+* Fix RLIKE folding with (unsupported) case insensitive pattern {es-pull}118454[#118454]
+
+ILM+SLM::
+* Add missing timeouts to rest-api-spec ILM APIs {es-pull}118837[#118837]
+* Add missing timeouts to rest-api-spec SLM APIs {es-pull}118958[#118958]
+
+Infra/Node Lifecycle::
+* Add missing timeouts to rest-api-spec shutdown APIs {es-pull}118921[#118921]
+
+Infra/REST API::
+* Add missing parameter to `xpack.info` rest-api-spec {es-pull}118954[#118954]
+
+Ingest Node::
+* Add missing timeouts to rest-api-spec ingest APIs {es-pull}118844[#118844]
+* Expose BwC enrich cache setting in plugin {es-pull}119131[#119131]
+* Fixing `GetDatabaseConfigurationAction` response serialization {es-pull}119233[#119233]
+
+License::
+* Remove unsupported timeout from rest-api-spec license API {es-pull}118919[#118919]
+
+Machine Learning::
+* Fix loss of context in the inference API for streaming APIs {es-pull}118999[#118999] (issue: {es-issue}119000[#119000])
+* Fix spike detection for short spikes at the tail of the data {es-pull}119637[#119637]
+* Fix timeout ingesting an empty string into a `semantic_text` field {es-pull}117840[#117840]
+* [Inference API] Fix bug checking for e5 or reranker default IDs {es-pull}119797[#119797]
+
+Search::
+* ESQL: `connect_transport_exception` should be thrown instead of `verification_exception` when ENRICH-ing if remote is disconnected {es-pull}119750[#119750]
+* Fix: do not let `_resolve/cluster` hang if remote is unresponsive {es-pull}119516[#119516]
+* Handle exceptions in query phase can match {es-pull}117469[#117469] (issue: {es-issue}104994[#104994])
+
+[[enhancement-8.17.1]]
+[float]
+=== Enhancements
+
+Authorization::
+* Improve handling of nested fields in index reader wrappers {es-pull}118757[#118757]
+
+Data streams::
+* Add mapping for `event_name` for OTel logs {es-pull}119495[#119495]
+
+Monitoring::
+* Addition of `tier_preference`, `creation_date` and `version` fields in Elasticsearch monitoring template {es-pull}117851[#117851]
+
+[[feature-8.17.1]]
+[float]
+=== New features
+
+Logs::
+* Make logsdb general available {es-pull}118559[#118559]
+
+
diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc
@@ -10,13 +10,15 @@ For detailed information about this release, see the <<es-release-notes>> and
 
 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]
+
 // end::notable-highlights[]