Prune changelogs after 8.17.3 release

docs/changelog/104125.yaml

@@ -1,18 +0,0 @@
-pr: 104125
-summary: Disable machine learning on macOS x86_64
-area: Machine Learning
-type: breaking
-issues: []
-breaking:
-  title: Disable machine learning on macOS x86_64
-  area: Packaging
-  details: The machine learning plugin is permanently disabled on macOS x86_64.
-    For the last three years Apple has been selling hardware based on the arm64
-    architecture, and support will increasingly focus on this architecture in
-    the future. Changes to upstream dependencies of Elastic's machine learning
-    functionality have made it unviable for Elastic to continue to build machine
-    learning on macOS x86_64.
-  impact: To continue to use machine learning functionality on macOS please switch to
-    an arm64 machine (Apple silicon). Alternatively, it will still be possible to run
-    Elasticsearch with machine learning enabled in a Docker container on macOS x86_64.
-  notable: false

docs/changelog/111104.yaml

@@ -1,6 +0,0 @@
-pr: 111104
-summary: "ESQL: Enable async get to support formatting"
-area: ES|QL
-type: feature
-issues:
- - 110926

docs/changelog/111494.yaml

@@ -1,5 +0,0 @@
-pr: 111494
-summary: Extensible Completion Postings Formats
-area: "Suggesters"
-type: enhancement
-issues: []

docs/changelog/111852.yaml

@@ -1,5 +0,0 @@
-pr: 111852
-summary: Add DeBERTa-V2/V3 tokenizer
-area: Machine Learning
-type: enhancement
-issues: []

docs/changelog/112258.yaml

@@ -1,6 +0,0 @@
-pr: 112258
-summary: Updated Date Range to Follow Documentation When Assuming Missing Values
-area: Search
-type: bug
-issues: 
-  - 111484

docs/changelog/112567.yaml

@@ -1,5 +0,0 @@
-pr: 112567
-summary: Track shard snapshot progress during node shutdown
-area: Snapshot/Restore
-type: enhancement
-issues: []

docs/changelog/112834.yaml

@@ -1,5 +0,0 @@
-pr: 112834
-summary: Increase `replica_unassigned_buffer_time` default from 3s to 5s
-area: Health
-type: enhancement
-issues: []

docs/changelog/112903.yaml

@@ -1,17 +0,0 @@
-pr: 112903
-summary: Remove unsupported legacy value for `discovery.type`
-area: Cluster Coordination
-type: breaking
-issues: []
-breaking:
-  title: Remove unsupported legacy value for `discovery.type`
-  area: Cluster and node setting
-  details: >-
-    Earlier versions of {es} had a `discovery.type` setting which permitted
-    values that referred to legacy discovery types. From v9.0.0 onwards, the
-    only supported values for this setting are `multi-node` (the default) and
-    `single-node`.
-  impact: >-
-    Remove any value for `discovery.type` from your `elasticsearch.yml`
-    configuration file except for `multi-node` and `single-node`.
-  notable: false

docs/changelog/113102.yaml

@@ -1,5 +0,0 @@
-pr: 113102
-summary: Trigger merges after recovery
-area: Recovery
-type: enhancement
-issues: []

docs/changelog/113120.yaml

@@ -1,5 +0,0 @@
-pr: 113120
-summary: ESQL - enabling scoring with METADATA `_score`
-area: ES|QL
-type: enhancement
-issues: []

docs/changelog/113131.yaml

@@ -1,10 +0,0 @@
-pr: 113131
-summary: Emit deprecation warning when executing one of the rollup APIs
-area: Rollup
-type: deprecation
-issues: []
-deprecation:
-  title: Emit deprecation warning when executing one of the rollup APIs
-  area: Rollup
-  details: Rollup is already deprecated since 8.11.0 via documentation and since 8.15.0 it is no longer possible to create new rollup jobs in clusters without rollup usage. This change updates the rollup APIs to emit a deprecation warning.
-  impact: Returning a deprecation warning when using one of the rollup APIs.

docs/changelog/113216.yaml

