@elastic/elasticsearch 9.3.0 → 9.3.2

package/lib/api/api/transform.d.ts

@@ -19,91 +19,91 @@ export default class Transform {
     constructor(transport: Transport);
     /**
       * Delete a transform.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-delete-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-delete-transform | Elasticsearch API documentation}
       */
     deleteTransform(this: That, params: T.TransformDeleteTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformDeleteTransformResponse>;
     deleteTransform(this: That, params: T.TransformDeleteTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformDeleteTransformResponse, unknown>>;
     deleteTransform(this: That, params: T.TransformDeleteTransformRequest, options?: TransportRequestOptions): Promise<T.TransformDeleteTransformResponse>;
     /**
       * Get node stats. Get per-node information about transform usage.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-get-node-stats | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-get-node-stats | Elasticsearch API documentation}
       */
     getNodeStats(this: That, params?: T.TransformGetNodeStatsRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformGetNodeStatsResponse>;
     getNodeStats(this: That, params?: T.TransformGetNodeStatsRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformGetNodeStatsResponse, unknown>>;
     getNodeStats(this: That, params?: T.TransformGetNodeStatsRequest, options?: TransportRequestOptions): Promise<T.TransformGetNodeStatsResponse>;
     /**
       * Get transforms. Get configuration information for transforms.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-get-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-get-transform | Elasticsearch API documentation}
       */
     getTransform(this: That, params?: T.TransformGetTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformGetTransformResponse>;
     getTransform(this: That, params?: T.TransformGetTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformGetTransformResponse, unknown>>;
     getTransform(this: That, params?: T.TransformGetTransformRequest, options?: TransportRequestOptions): Promise<T.TransformGetTransformResponse>;
     /**
       * Get transform stats. Get usage information for transforms.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-get-transform-stats | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-get-transform-stats | Elasticsearch API documentation}
       */
     getTransformStats(this: That, params: T.TransformGetTransformStatsRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformGetTransformStatsResponse>;
     getTransformStats(this: That, params: T.TransformGetTransformStatsRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformGetTransformStatsResponse, unknown>>;
     getTransformStats(this: That, params: T.TransformGetTransformStatsRequest, options?: TransportRequestOptions): Promise<T.TransformGetTransformStatsResponse>;
     /**
       * Preview a transform. Generates a preview of the results that you will get when you create a transform with the same configuration. It returns a maximum of 100 results. The calculations are based on all the current data in the source index. It also generates a list of mappings and settings for the destination index. These values are determined based on the field types of the source index and the transform aggregations.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-preview-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-preview-transform | Elasticsearch API documentation}
       */
     previewTransform<TTransform = unknown>(this: That, params?: T.TransformPreviewTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformPreviewTransformResponse<TTransform>>;
     previewTransform<TTransform = unknown>(this: That, params?: T.TransformPreviewTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformPreviewTransformResponse<TTransform>, unknown>>;
     previewTransform<TTransform = unknown>(this: That, params?: T.TransformPreviewTransformRequest, options?: TransportRequestOptions): Promise<T.TransformPreviewTransformResponse<TTransform>>;
     /**
       * Create a transform. Creates a transform. A transform copies data from source indices, transforms it, and persists it into an entity-centric destination index. You can also think of the destination index as a two-dimensional tabular data structure (known as a data frame). The ID for each document in the data frame is generated from a hash of the entity, so there is a unique row per entity. You must choose either the latest or pivot method for your transform; you cannot use both in a single transform. If you choose to use the pivot method for your transform, the entities are defined by the set of `group_by` fields in the pivot object. If you choose to use the latest method, the entities are defined by the `unique_key` field values in the latest object. You must have `create_index`, `index`, and `read` privileges on the destination index and `read` and `view_index_metadata` privileges on the source indices. When Elasticsearch security features are enabled, the transform remembers which roles the user that created it had at the time of creation and uses those same roles. If those roles do not have the required privileges on the source and destination indices, the transform fails when it attempts unauthorized operations. NOTE: You must use Kibana or this API to create a transform. Do not add a transform directly into any `.transform-internal*` indices using the Elasticsearch index API. If Elasticsearch security features are enabled, do not give users any privileges on `.transform-internal*` indices. If you used transforms prior to 7.5, also do not give users any privileges on `.data-frame-internal*` indices.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-put-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-put-transform | Elasticsearch API documentation}
       */
     putTransform(this: That, params: T.TransformPutTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformPutTransformResponse>;
     putTransform(this: That, params: T.TransformPutTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformPutTransformResponse, unknown>>;
     putTransform(this: That, params: T.TransformPutTransformRequest, options?: TransportRequestOptions): Promise<T.TransformPutTransformResponse>;
     /**
       * Reset a transform. Before you can reset it, you must stop it; alternatively, use the `force` query parameter. If the destination index was created by the transform, it is deleted.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-reset-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-reset-transform | Elasticsearch API documentation}
       */
     resetTransform(this: That, params: T.TransformResetTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformResetTransformResponse>;
     resetTransform(this: That, params: T.TransformResetTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformResetTransformResponse, unknown>>;
     resetTransform(this: That, params: T.TransformResetTransformRequest, options?: TransportRequestOptions): Promise<T.TransformResetTransformResponse>;
     /**
       * Schedule a transform to start now. Instantly run a transform to process data. If you run this API, the transform will process the new data instantly, without waiting for the configured frequency interval. After the API is called, the transform will be processed again at `now + frequency` unless the API is called again in the meantime.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-schedule-now-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-schedule-now-transform | Elasticsearch API documentation}
       */
     scheduleNowTransform(this: That, params: T.TransformScheduleNowTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformScheduleNowTransformResponse>;
     scheduleNowTransform(this: That, params: T.TransformScheduleNowTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformScheduleNowTransformResponse, unknown>>;
     scheduleNowTransform(this: That, params: T.TransformScheduleNowTransformRequest, options?: TransportRequestOptions): Promise<T.TransformScheduleNowTransformResponse>;
     /**
       * Set upgrade_mode for transform indices. Sets a cluster wide upgrade_mode setting that prepares transform indices for an upgrade. When upgrading your cluster, in some circumstances you must restart your nodes and reindex your transform indices. In those circumstances, there must be no transforms running. You can close the transforms, do the upgrade, then open all the transforms again. Alternatively, you can use this API to temporarily halt tasks associated with the transforms and prevent new transforms from opening. You can also use this API during upgrades that do not require you to reindex your transform indices, though stopping transforms is not a requirement in that case. You can see the current value for the upgrade_mode setting by using the get transform info API.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-set-upgrade-mode | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-set-upgrade-mode | Elasticsearch API documentation}
       */
     setUpgradeMode(this: That, params?: T.TransformSetUpgradeModeRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformSetUpgradeModeResponse>;
     setUpgradeMode(this: That, params?: T.TransformSetUpgradeModeRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformSetUpgradeModeResponse, unknown>>;
     setUpgradeMode(this: That, params?: T.TransformSetUpgradeModeRequest, options?: TransportRequestOptions): Promise<T.TransformSetUpgradeModeResponse>;
     /**
       * Start a transform. When you start a transform, it creates the destination index if it does not already exist. The `number_of_shards` is set to `1` and the `auto_expand_replicas` is set to `0-1`. If it is a pivot transform, it deduces the mapping definitions for the destination index from the source indices and the transform aggregations. If fields in the destination index are derived from scripts (as in the case of `scripted_metric` or `bucket_script` aggregations), the transform uses dynamic mappings unless an index template exists. If it is a latest transform, it does not deduce mapping definitions; it uses dynamic mappings. To use explicit mappings, create the destination index before you start the transform. Alternatively, you can create an index template, though it does not affect the deduced mappings in a pivot transform. When the transform starts, a series of validations occur to ensure its success. If you deferred validation when you created the transform, they occur when you start the transform—with the exception of privilege checks. When Elasticsearch security features are enabled, the transform remembers which roles the user that created it had at the time of creation and uses those same roles. If those roles do not have the required privileges on the source and destination indices, the transform fails when it attempts unauthorized operations.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-start-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-start-transform | Elasticsearch API documentation}
       */
     startTransform(this: That, params: T.TransformStartTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformStartTransformResponse>;
     startTransform(this: That, params: T.TransformStartTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformStartTransformResponse, unknown>>;
     startTransform(this: That, params: T.TransformStartTransformRequest, options?: TransportRequestOptions): Promise<T.TransformStartTransformResponse>;
     /**
       * Stop transforms. Stops one or more transforms.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-stop-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-stop-transform | Elasticsearch API documentation}
       */
     stopTransform(this: That, params: T.TransformStopTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformStopTransformResponse>;
     stopTransform(this: That, params: T.TransformStopTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformStopTransformResponse, unknown>>;
     stopTransform(this: That, params: T.TransformStopTransformRequest, options?: TransportRequestOptions): Promise<T.TransformStopTransformResponse>;
     /**
       * Update a transform. Updates certain properties of a transform. All updated properties except `description` do not take effect until after the transform starts the next checkpoint, thus there is data consistency in each checkpoint. To use this API, you must have `read` and `view_index_metadata` privileges for the source indices. You must also have `index` and `read` privileges for the destination index. When Elasticsearch security features are enabled, the transform remembers which roles the user who updated it had at the time of update and runs with those privileges.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-update-transform | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-update-transform | Elasticsearch API documentation}
       */
     updateTransform(this: That, params: T.TransformUpdateTransformRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformUpdateTransformResponse>;
     updateTransform(this: That, params: T.TransformUpdateTransformRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformUpdateTransformResponse, unknown>>;
     updateTransform(this: That, params: T.TransformUpdateTransformRequest, options?: TransportRequestOptions): Promise<T.TransformUpdateTransformResponse>;
     /**
       * Upgrade all transforms. Transforms are compatible across minor versions and between supported major versions. However, over time, the format of transform configuration information may change. This API identifies transforms that have a legacy configuration format and upgrades them to the latest version. It also cleans up the internal data structures that store the transform state and checkpoints. The upgrade does not affect the source and destination indices. The upgrade also does not affect the roles that transforms use when Elasticsearch security features are enabled; the role used to read source data and write to the destination index remains unchanged. If a transform upgrade step fails, the upgrade stops and an error is returned about the underlying issue. Resolve the issue then re-run the process again. A summary is returned when the upgrade is finished. To ensure continuous transforms remain running during a major version upgrade of the cluster – for example, from 7.16 to 8.0 – it is recommended to upgrade transforms before upgrading the cluster. You may want to perform a recent cluster backup prior to the upgrade.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-upgrade-transforms | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-transform-upgrade-transforms | Elasticsearch API documentation}
       */
     upgradeTransforms(this: That, params?: T.TransformUpgradeTransformsRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.TransformUpgradeTransformsResponse>;
     upgradeTransforms(this: That, params?: T.TransformUpgradeTransformsRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.TransformUpgradeTransformsResponse, unknown>>;

package/lib/api/api/update.d.ts

@@ -5,7 +5,7 @@ interface That {
 }
 /**
   * Update a document. Update a document by running a script or passing a partial document. If the Elasticsearch security features are enabled, you must have the `index` or `write` index privilege for the target index or index alias. The script can update, delete, or skip modifying the document. The API also supports passing a partial document, which is merged into the existing document. To fully replace an existing document, use the index API. This operation: * Gets the document (collocated with the shard) from the index. * Runs the specified script. * Indexes the result. The document must still be reindexed, but using this API removes some network roundtrips and reduces chances of version conflicts between the GET and the index operation. The `_source` field must be enabled to use this API. In addition to `_source`, you can access the following variables through the `ctx` map: `_index`, `_type`, `_id`, `_version`, `_routing`, and `_now` (the current timestamp). For usage examples such as partial updates, upserts, and scripted updates, see the External documentation.
-  * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update | Elasticsearch API documentation}
+  * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-update | Elasticsearch API documentation}
   */
 export default function UpdateApi<TDocument = unknown, TPartialDocument = unknown, TDocumentR = unknown>(this: That, params: T.UpdateRequest<TDocument, TPartialDocument>, options?: TransportRequestOptionsWithOutMeta): Promise<T.UpdateResponse<TDocumentR>>;
 export default function UpdateApi<TDocument = unknown, TPartialDocument = unknown, TDocumentR = unknown>(this: That, params: T.UpdateRequest<TDocument, TPartialDocument>, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.UpdateResponse<TDocumentR>, unknown>>;

package/lib/api/api/update_by_query.d.ts

@@ -5,7 +5,7 @@ interface That {
 }
 /**
   * Update documents. Updates documents that match the specified query. If no query is specified, performs an update on every document in the data stream or index without modifying the source, which is useful for picking up mapping changes. If the Elasticsearch security features are enabled, you must have the following index privileges for the target data stream, index, or alias: * `read` * `index` 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 an update by query request, Elasticsearch gets a snapshot of the data stream or index when it begins processing the request and updates matching documents using internal versioning. When the versions match, the document is updated and the version number is incremented. If a document changes between the time that the snapshot is taken and the update operation is processed, it results in a version conflict and the operation fails. 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 update more documents from the source than `max_docs` until it has successfully updated `max_docs` documents or it has gone through every document in the source query. NOTE: Documents with a version equal to 0 cannot be updated using update by query because internal versioning does not support 0 as a valid version number. While processing an update by query request, Elasticsearch performs multiple search requests sequentially to find all of the matching documents. A bulk update request is performed for each batch of matching documents. Any query or update failures cause the update by query request to fail and the failures are shown in the response. Any update requests that completed successfully still stick, they are not rolled back. **Refreshing shards** Specifying the `refresh` parameter refreshes all shards once the request completes. This is different to the update API's `refresh` parameter, which causes only the shard that received the request to be refreshed. Unlike the update API, it does not support `wait_for`. **Running update by query asynchronously** If the request contains `wait_for_completion=false`, Elasticsearch performs some preflight checks, launches the request, and returns a [task](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) 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}`. **Waiting for active shards** `wait_for_active_shards` controls how many copies of a shard must be active before proceeding with the request. See [`wait_for_active_shards`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-create#operation-create-wait_for_active_shards) for details. `timeout` controls how long each write request waits for unavailable shards to become available. Both work exactly the way they work in the [Bulk API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk). Update by query uses scrolled searches, so you can also specify the `scroll` parameter to control how long it keeps the search context alive, for example `?scroll=10m`. The default is 5 minutes. **Throttling update requests** To control the rate at which update by query issues batches of update 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 turn off 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** Update by query supports sliced scroll to parallelize the update process. This can improve efficiency and provide a convenient way to break the request down into smaller parts. Setting `slices` to `auto` chooses a reasonable number for most data streams and indices. 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 `_update_by_query` just automates the manual process of creating 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 point above about distribution being uneven and you should conclude that using `max_docs` with `slices` might not result in exactly `max_docs` documents being updated. * 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. * Update performance scales linearly across available resources with the number of slices. Whether query or update performance dominates the runtime depends on the documents being reindexed and cluster resources. Refer to the linked documentation for examples of how to update documents using the `_update_by_query` API:
-  * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update-by-query | Elasticsearch API documentation}
+  * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-update-by-query | Elasticsearch API documentation}
   */
 export default function UpdateByQueryApi(this: That, params: T.UpdateByQueryRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.UpdateByQueryResponse>;
 export default function UpdateByQueryApi(this: That, params: T.UpdateByQueryRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.UpdateByQueryResponse, unknown>>;

package/lib/api/api/update_by_query_rethrottle.d.ts

@@ -5,7 +5,7 @@ interface That {
 }
 /**
   * Throttle an update by query operation. Change the number of requests per second for a particular update by query operation. Rethrottling that speeds up the query takes effect immediately but rethrotting that slows down the query takes effect after completing the current batch to prevent scroll timeouts.
-  * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update-by-query-rethrottle | Elasticsearch API documentation}
+  * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-update-by-query-rethrottle | Elasticsearch API documentation}
   */
 export default function UpdateByQueryRethrottleApi(this: That, params: T.UpdateByQueryRethrottleRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.UpdateByQueryRethrottleResponse>;
 export default function UpdateByQueryRethrottleApi(this: That, params: T.UpdateByQueryRethrottleRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.UpdateByQueryRethrottleResponse, unknown>>;

package/lib/api/api/watcher.d.ts

@@ -19,91 +19,91 @@ export default class Watcher {
     constructor(transport: Transport);
     /**
       * Acknowledge a watch. Acknowledging a watch enables you to manually throttle the execution of the watch's actions. The acknowledgement state of an action is stored in the `status.actions.<id>.ack.state` structure. IMPORTANT: If the specified watch is currently being executed, this API will return an error The reason for this behavior is to prevent overwriting the watch status from a watch execution. Acknowledging an action throttles further executions of that action until its `ack.state` is reset to `awaits_successful_execution`. This happens when the condition of the watch is not met (the condition evaluates to false). To demonstrate how throttling works in practice and how it can be configured for individual actions within a watch, refer to External documentation.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-ack-watch | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-ack-watch | Elasticsearch API documentation}
       */
     ackWatch(this: That, params: T.WatcherAckWatchRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherAckWatchResponse>;
     ackWatch(this: That, params: T.WatcherAckWatchRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherAckWatchResponse, unknown>>;
     ackWatch(this: That, params: T.WatcherAckWatchRequest, options?: TransportRequestOptions): Promise<T.WatcherAckWatchResponse>;
     /**
       * Activate a watch. A watch can be either active or inactive.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-activate-watch | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-activate-watch | Elasticsearch API documentation}
       */
     activateWatch(this: That, params: T.WatcherActivateWatchRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherActivateWatchResponse>;
     activateWatch(this: That, params: T.WatcherActivateWatchRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherActivateWatchResponse, unknown>>;
     activateWatch(this: That, params: T.WatcherActivateWatchRequest, options?: TransportRequestOptions): Promise<T.WatcherActivateWatchResponse>;
     /**
       * Deactivate a watch. A watch can be either active or inactive.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-deactivate-watch | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-deactivate-watch | Elasticsearch API documentation}
       */
     deactivateWatch(this: That, params: T.WatcherDeactivateWatchRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherDeactivateWatchResponse>;
     deactivateWatch(this: That, params: T.WatcherDeactivateWatchRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherDeactivateWatchResponse, unknown>>;
     deactivateWatch(this: That, params: T.WatcherDeactivateWatchRequest, options?: TransportRequestOptions): Promise<T.WatcherDeactivateWatchResponse>;
     /**
       * Delete a watch. When the watch is removed, the document representing the watch in the `.watches` index is gone and it will never be run again. Deleting a watch does not delete any watch execution records related to this watch from the watch history. IMPORTANT: Deleting a watch must be done by using only this API. Do not delete the watch directly from the `.watches` index using the Elasticsearch delete document API When Elasticsearch security features are enabled, make sure no write privileges are granted to anyone for the `.watches` index.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-delete-watch | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-delete-watch | Elasticsearch API documentation}
       */
     deleteWatch(this: That, params: T.WatcherDeleteWatchRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherDeleteWatchResponse>;
     deleteWatch(this: That, params: T.WatcherDeleteWatchRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherDeleteWatchResponse, unknown>>;
     deleteWatch(this: That, params: T.WatcherDeleteWatchRequest, options?: TransportRequestOptions): Promise<T.WatcherDeleteWatchResponse>;
     /**
       * Run a watch. This API can be used to force execution of the watch outside of its triggering logic or to simulate the watch execution for debugging purposes. For testing and debugging purposes, you also have fine-grained control on how the watch runs. You can run the watch without running all of its actions or alternatively by simulating them. You can also force execution by ignoring the watch condition and control whether a watch record would be written to the watch history after it runs. You can use the run watch API to run watches that are not yet registered by specifying the watch definition inline. This serves as great tool for testing and debugging your watches prior to adding them to Watcher. When Elasticsearch security features are enabled on your cluster, watches are run with the privileges of the user that stored the watches. If your user is allowed to read index `a`, but not index `b`, then the exact same set of rules will apply during execution of a watch. When using the run watch API, the authorization data of the user that called the API will be used as a base, instead of the information who stored the watch. Refer to the external documentation for examples of watch execution requests, including existing, customized, and inline watches.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-execute-watch | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-execute-watch | Elasticsearch API documentation}
       */
     executeWatch(this: That, params?: T.WatcherExecuteWatchRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherExecuteWatchResponse>;
     executeWatch(this: That, params?: T.WatcherExecuteWatchRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherExecuteWatchResponse, unknown>>;
     executeWatch(this: That, params?: T.WatcherExecuteWatchRequest, options?: TransportRequestOptions): Promise<T.WatcherExecuteWatchResponse>;
     /**
       * Get Watcher index settings. Get settings for the Watcher internal index (`.watches`). Only a subset of settings are shown, for example `index.auto_expand_replicas` and `index.number_of_replicas`.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-get-settings | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-get-settings | Elasticsearch API documentation}
       */
     getSettings(this: That, params?: T.WatcherGetSettingsRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherGetSettingsResponse>;
     getSettings(this: That, params?: T.WatcherGetSettingsRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherGetSettingsResponse, unknown>>;
     getSettings(this: That, params?: T.WatcherGetSettingsRequest, options?: TransportRequestOptions): Promise<T.WatcherGetSettingsResponse>;
     /**
       * Get a watch.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-get-watch | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-get-watch | Elasticsearch API documentation}
       */
     getWatch(this: That, params: T.WatcherGetWatchRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherGetWatchResponse>;
     getWatch(this: That, params: T.WatcherGetWatchRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherGetWatchResponse, unknown>>;
     getWatch(this: That, params: T.WatcherGetWatchRequest, options?: TransportRequestOptions): Promise<T.WatcherGetWatchResponse>;
     /**
       * Create or update a watch. When a watch is registered, a new document that represents the watch is added to the `.watches` index and its trigger is immediately registered with the relevant trigger engine. Typically for the `schedule` trigger, the scheduler is the trigger engine. IMPORTANT: You must use Kibana or this API to create a watch. Do not add a watch directly to the `.watches` index by using the Elasticsearch index API. If Elasticsearch security features are enabled, do not give users write privileges on the `.watches` index. When you add a watch you can also define its initial active state by setting the *active* parameter. When Elasticsearch security features are enabled, your watch can index or search only on indices for which the user that stored the watch has privileges. If the user is able to read index `a`, but not index `b`, the same will apply when the watch runs.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-put-watch | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-put-watch | Elasticsearch API documentation}
       */
     putWatch(this: That, params: T.WatcherPutWatchRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherPutWatchResponse>;
     putWatch(this: That, params: T.WatcherPutWatchRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherPutWatchResponse, unknown>>;
     putWatch(this: That, params: T.WatcherPutWatchRequest, options?: TransportRequestOptions): Promise<T.WatcherPutWatchResponse>;
     /**
       * Query watches. Get all registered watches in a paginated manner and optionally filter watches by a query. Note that only the `_id` and `metadata.*` fields are queryable or sortable.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-query-watches | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-query-watches | Elasticsearch API documentation}
       */
     queryWatches(this: That, params?: T.WatcherQueryWatchesRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherQueryWatchesResponse>;
     queryWatches(this: That, params?: T.WatcherQueryWatchesRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherQueryWatchesResponse, unknown>>;
     queryWatches(this: That, params?: T.WatcherQueryWatchesRequest, options?: TransportRequestOptions): Promise<T.WatcherQueryWatchesResponse>;
     /**
       * Start the watch service. Start the Watcher service if it is not already running.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-start | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-start | Elasticsearch API documentation}
       */
     start(this: That, params?: T.WatcherStartRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherStartResponse>;
     start(this: That, params?: T.WatcherStartRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherStartResponse, unknown>>;
     start(this: That, params?: T.WatcherStartRequest, options?: TransportRequestOptions): Promise<T.WatcherStartResponse>;
     /**
       * Get Watcher statistics. This API always returns basic metrics. You retrieve more metrics by using the metric parameter.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-stats | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-stats | Elasticsearch API documentation}
       */
     stats(this: That, params?: T.WatcherStatsRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherStatsResponse>;
     stats(this: That, params?: T.WatcherStatsRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherStatsResponse, unknown>>;
     stats(this: That, params?: T.WatcherStatsRequest, options?: TransportRequestOptions): Promise<T.WatcherStatsResponse>;
     /**
       * Stop the watch service. Stop the Watcher service if it is running.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-stop | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-stop | Elasticsearch API documentation}
       */
     stop(this: That, params?: T.WatcherStopRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherStopResponse>;
     stop(this: That, params?: T.WatcherStopRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherStopResponse, unknown>>;
     stop(this: That, params?: T.WatcherStopRequest, options?: TransportRequestOptions): Promise<T.WatcherStopResponse>;
     /**
       * Update Watcher index settings. Update settings for the Watcher internal index (`.watches`). Only a subset of settings can be modified. This includes `index.auto_expand_replicas`, `index.number_of_replicas`, `index.routing.allocation.exclude.*`, `index.routing.allocation.include.*` and `index.routing.allocation.require.*`. Modification of `index.routing.allocation.include._tier_preference` is an exception and is not allowed as the Watcher shards must always be in the `data_content` tier.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-watcher-update-settings | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-watcher-update-settings | Elasticsearch API documentation}
       */
     updateSettings(this: That, params?: T.WatcherUpdateSettingsRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.WatcherUpdateSettingsResponse>;
     updateSettings(this: That, params?: T.WatcherUpdateSettingsRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.WatcherUpdateSettingsResponse, unknown>>;

package/lib/api/api/xpack.d.ts

@@ -19,14 +19,14 @@ export default class Xpack {
     constructor(transport: Transport);
     /**
       * Get information. The information provided by the API includes: * Build information including the build number and timestamp. * License information about the currently installed license. * Feature information for the features that are currently enabled and available under the current license.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-info | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-info | Elasticsearch API documentation}
       */
     info(this: That, params?: T.XpackInfoRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.XpackInfoResponse>;
     info(this: That, params?: T.XpackInfoRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.XpackInfoResponse, unknown>>;
     info(this: That, params?: T.XpackInfoRequest, options?: TransportRequestOptions): Promise<T.XpackInfoResponse>;
     /**
       * Get usage information. Get information about the features that are currently enabled and available under the current license. The API also provides some usage statistics.
-      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-xpack | Elasticsearch API documentation}
+      * @see {@link https://www.elastic.co/docs/api/doc/elasticsearch/v9/group/endpoint-xpack | Elasticsearch API documentation}
       */
     usage(this: That, params?: T.XpackUsageRequest, options?: TransportRequestOptionsWithOutMeta): Promise<T.XpackUsageResponse>;
     usage(this: That, params?: T.XpackUsageRequest, options?: TransportRequestOptionsWithMeta): Promise<TransportResult<T.XpackUsageResponse, unknown>>;

package/lib/api/types.d.ts

@@ -26,8 +26,8 @@ export interface BulkOperationBase {
     _id?: Id;
     /** The name of the index or index alias to perform the action on. */
     _index?: IndexName;
-    /** A custom value used to route operations to a specific shard. */
-    routing?: Routing;
+    /** A custom value used to route operations to a specific shard, or multiple comma separated values. */
+    routing?: string;
     if_primary_term?: long;
     if_seq_no?: SequenceNumber;
     version?: VersionNumber;
@@ -2426,7 +2426,7 @@ export interface ReindexDestination {
       * If it is `keep`, the routing on the bulk request sent for each match is set to the routing on the match.
       * If it is `discard`, the routing on the bulk request sent for each match is set to `null`.
       * If it is `=value`, the routing on the bulk request sent for each match is set to all value specified after the equals sign (`=`). */
-    routing?: Routing;
+    routing?: string;
     /** The versioning to use for the indexing operation. */
     version_type?: VersionType;
 }
@@ -3253,7 +3253,7 @@ export interface SearchCompletionSuggestOption<TDocument = unknown> {
     fields?: Record<string, any>;
     _id?: string;
     _index?: IndexName;
-    _routing?: Routing;
+    _routing?: string;
     _score?: double;
     _source?: TDocument;
     text: string;
@@ -5380,6 +5380,7 @@ export interface KnnSearch {
     inner_hits?: SearchInnerHits;
     /** Apply oversampling and rescoring to quantized vectors */
     rescore_vector?: RescoreVector;
+    _name?: string;
 }
 export interface LatLonGeoLocation {
     /** Latitude */
@@ -7127,13 +7128,20 @@ export interface AggregationsMultiBucketAggregateBase<TBucket = unknown> extends
 export interface AggregationsMultiBucketBase {
     doc_count: long;
 }
-export interface AggregationsMultiTermLookup {
-    /** A fields from which to retrieve terms. */
-    field: Field;
+interface AggregationsMultiTermLookupCommonProps {
     /** The value to apply to documents that do not have a value.
       * By default, documents without a value are ignored. */
     missing?: AggregationsMissing;
 }
+interface AggregationsMultiTermLookupExclusiveProps {
+    /** A field from which to retrieve terms.
+      * It is required if `script` is not provided. */
+    field?: Field;
+    /** A script to calculate terms to aggregate on.
+      * It is required if `field` is not provided. */
+    script?: Script | ScriptSource;
+}
+export type AggregationsMultiTermLookup = AggregationsMultiTermLookupCommonProps & ExactlyOne<AggregationsMultiTermLookupExclusiveProps>;
 export interface AggregationsMultiTermsAggregate extends AggregationsTermsAggregateBase<AggregationsMultiTermsBucket> {
 }
 export interface AggregationsMultiTermsAggregation extends AggregationsBucketAggregationBase {
@@ -9569,7 +9577,7 @@ export interface QueryDslFieldLookup {
     /** Name of the field. */
     path?: Field;
     /** Custom routing value. */
-    routing?: Routing;
+    routing?: string;
 }
 export type QueryDslFieldValueFactorModifier = 'none' | 'log' | 'log1p' | 'log2p' | 'ln' | 'ln1p' | 'ln2p' | 'square' | 'sqrt' | 'reciprocal';
 export interface QueryDslFieldValueFactorScoreFunction {
@@ -10015,7 +10023,7 @@ export interface QueryDslMoreLikeThisQuery extends QueryDslQueryBase {
     min_term_freq?: integer;
     /** The minimum word length below which the terms are ignored. */
     min_word_length?: integer;
-    routing?: Routing;
+    routing?: string;
     /** An array of stop words.
       * Any word in this set is ignored. */
     stop_words?: AnalysisStopWords;
@@ -10106,7 +10114,7 @@ export interface QueryDslPercolateQuery extends QueryDslQueryBase {
     /** Preference used to fetch document to percolate. */
     preference?: string;
     /** Routing used to fetch document to percolate. */
-    routing?: Routing;
+    routing?: string;
     /** The expected version of a stored document to percolate. */
     version?: VersionNumber;
 }
@@ -10602,7 +10610,7 @@ export interface QueryDslTermsLookup {
     index: IndexName;
     id: Id;
     path: Field;
-    routing?: Routing;
+    routing?: string;
 }
 export interface QueryDslTermsQueryKeys extends QueryDslQueryBase {
 }
@@ -20270,6 +20278,15 @@ export interface EsqlAsyncQueryRequest extends RequestBase {
     /** Indicates whether the query and its results are stored in the cluster.
       * If false, the query and its results are stored in the cluster only if the request does not complete during the period set by the `wait_for_completion_timeout` parameter. */
     keep_on_completion?: boolean;
+    /** Specifies a subset of projects to target using project
+      * metadata tags in a subset of Lucene query syntax.
+      * Allowed Lucene queries: the _alias tag and a single value (possibly wildcarded).
+      * Examples:
+      *  _alias:my-project
+      *  _alias:_origin
+      *  _alias:*pr*
+      * Supported in serverless only. */
+    project_routing?: ProjectRouting;
     /** All values in `body` will be added to the request body. */
     body?: string | ({
         [key: string]: any;
@@ -20290,6 +20307,7 @@ export interface EsqlAsyncQueryRequest extends RequestBase {
         wait_for_completion_timeout?: never;
         keep_alive?: never;
         keep_on_completion?: never;
+        project_routing?: never;
     });
     /** All values in `querystring` will be added to the request querystring. */
     querystring?: {
@@ -20311,6 +20329,7 @@ export interface EsqlAsyncQueryRequest extends RequestBase {
         wait_for_completion_timeout?: never;
         keep_alive?: never;
         keep_on_completion?: never;
+        project_routing?: never;
     };
 }
 export type EsqlAsyncQueryResponse = EsqlAsyncEsqlResult;
@@ -20540,6 +20559,15 @@ export interface EsqlQueryRequest extends RequestBase {
       * count.
       * This is similar to `include_ccs_metadata`, but it also returns metadata when the query is not CCS/CPS */
     include_execution_metadata?: boolean;
+    /** Specifies a subset of projects to target using project
+      * metadata tags in a subset of Lucene query syntax.
+      * Allowed Lucene queries: the _alias tag and a single value (possibly wildcarded).
+      * Examples:
+      *  _alias:my-project
+      *  _alias:_origin
+      *  _alias:*pr*
+      * Supported in serverless only. */
+    project_routing?: ProjectRouting;
     /** All values in `body` will be added to the request body. */
     body?: string | ({
         [key: string]: any;
@@ -20557,6 +20585,7 @@ export interface EsqlQueryRequest extends RequestBase {
         tables?: never;
         include_ccs_metadata?: never;
         include_execution_metadata?: never;
+        project_routing?: never;
     });
     /** All values in `querystring` will be added to the request querystring. */
     querystring?: {
@@ -20575,6 +20604,7 @@ export interface EsqlQueryRequest extends RequestBase {
         tables?: never;
         include_ccs_metadata?: never;
         include_execution_metadata?: never;
+        project_routing?: never;
     };
 }
 export type EsqlQueryResponse = EsqlEsqlResult;
@@ -21597,17 +21627,17 @@ export interface IndicesAlias {
     filter?: QueryDslQueryContainer;
     /** Value used to route indexing operations to a specific shard.
       * If specified, this overwrites the `routing` value for indexing operations. */
-    index_routing?: Routing;
+    index_routing?: string;
     /** If `true`, the alias is hidden.
       * All indices for the alias must have the same `is_hidden` value. */
     is_hidden?: boolean;
     /** If `true`, the index is the write index for the alias. */
     is_write_index?: boolean;
     /** Value used to route indexing and search operations to a specific shard. */
-    routing?: Routing;
+    routing?: string;
     /** Value used to route search operations to a specific shard.
       * If specified, this overwrites the `routing` value for search operations. */
-    search_routing?: Routing;
+    search_routing?: string;
 }
 export interface IndicesAliasDefinition {
     /** Query used to limit documents the alias can access. */
@@ -24320,7 +24350,7 @@ export interface IndicesPutAliasRequest extends RequestBase {
     /** Value used to route indexing operations to a specific shard.
       * If specified, this overwrites the `routing` value for indexing operations.
       * Data stream aliases don’t support this parameter. */
-    index_routing?: Routing;
+    index_routing?: string;
     /** If `true`, sets the write index or data stream for the alias.
       * If an alias points to multiple indices or data streams and `is_write_index` isn’t set, the alias rejects write requests.
       * If an index alias points to one index and `is_write_index` isn’t set, the index automatically acts as the write index.
@@ -24328,11 +24358,11 @@ export interface IndicesPutAliasRequest extends RequestBase {
     is_write_index?: boolean;
     /** Value used to route indexing and search operations to a specific shard.
       * Data stream aliases don’t support this parameter. */
-    routing?: Routing;
+    routing?: string;
     /** Value used to route search operations to a specific shard.
       * If specified, this overwrites the `routing` value for search operations.
       * Data stream aliases don’t support this parameter. */
-    search_routing?: Routing;
+    search_routing?: string;
     /** All values in `body` will be added to the request body. */
     body?: string | ({
         [key: string]: any;
@@ -26054,18 +26084,18 @@ export interface IndicesUpdateAliasesAddAction {
     /** Value used to route indexing operations to a specific shard.
       * If specified, this overwrites the `routing` value for indexing operations.
       * Data stream aliases don’t support this parameter. */
-    index_routing?: Routing;
+    index_routing?: string;
     /** If `true`, the alias is hidden. */
     is_hidden?: boolean;
     /** If `true`, sets the write index or data stream for the alias. */
     is_write_index?: boolean;
     /** Value used to route indexing and search operations to a specific shard.
       * Data stream aliases don’t support this parameter. */
-    routing?: Routing;
+    routing?: string;
     /** Value used to route search operations to a specific shard.
       * If specified, this overwrites the `routing` value for search operations.
       * Data stream aliases don’t support this parameter. */
-    search_routing?: Routing;
+    search_routing?: string;
     /** If `true`, the alias must exist to perform the action. */
     must_exist?: boolean;
 }
@@ -27844,9 +27874,10 @@ export interface InferenceDeleteRequest extends RequestBase {
 }
 export type InferenceDeleteResponse = InferenceDeleteInferenceEndpointResult;
 export interface InferenceGetRequest extends RequestBase {
-    /** The task type */
+    /** The task type of the endpoint to return */
     task_type?: InferenceTaskType;
-    /** The inference Id */
+    /** The inference Id of the endpoint to return. Using `_all` or `*` will return all endpoints with the specified
+      * `task_type` if one is specified, or all endpoints for all task types if no `task_type` is specified */
     inference_id?: Id;
     /** All values in `body` will be added to the request body. */
     body?: string | ({
@@ -29835,7 +29866,7 @@ interface IngestProcessorContainerExclusiveProps {
     /** Joins each element of an array into a single string using a separator character between each element.
       * Throws an error when the field is not an array. */
     join?: IngestJoinProcessor;
-    /** Converts a JSON string into a structured JSON object. */
+    /** Parses a string containing JSON data into a structured object, string, or other value. */
     json?: IngestJsonProcessor;
     /** This processor helps automatically parse messages (or specific event fields) which are of the `foo=bar` variety. */
     kv?: IngestKeyValueProcessor;
@@ -37568,9 +37599,14 @@ export interface NodesStatsResponseBase extends NodesNodesResponseBase {
     nodes: Record<string, NodesStats>;
 }
 export interface NodesUsageNodeUsage {
+    /** The total number of times each REST endpoint has been called on this node since the last restart.
+      *  Note that the REST endpoint names are not considered stable. */
     rest_actions: Record<string, integer>;
+    /** The timestamp for when the collection of these statistics started. */
     since: EpochTime<UnitMillis>;
+    /** The timestamp for when these statistics were collected. */
     timestamp: EpochTime<UnitMillis>;
+    /** The total number of times search aggregations have been called on this node since the last restart. */
     aggregations: Record<string, any>;
 }
 export type NodesUsageNodesUsageMetric = '_all' | 'rest_actions' | 'aggregations';

package/lib/client.js

@@ -17,19 +17,16 @@ const helpers_1 = tslib_1.__importDefault(require("./helpers"));
 const api_1 = tslib_1.__importDefault(require("./api"));
 const symbols_1 = require("./symbols");
 Object.defineProperty(exports, "kAcceptedParams", { enumerable: true, get: function () { return symbols_1.kAcceptedParams; } });
-/* eslint-disable @typescript-eslint/no-var-requires */
-const packageJson = require('../package.json');
-const transportPackageJson = require('@elastic/transport/package.json');
-/* eslint-enable @typescript-eslint/no-var-requires */
+const version_generated_1 = require("./version.generated");
 const kChild = Symbol('elasticsearchjs-child');
 const kInitialOptions = Symbol('elasticsearchjs-initial-options');
-let clientVersion = packageJson.version;
+let clientVersion = version_generated_1.clientVersion;
 /* istanbul ignore next */
 if (clientVersion.includes('-')) {
     // clean prerelease
     clientVersion = clientVersion.slice(0, clientVersion.indexOf('-')) + 'p';
 }
-let transportVersion = transportPackageJson.version; // eslint-disable-line
+let transportVersion = version_generated_1.transportVersion;
 /* istanbul ignore next */
 if (transportVersion.includes('-')) {
     // clean prerelease