Merge branch 'main' into log_testListTasksWaitForCompletion

.ci/jobs.t/elastic+elasticsearch+periodic+concurrent-search-tests.yml

@@ -2,7 +2,8 @@
 - job:
     name: elastic+elasticsearch+%BRANCH%+periodic+concurrent-search-tests
     display-name: "elastic / elasticsearch # %BRANCH% - concurrent search tests"
-    description: "Testing concurrent search enabled for the Elasticsearch %BRANCH% branch.\n"
+    description: "This job has been migrated to Buildkite.\n"
+    disabled: true
     node: "general-purpose && docker"
     builders:
       - inject:

.ci/jobs.t/elastic+elasticsearch+periodic+ear.yml

@@ -2,7 +2,8 @@
 - job:
     name: elastic+elasticsearch+%BRANCH%+periodic+ear
     display-name: "elastic / elasticsearch # %BRANCH% - encryption at rest"
-    description: "The Elasticsearch %BRANCH% branch encryption at rest compatibility tests.\n\n"
+    description: "This job has been migrated to Buildkite.\n"
+    disabled: true
     node: packaging-large
     builders:
       - inject:

.ci/jobs.t/elastic+elasticsearch+periodic+eql-correctness.yml

@@ -3,7 +3,8 @@
     name: elastic+elasticsearch+%BRANCH%+periodic+eql-correctness
     workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+periodic+eql-correctness
     display-name: "elastic / elasticsearch # %BRANCH% - eql correctness tests"
-    description: "Testing of Elasticsearch %BRANCH% EQL.\n"
+    description: "This job has been migrated to Buildkite.\n"
+    disabled: true
     builders:
       - inject:
           properties-file: '.ci/java-versions.properties'

.ci/jobs.t/elastic+elasticsearch+periodic+example-plugins.yml

@@ -3,7 +3,8 @@
     name: elastic+elasticsearch+%BRANCH%+periodic+example-plugins
     workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+periodic+example-plugins
     display-name: "elastic / elasticsearch # %BRANCH% - example plugin tests"
-    description: "Testing of Elasticsearch %BRANCH% example plugins.\n"
+    description: "This job has been migrated to Buildkite.\n"
+    disabled: true
     builders:
       - inject:
           properties-file: '.ci/java-versions.properties'

.ci/jobs.t/elastic+elasticsearch+periodic+release-tests.yml

@@ -4,7 +4,8 @@
     # Don't use ramdisk since this build generates lots of large artifacts and results in oomkiller issues
     # workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+periodic+release-tests
     display-name: "elastic / elasticsearch # %BRANCH% - release tests"
-    description: "Release version tests for the Elasticsearch %BRANCH% branch.\n"
+    description: "This job has been migrated to Buildkite.\n"
+    disabled: true
     node: "general-purpose && docker"
     builders:
       - inject:

.ci/jobs.t/elastic+elasticsearch+periodic+single-processor-node-tests.yml

@@ -2,7 +2,8 @@
 - job:
     name: elastic+elasticsearch+%BRANCH%+periodic+single-processor-node-tests
     display-name: "elastic / elasticsearch # %BRANCH% - single processor node tests"
-    description: "Testing with node.processors set to '1' for the Elasticsearch %BRANCH% branch.\n"
+    description: "This job has been migrated to Buildkite.\n"
+    disabled: true
     node: "general-purpose && docker"
     builders:
       - inject:

.ci/jobs.t/elastic+elasticsearch+periodic+snyk-dependency-monitoring.yml

@@ -3,7 +3,8 @@
     name: elastic+elasticsearch+%BRANCH%+snyk-dependency-monitoring
     workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+snyk-dependency-monitoring
     display-name: "elastic / elasticsearch # %BRANCH% - snyk dependency monitoring"
-    description: "Publishing of the Elasticsearch %BRANCH% dependencies graph to snyk dependency monitoring"
+    description: "This job has been migrated to Buildkite.\n"
+    disabled: true
     builders:
       - inject:
           properties-file: '.ci/java-versions.properties'

benchmarks/src/main/java/org/elasticsearch/benchmark/compute/operator/ValuesSourceReaderBenchmark.java

@@ -19,6 +19,7 @@
 import org.apache.lucene.store.Directory;
 import org.apache.lucene.util.BytesRef;
 import org.apache.lucene.util.NumericUtils;
+import org.elasticsearch.compute.data.BlockFactory;
 import org.elasticsearch.compute.data.BytesRefBlock;
 import org.elasticsearch.compute.data.BytesRefVector;
 import org.elasticsearch.compute.data.DocVector;