@@ -1,10 +0,0 @@
-pr: 113216
-summary: "[Inference API] Deprecate elser service"
-area: Machine Learning
-type: deprecation
-issues: []
-deprecation:
-  title: "[Inference API] Deprecate elser service"
-  area: REST API
-  details: The `elser` service of the inference API will be removed in an upcoming release. Please use the elasticsearch service instead. 
-  impact: In the current version there is no impact. In a future version, users of the `elser` service will no longer be able to use it, and will be required to use the `elasticsearch` service to access elser through the inference API.

docs/changelog/113237.yaml

@@ -1,5 +0,0 @@
-pr: 113237
-summary: Retry throttled snapshot deletions
-area: Snapshot/Restore
-type: bug
-issues: []

docs/changelog/113413.yaml

@@ -1,6 +0,0 @@
-pr: 113413
-summary: Fixed a `NullPointerException` in `_capabilities` API when the `path` parameter is null.
-area: Infra/REST API
-type: bug
-issues:
-  - 113413

docs/changelog/113425.yaml

@@ -1,5 +0,0 @@
-pr: 113425
-summary: Add `ensureGreen` test method for use with `adminClient`
-area: Infra/Metrics
-type: enhancement
-issues: []

docs/changelog/113462.yaml

@@ -1,5 +0,0 @@
-pr: 113462
-summary: Suppress merge-on-recovery for older indices
-area: CRUD
-type: enhancement
-issues: []

docs/changelog/113482.yaml

@@ -1,27 +0,0 @@
-pr: 113482
-summary: The 'persian' analyzer has stemmer by default
-area: Analysis
-type: breaking
-issues:
-- 113050
-breaking:
-  title: The 'persian' analyzer has stemmer by default
-  area: Analysis
-  details: >-
-    Lucene 10 has added a final stemming step to its PersianAnalyzer that Elasticsearch
-    exposes as 'persian' analyzer. Existing indices will keep the old
-    non-stemming behaviour while new indices will see the updated behaviour with
-    added stemming.
-    Users that wish to maintain the non-stemming behaviour need to define their
-    own analyzer as outlined in
-    https://www.elastic.co/guide/en/elasticsearch/reference/8.15/analysis-lang-analyzer.html#persian-analyzer.
-    Users that wish to use the new stemming behaviour for existing indices will
-    have to reindex their data.
-  impact: >-
-    Indexing with the 'persian' analyzer will produce slightly different tokens.
-    Users should check if this impacts their search results. If they wish to
-    maintain the legacy non-stemming behaviour they can define their own
-    analyzer equivalent as explained in
-    https://www.elastic.co/guide/en/elasticsearch/reference/8.15/analysis-lang-analyzer.html#persian-analyzer.
-  notable: false
-

docs/changelog/113561.yaml

@@ -1,5 +0,0 @@
-pr: 113561
-summary: Add link to Circuit Breaker "Data too large" exception message
-area: Infra/Circuit Breakers
-type: enhancement
-issues: []

docs/changelog/113614.yaml

@@ -1,18 +0,0 @@
-pr: 113614
-summary: The 'german2' stemmer is now an alias for the 'german' snowball stemmer
-area: Analysis
-type: breaking
-issues: []
-breaking:
-  title: The "german2" snowball stemmer is now an alias for the "german" stemmer
-  area: Analysis
-  details: >-
-    Lucene 10 has merged the improved "german2" snowball language stemmer with the
-    "german" stemmer. For Elasticsearch, "german2" is now a deprecated alias for
-    "german". This may results in slightly different tokens being generated for
-    terms with umlaut substitution (like "ue" for "ü" etc...)
-  impact: >-
-    Replace usages of "german2" with "german" in analysis configuration. Old
-    indices that use the "german" stemmer should be reindexed if possible.
-  notable: false
-

docs/changelog/113827.yaml

@@ -1,5 +0,0 @@
-pr: 113827
-summary: Add Optional Source Filtering to Source Loaders
-area: Mapping
-type: enhancement
-issues: []

docs/changelog/114002.yaml

@@ -1,5 +0,0 @@
-pr: 114002
-summary: Add a `mustache.max_output_size_bytes` setting to limit the length of results from mustache scripts
-area: Infra/Scripting
-type: enhancement
-issues: []

docs/changelog/114124.yaml

