[API] Updates source code docs and specification commit

cd2d1fba07d3224129ca5a8d6018d86f67004fdf

Author: picandocodigo

elasticsearch-api/lib/elasticsearch/api/actions/esql/async_query_get.rb

@@ -31,6 +31,7 @@ module Actions
         #  A query ID is also provided when the request was submitted with the `keep_on_completion` parameter set to `true`. (*Required*)
         # @option arguments [Boolean] :drop_null_columns Indicates whether columns that are entirely `null` will be removed from the `columns` and `values` portion of the results.
         #  If `true`, the response will include an extra section under the name `all_columns` which has the name of all the columns.
+        # @option arguments [String] :format A short version of the Accept header, for example `json` or `yaml`.
         # @option arguments [Time] :keep_alive The period for which the query and its results are stored in the cluster.
         #  When this period expires, the query and its results are deleted, even if the query is still ongoing.
         # @option arguments [Time] :wait_for_completion_timeout The period to wait for the request to finish.

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

@@ -30,54 +30,6 @@ module Actions
       # * A `geotile_grid` or `geohex_grid` aggregation on the `<field>`. The `grid_agg` parameter determines the aggregation type. The aggregation uses the `<zoom>/<x>/<y>` tile as a bounding box.
       # * Optionally, a `geo_bounds` aggregation on the `<field>`. The search only includes this aggregation if the `exact_bounds` parameter is `true`.
       # * If the optional parameter `with_labels` is `true`, the internal search will include a dynamic runtime field that calls the `getLabelPosition` function of the geometry doc value. This enables the generation of new point features containing suggested geometry labels, so that, for example, multi-polygons will have only one label.
-      # For example, Elasticsearch may translate a vector tile search API request with a `grid_agg` argument of `geotile` and an `exact_bounds` argument of `true` into the following search
-      #
-      # ```
-      # GET my-index/_search
-      # {
-      #   "size": 10000,
-      #   "query": {
-      #     "geo_bounding_box": {
-      #       "my-geo-field": {
-      #         "top_left": {
-      #           "lat": -40.979898069620134,
-      #           "lon": -45
-      #         },
-      #         "bottom_right": {
-      #           "lat": -66.51326044311186,
-      #           "lon": 0
-      #         }
-      #       }
-      #     }
-      #   },
-      #   "aggregations": {
-      #     "grid": {
-      #       "geotile_grid": {
-      #         "field": "my-geo-field",
-      #         "precision": 11,
-      #         "size": 65536,
-      #         "bounds": {
-      #           "top_left": {
-      #             "lat": -40.979898069620134,
-      #             "lon": -45
-      #           },
-      #           "bottom_right": {
-      #             "lat": -66.51326044311186,
-      #             "lon": 0
-      #           }
-      #         }
-      #       }
-      #     },
-      #     "bounds": {
-      #       "geo_bounds": {
-      #         "field": "my-geo-field",
-      #         "wrap_longitude": false
-      #       }
-      #     }
-      #   }
-      # }
-      # ```
-      #
       # The API returns results as a binary Mapbox vector tile.
       # Mapbox vector tiles are encoded as Google Protobufs (PBF). By default, the tile contains three layers:
       # * A `hits` layer containing a feature for each `<field>` value matching the `geo_bounding_box` query.
@@ -142,6 +94,7 @@ module Actions
       # Some cells may intersect more than one vector tile.
       # To compute the H3 resolution for each precision, Elasticsearch compares the average density of hexagonal bins at each resolution with the average density of tile bins at each zoom level.
       # Elasticsearch uses the H3 resolution that is closest to the corresponding geotile density.
+      # Learn how to use the vector tile search API with practical examples in the {https://www.elastic.co/docs/reference/elasticsearch/rest-apis/vector-tile-search Vector tile search examples} guide.
       #
       # @option arguments [String, Array] :index Comma-separated list of data streams, indices, or aliases to search (*Required*)
       # @option arguments [String] :field Field containing geospatial data to return (*Required*)

elasticsearch-api/lib/elasticsearch/api/actions/security/query_api_keys.rb

@@ -28,6 +28,7 @@ module Actions
         # To use this API, you must have at least the `manage_own_api_key` or the `read_security` cluster privileges.
         # If you have only the `manage_own_api_key` privilege, this API returns only the API keys that you own.
         # If you have the `read_security`, `manage_api_key`, or greater privileges (including `manage_security`), this API returns all API keys regardless of ownership.
+        # Refer to the linked documentation for examples of how to find API keys:
         #
         # @option arguments [Boolean] :with_limited_by Return the snapshot of the owner user's role descriptors associated with the API key.
         #  An API key's actual permission is the intersection of its assigned role descriptors and the owner user's role descriptors (effectively limited by it).

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

@@ -18,6 +18,6 @@
 module Elasticsearch
   module API
     VERSION = '9.1.0'.freeze
-    ES_SPECIFICATION_COMMIT = '09ebf27a057301e6f26581259d3c1d105074bdfd'.freeze
+    ES_SPECIFICATION_COMMIT = 'cd2d1fba07d3224129ca5a8d6018d86f67004fdf'.freeze
   end
 end