@@ -132,6 +133,7 @@ private static BlockLoader numericBlockLoader(String name, NumberFieldMapper.Num
     @OperationsPerInvocation(INDEX_SIZE)
     public void benchmark() {
         ValuesSourceReaderOperator op = new ValuesSourceReaderOperator(
+            BlockFactory.getNonBreakingInstance(),
             List.of(BlockReaderFactories.loaderToFactory(reader, blockLoader(name))),
             0,
             name

distribution/docker/build.gradle

@@ -407,7 +407,7 @@ void addBuildDockerImageTask(Architecture architecture, DockerBase base) {
       if (base == DockerBase.IRON_BANK) {
         Map<String, String> buildArgsMap = [
           'BASE_REGISTRY': 'docker.elastic.co',
-          'BASE_IMAGE'   : 'ubi8/ubi',
+          'BASE_IMAGE'   : 'ubi9/ubi',
           'BASE_TAG'     : 'latest'
         ]
 

distribution/docker/src/docker/Dockerfile

@@ -21,8 +21,8 @@
 
 <% if (docker_base == 'iron_bank') { %>
 ARG BASE_REGISTRY=registry1.dso.mil
-ARG BASE_IMAGE=ironbank/redhat/ubi/ubi8
-ARG BASE_TAG=8.6
+ARG BASE_IMAGE=redhat/ubi/ubi9
+ARG BASE_TAG=9.2
 <% } %>
 
 ################################################################################

distribution/docker/src/docker/iron_bank/hardening_manifest.yaml

@@ -13,8 +13,8 @@ tags:
 
 # Build args passed to Dockerfile ARGs
 args:
-  BASE_IMAGE: "redhat/ubi/ubi8"
-  BASE_TAG: "8.6"
+  BASE_IMAGE: "redhat/ubi/ubi9"
+  BASE_TAG: "9.2"
 
 # Docker image labels
 labels:

docs/changelog/101147.yaml

@@ -0,0 +1,5 @@
+pr: 101147
+summary: Persist data counts on job close before results index refresh
+area: Machine Learning
+type: bug
+issues: []

docs/changelog/101230.yaml

@@ -0,0 +1,12 @@
+pr: 101230
+summary: Enable query phase parallelism within a single shard
+area: Search
+type: enhancement
+issues:
+ - 80693
+highlight:
+  title: Enable query phase parallelism within a single shard
+  body: |-
+    Activate inter-segment search concurrency by default in the query phase, in order to
+    enable parallelizing search execution across segments that a single shard is made of.
+  notable: true

docs/changelog/101346.yaml

@@ -0,0 +1,5 @@
+pr: 101346
+summary: Report full stack trace for non-state file settings transforms
+area: Infra/Settings
+type: bug
+issues: []

docs/changelog/101358.yaml

@@ -0,0 +1,6 @@
+pr: 101358
+summary: Make DISSECT parameter `append_separator` case insensitive
+area: ES|QL
+type: bug
+issues:
+ - 101138

docs/changelog/101383.yaml

@@ -0,0 +1,5 @@
+pr: 101383
+summary: "ESQL: Track memory from values loaded from lucene"
+area: ES|QL
+type: enhancement
+issues: []

docs/changelog/101396.yaml

@@ -0,0 +1,5 @@
+pr: 101396
+summary: "ESQL: Track blocks emitted from lucene"
+area: ES|QL
+type: enhancement
+issues: []

docs/reference/data-streams/data-stream-apis.asciidoc

@@ -15,6 +15,8 @@ The following APIs are available for managing <<data-streams,data streams>>:
 [[data-stream-lifecycle-api]]
 The following APIs are available for managing the built-in lifecycle of data streams:
 
+preview::[]
+
 * <<data-streams-put-lifecycle,Update data stream lifecycle>> 
 preview:[]
 * <<data-streams-get-lifecycle,Get data stream lifecycle>> 

docs/reference/data-streams/lifecycle/apis/delete-lifecycle.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Delete Data Stream Lifecycle</titleabbrev>
 ++++
 
-preview:[]
+preview::[]
 
 Deletes the lifecycle from a set of data streams.
 

docs/reference/data-streams/lifecycle/apis/explain-lifecycle.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Explain Data Stream Lifecycle</titleabbrev>
 ++++
 
-preview:[]
+preview::[]
 
 Retrieves the current data stream lifecycle status for one or more data stream backing indices.
 

docs/reference/data-streams/lifecycle/apis/get-lifecycle.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Get Data Stream Lifecycle</titleabbrev>
 ++++
 
-preview:[]
+preview::[]
 
 Gets the lifecycle of a set of data streams.
 

docs/reference/data-streams/lifecycle/apis/put-lifecycle.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Put Data Stream Lifecycle</titleabbrev>
 ++++
 
-preview:[]
+preview::[]
 
 Configures the data stream lifecycle for the targeted data streams.
 

docs/reference/data-streams/lifecycle/index.asciidoc

@@ -2,7 +2,7 @@
 [[data-stream-lifecycle]]
 == Data stream lifecycle
 
-preview:[]
+preview::[]
 
 A data stream lifecycle is the built-in mechanism data streams use to manage their lifecycle. It enables you to easily
 automate the management of your data streams according to your retention requirements. For example, you could configure

docs/reference/data-streams/lifecycle/tutorial-manage-existing-data-stream.asciidoc

@@ -2,7 +2,7 @@
 [[tutorial-manage-existing-data-stream]]
 === Tutorial: Update existing data stream
 
-preview:[]
+preview::[]
 
 To update the lifecycle of an existing data stream you do the following actions:
 

docs/reference/data-streams/lifecycle/tutorial-manage-new-data-stream.asciidoc

@@ -2,7 +2,7 @@
 [[tutorial-manage-new-data-stream]]
 === Tutorial: Create a data stream with a lifecycle
 
-preview:[]
+preview::[]
 
 To create a data stream with a built-in lifecycle, follow these steps:
 

docs/reference/data-streams/lifecycle/tutorial-migrate-data-stream-from-ilm-to-dsl.asciidoc

@@ -2,7 +2,7 @@
 [[tutorial-migrate-data-stream-from-ilm-to-dsl]]
 === Tutorial: Migrate ILM managed data stream to Data stream lifecycle 
 
-preview:[]
+preview::[]
 
 In this tutorial we'll look at migrating an existing data stream from {ilm-init} to 
 Data stream lifecycle. The existing {ilm-init} managed backing indices will continue 

docs/reference/esql/esql-enrich-data.asciidoc

@@ -1,5 +1,5 @@
 [[esql-enrich-data]]
-== Data enrichment
+=== Data enrichment
 
 ++++
 <titleabbrev>Data enrichment</titleabbrev>
@@ -17,7 +17,7 @@ For example, you can use `ENRICH` to:
 
 [discrete]
 [[esql-how-enrich-works]]
-=== How the `ENRICH` command works
+==== How the `ENRICH` command works
 
 The `ENRICH` command adds new columns to a table, with data from {es} indices.
 It requires a few special components:
@@ -65,7 +65,7 @@ include::../ingest/enrich.asciidoc[tag=enrich-index]
 
 [discrete]
 [[esql-set-up-enrich-policy]]
-=== Set up an enrich policy
+==== Set up an enrich policy
 
 To start using `ENRICH`, follow these steps:
 
@@ -89,25 +89,25 @@ your query.
 
 [discrete]
 [[esql-enrich-prereqs]]
-=== Prerequisites
+==== Prerequisites
 
 include::{es-repo-dir}/ingest/apis/enrich/put-enrich-policy.asciidoc[tag=enrich-policy-api-prereqs]
 
 [discrete]
 [[esql-create-enrich-source-index]]
-=== Add enrich data
+==== Add enrich data
 
 include::../ingest/enrich.asciidoc[tag=create-enrich-source-index]
 
 [discrete]
 [[esql-create-enrich-policy]]
-=== Create an enrich policy
+==== Create an enrich policy
 
 include::../ingest/enrich.asciidoc[tag=create-enrich-policy]
 
 [discrete]
 [[esql-execute-enrich-policy]]
-=== Execute the enrich policy
+==== Execute the enrich policy
 
 include::../ingest/enrich.asciidoc[tag=execute-enrich-policy1]
 
@@ -117,7 +117,7 @@ include::../ingest/enrich.asciidoc[tag=execute-enrich-policy2]
 
 [discrete]
 [[esql-use-enrich]]
-=== Use the enrich policy
+==== Use the enrich policy
 
 After the policy has been executed, you can use the <<esql-enrich,`ENRICH`
 command>> to enrich your data.
@@ -128,12 +128,12 @@ include::processing-commands/enrich.asciidoc[tag=examples]
 
 [discrete]
 [[esql-update-enrich-data]]
-=== Update an enrich index
+==== Update an enrich index
 
 include::{es-repo-dir}/ingest/apis/enrich/execute-enrich-policy.asciidoc[tag=update-enrich-index]
 
 [discrete]
 [[esql-update-enrich-policies]]
-=== Update an enrich policy
+==== Update an enrich policy
 
 include::../ingest/enrich.asciidoc[tag=update-enrich-policy]

docs/reference/esql/esql-examples.asciidoc

@@ -1,5 +1,5 @@
 [[esql-examples]]
-== Examples
+== {esql} examples
 
 ++++
 <titleabbrev>Examples</titleabbrev>