@@ -1,18 +0,0 @@
-pr: 114124
-summary: The Korean dictionary for Nori has been updated 
-area: Analysis
-type: breaking
-issues: []
-breaking:
-  title: The Korean dictionary for Nori has been updated
-  area: Analysis
-  details: >-
-    Lucene 10 ships with an updated Korean dictionary (mecab-ko-dic-2.1.1). 
-    For details see https://github.com/apache/lucene/issues/11452. Users
-    experiencing changes in search behaviour on existing data are advised to
-    reindex.
-  impact: >-
-    The change is small and should generally provide better analysis results.
-    Existing indices for full-text use cases should be reindexed though.
-  notable: false
-

docs/changelog/114146.yaml

@@ -1,20 +0,0 @@
-pr: 114146 
-summary: Snowball stemmers have been upgraded 
-area: Analysis
-type: breaking
-issues: []
-breaking:
-  title: Snowball stemmers have been upgraded
-  area: Analysis
-  details: >-
-    Lucene 10 ships with an upgrade of its Snowball stemmers. 
-    For details see https://github.com/apache/lucene/issues/13209. Users using
-    Snowball stemmers that are experiencing changes in search behaviour on 
-    existing data are advised to reindex.
-  impact: >-
-    The upgrade should generally provide improved stemming results. Small changes
-    in token analysis can lead to mismatches with previously index data, so
-    existing indices using Snowball stemmers as part of their analysis chain
-    should be reindexed.
-  notable: false
-

docs/changelog/114177.yaml

@@ -1,5 +0,0 @@
-pr: 114177
-summary: "Make `randomInstantBetween` always return value in range [minInstant, `maxInstant]`"
-area: Infra/Metrics
-type: bug
-issues: []

docs/changelog/114202.yaml

@@ -1,14 +0,0 @@
-pr: 114202
-summary: Remove deprecated `xpack.searchable.snapshot.allocate_on_rolling_restart` setting
-area: Snapshot/Restore
-type: breaking
-issues: []
-breaking:
-  title: Remove deprecated `xpack.searchable.snapshot.allocate_on_rolling_restart` setting
-  area: 'Cluster and node setting'
-  details: >-
-    The `xpack.searchable.snapshot.allocate_on_rolling_restart` setting was created as an escape-hatch just in case
-    relying on the `cluster.routing.allocation.enable=primaries` setting for allocating searchable snapshots during
-    rolling restarts had some unintended side-effects. It has been deprecated since 8.2.0.
-  impact: Remove `xpack.searchable.snapshot.allocate_on_rolling_restart` from your settings if present.
-  notable: false

docs/changelog/114207.yaml

@@ -1,15 +0,0 @@
-pr: 114207
-summary: Remove `cluster.routing.allocation.disk.watermark.enable_for_single_data_node` setting
-area: Allocation
-type: breaking
-issues: []
-breaking:
-  title: Remove `cluster.routing.allocation.disk.watermark.enable_for_single_data_node` setting
-  area: 'Cluster and node setting'
-  details: >-
-    Prior to 7.8, whenever a cluster had only a single data node, the watermarks would not be respected.
-    In order to change this in 7.8+ in a backwards compatible way, we introduced the 
-    `cluster.routing.allocation.disk.watermark.enable_for_single_data_node`
-    node setting. The setting was deprecated in 7.14 and was made to accept only true in 8.0
-  impact: No known end user impact
-  notable: false

docs/changelog/114231.yaml

@@ -1,17 +0,0 @@
-pr: 114231
-summary: Remove cluster state from `/_cluster/reroute` response
-area: Allocation
-type: breaking
-issues:
- - 88978
-breaking:
-  title: Remove cluster state from `/_cluster/reroute` response
-  area: REST API
-  details: >-
-    The `POST /_cluster/reroute` API no longer returns the cluster state in its
-    response. The `?metric` query parameter to this API now has no effect and
-    its use will be forbidden in a future version.
-  impact: >-
-    Cease usage of the `?metric` query parameter when calling the
-    `POST /_cluster/reroute` API.
-  notable: false

docs/changelog/114303.yaml

@@ -1,6 +0,0 @@
-pr: 114303
-summary: Fix TDigestState.read CB leaks
-area: ES|QL
-type: bug
-issues:
- - 114194

