From 9b5546a7ccfa451282b057d211117ede9da24a4d Mon Sep 17 00:00:00 2001
From: Zach Brisson <162374237+ZachBrisson-Elastic@users.noreply.github.com>
Date: Fri, 6 Dec 2024 09:18:27 -0500
Subject: [PATCH 1/2] Update migrate_8_16.asciidoc to include enrich.cache_size
 breaking change

Heya, due to a bug found in https://github.com/elastic/sdh-elasticsearch/issues/8603 a new breaking change was discovered with the enrich.cache_size setting changed to enrich.cache.size parameter. A Support KB now outlines the issue, https://support.elastic.co/knowledge/4821af0d.

This commit adds an "Ingest changes" to the breaking changes section to outline this new behavior.
---
 docs/reference/migration/migrate_8_16.asciidoc | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/docs/reference/migration/migrate_8_16.asciidoc b/docs/reference/migration/migrate_8_16.asciidoc
index adeb62e343d78..4e38a29fb9d0e 100644
--- a/docs/reference/migration/migrate_8_16.asciidoc
+++ b/docs/reference/migration/migrate_8_16.asciidoc
@@ -134,6 +134,23 @@ renamed it to `data_retention` and added telemetry about the other configuration
 Users that use the field `data_lifecycle.retention` should use the `data_lifecycle.data_retention`
 ====
 
+[discrete]
+[[breaking_816_ingest_changes]]
+==== Ingest changes
+
+[[ingest_enrich.cache_size_schema_change]]
+.Ingest enrich.cache_size schema change
+[%collapsible]
+====
+*Details* +
+Changed `enrich.cache_size` parameter to `enrich.cache.size`. 
+Update the setting to `enrich.cache.size` or remove the setting from your elasticsearch.yml before upgrading.
+
+*Impact* +
+If your cluster has `enrich.cache_size` configured prior to upgrading to 8.16 you may see errors that prevent the upgrade from proceeding. 
+====
+
+
 
 [discrete]
 [[deprecated-8.16]]

From 39e1205fcc0282b424de4c08367eab52acd54b04 Mon Sep 17 00:00:00 2001
From: Niels Bauman <33722607+nielsbauman@users.noreply.github.com>
Date: Mon, 13 Jan 2025 10:53:39 +1000
Subject: [PATCH 2/2] Update docs/reference/migration/migrate_8_16.asciidoc

---
 docs/reference/migration/migrate_8_16.asciidoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/reference/migration/migrate_8_16.asciidoc b/docs/reference/migration/migrate_8_16.asciidoc
index 4e38a29fb9d0e..94c7a714be4b0 100644
--- a/docs/reference/migration/migrate_8_16.asciidoc
+++ b/docs/reference/migration/migrate_8_16.asciidoc
@@ -138,16 +138,16 @@ Users that use the field `data_lifecycle.retention` should use the `data_lifecyc
 [[breaking_816_ingest_changes]]
 ==== Ingest changes
 
-[[ingest_enrich.cache_size_schema_change]]
-.Ingest enrich.cache_size schema change
+[[ingest_enrich.cache_size_name_inconsistency]]
+.Ingest enrich.cache_size name inconsistency
 [%collapsible]
 ====
 *Details* +
-Changed `enrich.cache_size` parameter to `enrich.cache.size`. 
-Update the setting to `enrich.cache.size` or remove the setting from your elasticsearch.yml before upgrading.
+The setting `enrich.cache_size` was temporarily renamed to `enrich.cache.size` in `8.16.0` and `8.16.1`.
+The preferred resolution is upgrading to `8.16.2` or higher. If that is not possible, temporarily rename the setting to `enrich.cache.size` until you are able to upgrade to `8.16.2` or higher. The temporary name is deprecated and will be removed in a future version.
 
 *Impact* +
-If your cluster has `enrich.cache_size` configured prior to upgrading to 8.16 you may see errors that prevent the upgrade from proceeding. 
+If your cluster has `enrich.cache_size` configured prior to upgrading to `8.16.0` or `8.16.1` you may see errors that prevent the upgrade from proceeding. 
 ====