Merge branch 'main' into 2024/04/30/do-not-execute-listeners-when-pro…

…gress-is-updated-to-end

build-tools-internal/src/main/resources/changelog-schema.json

@@ -68,6 +68,7 @@
             "Java High Level REST Client",
             "Java Low Level REST Client",
             "License",
+            "Logs",
             "Machine Learning",
             "Mapping",
             "Monitoring",

docs/changelog/108896.yaml

@@ -0,0 +1,6 @@
+pr: 108896
+summary: Introduce `logs` index mode as Tech Preview
+area: Logs
+type: feature
+issues:
+ - 108896

docs/changelog/109174.yaml

@@ -0,0 +1,5 @@
+pr: 109174
+summary: "ESQL: Change \"substring\" function to not return null on empty string"
+area: ES|QL
+type: bug
+issues: []

docs/changelog/109205.yaml

@@ -0,0 +1,6 @@
+pr: 109205
+summary: "ESQL: Fix `IpPrefix` function not handling correctly `ByteRefs`"
+area: ES|QL
+type: bug
+issues:
+ - 109198

docs/reference/index-modules.asciidoc

@@ -82,6 +82,37 @@ breaking change].
     after segments are merged. Segment merging can be forced using
     <<indices-forcemerge,force merge>>.
 
+[[index-mode-setting]] `index.mode`::
++
+The `index.mode` setting is used to control settings applied in specific domains like ingestion of time series data or logs.
+Different mutually exclusive modes exist, which are used to apply settings or default values controlling indexing of documents,
+sorting and other parameters whose value affects indexing or query performance.
++
+[source,console]
+----------------
+PUT my-index-000001
+{
+  "settings": {
+    "index":{
+      "mode":"standard" <1>
+    }
+  }
+}
+----------------
++
+<1> This index uses the `standard` index mode
++
+Index mode supports the following values:
+
+`null`::: Default value (same as `standard`).
+
+`standard`::: Standard indexing with default settings.
+
+`time_series`::: Index mode optimized for storage of metrics documented in <<tsds-index-settings,TSDS Settings>>.
+
+`logs`::: Index mode optimized for storage of logs. It applies default sort settings on the `hostname` and `timestamp` fields and uses <<synthetic-source,synthetic `_source`>>. <<index-modules-index-sorting,Index sorting>> on different fields is still allowed.
+preview:[]
+
 [[routing-partition-size]] `index.routing_partition_size`::
 
     The number of shards a custom <<mapping-routing-field,routing>> value can go to.

modules/transport-netty4/src/test/java/org/elasticsearch/transport/netty4/SimpleNetty4TransportTests.java

@@ -16,7 +16,6 @@
 import org.elasticsearch.cluster.node.DiscoveryNodeUtils;
 import org.elasticsearch.cluster.node.VersionInformation;
 import org.elasticsearch.common.io.stream.NamedWriteableRegistry;
-import org.elasticsearch.common.network.NetworkService;
 import org.elasticsearch.common.settings.ClusterSettings;
 import org.elasticsearch.common.settings.Settings;
 import org.elasticsearch.common.transport.TransportAddress;
@@ -63,7 +62,7 @@ protected Transport build(Settings settings, TransportVersion version, ClusterSe
             settings,
             version,
             threadPool,
-            new NetworkService(Collections.emptyList()),
+            networkService,
             PageCacheRecycler.NON_RECYCLING_INSTANCE,
             namedWriteableRegistry,
             new NoneCircuitBreakerService(),

muted-tests.yml

@@ -49,9 +49,6 @@ tests:
 - class: "org.elasticsearch.upgrades.SearchStatesIT"
   issue: "https://github.com/elastic/elasticsearch/issues/109190"
   method: "testBWCSearchStates"
-- class: "org.elasticsearch.xpack.esql.CsvTests"
-  issue: "https://github.com/elastic/elasticsearch/issues/109198"
-  method: "test {ip.IpPrefixLengthFromColumn}"
 - class: "org.elasticsearch.xpack.test.rest.XPackRestIT"
   issue: "https://github.com/elastic/elasticsearch/issues/109200"
   method: "test {p0=esql/70_locale/Date format with Italian locale}"