docs/changelog/114317.yaml

@@ -1,5 +0,0 @@
-pr: 114317
-summary: "ESQL: CATEGORIZE as a `BlockHash`"
-area: ES|QL
-type: enhancement
-issues: []

docs/changelog/114445.yaml

@@ -1,6 +0,0 @@
-pr: 114445
-summary: Wrap jackson exception on malformed json string
-area: Infra/Core
-type: bug
-issues:
- - 114142

docs/changelog/114566.yaml

@@ -1,5 +0,0 @@
-pr: 114566
-summary: Use Azure blob batch API to delete blobs in batches
-area: Distributed
-type: enhancement
-issues: []

docs/changelog/114618.yaml

@@ -1,5 +0,0 @@
-pr: 114618
-summary: Add a new index setting to skip recovery source when synthetic source is enabled
-area: Logs
-type: enhancement
-issues: []

docs/changelog/114623.yaml

@@ -1,5 +0,0 @@
-pr: 114623
-summary: Preserve thread context when waiting for segment generation in RTG
-area: CRUD
-type: bug
-issues: []

docs/changelog/114741.yaml

@@ -1,5 +0,0 @@
-pr: 114741
-summary: Upgrade to Lucene 10
-area: Search
-type: upgrade
-issues: []

docs/changelog/114813.yaml

@@ -1,5 +0,0 @@
-pr: 114813
-summary: Retry `S3BlobContainer#getRegister` on all exceptions
-area: Snapshot/Restore
-type: enhancement
-issues: []

docs/changelog/114837.yaml

@@ -1,5 +0,0 @@
-pr: 114837
-summary: Add warning headers for ingest pipelines containing special characters
-area: Ingest Node
-type: bug
-issues: [ 104411 ]

docs/changelog/114879.yaml

@@ -1,5 +0,0 @@
-pr: 114879
-summary: Add refresh `.security` index call between security migrations
-area: Security
-type: enhancement
-issues: []

docs/changelog/114914.yaml

@@ -1,5 +0,0 @@
-pr: 114914
-summary: Adding chunking settings to `IbmWatsonxService`
-area: Machine Learning
-type: enhancement
-issues: []

docs/changelog/115020.yaml

@@ -1,5 +0,0 @@
-pr: 115020
-summary: Adding endpoint creation validation for all task types to remaining services
-area: Machine Learning
-type: enhancement
-issues: []

docs/changelog/115241.yaml

@@ -1,6 +0,0 @@
-pr: 115241
-summary: "[Security Solution] Add `create_index` to `kibana_system` role for index/DS\
-  \ `.logs-endpoint.action.responses-*`"
-area: Authorization
-type: enhancement
-issues: []

docs/changelog/115314.yaml

@@ -1,5 +0,0 @@
-pr: 115314
-summary: Only aggregations require at least one shard request
-area: Search
-type: enhancement
-issues: []

docs/changelog/115383.yaml

@@ -1,5 +0,0 @@
-pr: 115383
-summary: Only publish desired balance gauges on master
-area: Allocation
-type: enhancement
-issues: []

docs/changelog/115393.yaml

@@ -1,18 +0,0 @@
-pr: 115393
-summary: Remove deprecated local attribute from alias APIs
-area: Indices APIs
-type: breaking
-issues: []
-breaking:
-  title: Remove deprecated local attribute from alias APIs
-  area: REST API
-  details: >-
-    The following APIs no longer accept the `?local` query parameter:
-    `GET /_alias`, `GET /_aliases`, `GET /_alias/{name}`,
-    `HEAD /_alias/{name}`, `GET /{index}/_alias`, `HEAD /{index}/_alias`,
-    `GET /{index}/_alias/{name}`, `HEAD /{index}/_alias/{name}`,
-    `GET /_cat/aliases`, and `GET /_cat/aliases/{alias}`. This parameter
-    has been deprecated and ignored since version 8.12.
-  impact: >-
-    Cease usage of the `?local` query parameter when calling the listed APIs.
-  notable: false

docs/changelog/115616.yaml

