[API] Updates API to 31789f4

elasticsearch-api/lib/elasticsearch/api/actions/indices/downsample.rb

@@ -32,9 +32,6 @@ module Actions
         # NOTE: Only indices in a time series data stream are supported.
         # Neither field nor document level security can be defined on the source index.
         # The source index must be read-only (`index.blocks.write: true`).
-        # This functionality is in technical preview and may be changed or removed in a future
-        # release. Elastic will apply best effort to fix any issues, but features in technical
-        # preview are not subject to the support SLA of official GA features.
         #
         # @option arguments [String] :index Name of the time series index to downsample. (*Required*)
         # @option arguments [String] :target_index Name of the index to create. (*Required*)

elasticsearch-api/lib/elasticsearch/api/actions/indices/split.rb

@@ -47,6 +47,7 @@ module Actions
         # * The target index must not exist.
         # * The source index must have fewer primary shards than the target index.
         # * The number of primary shards in the target index must be a multiple of the number of primary shards in the source index.
+        # * The number of primary shards in the target index must be a divisor of the source index's `index.number_of_routing_shards`.
         # * The node handling the split process must have sufficient free disk space to accommodate a second copy of the existing index.
         #
         # @option arguments [String] :index Name of the source index to split. (*Required*)

elasticsearch-api/lib/elasticsearch/api/actions/reindex.rb

@@ -37,7 +37,7 @@ module Actions
       # * To automatically create a data stream or index with a reindex API request, you must have the `auto_configure`, `create_index`, or `manage` index privilege for the destination data stream, index, or alias.
       # * If reindexing from a remote cluster, the `source.remote.user` must have the `monitor` cluster privilege and the `read` index privilege for the source data stream, index, or alias.
       # If reindexing from a remote cluster into a cluster using Elastic Stack, you must explicitly allow the remote host using the `reindex.remote.whitelist` node setting on the destination cluster.
-      # If reindexing from a remote cluster into an Elastic Cloud Serverless project, only remote hosts from Elastic Cloud Hosted are allowed.
+      # If reindexing from a remote cluster into an Elastic Cloud Serverless project, only remote hosts from {https://cloud.elastic.co/registration?page=docs&placement=docs-body Elastic Cloud Hosted} are allowed.
       # Automatic data stream creation requires a matching index template with data stream enabled.
       # The `dest` element can be configured like the index API to control optimistic concurrency control.
       # Omitting `version_type` or setting it to `internal` causes Elasticsearch to blindly dump documents into the destination, overwriting any that happen to have the same ID.

elasticsearch-api/lib/elasticsearch/api/actions/snapshot/repository_analyze.rb

@@ -45,6 +45,10 @@ module Actions
         # This allows you to demonstrate to your storage supplier that a repository analysis failure must only be caused by an incompatibility with AWS S3 and cannot be attributed to a problem in Elasticsearch.
         # Please do not report Elasticsearch issues involving third-party storage systems unless you can demonstrate that the same issue exists when analysing a repository that uses the reference implementation of the same storage protocol.
         # You will need to work with the supplier of your storage system to address the incompatibilities that Elasticsearch detects.
+        # The analysis may also report a failure if your repository experienced a service disruption while the analysis was running.
+        # In practice, occasional service disruptions are inevitable, but the analysis cannot itself distinguish such disruptions from incorrect behavior so must report all deviations from the expected behavior as failures.
+        # If you are certain that you can ascribe an analysis failure to such a service disruption, wait for your service provider to resolve the disruption and then re-run the analysis.
+        # Elasticsearch will be unable to create or restore snapshots during repository service disruptions, so you must ensure that these events occur only very rarely.
         # If the analysis is successful, the API returns details of the testing process, optionally including how long each operation took.
         # You can use this information to determine the performance of your storage system.
         # If any operation fails or returns an incorrect result, the API returns an error.

elasticsearch-api/lib/elasticsearch/api/version.rb

@@ -18,6 +18,6 @@
 module Elasticsearch
   module API
     VERSION = '9.3.1'.freeze
-    ES_SPECIFICATION_COMMIT = 'df81426e814ecb513b012f2c0a706572964c606c'.freeze
+    ES_SPECIFICATION_COMMIT = '31789f4216047ef7ba7969e31610fa2bbfe696b1'.freeze
   end
 end