Merge branch 'main' of https://github.com/elastic/elasticsearch into esql-semantinc-reranker-poc

Author: afoucret

.buildkite/pipelines/pull-request/part-4-entitlements.yml

@@ -7,5 +7,5 @@ steps:
     agents:
       provider: gcp
       image: family/elasticsearch-ubuntu-2004
-      machineType: custom-32-98304
+      machineType: n1-standard-32
       buildDirectory: /dev/shm/bk

.buildkite/pipelines/pull-request/part-4-fips.yml

@@ -7,5 +7,5 @@ steps:
     agents:
       provider: gcp
       image: family/elasticsearch-ubuntu-2004
-      machineType: custom-32-98304
+      machineType: n1-standard-32
       buildDirectory: /dev/shm/bk

.buildkite/pipelines/pull-request/part-4.yml

@@ -7,5 +7,5 @@ steps:
     agents:
       provider: gcp
       image: family/elasticsearch-ubuntu-2004
-      machineType: custom-32-98304
+      machineType: n1-standard-32
       buildDirectory: /dev/shm/bk

docs/changelog/117504.yaml

@@ -0,0 +1,6 @@
+pr: 117504
+summary: Fix NPE caused by race condition in async search when minimise round trips
+  is true
+area: Search
+type: bug
+issues: []

docs/changelog/119003.yaml

@@ -0,0 +1,5 @@
+pr: 119003
+summary: Add a `replicate_for` option to the ILM `searchable_snapshot` action
+area: ILM+SLM
+type: enhancement
+issues: []

docs/changelog/120527.yaml

@@ -0,0 +1,6 @@
+pr: 120527
+summary: Implement a `MetricsAware` interface
+area: ES|QL
+type: enhancement
+issues:
+ - 115992

docs/changelog/120813.yaml

@@ -0,0 +1,17 @@
+pr: 120813
+summary: Change Semantic Text To Act Like A Normal Text Field
+area: Search
+type: breaking
+issues: []
+breaking:
+  title: Change Semantic Text To Act Like A Normal Text Field
+  area: Search
+  details:
+    The previous semantic_text format used a complex subfield structure in _source to store the embeddings.
+    This complicated interactions/integrations with semantic_text fields and _source in general.
+    This new semantic_text format treats it as a normal text field, where the field's value in _source is the value assigned by the user.
+  impact:
+    Users who parsed the subfield structure of the previous semantic_text format in _source will need to update their parsing logic.
+    The new format does not directly expose the chunks and embeddings generated from the input text.
+    The new format will be applied to all new indices, any existing indices will continue to use the previous format.
+  notable: true

docs/changelog/120833.yaml

@@ -0,0 +1,5 @@
+pr: 120833
+summary: Optimize `IngestCtxMap` construction
+area: Ingest Node
+type: enhancement
+issues: []

docs/changelog/120959.yaml

@@ -0,0 +1,5 @@
+pr: 120959
+summary: Remove unnecessary entitlement
+area: Infra/Plugins
+type: bug
+issues: []

docs/reference/ilm/actions/ilm-searchable-snapshot.asciidoc

@@ -55,6 +55,13 @@ snapshot retention runs off the index lifecycle management (ILM) policies and is
 (Required, string)
 <<snapshots-register-repository,Repository>> used to store the snapshot.
 
+`replicate_for`::
+(Optional, TimeValue)
+By default, searchable snapshot indices are mounted without replicas. Using this will
+result in a searchable snapshot index being mounted with a single replica for the time period
+specified, after which the replica will be removed. This option is only permitted on the
+first searchable snapshot action of a policy.
+
 `force_merge_index`::
 (Optional, Boolean)
 Force merges the managed index to one segment.
@@ -109,3 +116,44 @@ PUT _ilm/policy/my_policy
   }
 }
 --------------------------------------------------
+
+[[ilm-searchable-snapshot-replicate-for-ex]]
+===== Mount a searchable snapshot with replicas for fourteen days
+
+This policy mounts a searchable snapshot in the hot phase with a
+single replica and maintains that replica for fourteen days. After
+that time has elapsed, the searchable snapshot index will remain (with
+no replicas) for another fourteen days, at which point it will proceed
+into the delete phase and will be deleted.
+
+[source,console]
+--------------------------------------------------
+PUT _ilm/policy/my_policy
+{
+  "policy": {
+    "phases": {
+      "hot": {
+        "actions": {
+          "rollover" : {
+            "max_primary_shard_size": "50gb"
+          },
+          "searchable_snapshot" : {
+            "snapshot_repository" : "backing_repo",
+            "replicate_for": "14d"
+          }
+        }
+      },
+      "delete": {
+        "min_age": "28d",
+        "actions": {
+          "delete" : { }
+        }
+      }
+    }
+  }
+}
+--------------------------------------------------
+
+[NOTE]
+If the `replicate_for` option is specified, its value must be
+less than the minimum age of the next phase in the policy.