@@ -1,6 +0,0 @@
-pr: 115616
-summary: Fix double lookup failure on ESQL
-area: ES|QL
-type: bug
-issues:
-  - 111398

docs/changelog/115721.yaml

@@ -1,5 +0,0 @@
-pr: 115721
-summary: Change Reindexing metrics unit from millis to seconds
-area: Reindex
-type: enhancement
-issues: []

docs/changelog/115779.yaml

@@ -1,6 +0,0 @@
-pr: 115779
-summary: Don't allow secure settings in YML config (109115)
-area: Infra/Settings
-type: bug
-issues:
- - 109115

docs/changelog/115831.yaml

@@ -1,13 +0,0 @@
-pr: 115831
-summary: Increase minimum threshold in shard balancer
-area: Allocation
-type: breaking
-issues: []
-breaking:
-  title: Minimum shard balancer threshold is now 1.0
-  area: Cluster and node setting
-  details: >-
-    Earlier versions of {es} accepted any non-negative value for `cluster.routing.allocation.balance.threshold`, but values smaller than
-    `1.0` do not make sense and have been ignored since version 8.6.1. From 9.0.0 these nonsensical values are now forbidden.
-  impact: Do not set `cluster.routing.allocation.balance.threshold` to a value less than `1.0`.
-  notable: false

docs/changelog/115836.yaml

@@ -1,5 +0,0 @@
-pr: 115836
-summary: Catch and handle disconnect exceptions in search
-area: Search
-type: bug
-issues: []

docs/changelog/115876.yaml

@@ -1,5 +0,0 @@
-pr: 115876
-summary: Inference duration and error metrics
-area: Machine Learning
-type: enhancement
-issues: []

docs/changelog/115923.yaml

@@ -1,16 +0,0 @@
-pr: 115923
-summary: Apply more strict parsing of actions in bulk API
-area: Indices APIs
-type: breaking
-issues: [ ]
-breaking:
-  title: Apply more strict parsing of actions in bulk API
-  area: REST API
-  details: >-
-    Previously, the following classes of malformed input were deprecated but not rejected in the action lines of the a
-    bulk request: missing closing brace; additional keys after the action (which were ignored); additional data after
-    the closing brace (which was ignored). They will now be considered errors and rejected.
-  impact: >-
-    Users must provide well-formed input when using the bulk API. (They can request REST API compatibility with v8 to
-    get the previous behaviour back as an interim measure.)
-  notable: false

docs/changelog/115930.yaml

@@ -1,5 +0,0 @@
-pr: 115930
-summary:  Inconsistency in the _analyzer api when the index is not included 
-area: Search
-type: bug
-issues: []

docs/changelog/115938.yaml

@@ -1,9 +0,0 @@
-pr: 115938
-summary: Wait for up to 2 seconds for yellow status before starting search
-area: Machine Learning
-type: bug
-issues:
- - 107777
- - 105955
- - 107815
- - 112191

docs/changelog/116026.yaml

@@ -1,13 +0,0 @@
-pr: 116026
-summary: Change Elasticsearch timeouts to 429 response instead of 5xx
-area: Infra/Core
-type: breaking
-issues: []
-breaking:
-  title: Change most Elasticsearch timeouts to 429 response instead of 5xx
-  area: REST API
-  details: When a timeout occurs in most REST requests, whether via a per-request timeout, or a system default, the
-    request would return a 5xx response code. The response code from those APIs when a timeout occurs is now 429.
-  impact: Adjust any code relying on retrying on 5xx responses for timeouts to look for a 429 response code and
-    inspect the response to determine whether a timeout occured.
-  notable: false

docs/changelog/116043.yaml

@@ -1,6 +0,0 @@
-pr: 116043
-summary: Support partial sort fields in TopN pushdown
-area: ES|QL
-type: enhancement
-issues:
- - 114515

docs/changelog/116060.yaml

@@ -1,6 +0,0 @@
-pr: 116060
-summary: Fix leak in `DfsQueryPhase` and introduce search disconnect stress test
-area: Search
-type: bug
-issues:
- - 115056

docs/changelog/116077.yaml

