elasticsearch-api 9.2.1 → 9.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6d8a67d5fa8414a8e09624ea2d41332567167610104a71e90d98ef526a9f5c43
-  data.tar.gz: 8cf41f2ea31c275b6f53e3250a0b5cd4ebff0b35e28b205cdd5d31feb8c9744f
+  metadata.gz: 29ea3f1d155d5f8b3d609053ca966eccc4b069548eee22c49f9cdfc485c58abc
+  data.tar.gz: 4d537313bd5693730065ad01005c483bfe5c2a57657d9300b1be13a1f8ef41ce
 SHA512:
-  metadata.gz: 17a9ce971775e193083d266768731a0ace9ebdc04656847dbf00d6c3f4d6ad0980619314dfd0cb3ecebb1a29ef6eebb3e744add150e88c3f92d714301fe5e805
-  data.tar.gz: 6b5afa5dbf3deba0364541e23675682a0ffe6b22e07c7c3c7559926c7a2987b7fb724d15a8dbedccc5affe2d7fad6861ae5f3e6c13d062232ed9a437074b96e9
+  metadata.gz: 6570ebed7a0242e8bb75e56480503cbaa472c57c4568f8ec11415172b279bc2f12e71a0fb73b367266d9e552168a118169544e3f6d027577c9f395009c5a65ba
+  data.tar.gz: 0efdf3fc2048be8d0187180a1ed4ab1a67232ffcef05ba11e1d6c9223bf17959d482ea072edde5e34d27c02c7c5132ea00b056b7fa9ed65efbf2fe979ef58b09

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

@@ -29,9 +29,6 @@ module Elasticsearch
         # 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*)

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

@@ -36,7 +36,8 @@ module Elasticsearch
       # * The `write` index privilege for the destination data stream, index, or index alias.
       # * 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, you must explicitly allow the remote host in the `reindex.remote.whitelist` setting.
+      # 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 {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.

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

@@ -45,6 +45,10 @@ module Elasticsearch
         # 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.

data/lib/elasticsearch/api/version.rb

@@ -17,7 +17,7 @@
 
 module Elasticsearch
   module API
-    VERSION = '9.2.1'.freeze
-    ES_SPECIFICATION_COMMIT = '49022a2c08d291955de83e26c583b7dc628fb558'.freeze
+    VERSION = '9.2.2'.freeze
+    ES_SPECIFICATION_COMMIT = '2d7de011d88518dc8e20a02fb235f197c43866bc'.freeze
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: elasticsearch-api
 version: !ruby/object:Gem::Version
-  version: 9.2.1
+  version: 9.2.2
 platform: ruby
 authors:
 - Elastic Client Library Maintainers
@@ -841,7 +841,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.3
+rubygems_version: 4.0.12
 specification_version: 4
 summary: Ruby API for Elasticsearch.
 test_files: []