elasticsearch-api 8.17.2 → 9.0.0

data/lib/elasticsearch/api/actions/cross_cluster_replication/resume_auto_follow_pattern.rb

@@ -15,20 +15,25 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module CrossClusterReplication
       module Actions
-        # Resumes an auto-follow pattern that has been paused
+        # Resume an auto-follow pattern.
+        # Resume a cross-cluster replication auto-follow pattern that was paused.
+        # The auto-follow pattern will resume configuring following indices for newly created indices that match its patterns on the remote cluster.
+        # Remote indices created while the pattern was paused will also be followed unless they have been deleted or closed in the interim.
         #
-        # @option arguments [String] :name The name of the auto follow pattern to resume discovering new indices to follow.
-        # @option arguments [Time] :master_timeout Explicit operation timeout for connection to master node
+        # @option arguments [String] :name The name of the auto-follow pattern to resume. (*Required*)
+        # @option arguments [Time] :master_timeout The period to wait for a connection to the master node.
+        #  If the master node is not available before the timeout expires, the request fails and returns an error.
+        #  It can also be set to +-1+ to indicate that the request should never timeout. Server default: 30s.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/ccr-resume-auto-follow-pattern.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-ccr-resume-auto-follow-pattern
         #
         def resume_auto_follow_pattern(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'ccr.resume_auto_follow_pattern' }
@@ -48,7 +53,7 @@ module Elasticsearch
           _name = arguments.delete(:name)
 
           method = Elasticsearch::API::HTTP_POST