@@ -1,14 +0,0 @@
-pr: 116077
-summary: Remove `ecs` option on `user_agent` processor
-area: Ingest Node
-type: breaking
-issues: []
-breaking:
-  title: Remove `ecs` option on `user_agent` processor
-  area: Ingest
-  details: >-
-    The `user_agent` ingest processor no longer accepts the `ecs` option. (It was previously deprecated and ignored.)
-  impact: >-
-    Users should stop using the `ecs` option when creating instances of the `user_agent` ingest processor.
-    The option will be removed from existing processors stored in the cluster state on upgrade.
-  notable: false

docs/changelog/116112.yaml

@@ -1,13 +0,0 @@
-pr: 116112
-summary: Remove ignored fallback option on GeoIP processor
-area: Ingest Node
-type: breaking
-issues: []
-breaking:
-  title: Remove ignored fallback option on GeoIP processor
-  area: Ingest
-  details: >-
-    The option fallback_to_default_databases on the geoip ingest processor has been removed.
-    (It was deprecated and ignored since 8.0.0.)
-  impact: Customers should stop remove the noop fallback_to_default_databases option on any geoip ingest processors.
-  notable: false

docs/changelog/116115.yaml

@@ -1,5 +0,0 @@
-pr: 116115
-summary: Allow http unsafe buffers by default
-area: Network
-type: enhancement
-issues: []

docs/changelog/116174.yaml

@@ -1,7 +0,0 @@
-pr: 116174
-summary: Handle with `illegalArgumentExceptions` negative values in HDR percentile
-  aggregations
-area: Aggregations
-type: bug
-issues:
- - 115777

docs/changelog/116259.yaml

@@ -1,14 +0,0 @@
-pr: 116259
-summary: Fix `_type` deprecation on simulate pipeline API
-area: Ingest Node
-type: deprecation
-issues: []
-deprecation:
-  title: Document `_type` deprecated on simulate pipeline API
-  area: REST API
-  details: >-
-    Passing a document with a `_type` property is deprecated in the `/_ingest/pipeline/{id}/_simulate` and
-    `/_ingest/pipeline/_simulate` APIs.
-  impact: >-
-    Users should already have stopped using mapping types, which were deprecated in {es} 7. This deprecation warning
-    will fire if they specify mapping types on documents pass to the simulate pipeline API.

docs/changelog/116388.yaml

@@ -1,5 +0,0 @@
-pr: 116388
-summary: Add support for partial shard results
-area: EQL
-type: enhancement
-issues: []

docs/changelog/116531.yaml

@@ -1,5 +0,0 @@
-pr: 116531
-summary: "Add a standard deviation aggregating function: STD_DEV"
-area: ES|QL
-type: enhancement
-issues: []

docs/changelog/116663.yaml

@@ -1,5 +0,0 @@
-pr: 116663
-summary: KNN vector rescoring for quantized vectors
-area: Vector Search
-type: feature
-issues: []

docs/changelog/116687.yaml

@@ -1,5 +0,0 @@
-pr: 116687
-summary: Add LogsDB option to route on sort fields
-area: Logs
-type: enhancement
-issues: []

docs/changelog/116692.yaml

@@ -1,5 +0,0 @@
-pr: 116692
-summary: Remove all mentions of eis and gateway and deprecate flags that do
-area: Machine Learning
-type: enhancement
-issues: []

docs/changelog/116739.yaml

@@ -1,5 +0,0 @@
-pr: 116739
-summary: Change default Docker image to be based on UBI minimal instead of Ubuntu
-area: Infra/Core
-type: enhancement
-issues: []

docs/changelog/116755.yaml

@@ -1,5 +0,0 @@
-pr: 116755
-summary: Smarter field caps with subscribable listener
-area: ES|QL
-type: enhancement
-issues: []

docs/changelog/116765.yaml

@@ -1,5 +0,0 @@
-pr: 116765
-summary: Metrics for incremental bulk splits
-area: Distributed
-type: enhancement
-issues: []

docs/changelog/116868.yaml

@@ -1,5 +0,0 @@
-pr: 116868
-summary: Run `TransportGetComponentTemplateAction` on local node
-area: Indices APIs
-type: enhancement
-issues: []

docs/changelog/116904.yaml

@@ -1,5 +0,0 @@
-pr: 116904
-summary: Add a not-master state for desired balance
-area: Allocation
-type: enhancement
-issues: []

