Merge branch 'main' into sp_extension_attributes

Author: tvernum

docs/changelog/127797.yaml

@@ -0,0 +1,6 @@
+pr: 127797
+summary: "Date nanos implicit casting in union types option #2"
+area: ES|QL
+type: enhancement
+issues:
+ - 110009

docs/changelog/128890.yaml

@@ -0,0 +1,5 @@
+pr: 128890
+summary: Improve cache invalidation in IdP SP cache
+area: IdentityProvider
+type: bug
+issues: []

docs/reference/elasticsearch/mapping-reference/aggregate-metric-double.md

@@ -202,11 +202,6 @@ The search returns the following hit. The value of the `default_metric` field, `
 
 ## Synthetic `_source` [aggregate-metric-double-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices (indices that have `index.mode` set to `time_series`). For other indices synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
-
 For example:
 
 $$$synthetic-source-aggregate-metric-double-example$$$

docs/reference/elasticsearch/mapping-reference/binary.md

@@ -47,11 +47,6 @@ The following parameters are accepted by `binary` fields:
 
 ## Synthetic `_source` [binary-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices (indices that have `index.mode` set to `time_series`). For other indices synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
-
 Synthetic source may sort `binary` values in order of their byte representation. For example:
 
 $$$synthetic-source-binary-example$$$

docs/reference/elasticsearch/mapping-reference/boolean.md

@@ -126,11 +126,6 @@ The following parameters are accepted by `boolean` fields:
 
 ## Synthetic `_source` [boolean-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices (indices that have `index.mode` set to `time_series`). For other indices synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
-
 `boolean` fields support [synthetic `_source`](/reference/elasticsearch/mapping-reference/mapping-source-field.md#synthetic-source) in their default configuration.
 
 Synthetic source may sort `boolean` field values. For example:

docs/reference/elasticsearch/mapping-reference/date.md

@@ -186,11 +186,6 @@ Which will reply with a date like:
 
 ## Synthetic `_source` [date-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices (indices that have `index.mode` set to `time_series`). For other indices synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
-
 Synthetic source may sort `date` field values. For example:
 
 $$$synthetic-source-date-example$$$

docs/reference/elasticsearch/mapping-reference/date_nanos.md

@@ -85,11 +85,6 @@ Aggregations are still on millisecond resolution, even when using a `date_nanos`
 
 ## Synthetic `_source` [date-nanos-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices (indices that have `index.mode` set to `time_series`). For other indices synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
-
 Synthetic source may sort `date_nanos` field values. For example:
 
 $$$synthetic-source-date-nanos-example$$$

docs/reference/elasticsearch/mapping-reference/dense-vector.md

@@ -287,11 +287,6 @@ $$$dense-vector-index-options$$$
 
 ## Synthetic `_source` [dense-vector-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices (indices that have `index.mode` set to `time_series`). For other indices synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
-
 `dense_vector` fields support [synthetic `_source`](/reference/elasticsearch/mapping-reference/mapping-source-field.md#synthetic-source) .
 
 

docs/reference/elasticsearch/mapping-reference/flattened.md

@@ -236,11 +236,6 @@ The following mapping parameters are accepted:
 
 ## Synthetic `_source` [flattened-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices (indices that have `index.mode` set to `time_series`). For other indices synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
-::::
-
-
 Flattened fields support [synthetic`_source`](/reference/elasticsearch/mapping-reference/mapping-source-field.md#synthetic-source) in their default configuration.
 
 Synthetic source may sort `flattened` field values and remove duplicates. For example:

docs/reference/elasticsearch/mapping-reference/geo-point.md

@@ -207,16 +207,6 @@ def lon      = doc['location'].lon;
 
 ## Synthetic source [geo-point-synthetic-source]
 
-::::{important}
-Synthetic `_source` is Generally Available only for TSDB indices
-(indices that have `index.mode` set to `time_series`). For other indices
-synthetic `_source` is in technical preview. Features in technical preview may
-be changed or removed in a future release. Elastic will work to fix
-any issues, but features in technical preview are not subject to the support SLA
-of official GA features.
-::::
-
-
 Synthetic source may sort `geo_point` fields (first by latitude and then
 longitude) and reduces them to their stored precision. Additionally, unlike most
 types, arrays of `geo_point` fields will not preserve order if