-          path   = "_ccr/auto_follow/#{Utils.__listify(_name)}/resume"
+          path   = "_ccr/auto_follow/#{Utils.listify(_name)}/resume"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(

data/lib/elasticsearch/api/actions/cross_cluster_replication/resume_follow.rb

@@ -15,21 +15,25 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module CrossClusterReplication
       module Actions
-        # Resumes a follower index that has been paused
+        # Resume a follower.
+        # Resume a cross-cluster replication follower index that was paused.
+        # The follower index could have been paused with the pause follower API.
+        # Alternatively it could be paused due to replication that cannot be retried due to failures during following tasks.
+        # When this API returns, the follower index will resume fetching operations from the leader index.
         #
-        # @option arguments [String] :index The name of the follow index to resume following.
-        # @option arguments [Time] :master_timeout Explicit operation timeout for connection to master node
+        # @option arguments [String] :index The name of the follow index to resume following. (*Required*)
+        # @option arguments [Time] :master_timeout Period to wait for a connection to the master node. Server default: 30s.
         # @option arguments [Hash] :headers Custom HTTP headers
-        # @option arguments [Hash] :body The name of the leader index and other optional ccr related parameters
+        # @option arguments [Hash] :body request body
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/ccr-post-resume-follow.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-ccr-resume-follow
         #
         def resume_follow(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'ccr.resume_follow' }
@@ -44,12 +48,12 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = arguments.delete(:body)
+          body = arguments.delete(:body)
 
           _index = arguments.delete(:index)
 
           method = Elasticsearch::API::HTTP_POST
-          path   = "#{Utils.__listify(_index)}/_ccr/resume_follow"
+          path   = "#{Utils.listify(_index)}/_ccr/resume_follow"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(

data/lib/elasticsearch/api/actions/cross_cluster_replication/stats.rb

@@ -15,20 +15,23 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module CrossClusterReplication
       module Actions
-        # Gets all stats related to cross-cluster replication.
+        # Get cross-cluster replication stats.
+        # This API returns stats about auto-following and the same shard-level stats as the get follower stats API.
         #
-        # @option arguments [Time] :timeout Explicit operation timeout
-        # @option arguments [Time] :master_timeout Explicit operation timeout for connection to master node
+        # @option arguments [Time] :master_timeout The period to wait for a connection to the master node.
+        #  If the master node is not available before the timeout expires, the request fails and returns an error.
+        #  It can also be set to +-1+ to indicate that the request should never timeout. Server default: 30s.
+        # @option arguments [Time] :timeout The period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. Server default: 30s.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/ccr-get-stats.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-ccr-stats
         #
         def stats(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'ccr.stats' }
@@ -36,7 +39,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = nil
+          body = nil
 
           method = Elasticsearch::API::HTTP_GET
           path   = '_ccr/stats'

data/lib/elasticsearch/api/actions/cross_cluster_replication/unfollow.rb

@@ -15,20 +15,25 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module CrossClusterReplication
       module Actions
-        # Stops the following task associated with a follower index and removes index metadata and settings associated with cross-cluster replication.
+        # Unfollow an index.
+        # Convert a cross-cluster replication follower index to a regular index.
+        # The API stops the following task associated with a follower index and removes index metadata and settings associated with cross-cluster replication.
+        # The follower index must be paused and closed before you call the unfollow API.
         #
-        # @option arguments [String] :index The name of the follower index that should be turned into a regular index.
-        # @option arguments [Time] :master_timeout Explicit operation timeout for connection to master node
+        # @option arguments [String] :index The name of the follower index. (*Required*)
+        # @option arguments [Time] :master_timeout The period to wait for a connection to the master node.
+        #  If the master node is not available before the timeout expires, the request fails and returns an error.
+        #  It can also be set to +-1+ to indicate that the request should never timeout. Server default: 30s.
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/ccr-post-unfollow.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-ccr-unfollow
         #
         def unfollow(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'ccr.unfollow' }
@@ -43,12 +48,12 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = nil
+          body = nil
 
           _index = arguments.delete(:index)
 
           method = Elasticsearch::API::HTTP_POST
-          path   = "#{Utils.__listify(_index)}/_ccr/unfollow"
+          path   = "#{Utils.listify(_index)}/_ccr/unfollow"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(

data/lib/elasticsearch/api/actions/dangling_indices/delete_dangling_index.rb

@@ -15,22 +15,24 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module DanglingIndices
       module Actions
-        # Deletes the specified dangling index
+        # Delete a dangling index.
+        # If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling.
+        # For example, this can happen if you delete more than +cluster.indices.tombstones.size+ indices while an Elasticsearch node is offline.
         #
-        # @option arguments [String] :index_uuid The UUID of the dangling index
-        # @option arguments [Boolean] :accept_data_loss Must be set to true in order to delete the dangling index
-        # @option arguments [Time] :timeout Explicit operation timeout
+        # @option arguments [String] :index_uuid The UUID of the index to delete. Use the get dangling indices API to find the UUID. (*Required*)
+        # @option arguments [Boolean] :accept_data_loss This parameter must be set to true to acknowledge that it will no longer be possible to recove data from the dangling index. (*Required*)
         # @option arguments [Time] :master_timeout Specify timeout for connection to master
+        # @option arguments [Time] :timeout Explicit operation timeout
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/modules-gateway-dangling-indices.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-dangling-indices-delete-dangling-index
         #
         def delete_dangling_index(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'dangling_indices.delete_dangling_index' }
@@ -50,7 +52,7 @@ module Elasticsearch
           _index_uuid = arguments.delete(:index_uuid)
 
           method = Elasticsearch::API::HTTP_DELETE
-          path   = "_dangling/#{Utils.__listify(_index_uuid)}"
+          path   = "_dangling/#{Utils.listify(_index_uuid)}"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(

data/lib/elasticsearch/api/actions/dangling_indices/import_dangling_index.rb

@@ -15,22 +15,25 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module DanglingIndices
       module Actions
-        # Imports the specified dangling index
+        # Import a dangling index.
+        # If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling.
+        # For example, this can happen if you delete more than +cluster.indices.tombstones.size+ indices while an Elasticsearch node is offline.
         #
-        # @option arguments [String] :index_uuid The UUID of the dangling index
-        # @option arguments [Boolean] :accept_data_loss Must be set to true in order to import the dangling index
-        # @option arguments [Time] :timeout Explicit operation timeout
+        # @option arguments [String] :index_uuid The UUID of the index to import. Use the get dangling indices API to locate the UUID. (*Required*)
+        # @option arguments [Boolean] :accept_data_loss This parameter must be set to true to import a dangling index.
+        #  Because Elasticsearch cannot know where the dangling index data came from or determine which shard copies are fresh and which are stale, it cannot guarantee that the imported data represents the latest state of the index when it was last in the cluster. (*Required*)
         # @option arguments [Time] :master_timeout Specify timeout for connection to master
+        # @option arguments [Time] :timeout Explicit operation timeout
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/modules-gateway-dangling-indices.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-dangling-indices-import-dangling-index
         #
         def import_dangling_index(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'dangling_indices.import_dangling_index' }
@@ -50,7 +53,7 @@ module Elasticsearch
           _index_uuid = arguments.delete(:index_uuid)
 
           method = Elasticsearch::API::HTTP_POST
-          path   = "_dangling/#{Utils.__listify(_index_uuid)}"
+          path   = "_dangling/#{Utils.listify(_index_uuid)}"
           params = Utils.process_params(arguments)
 
           Elasticsearch::API::Response.new(

data/lib/elasticsearch/api/actions/dangling_indices/list_dangling_indices.rb

@@ -15,18 +15,21 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module DanglingIndices
       module Actions
-        # Returns all dangling indices.
+        # Get the dangling indices.
+        # If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling.
+        # For example, this can happen if you delete more than +cluster.indices.tombstones.size+ indices while an Elasticsearch node is offline.
+        # Use this API to list dangling indices, which you can then import or delete.
         #
         # @option arguments [Hash] :headers Custom HTTP headers
         #
-        # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/modules-gateway-dangling-indices.html
+        # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-dangling-indices-list-dangling-indices
         #
         def list_dangling_indices(arguments = {})
           request_opts = { endpoint: arguments[:endpoint] || 'dangling_indices.list_dangling_indices' }
@@ -34,7 +37,7 @@ module Elasticsearch
           arguments = arguments.clone
           headers = arguments.delete(:headers) || {}
 
-          body   = nil
+          body = nil
 
           method = Elasticsearch::API::HTTP_GET
           path   = '_dangling'

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

@@ -15,32 +15,63 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Actions
-      # Removes a document from the index.
+      # Delete a document.
+      # Remove a JSON document from the specified index.
+      # NOTE: You cannot send deletion requests directly to a data stream.
+      # To delete a document in a data stream, you must target the backing index containing the document.
+      # **Optimistic concurrency control**
+      # Delete operations can be made conditional and only be performed if the last modification to the document was assigned the sequence number and primary term specified by the +if_seq_no+ and +if_primary_term+ parameters.
+      # If a mismatch is detected, the operation will result in a +VersionConflictException+ and a status code of +409+.
+      # **Versioning**
+      # Each document indexed is versioned.
+      # When deleting a document, the version can be specified to make sure the relevant document you are trying to delete is actually being deleted and it has not changed in the meantime.
+      # Every write operation run on a document, deletes included, causes its version to be incremented.
+      # The version number of a deleted document remains available for a short time after deletion to allow for control of concurrent operations.
+      # The length of time for which a deleted document's version remains available is determined by the +index.gc_deletes+ index setting.
+      # **Routing**
+      # If routing is used during indexing, the routing value also needs to be specified to delete a document.
+      # If the +_routing+ mapping is set to +required+ and no routing value is specified, the delete API throws a +RoutingMissingException+ and rejects the request.
+      # For example:
+      # +
+      # DELETE /my-index-000001/_doc/1?routing=shard-1
+      # +
+      # This request deletes the document with ID 1, but it is routed based on the user.
+      # The document is not deleted if the correct routing is not specified.
+      # **Distributed**
+      # The delete operation gets hashed into a specific shard ID.
+      # It then gets redirected into the primary shard within that ID group and replicated (if needed) to shard replicas within that ID group.
       #
-      # @option arguments [String] :id The document ID
-      # @option arguments [String] :index The name of the index
-      # @option arguments [String] :wait_for_active_shards Sets the number of shard copies that must be active before proceeding with the delete operation. Defaults to 1, meaning the primary shard only. Set to `all` for all shard copies, otherwise set to any non-negative value less than or equal to the total number of copies for the shard (number of replicas + 1)
-      # @option arguments [String] :refresh If `true` then refresh the affected shards to make this operation visible to search, if `wait_for` then wait for a refresh to make this operation visible to search, if `false` (the default) then do nothing with refreshes. (options: true, false, wait_for)
-      # @option arguments [String] :routing Specific routing value
-      # @option arguments [Time] :timeout Explicit operation timeout
-      # @option arguments [Number] :if_seq_no only perform the delete operation if the last operation that has changed the document has the specified sequence number
-      # @option arguments [Number] :if_primary_term only perform the delete operation if the last operation that has changed the document has the specified primary term
-      # @option arguments [Number] :version Explicit version number for concurrency control
-      # @option arguments [String] :version_type Specific version type (options: internal, external, external_gte)
+      # @option arguments [String] :id A unique identifier for the document. (*Required*)
+      # @option arguments [String] :index The name of the target index. (*Required*)
+      # @option arguments [Integer] :if_primary_term Only perform the operation if the document has this primary term.
+      # @option arguments [Integer] :if_seq_no Only perform the operation if the document has this sequence number.
+      # @option arguments [String] :refresh If +true+, Elasticsearch refreshes the affected shards to make this operation visible to search.
+      #  If +wait_for+, it waits for a refresh to make this operation visible to search.
+      #  If +false+, it does nothing with refreshes. Server default: false.
+      # @option arguments [String] :routing A custom value used to route operations to a specific shard.
+      # @option arguments [Time] :timeout The period to wait for active shards.This parameter is useful for situations where the primary shard assigned to perform the delete operation might not be available when the delete operation runs.
+      #  Some reasons for this might be that the primary shard is currently recovering from a store or undergoing relocation.
+      #  By default, the delete operation will wait on the primary shard to become available for up to 1 minute before failing and responding with an error. Server default: 1m.
+      # @option arguments [Integer] :version An explicit version number for concurrency control.
+      #  It must match the current version of the document for the request to succeed.
+      # @option arguments [String] :version_type The version type.
+      # @option arguments [Integer, String] :wait_for_active_shards The minimum number of shard copies that must be active before proceeding with the operation.
+      #  You can set it to +all+ or any positive integer up to the total number of shards in the index (+number_of_replicas+1+).
+      #  The default value of +1+ means it waits for each primary shard to be active. Server default: 1.
       # @option arguments [Hash] :headers Custom HTTP headers
       #
-      # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/docs-delete.html
+      # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-delete
       #
       def delete(arguments = {})
         request_opts = { endpoint: arguments[:endpoint] || 'delete' }
 
-        defined_params = %i[index id].each_with_object({}) do |variable, set_variables|
+        defined_params = [:index, :id].each_with_object({}) do |variable, set_variables|
           set_variables[variable] = arguments[variable] if arguments.key?(variable)
         end
         request_opts[:defined_params] = defined_params unless defined_params.empty?
@@ -58,11 +89,11 @@ module Elasticsearch
         _index = arguments.delete(:index)
 
         method = Elasticsearch::API::HTTP_DELETE
-        path   = "#{Utils.__listify(_index)}/_doc/#{Utils.__listify(_id)}"
+        path   = "#{Utils.listify(_index)}/_doc/#{Utils.listify(_id)}"
         params = Utils.process_params(arguments)
 
         if Array(arguments[:ignore]).include?(404)
-          Utils.__rescue_from_not_found do
+          Utils.rescue_from_not_found do
             Elasticsearch::API::Response.new(
               perform_request(method, path, params, body, headers, request_opts)
             )

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

@@ -15,48 +15,130 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Auto generated from build hash f284cc16f4d4b4289bc679aa1529bb504190fe80
-# @see https://github.com/elastic/elasticsearch/tree/main/rest-api-spec
-#
+# This code was automatically generated from the Elasticsearch Specification
+# See https://github.com/elastic/elasticsearch-specification
+# See Elasticsearch::ES_SPECIFICATION_COMMIT for commit hash.
 module Elasticsearch
   module API
     module Actions
-      # Deletes documents matching the provided query.
+      # Delete documents.
+      # Deletes documents that match the specified query.
+      # If the Elasticsearch security features are enabled, you must have the following index privileges for the target data stream, index, or alias:
+      # * +read+
+      # * +delete+ or +write+
+      # You can specify the query criteria in the request URI or the request body using the same syntax as the search API.
+      # When you submit a delete by query request, Elasticsearch gets a snapshot of the data stream or index when it begins processing the request and deletes matching documents using internal versioning.
+      # If a document changes between the time that the snapshot is taken and the delete operation is processed, it results in a version conflict and the delete operation fails.
+      # NOTE: Documents with a version equal to 0 cannot be deleted using delete by query because internal versioning does not support 0 as a valid version number.
+      # While processing a delete by query request, Elasticsearch performs multiple search requests sequentially to find all of the matching documents to delete.
+      # A bulk delete request is performed for each batch of matching documents.
+      # If a search or bulk request is rejected, the requests are retried up to 10 times, with exponential back off.
+      # If the maximum retry limit is reached, processing halts and all failed requests are returned in the response.
+      # Any delete requests that completed successfully still stick, they are not rolled back.
+      # You can opt to count version conflicts instead of halting and returning by setting +conflicts+ to +proceed+.
+      # Note that if you opt to count version conflicts the operation could attempt to delete more documents from the source than +max_docs+ until it has successfully deleted +max_docs documents+, or it has gone through every document in the source query.
+      # **Throttling delete requests**
+      # To control the rate at which delete by query issues batches of delete operations, you can set +requests_per_second+ to any positive decimal number.
+      # This pads each batch with a wait time to throttle the rate.
+      # Set +requests_per_second+ to +-1+ to disable throttling.
+      # Throttling uses a wait time between batches so that the internal scroll requests can be given a timeout that takes the request padding into account.
+      # The padding time is the difference between the batch size divided by the +requests_per_second+ and the time spent writing.
+      # By default the batch size is +1000+, so if +requests_per_second+ is set to +500+:
+      # +
+      # target_time = 1000 / 500 per second = 2 seconds
+      # wait_time = target_time - write_time = 2 seconds - .5 seconds = 1.5 seconds
+      # +
+      # Since the batch is issued as a single +_bulk+ request, large batch sizes cause Elasticsearch to create many requests and wait before starting the next set.
+      # This is "bursty" instead of "smooth".
+      # **Slicing**
+      # Delete by query supports sliced scroll to parallelize the delete process.
+      # This can improve efficiency and provide a convenient way to break the request down into smaller parts.
+      # Setting +slices+ to +auto+ lets Elasticsearch choose the number of slices to use.
+      # This setting will use one slice per shard, up to a certain limit.
+      # If there are multiple source data streams or indices, it will choose the number of slices based on the index or backing index with the smallest number of shards.
+      # Adding slices to the delete by query operation creates sub-requests which means it has some quirks:
+      # * You can see these requests in the tasks APIs. These sub-requests are "child" tasks of the task for the request with slices.
+      # * Fetching the status of the task for the request with slices only contains the status of completed slices.
+      # * These sub-requests are individually addressable for things like cancellation and rethrottling.
+      # * Rethrottling the request with +slices+ will rethrottle the unfinished sub-request proportionally.
+      # * Canceling the request with +slices+ will cancel each sub-request.
+      # * Due to the nature of +slices+ each sub-request won't get a perfectly even portion of the documents. All documents will be addressed, but some slices may be larger than others. Expect larger slices to have a more even distribution.
+      # * Parameters like +requests_per_second+ and +max_docs+ on a request with +slices+ are distributed proportionally to each sub-request. Combine that with the earlier point about distribution being uneven and you should conclude that using +max_docs+ with +slices+ might not result in exactly +max_docs+ documents being deleted.
+      # * Each sub-request gets a slightly different snapshot of the source data stream or index though these are all taken at approximately the same time.
+      # If you're slicing manually or otherwise tuning automatic slicing, keep in mind that:
+      # * Query performance is most efficient when the number of slices is equal to the number of shards in the index or backing index. If that number is large (for example, 500), choose a lower number as too many +slices+ hurts performance. Setting +slices+ higher than the number of shards generally does not improve efficiency and adds overhead.
+      # * Delete performance scales linearly across available resources with the number of slices.
+      # Whether query or delete performance dominates the runtime depends on the documents being reindexed and cluster resources.
+      # **Cancel a delete by query operation**
+      # Any delete by query can be canceled using the task cancel API. For example:
+      # +
+      # POST _tasks/r1A2WoRbTwKZ516z6NEs5A:36619/_cancel
+      # +
+      # The task ID can be found by using the get tasks API.
+      # Cancellation should happen quickly but might take a few seconds.
+      # The get task status API will continue to list the delete by query task until this task checks that it has been cancelled and terminates itself.
       #
-      # @option arguments [List] :index A comma-separated list of index names to search; use `_all` or empty string to perform the operation on all indices
-      # @option arguments [String] :analyzer The analyzer to use for the query string
-      # @option arguments [Boolean] :analyze_wildcard Specify whether wildcard and prefix queries should be analyzed (default: false)
-      # @option arguments [String] :default_operator The default operator for query string query (AND or OR) (options: AND, OR)
-      # @option arguments [String] :df The field to use as default where no field prefix is given in the query string
-      # @option arguments [Number] :from Starting offset (default: 0)
-      # @option arguments [Boolean] :ignore_unavailable Whether specified concrete indices should be ignored when unavailable (missing or closed)
-      # @option arguments [Boolean] :allow_no_indices Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified)
-      # @option arguments [String] :conflicts What to do when the delete by query hits version conflicts? (options: abort, proceed)
-      # @option arguments [String] :expand_wildcards Whether to expand wildcard expression to concrete indices that are open, closed or both. (options: open, closed, hidden, none, all)
-      # @option arguments [Boolean] :lenient Specify whether format-based query failures (such as providing text to a numeric field) should be ignored
-      # @option arguments [String] :preference Specify the node or shard the operation should be performed on (default: random)
-      # @option arguments [String] :q Query in the Lucene query string syntax
-      # @option arguments [List] :routing A comma-separated list of specific routing values
-      # @option arguments [Time] :scroll Specify how long a consistent view of the index should be maintained for scrolled search
-      # @option arguments [String] :search_type Search operation type (options: query_then_fetch, dfs_query_then_fetch)
-      # @option arguments [Time] :search_timeout Explicit timeout for each search request. Defaults to no timeout.
-      # @option arguments [Number] :max_docs Maximum number of documents to process (default: all documents)
-      # @option arguments [List] :sort A comma-separated list of <field>:<direction> pairs
-      # @option arguments [Number] :terminate_after The maximum number of documents to collect for each shard, upon reaching which the query execution will terminate early.
-      # @option arguments [List] :stats Specific 'tag' of the request for logging and statistical purposes
-      # @option arguments [Boolean] :version Specify whether to return document version as part of a hit
-      # @option arguments [Boolean] :request_cache Specify if request cache should be used for this request or not, defaults to index level setting
-      # @option arguments [Boolean] :refresh Should the affected indexes be refreshed?
-      # @option arguments [Time] :timeout Time each individual bulk request should wait for shards that are unavailable.
-      # @option arguments [String] :wait_for_active_shards Sets the number of shard copies that must be active before proceeding with the delete by query operation. Defaults to 1, meaning the primary shard only. Set to `all` for all shard copies, otherwise set to any non-negative value less than or equal to the total number of copies for the shard (number of replicas + 1)
-      # @option arguments [Number] :scroll_size Size on the scroll request powering the delete by query
-      # @option arguments [Boolean] :wait_for_completion Should the request should block until the delete by query is complete.
-      # @option arguments [Number] :requests_per_second The throttle for this request in sub-requests per second. -1 means no throttle.
-      # @option arguments [Number|string] :slices The number of slices this task should be divided into. Defaults to 1, meaning the task isn't sliced into subtasks. Can be set to `auto`.
+      # @option arguments [String, Array] :index A comma-separated list of data streams, indices, and aliases to search.
+      #  It supports wildcards (+*+).
+      #  To search all data streams or indices, omit this parameter or use +*+ or +_all+. (*Required*)
+      # @option arguments [Boolean] :allow_no_indices If +false+, the request returns an error if any wildcard expression, index alias, or +_all+ value targets only missing or closed indices.
+      #  This behavior applies even if the request targets other open indices.
+      #  For example, a request targeting +foo*,bar*+ returns an error if an index starts with +foo+ but no index starts with +bar+. Server default: true.
+      # @option arguments [String] :analyzer Analyzer to use for the query string.
+      #  This parameter can be used only when the +q+ query string parameter is specified.
+      # @option arguments [Boolean] :analyze_wildcard If +true+, wildcard and prefix queries are analyzed.
+      #  This parameter can be used only when the +q+ query string parameter is specified.
+      # @option arguments [String] :conflicts What to do if delete by query hits version conflicts: +abort+ or +proceed+. Server default: abort.
+      # @option arguments [String] :default_operator The default operator for query string query: +AND+ or +OR+.
+      #  This parameter can be used only when the +q+ query string parameter is specified. Server default: OR.
+      # @option arguments [String] :df The field to use as default where no field prefix is given in the query string.
+      #  This parameter can be used only when the +q+ query string parameter is specified.
+      # @option arguments [String, Array<String>] :expand_wildcards The type of index that wildcard patterns can match.
+      #  If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams.
+      #  It supports comma-separated values, such as +open,hidden+. Server default: open.
+      # @option arguments [Integer] :from Skips the specified number of documents. Server default: 0.
+      # @option arguments [Boolean] :ignore_unavailable If +false+, the request returns an error if it targets a missing or closed index.
+      # @option arguments [Boolean] :lenient If +true+, format-based query failures (such as providing text to a numeric field) in the query string will be ignored.
+      #  This parameter can be used only when the +q+ query string parameter is specified.
+      # @option arguments [Integer] :max_docs The maximum number of documents to process.
+      #  Defaults to all documents.
+      #  When set to a value less then or equal to +scroll_size+, a scroll will not be used to retrieve the results for the operation.
+      # @option arguments [String] :preference The node or shard the operation should be performed on.
+      #  It is random by default.
+      # @option arguments [Boolean] :refresh If +true+, Elasticsearch refreshes all shards involved in the delete by query after the request completes.
+      #  This is different than the delete API's +refresh+ parameter, which causes just the shard that received the delete request to be refreshed.
+      #  Unlike the delete API, it does not support +wait_for+.
+      # @option arguments [Boolean] :request_cache If +true+, the request cache is used for this request.
+      #  Defaults to the index-level setting.
+      # @option arguments [Float] :requests_per_second The throttle for this request in sub-requests per second. Server default: -1.
+      # @option arguments [String] :routing A custom value used to route operations to a specific shard.
+      # @option arguments [String] :q A query in the Lucene query string syntax.
+      # @option arguments [Time] :scroll The period to retain the search context for scrolling.
+      # @option arguments [Integer] :scroll_size The size of the scroll request that powers the operation. Server default: 1000.
+      # @option arguments [Time] :search_timeout The explicit timeout for each search request.
+      #  It defaults to no timeout.
+      # @option arguments [String] :search_type The type of the search operation.
+      #  Available options include +query_then_fetch+ and +dfs_query_then_fetch+.
+      # @option arguments [Integer, String] :slices The number of slices this task should be divided into. Server default: 1.
+      # @option arguments [Array<String>] :sort A comma-separated list of +<field>:<direction>+ pairs.
+      # @option arguments [Array<String>] :stats The specific +tag+ of the request for logging and statistical purposes.
+      # @option arguments [Integer] :terminate_after The maximum number of documents to collect for each shard.
+      #  If a query reaches this limit, Elasticsearch terminates the query early.
+      #  Elasticsearch collects documents before sorting.Use with caution.
+      #  Elasticsearch applies this parameter to each shard handling the request.
+      #  When possible, let Elasticsearch perform early termination automatically.
+      #  Avoid specifying this parameter for requests that target data streams with backing indices across multiple data tiers.
+      # @option arguments [Time] :timeout The period each deletion request waits for active shards. Server default: 1m.
+      # @option arguments [Boolean] :version If +true+, returns the document version as part of a hit.
+      # @option arguments [Integer, String] :wait_for_active_shards The number of shard copies that must be active before proceeding with the operation.
+      #  Set to +all+ or any positive integer up to the total number of shards in the index (+number_of_replicas+1+).
+      #  The +timeout+ value controls how long each write request waits for unavailable shards to become available. Server default: 1.
+      # @option arguments [Boolean] :wait_for_completion If +true+, the request blocks until the operation is complete.
+      #  If +false+, Elasticsearch performs some preflight checks, launches the request, and returns a task you can use to cancel or get the status of the task. Elasticsearch creates a record of this task as a document at +.tasks/task/${taskId}+. When you are done with a task, you should delete the task document so Elasticsearch can reclaim the space. Server default: true.
       # @option arguments [Hash] :headers Custom HTTP headers
-      # @option arguments [Hash] :body The search definition using the Query DSL (*Required*)
+      # @option arguments [Hash] :body request body
       #
-      # @see https://www.elastic.co/guide/en/elasticsearch/reference/8.17/docs-delete-by-query.html
+      # @see https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-delete-by-query
       #
       def delete_by_query(arguments = {})
         request_opts = { endpoint: arguments[:endpoint] || 'delete_by_query' }
@@ -72,12 +154,12 @@ module Elasticsearch
         arguments = arguments.clone
         headers = arguments.delete(:headers) || {}
 
-        body   = arguments.delete(:body)
+        body = arguments.delete(:body)
 
         _index = arguments.delete(:index)
 
         method = Elasticsearch::API::HTTP_POST
-        path   = "#{Utils.__listify(_index)}/_delete_by_query"
+        path   = "#{Utils.listify(_index)}/_delete_by_query"
         params = Utils.process_params(arguments)
 
         Elasticsearch::API::Response.new(