docs/changelog/116922.yaml

@@ -1,5 +0,0 @@
-pr: 116922
-summary: Always check if index mode is logsdb
-area: Logs
-type: bug
-issues: []

docs/changelog/116943.yaml

@@ -1,11 +0,0 @@
-pr: 116943
-summary: Remove support for deprecated `force_source` highlighting parameter
-area: Highlighting
-type: breaking
-issues: []
-breaking:
-  title: Remove support for deprecated `force_source` highlighting parameter
-  area: REST API
-  details: The deprecated highlighting `force_source` parameter is no longer supported.
-  impact: Users should remove usages of the `force_source` parameter from their search requests.
-  notable: false

docs/changelog/116964.yaml

@@ -1,6 +0,0 @@
-pr: 116964
-summary: "Support ST_ENVELOPE and related (ST_XMIN, ST_XMAX, ST_YMIN, ST_YMAX) functions"
-area: ES|QL
-type: feature
-issues:
- - 104875

docs/changelog/116970.yaml

@@ -1,11 +0,0 @@
-pr: 116970
-summary: Remove legacy params from range query
-area: Search
-type: breaking
-issues: []
-breaking:
-  title: Remove legacy params from range query
-  area: REST API
-  details: The deprecated range query parameters `to`, `from`, `include_lower`, and `include_upper` are no longer supported.
-  impact: Users should use `lt`, `lte`, `gt`, and `gte` query parameters instead.
-  notable: false

docs/changelog/116996.yaml

@@ -1,5 +0,0 @@
-pr: 116996
-summary: Initial work on `ReindexDatastreamIndexAction`
-area: Data streams
-type: enhancement
-issues: []

docs/changelog/117095.yaml

@@ -1,5 +0,0 @@
-pr: 117095
-summary: Add version prefix to Inference Service API path
-area: Inference
-type: enhancement
-issues: []

docs/changelog/117148.yaml

@@ -1,5 +0,0 @@
-pr: 117148
-summary: Preserve thread context when waiting for segment generation in RTG
-area: CRUD
-type: bug
-issues: []

docs/changelog/117176.yaml

@@ -1,5 +0,0 @@
-pr: 117176
-summary: Integrate IBM watsonx to Inference API for re-ranking task
-area: Experiences
-type: enhancement
-issues: []

docs/changelog/117199.yaml

@@ -1,5 +0,0 @@
-pr: 117199
-summary: Speed up bit compared with floats or bytes script operations
-area: Vector Search
-type: enhancement
-issues: []

docs/changelog/117214.yaml

@@ -1,5 +0,0 @@
-pr: 117214
-summary: Returning ignored fields in the simulate ingest API
-area: Ingest Node
-type: enhancement
-issues: []

docs/changelog/117229.yaml

@@ -1,6 +0,0 @@
-pr: 117229
-summary: "In this pr, a 400 error is returned when _source / _seq_no / _feature /\
-  \ _nested_path / _field_names is requested, rather a 5xx"
-area: Search
-type: bug
-issues: []

docs/changelog/117230.yaml

@@ -1,5 +0,0 @@
-pr: 117230
-summary: Make various alias retrieval APIs wait for cluster to unblock
-area: Distributed
-type: enhancement
-issues: []

docs/changelog/117243.yaml

@@ -1,5 +0,0 @@
-pr: 117243
-summary: Bump major version for feature migration system indices
-area: Infra/Core
-type: upgrade
-issues: []

docs/changelog/117246.yaml

@@ -1,5 +0,0 @@
-pr: 117246
-summary: LOOKUP JOIN using field-caps for field mapping
-area: ES|QL
-type: enhancement
-issues: []

docs/changelog/117265.yaml

@@ -1,5 +0,0 @@
-pr: 117265
-summary: Async search responses have CCS metadata while searches are running
-area: ES|QL
-type: enhancement
-issues: []

docs/changelog/117287.yaml

@@ -1,5 +0,0 @@
-pr: 117287
-summary: Fixing bug setting index when parsing Google Vertex AI results
-area: Machine Learning
-type: bug
-issues: []

docs/changelog/117303.yaml

@@ -1,5 +0,0 @@
-pr: 117303
-summary: Remove HTTP content copies
-area: Network
-type: enhancement
-issues: []

docs/changelog/117359.yaml

@@ -1,5 +0,0 @@
-pr: 117359
-summary: Term query for ES|QL
-area: ES|QL
-type: enhancement
-issues: []

docs/changelog/117451.yaml

@@ -1,6 +0,0 @@
-pr: 117451
-summary: ST_EXTENT aggregation
-area: ES|QL
-type: feature
-issues:
- - 104659

docs/changelog/117519.yaml

@@ -1,20 +0,0 @@
-pr: 117519
-summary: Remove `data_frame_transforms` roles
-area: Transform
-type: breaking
-issues: []
-breaking:
-  title: Remove `data_frame_transforms` roles
-  area: Transform
-  details: >-
-    `data_frame_transforms_admin` and `data_frame_transforms_user` were deprecated in
-    Elasticsearch 7 and are being removed in Elasticsearch 9.
-    `data_frame_transforms_admin` is now `transform_admin`.
-    `data_frame_transforms_user` is now `transform_user`.
-    Users must call the `_update` API to replace the permissions on the Transform before the
-    Transform can be started.
-  impact: >-
-    Transforms created with either the `data_frame_transforms_admin` or the
-    `data_frame_transforms_user` role will fail to start. The Transform will remain
-    in a `stopped` state, and its health will be red while displaying permission failures.
-  notable: false

docs/changelog/117530.yaml

@@ -1,6 +0,0 @@
-pr: 117530
-summary: Expose operation and request counts separately in repository stats
-area: Snapshot/Restore
-type: enhancement
-issues:
- - 104443

docs/changelog/117555.yaml

@@ -1,5 +0,0 @@
-pr: 117555
-summary: Expand type compatibility for match function and operator
-area: ES|QL
-type: feature
-issues: []

docs/changelog/117572.yaml

@@ -1,5 +0,0 @@
-pr: 117572
-summary: Address and remove any references of RestApiVersion version 7
-area: Search
-type: enhancement
-issues: []

docs/changelog/117581.yaml

@@ -1,5 +0,0 @@
-pr: 117581
-summary: Make reserved built-in roles queryable
-area: Authorization
-type: enhancement
-issues: []

docs/changelog/117583.yaml

@@ -1,17 +0,0 @@
-pr: 117583
-summary: Removing index alias creation for deprecated transforms notification index
-area: Machine Learning
-type: deprecation
-issues: []
-deprecation:
-  title: Removing index alias creation for deprecated transforms notification index
-  area: Transform
-  details: >-
-    As part of the migration from 7.x to 8.x, the `.data-frame-notifications-1` index
-    was deprecated and replaced with the `.transform-notifications-000002` index.
-    The index is no longer created by default, all writes are directed to the new index,
-    and any clusters with the deprecated index will have an alias created to ensure that
-    reads are still retrieving data that was written to the index before the migration to 8.x.
-    This change removes the alias from the deprecated index in 9.x. Any clusters with the alias present
-    will retain it, but it will not be created on new clusters.
-  impact: No known end user impact.

docs/changelog/117589.yaml

@@ -1,5 +0,0 @@
-pr: 117589
-summary: "Add Inference Unified API for chat completions for OpenAI"
-area: Machine Learning
-type: enhancement
-issues: []

docs/changelog/117606.yaml

@@ -1,5 +0,0 @@
-pr: 117606
-summary: Remove deprecated sort from reindex operation within dataframe analytics procedure
-area: Machine Learning
-type: enhancement
-issues: []

docs/changelog/117618.yaml

@@ -1,5 +0,0 @@
-pr: 117618
-summary: SearchStatesIt failures reported by CI
-area: Search
-type: bug
-issues: [116617, 116618]

docs/changelog/117643.yaml

@@ -1,6 +0,0 @@
-pr: 117643
-summary: Drop null columns in text formats
-area: ES|QL
-type: bug
-issues:
-  - 116848

docs/changelog/117655.yaml

@@ -1,5 +0,0 @@
-pr: 117655
-summary: Add nulls support to Categorize
-area: ES|QL
-type: enhancement
-issues: []