diff --git a/docs/index.asciidoc b/docs/index.asciidoc index 51206f0b0..7a438c11d 100644 --- a/docs/index.asciidoc +++ b/docs/index.asciidoc @@ -17,7 +17,7 @@ include::integrations.asciidoc[] include::observability.asciidoc[] include::transport.asciidoc[] include::typescript.asciidoc[] -include::reference.asciidoc[] +include::reference-main-index.asciidoc[] include::examples/index.asciidoc[] include::helpers.asciidoc[] include::redirects.asciidoc[] diff --git a/docs/reference-async_search-delete.asciidoc b/docs/reference-async_search-delete.asciidoc new file mode 100644 index 000000000..ea7b44eff --- /dev/null +++ b/docs/reference-async_search-delete.asciidoc @@ -0,0 +1,60 @@ +[[reference-async_search-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.asyncSearch.delete + +Delete an async search. If the asynchronous search is still running, it is cancelled. Otherwise, the saved search results are deleted. If the Elasticsearch security features are enabled, the deletion of a specific async search is restricted to: the authenticated user that submitted the original search request; users that have the `cancel_task` cluster privilege. + +{ref}/async-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AsyncSearchDeleteRequest, options?): Promise +---- + +[discrete] +===== `AsyncSearchDeleteRequest` + +[source,ts] +---- +interface AsyncSearchDeleteRequest extends <> { + id: <> +} +---- + +[discrete] +===== `AsyncSearchDeleteResponse` + +[source,ts] +---- +type AsyncSearchDeleteResponse = <> +---- + diff --git a/docs/reference-async_search-get.asciidoc b/docs/reference-async_search-get.asciidoc new file mode 100644 index 000000000..a31dfbcf9 --- /dev/null +++ b/docs/reference-async_search-get.asciidoc @@ -0,0 +1,63 @@ +[[reference-async_search-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.asyncSearch.get + +Get async search results. Retrieve the results of a previously submitted asynchronous search request. If the Elasticsearch security features are enabled, access to the results of a specific async search is restricted to the user or API key that submitted it. + +{ref}/async-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AsyncSearchGetRequest, options?): Promise +---- + +[discrete] +===== `AsyncSearchGetRequest` + +[source,ts] +---- +interface AsyncSearchGetRequest extends <> { + id: <> + keep_alive?: <> + typed_keys?: boolean + wait_for_completion_timeout?: <> +} +---- + +[discrete] +===== `AsyncSearchGetResponse` + +[source,ts] +---- +type AsyncSearchGetResponse>, AggregationsAggregate>> = AsyncSearchAsyncSearchDocumentResponseBase +---- + diff --git a/docs/reference-async_search-status.asciidoc b/docs/reference-async_search-status.asciidoc new file mode 100644 index 000000000..f283fc939 --- /dev/null +++ b/docs/reference-async_search-status.asciidoc @@ -0,0 +1,60 @@ +[[reference-async_search-status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.asyncSearch.status + +Get the async search status. Get the status of a previously submitted async search request given its identifier, without retrieving search results. If the Elasticsearch security features are enabled, use of this API is restricted to the `monitoring_user` role. + +{ref}/async-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AsyncSearchStatusRequest, options?): Promise +---- + +[discrete] +===== `AsyncSearchStatusRequest` + +[source,ts] +---- +interface AsyncSearchStatusRequest extends <> { + id: <> +} +---- + +[discrete] +===== `AsyncSearchStatusResponse` + +[source,ts] +---- +type AsyncSearchStatusResponse = AsyncSearchStatusStatusResponseBase +---- + diff --git a/docs/reference-async_search-submit.asciidoc b/docs/reference-async_search-submit.asciidoc new file mode 100644 index 000000000..db079d085 --- /dev/null +++ b/docs/reference-async_search-submit.asciidoc @@ -0,0 +1,126 @@ +[[reference-async_search-submit]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.asyncSearch.submit + +Run an async search. When the primary sort of the results is an indexed field, shards get sorted based on minimum and maximum value that they hold for that field. Partial results become available following the sort criteria that was requested. Warning: Asynchronous search does not support scroll or search requests that include only the suggest section. By default, Elasticsearch does not allow you to store an async search response larger than 10Mb and an attempt to do this results in an error. The maximum allowed size for a stored async search response can be set by changing the `search.max_async_search_response_size` cluster level setting. + +{ref}/async-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AsyncSearchSubmitRequest, options?): Promise +---- + +[discrete] +===== `AsyncSearchSubmitRequest` + +[source,ts] +---- +interface AsyncSearchSubmitRequest extends <> { + index?: <> + wait_for_completion_timeout?: <> + keep_on_completion?: boolean + keep_alive?: <> + allow_no_indices?: boolean + allow_partial_search_results?: boolean + analyzer?: string + analyze_wildcard?: boolean + batched_reduce_size?: <> + ccs_minimize_roundtrips?: boolean + default_operator?: QueryDslOperator + df?: string + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + lenient?: boolean + max_concurrent_shard_requests?: <> + min_compatible_shard_node?: <> + preference?: string + pre_filter_shard_size?: <> + request_cache?: boolean + routing?: <> + scroll?: <> + search_type?: <> + suggest_field?: <> + suggest_mode?: <> + suggest_size?: <> + suggest_text?: string + typed_keys?: boolean + rest_total_hits_as_int?: boolean + _source_excludes?: <> + _source_includes?: <> + q?: string + aggregations?: Record + /** @alias aggregations */ + aggs?: Record + collapse?: SearchFieldCollapse + explain?: boolean + ext?: Record + from?: <> + highlight?: SearchHighlight + track_total_hits?: SearchTrackHits + indices_boost?: Record<<>, <>>[] + docvalue_fields?: (QueryDslFieldAndFormat | <>)[] + knn?: <> | <>[] + min_score?: <> + post_filter?: QueryDslQueryContainer + profile?: boolean + query?: QueryDslQueryContainer + rescore?: SearchRescore | SearchRescore[] + script_fields?: Record>> + search_after?: <> + size?: <> + slice?: <> + sort?: <> + _source?: SearchSourceConfig + fields?: (QueryDslFieldAndFormat | <>)[] + suggest?: SearchSuggester + terminate_after?: <> + timeout?: string + track_scores?: boolean + version?: boolean + seq_no_primary_term?: boolean + stored_fields?: <> + pit?: SearchPointInTimeReference + runtime_mappings?: MappingRuntimeFields + stats?: string[] +} +---- + +[discrete] +===== `AsyncSearchSubmitResponse` + +[source,ts] +---- +type AsyncSearchSubmitResponse>, AggregationsAggregate>> = AsyncSearchAsyncSearchDocumentResponseBase +---- + diff --git a/docs/reference-autoscaling-delete_autoscaling_policy.asciidoc b/docs/reference-autoscaling-delete_autoscaling_policy.asciidoc new file mode 100644 index 000000000..9ad26d828 --- /dev/null +++ b/docs/reference-autoscaling-delete_autoscaling_policy.asciidoc @@ -0,0 +1,60 @@ +[[reference-autoscaling-delete_autoscaling_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.autoscaling.deleteAutoscalingPolicy + +Delete an autoscaling policy. NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. + +{ref}/autoscaling-delete-autoscaling-policy.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AutoscalingDeleteAutoscalingPolicyRequest, options?): Promise +---- + +[discrete] +===== `AutoscalingDeleteAutoscalingPolicyRequest` + +[source,ts] +---- +interface AutoscalingDeleteAutoscalingPolicyRequest extends <> { + name: <> +} +---- + +[discrete] +===== `AutoscalingDeleteAutoscalingPolicyResponse` + +[source,ts] +---- +type AutoscalingDeleteAutoscalingPolicyResponse = <> +---- + diff --git a/docs/reference-autoscaling-get_autoscaling_capacity.asciidoc b/docs/reference-autoscaling-get_autoscaling_capacity.asciidoc new file mode 100644 index 000000000..ea41b2413 --- /dev/null +++ b/docs/reference-autoscaling-get_autoscaling_capacity.asciidoc @@ -0,0 +1,61 @@ +[[reference-autoscaling-get_autoscaling_capacity]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.autoscaling.getAutoscalingCapacity + +Get the autoscaling capacity. NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. This API gets the current autoscaling capacity based on the configured autoscaling policy. It will return information to size the cluster appropriately to the current workload. The `required_capacity` is calculated as the maximum of the `required_capacity` result of all individual deciders that are enabled for the policy. The operator should verify that the `current_nodes` match the operator’s knowledge of the cluster to avoid making autoscaling decisions based on stale or incomplete information. The response contains decider-specific information you can use to diagnose how and why autoscaling determined a certain capacity was required. This information is provided for diagnosis only. Do not use this information to make autoscaling decisions. + +{ref}/autoscaling-get-autoscaling-capacity.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AutoscalingGetAutoscalingCapacityRequest, options?): Promise +---- + +[discrete] +===== `AutoscalingGetAutoscalingCapacityRequest` + +[source,ts] +---- +interface AutoscalingGetAutoscalingCapacityRequest extends <> { +} +---- + +[discrete] +===== `AutoscalingGetAutoscalingCapacityResponse` + +[source,ts] +---- +interface AutoscalingGetAutoscalingCapacityResponse { + policies: Record +} +---- + diff --git a/docs/reference-autoscaling-get_autoscaling_policy.asciidoc b/docs/reference-autoscaling-get_autoscaling_policy.asciidoc new file mode 100644 index 000000000..93a759224 --- /dev/null +++ b/docs/reference-autoscaling-get_autoscaling_policy.asciidoc @@ -0,0 +1,60 @@ +[[reference-autoscaling-get_autoscaling_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.autoscaling.getAutoscalingPolicy + +Get an autoscaling policy. NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. + +{ref}/autoscaling-get-autoscaling-capacity.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AutoscalingGetAutoscalingPolicyRequest, options?): Promise +---- + +[discrete] +===== `AutoscalingGetAutoscalingPolicyRequest` + +[source,ts] +---- +interface AutoscalingGetAutoscalingPolicyRequest extends <> { + name: <> +} +---- + +[discrete] +===== `AutoscalingGetAutoscalingPolicyResponse` + +[source,ts] +---- +type AutoscalingGetAutoscalingPolicyResponse = AutoscalingAutoscalingPolicy +---- + diff --git a/docs/reference-autoscaling-put_autoscaling_policy.asciidoc b/docs/reference-autoscaling-put_autoscaling_policy.asciidoc new file mode 100644 index 000000000..9b7d4718f --- /dev/null +++ b/docs/reference-autoscaling-put_autoscaling_policy.asciidoc @@ -0,0 +1,61 @@ +[[reference-autoscaling-put_autoscaling_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.autoscaling.putAutoscalingPolicy + +Create or update an autoscaling policy. NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. + +{ref}/autoscaling-put-autoscaling-policy.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(AutoscalingPutAutoscalingPolicyRequest, options?): Promise +---- + +[discrete] +===== `AutoscalingPutAutoscalingPolicyRequest` + +[source,ts] +---- +interface AutoscalingPutAutoscalingPolicyRequest extends <> { + name: <> + policy?: AutoscalingAutoscalingPolicy +} +---- + +[discrete] +===== `AutoscalingPutAutoscalingPolicyResponse` + +[source,ts] +---- +type AutoscalingPutAutoscalingPolicyResponse = <> +---- + diff --git a/docs/reference-bulk.asciidoc b/docs/reference-bulk.asciidoc new file mode 100644 index 000000000..d1f984a70 --- /dev/null +++ b/docs/reference-bulk.asciidoc @@ -0,0 +1,75 @@ +[[reference-bulk]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.bulk + +Bulk index or delete documents. Performs multiple indexing or delete operations in a single API call. This reduces overhead and can greatly increase indexing speed. + +{ref}/docs-bulk.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(BulkRequest, options?): Promise +---- + +[discrete] +===== `BulkRequest` + +[source,ts] +---- +interface BulkRequest extends <> { + index?: <> + pipeline?: string + refresh?: <> + routing?: <> + _source?: SearchSourceConfigParam + _source_excludes?: <> + _source_includes?: <> + timeout?: <> + wait_for_active_shards?: <> + require_alias?: boolean + operations?: (BulkOperationContainer | BulkUpdateAction | TDocument)[] +} +---- + +[discrete] +===== `BulkResponse` + +[source,ts] +---- +interface BulkResponse { + errors: boolean + items: Partial>[] + took: <> + ingest_took?: <> +} +---- + diff --git a/docs/reference-cat-aliases.asciidoc b/docs/reference-cat-aliases.asciidoc new file mode 100644 index 000000000..e324d30d1 --- /dev/null +++ b/docs/reference-cat-aliases.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-aliases]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.aliases + +Get aliases. Retrieves the cluster’s index aliases, including filter and routing information. The API does not return data stream aliases. CAT APIs are only intended for human consumption using the command line or the Kibana console. They are not intended for use by applications. For application consumption, use the aliases API. + +{ref}/cat-alias.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatAliasesRequest, options?): Promise +---- + +[discrete] +===== `CatAliasesRequest` + +[source,ts] +---- +interface CatAliasesRequest extends CatCatRequestBase { + name?: <> + expand_wildcards?: <> +} +---- + +[discrete] +===== `CatAliasesResponse` + +[source,ts] +---- +type CatAliasesResponse = CatAliasesAliasesRecord[] +---- + diff --git a/docs/reference-cat-allocation.asciidoc b/docs/reference-cat-allocation.asciidoc new file mode 100644 index 000000000..13f2a3b6b --- /dev/null +++ b/docs/reference-cat-allocation.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-allocation]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.allocation + +Provides a snapshot of the number of shards allocated to each data node and their disk space. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. + +{ref}/cat-allocation.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatAllocationRequest, options?): Promise +---- + +[discrete] +===== `CatAllocationRequest` + +[source,ts] +---- +interface CatAllocationRequest extends CatCatRequestBase { + node_id?: <> + bytes?: <> +} +---- + +[discrete] +===== `CatAllocationResponse` + +[source,ts] +---- +type CatAllocationResponse = CatAllocationAllocationRecord[] +---- + diff --git a/docs/reference-cat-component_templates.asciidoc b/docs/reference-cat-component_templates.asciidoc new file mode 100644 index 000000000..bc52e218e --- /dev/null +++ b/docs/reference-cat-component_templates.asciidoc @@ -0,0 +1,60 @@ +[[reference-cat-component_templates]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.componentTemplates + +Get component templates. Returns information about component templates in a cluster. Component templates are building blocks for constructing index templates that specify index mappings, settings, and aliases. CAT APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the get component template API. + +{ref}/cat-component-templates.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatComponentTemplatesRequest, options?): Promise +---- + +[discrete] +===== `CatComponentTemplatesRequest` + +[source,ts] +---- +interface CatComponentTemplatesRequest extends CatCatRequestBase { + name?: string +} +---- + +[discrete] +===== `CatComponentTemplatesResponse` + +[source,ts] +---- +type CatComponentTemplatesResponse = CatComponentTemplatesComponentTemplate[] +---- + diff --git a/docs/reference-cat-count.asciidoc b/docs/reference-cat-count.asciidoc new file mode 100644 index 000000000..bdec787cf --- /dev/null +++ b/docs/reference-cat-count.asciidoc @@ -0,0 +1,60 @@ +[[reference-cat-count]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.count + +Get a document count. Provides quick access to a document count for a data stream, an index, or an entire cluster. The document count only includes live documents, not deleted documents which have not yet been removed by the merge process. CAT APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the count API. + +{ref}/cat-count.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatCountRequest, options?): Promise +---- + +[discrete] +===== `CatCountRequest` + +[source,ts] +---- +interface CatCountRequest extends CatCatRequestBase { + index?: <> +} +---- + +[discrete] +===== `CatCountResponse` + +[source,ts] +---- +type CatCountResponse = CatCountCountRecord[] +---- + diff --git a/docs/reference-cat-fielddata.asciidoc b/docs/reference-cat-fielddata.asciidoc new file mode 100644 index 000000000..e54098ff6 --- /dev/null +++ b/docs/reference-cat-fielddata.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-fielddata]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.fielddata + +Returns the amount of heap memory currently used by the field data cache on every data node in the cluster. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes stats API. + +{ref}/cat-fielddata.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatFielddataRequest, options?): Promise +---- + +[discrete] +===== `CatFielddataRequest` + +[source,ts] +---- +interface CatFielddataRequest extends CatCatRequestBase { + fields?: <> + bytes?: <> +} +---- + +[discrete] +===== `CatFielddataResponse` + +[source,ts] +---- +type CatFielddataResponse = CatFielddataFielddataRecord[] +---- + diff --git a/docs/reference-cat-health.asciidoc b/docs/reference-cat-health.asciidoc new file mode 100644 index 000000000..c918c3ad9 --- /dev/null +++ b/docs/reference-cat-health.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-health]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.health + +Returns the health status of a cluster, similar to the cluster health API. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the cluster health API. This API is often used to check malfunctioning clusters. To help you track cluster health alongside log files and alerting systems, the API returns timestamps in two formats: `HH:MM:SS`, which is human-readable but includes no date information; `Unix epoch time`, which is machine-sortable and includes date information. The latter format is useful for cluster recoveries that take multiple days. You can use the cat health API to verify cluster health across multiple nodes. You also can use the API to track the recovery of a large cluster over a longer period of time. + +{ref}/cat-health.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatHealthRequest, options?): Promise +---- + +[discrete] +===== `CatHealthRequest` + +[source,ts] +---- +interface CatHealthRequest extends CatCatRequestBase { + time?: <> + ts?: boolean +} +---- + +[discrete] +===== `CatHealthResponse` + +[source,ts] +---- +type CatHealthResponse = CatHealthHealthRecord[] +---- + diff --git a/docs/reference-cat-help.asciidoc b/docs/reference-cat-help.asciidoc new file mode 100644 index 000000000..d240a6b1e --- /dev/null +++ b/docs/reference-cat-help.asciidoc @@ -0,0 +1,59 @@ +[[reference-cat-help]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.help + +Get CAT help. Returns help for the CAT APIs. + +{ref}/cat.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatHelpRequest, options?): Promise +---- + +[discrete] +===== `CatHelpRequest` + +[source,ts] +---- +interface CatHelpRequest extends CatCatRequestBase { +} +---- + +[discrete] +===== `CatHelpResponse` + +[source,ts] +---- +type CatHelpResponse = CatHelpHelpRecord[] +---- + diff --git a/docs/reference-cat-indices.asciidoc b/docs/reference-cat-indices.asciidoc new file mode 100644 index 000000000..712e2dd69 --- /dev/null +++ b/docs/reference-cat-indices.asciidoc @@ -0,0 +1,66 @@ +[[reference-cat-indices]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.indices + +Get index information. Returns high-level information about indices in a cluster, including backing indices for data streams. Use this request to get the following information for each index in a cluster: - shard count - document count - deleted document count - primary store size - total store size of all shards, including shard replicas These metrics are retrieved directly from Lucene, which Elasticsearch uses internally to power indexing and search. As a result, all document counts include hidden nested documents. To get an accurate count of Elasticsearch documents, use the cat count or count APIs. CAT APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use an index endpoint. + +{ref}/cat-indices.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatIndicesRequest, options?): Promise +---- + +[discrete] +===== `CatIndicesRequest` + +[source,ts] +---- +interface CatIndicesRequest extends CatCatRequestBase { + index?: <> + bytes?: <> + expand_wildcards?: <> + health?: <> + include_unloaded_segments?: boolean + pri?: boolean + time?: <> +} +---- + +[discrete] +===== `CatIndicesResponse` + +[source,ts] +---- +type CatIndicesResponse = CatIndicesIndicesRecord[] +---- + diff --git a/docs/reference-cat-master.asciidoc b/docs/reference-cat-master.asciidoc new file mode 100644 index 000000000..cddacfc85 --- /dev/null +++ b/docs/reference-cat-master.asciidoc @@ -0,0 +1,59 @@ +[[reference-cat-master]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.master + +Returns information about the master node, including the ID, bound IP address, and name. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. + +{ref}/cat-master.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatMasterRequest, options?): Promise +---- + +[discrete] +===== `CatMasterRequest` + +[source,ts] +---- +interface CatMasterRequest extends CatCatRequestBase { +} +---- + +[discrete] +===== `CatMasterResponse` + +[source,ts] +---- +type CatMasterResponse = CatMasterMasterRecord[] +---- + diff --git a/docs/reference-cat-ml_data_frame_analytics.asciidoc b/docs/reference-cat-ml_data_frame_analytics.asciidoc new file mode 100644 index 000000000..5f6d2565b --- /dev/null +++ b/docs/reference-cat-ml_data_frame_analytics.asciidoc @@ -0,0 +1,65 @@ +[[reference-cat-ml_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.mlDataFrameAnalytics + +Get data frame analytics jobs. Returns configuration and usage information about data frame analytics jobs. CAT APIs are only intended for human consumption using the Kibana console or command line. They are not intended for use by applications. For application consumption, use the get data frame analytics jobs statistics API. + +{ref}/cat-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatMlDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `CatMlDataFrameAnalyticsRequest` + +[source,ts] +---- +interface CatMlDataFrameAnalyticsRequest extends CatCatRequestBase { + id?: <> + allow_no_match?: boolean + bytes?: <> + h?: CatCatDfaColumns + s?: CatCatDfaColumns + time?: <> +} +---- + +[discrete] +===== `CatMlDataFrameAnalyticsResponse` + +[source,ts] +---- +type CatMlDataFrameAnalyticsResponse = CatMlDataFrameAnalyticsDataFrameAnalyticsRecord[] +---- + diff --git a/docs/reference-cat-ml_datafeeds.asciidoc b/docs/reference-cat-ml_datafeeds.asciidoc new file mode 100644 index 000000000..ee0b55e05 --- /dev/null +++ b/docs/reference-cat-ml_datafeeds.asciidoc @@ -0,0 +1,64 @@ +[[reference-cat-ml_datafeeds]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.mlDatafeeds + +Get datafeeds. Returns configuration and usage information about datafeeds. This API returns a maximum of 10,000 datafeeds. If the Elasticsearch security features are enabled, you must have `monitor_ml`, `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. CAT APIs are only intended for human consumption using the Kibana console or command line. They are not intended for use by applications. For application consumption, use the get datafeed statistics API. + +{ref}/cat-datafeeds.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatMlDatafeedsRequest, options?): Promise +---- + +[discrete] +===== `CatMlDatafeedsRequest` + +[source,ts] +---- +interface CatMlDatafeedsRequest extends CatCatRequestBase { + datafeed_id?: <> + allow_no_match?: boolean + h?: CatCatDatafeedColumns + s?: CatCatDatafeedColumns + time?: <> +} +---- + +[discrete] +===== `CatMlDatafeedsResponse` + +[source,ts] +---- +type CatMlDatafeedsResponse = CatMlDatafeedsDatafeedsRecord[] +---- + diff --git a/docs/reference-cat-ml_jobs.asciidoc b/docs/reference-cat-ml_jobs.asciidoc new file mode 100644 index 000000000..713621775 --- /dev/null +++ b/docs/reference-cat-ml_jobs.asciidoc @@ -0,0 +1,65 @@ +[[reference-cat-ml_jobs]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.mlJobs + +Get anomaly detection jobs. Returns configuration and usage information for anomaly detection jobs. This API returns a maximum of 10,000 jobs. If the Elasticsearch security features are enabled, you must have `monitor_ml`, `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. CAT APIs are only intended for human consumption using the Kibana console or command line. They are not intended for use by applications. For application consumption, use the get anomaly detection job statistics API. + +{ref}/cat-anomaly-detectors.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatMlJobsRequest, options?): Promise +---- + +[discrete] +===== `CatMlJobsRequest` + +[source,ts] +---- +interface CatMlJobsRequest extends CatCatRequestBase { + job_id?: <> + allow_no_match?: boolean + bytes?: <> + h?: CatCatAnonalyDetectorColumns + s?: CatCatAnonalyDetectorColumns + time?: <> +} +---- + +[discrete] +===== `CatMlJobsResponse` + +[source,ts] +---- +type CatMlJobsResponse = CatMlJobsJobsRecord[] +---- + diff --git a/docs/reference-cat-ml_trained_models.asciidoc b/docs/reference-cat-ml_trained_models.asciidoc new file mode 100644 index 000000000..74aebc295 --- /dev/null +++ b/docs/reference-cat-ml_trained_models.asciidoc @@ -0,0 +1,66 @@ +[[reference-cat-ml_trained_models]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.mlTrainedModels + +Get trained models. Returns configuration and usage information about inference trained models. CAT APIs are only intended for human consumption using the Kibana console or command line. They are not intended for use by applications. For application consumption, use the get trained models statistics API. + +{ref}/cat-trained-model.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatMlTrainedModelsRequest, options?): Promise +---- + +[discrete] +===== `CatMlTrainedModelsRequest` + +[source,ts] +---- +interface CatMlTrainedModelsRequest extends CatCatRequestBase { + model_id?: <> + allow_no_match?: boolean + bytes?: <> + h?: CatCatTrainedModelsColumns + s?: CatCatTrainedModelsColumns + from?: <> + size?: <> +} +---- + +[discrete] +===== `CatMlTrainedModelsResponse` + +[source,ts] +---- +type CatMlTrainedModelsResponse = CatMlTrainedModelsTrainedModelsRecord[] +---- + diff --git a/docs/reference-cat-nodeattrs.asciidoc b/docs/reference-cat-nodeattrs.asciidoc new file mode 100644 index 000000000..e7190d1d5 --- /dev/null +++ b/docs/reference-cat-nodeattrs.asciidoc @@ -0,0 +1,59 @@ +[[reference-cat-nodeattrs]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.nodeattrs + +Returns information about custom node attributes. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. + +{ref}/cat-nodeattrs.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatNodeattrsRequest, options?): Promise +---- + +[discrete] +===== `CatNodeattrsRequest` + +[source,ts] +---- +interface CatNodeattrsRequest extends CatCatRequestBase { +} +---- + +[discrete] +===== `CatNodeattrsResponse` + +[source,ts] +---- +type CatNodeattrsResponse = CatNodeattrsNodeAttributesRecord[] +---- + diff --git a/docs/reference-cat-nodes.asciidoc b/docs/reference-cat-nodes.asciidoc new file mode 100644 index 000000000..be64457d0 --- /dev/null +++ b/docs/reference-cat-nodes.asciidoc @@ -0,0 +1,62 @@ +[[reference-cat-nodes]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.nodes + +Returns information about the nodes in a cluster. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. + +{ref}/cat-nodes.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatNodesRequest, options?): Promise +---- + +[discrete] +===== `CatNodesRequest` + +[source,ts] +---- +interface CatNodesRequest extends CatCatRequestBase { + bytes?: <> + full_id?: boolean | string + include_unloaded_segments?: boolean +} +---- + +[discrete] +===== `CatNodesResponse` + +[source,ts] +---- +type CatNodesResponse = CatNodesNodesRecord[] +---- + diff --git a/docs/reference-cat-pending_tasks.asciidoc b/docs/reference-cat-pending_tasks.asciidoc new file mode 100644 index 000000000..1ba36e7cb --- /dev/null +++ b/docs/reference-cat-pending_tasks.asciidoc @@ -0,0 +1,59 @@ +[[reference-cat-pending_tasks]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.pendingTasks + +Returns cluster-level changes that have not yet been executed. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the pending cluster tasks API. + +{ref}/cat-pending-tasks.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatPendingTasksRequest, options?): Promise +---- + +[discrete] +===== `CatPendingTasksRequest` + +[source,ts] +---- +interface CatPendingTasksRequest extends CatCatRequestBase { +} +---- + +[discrete] +===== `CatPendingTasksResponse` + +[source,ts] +---- +type CatPendingTasksResponse = CatPendingTasksPendingTasksRecord[] +---- + diff --git a/docs/reference-cat-plugins.asciidoc b/docs/reference-cat-plugins.asciidoc new file mode 100644 index 000000000..21aade07b --- /dev/null +++ b/docs/reference-cat-plugins.asciidoc @@ -0,0 +1,59 @@ +[[reference-cat-plugins]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.plugins + +Returns a list of plugins running on each node of a cluster. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. + +{ref}/cat-plugins.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatPluginsRequest, options?): Promise +---- + +[discrete] +===== `CatPluginsRequest` + +[source,ts] +---- +interface CatPluginsRequest extends CatCatRequestBase { +} +---- + +[discrete] +===== `CatPluginsResponse` + +[source,ts] +---- +type CatPluginsResponse = CatPluginsPluginsRecord[] +---- + diff --git a/docs/reference-cat-recovery.asciidoc b/docs/reference-cat-recovery.asciidoc new file mode 100644 index 000000000..d79867511 --- /dev/null +++ b/docs/reference-cat-recovery.asciidoc @@ -0,0 +1,63 @@ +[[reference-cat-recovery]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.recovery + +Returns information about ongoing and completed shard recoveries. Shard recovery is the process of initializing a shard copy, such as restoring a primary shard from a snapshot or syncing a replica shard from a primary shard. When a shard recovery completes, the recovered shard is available for search and indexing. For data streams, the API returns information about the stream’s backing indices. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the index recovery API. + +{ref}/cat-recovery.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatRecoveryRequest, options?): Promise +---- + +[discrete] +===== `CatRecoveryRequest` + +[source,ts] +---- +interface CatRecoveryRequest extends CatCatRequestBase { + index?: <> + active_only?: boolean + bytes?: <> + detailed?: boolean +} +---- + +[discrete] +===== `CatRecoveryResponse` + +[source,ts] +---- +type CatRecoveryResponse = CatRecoveryRecoveryRecord[] +---- + diff --git a/docs/reference-cat-repositories.asciidoc b/docs/reference-cat-repositories.asciidoc new file mode 100644 index 000000000..ef5967fbe --- /dev/null +++ b/docs/reference-cat-repositories.asciidoc @@ -0,0 +1,59 @@ +[[reference-cat-repositories]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.repositories + +Returns the snapshot repositories for a cluster. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the get snapshot repository API. + +{ref}/cat-repositories.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatRepositoriesRequest, options?): Promise +---- + +[discrete] +===== `CatRepositoriesRequest` + +[source,ts] +---- +interface CatRepositoriesRequest extends CatCatRequestBase { +} +---- + +[discrete] +===== `CatRepositoriesResponse` + +[source,ts] +---- +type CatRepositoriesResponse = CatRepositoriesRepositoriesRecord[] +---- + diff --git a/docs/reference-cat-segments.asciidoc b/docs/reference-cat-segments.asciidoc new file mode 100644 index 000000000..4a1de7bae --- /dev/null +++ b/docs/reference-cat-segments.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-segments]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.segments + +Returns low-level information about the Lucene segments in index shards. For data streams, the API returns information about the backing indices. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the index segments API. + +{ref}/cat-segments.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatSegmentsRequest, options?): Promise +---- + +[discrete] +===== `CatSegmentsRequest` + +[source,ts] +---- +interface CatSegmentsRequest extends CatCatRequestBase { + index?: <> + bytes?: <> +} +---- + +[discrete] +===== `CatSegmentsResponse` + +[source,ts] +---- +type CatSegmentsResponse = CatSegmentsSegmentsRecord[] +---- + diff --git a/docs/reference-cat-shards.asciidoc b/docs/reference-cat-shards.asciidoc new file mode 100644 index 000000000..f1ce92cdb --- /dev/null +++ b/docs/reference-cat-shards.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-shards]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.shards + +Returns information about the shards in a cluster. For data streams, the API returns information about the backing indices. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. + +{ref}/cat-shards.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatShardsRequest, options?): Promise +---- + +[discrete] +===== `CatShardsRequest` + +[source,ts] +---- +interface CatShardsRequest extends CatCatRequestBase { + index?: <> + bytes?: <> +} +---- + +[discrete] +===== `CatShardsResponse` + +[source,ts] +---- +type CatShardsResponse = CatShardsShardsRecord[] +---- + diff --git a/docs/reference-cat-snapshots.asciidoc b/docs/reference-cat-snapshots.asciidoc new file mode 100644 index 000000000..d1c770d92 --- /dev/null +++ b/docs/reference-cat-snapshots.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-snapshots]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.snapshots + +Returns information about the snapshots stored in one or more repositories. A snapshot is a backup of an index or running Elasticsearch cluster. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the get snapshot API. + +{ref}/cat-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatSnapshotsRequest, options?): Promise +---- + +[discrete] +===== `CatSnapshotsRequest` + +[source,ts] +---- +interface CatSnapshotsRequest extends CatCatRequestBase { + repository?: <> + ignore_unavailable?: boolean +} +---- + +[discrete] +===== `CatSnapshotsResponse` + +[source,ts] +---- +type CatSnapshotsResponse = CatSnapshotsSnapshotsRecord[] +---- + diff --git a/docs/reference-cat-tasks.asciidoc b/docs/reference-cat-tasks.asciidoc new file mode 100644 index 000000000..f8b8aad21 --- /dev/null +++ b/docs/reference-cat-tasks.asciidoc @@ -0,0 +1,63 @@ +[[reference-cat-tasks]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.tasks + +Returns information about tasks currently executing in the cluster. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the task management API. + +{ref}/tasks.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatTasksRequest, options?): Promise +---- + +[discrete] +===== `CatTasksRequest` + +[source,ts] +---- +interface CatTasksRequest extends CatCatRequestBase { + actions?: string[] + detailed?: boolean + node_id?: string[] + parent_task_id?: string +} +---- + +[discrete] +===== `CatTasksResponse` + +[source,ts] +---- +type CatTasksResponse = CatTasksTasksRecord[] +---- + diff --git a/docs/reference-cat-templates.asciidoc b/docs/reference-cat-templates.asciidoc new file mode 100644 index 000000000..ce7d5b8af --- /dev/null +++ b/docs/reference-cat-templates.asciidoc @@ -0,0 +1,60 @@ +[[reference-cat-templates]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.templates + +Returns information about index templates in a cluster. You can use index templates to apply index settings and field mappings to new indices at creation. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the get index template API. + +{ref}/cat-templates.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatTemplatesRequest, options?): Promise +---- + +[discrete] +===== `CatTemplatesRequest` + +[source,ts] +---- +interface CatTemplatesRequest extends CatCatRequestBase { + name?: <> +} +---- + +[discrete] +===== `CatTemplatesResponse` + +[source,ts] +---- +type CatTemplatesResponse = CatTemplatesTemplatesRecord[] +---- + diff --git a/docs/reference-cat-thread_pool.asciidoc b/docs/reference-cat-thread_pool.asciidoc new file mode 100644 index 000000000..368b1d065 --- /dev/null +++ b/docs/reference-cat-thread_pool.asciidoc @@ -0,0 +1,61 @@ +[[reference-cat-thread_pool]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.threadPool + +Returns thread pool statistics for each node in a cluster. Returned information includes all built-in thread pools and custom thread pools. IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. + +{ref}/cat-thread-pool.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatThreadPoolRequest, options?): Promise +---- + +[discrete] +===== `CatThreadPoolRequest` + +[source,ts] +---- +interface CatThreadPoolRequest extends CatCatRequestBase { + thread_pool_patterns?: <> + time?: <> +} +---- + +[discrete] +===== `CatThreadPoolResponse` + +[source,ts] +---- +type CatThreadPoolResponse = CatThreadPoolThreadPoolRecord[] +---- + diff --git a/docs/reference-cat-transforms.asciidoc b/docs/reference-cat-transforms.asciidoc new file mode 100644 index 000000000..0747ea735 --- /dev/null +++ b/docs/reference-cat-transforms.asciidoc @@ -0,0 +1,66 @@ +[[reference-cat-transforms]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cat.transforms + +Get transforms. Returns configuration and usage information about transforms. CAT APIs are only intended for human consumption using the Kibana console or command line. They are not intended for use by applications. For application consumption, use the get transform statistics API. + +{ref}/cat-transforms.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CatTransformsRequest, options?): Promise +---- + +[discrete] +===== `CatTransformsRequest` + +[source,ts] +---- +interface CatTransformsRequest extends CatCatRequestBase { + transform_id?: <> + allow_no_match?: boolean + from?: <> + h?: CatCatTransformColumns + s?: CatCatTransformColumns + time?: <> + size?: <> +} +---- + +[discrete] +===== `CatTransformsResponse` + +[source,ts] +---- +type CatTransformsResponse = CatTransformsTransformsRecord[] +---- + diff --git a/docs/reference-ccr-delete_auto_follow_pattern.asciidoc b/docs/reference-ccr-delete_auto_follow_pattern.asciidoc new file mode 100644 index 000000000..80cb4b2fb --- /dev/null +++ b/docs/reference-ccr-delete_auto_follow_pattern.asciidoc @@ -0,0 +1,60 @@ +[[reference-ccr-delete_auto_follow_pattern]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.deleteAutoFollowPattern + +Deletes auto-follow patterns. + +{ref}/ccr-delete-auto-follow-pattern.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrDeleteAutoFollowPatternRequest, options?): Promise +---- + +[discrete] +===== `CcrDeleteAutoFollowPatternRequest` + +[source,ts] +---- +interface CcrDeleteAutoFollowPatternRequest extends <> { + name: <> +} +---- + +[discrete] +===== `CcrDeleteAutoFollowPatternResponse` + +[source,ts] +---- +type CcrDeleteAutoFollowPatternResponse = <> +---- + diff --git a/docs/reference-ccr-follow.asciidoc b/docs/reference-ccr-follow.asciidoc new file mode 100644 index 000000000..7efa85e0f --- /dev/null +++ b/docs/reference-ccr-follow.asciidoc @@ -0,0 +1,77 @@ +[[reference-ccr-follow]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.follow + +Creates a new follower index configured to follow the referenced leader index. + +{ref}/ccr-put-follow.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrFollowRequest, options?): Promise +---- + +[discrete] +===== `CcrFollowRequest` + +[source,ts] +---- +interface CcrFollowRequest extends <> { + index: <> + wait_for_active_shards?: <> + leader_index?: <> + max_outstanding_read_requests?: <> + max_outstanding_write_requests?: <> + max_read_request_operation_count?: <> + max_read_request_size?: string + max_retry_delay?: <> + max_write_buffer_count?: <> + max_write_buffer_size?: string + max_write_request_operation_count?: <> + max_write_request_size?: string + read_poll_timeout?: <> + remote_cluster?: string +} +---- + +[discrete] +===== `CcrFollowResponse` + +[source,ts] +---- +interface CcrFollowResponse { + follow_index_created: boolean + follow_index_shards_acked: boolean + index_following_started: boolean +} +---- + diff --git a/docs/reference-ccr-follow_info.asciidoc b/docs/reference-ccr-follow_info.asciidoc new file mode 100644 index 000000000..d5765de5f --- /dev/null +++ b/docs/reference-ccr-follow_info.asciidoc @@ -0,0 +1,62 @@ +[[reference-ccr-follow_info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.followInfo + +Retrieves information about all follower indices, including parameters and status for each follower index + +{ref}/ccr-get-follow-info.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrFollowInfoRequest, options?): Promise +---- + +[discrete] +===== `CcrFollowInfoRequest` + +[source,ts] +---- +interface CcrFollowInfoRequest extends <> { + index: <> +} +---- + +[discrete] +===== `CcrFollowInfoResponse` + +[source,ts] +---- +interface CcrFollowInfoResponse { + follower_indices: CcrFollowInfoFollowerIndex[] +} +---- + diff --git a/docs/reference-ccr-follow_stats.asciidoc b/docs/reference-ccr-follow_stats.asciidoc new file mode 100644 index 000000000..3e65632d1 --- /dev/null +++ b/docs/reference-ccr-follow_stats.asciidoc @@ -0,0 +1,62 @@ +[[reference-ccr-follow_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.followStats + +Retrieves follower stats. return shard-level stats about the following tasks associated with each shard for the specified indices. + +{ref}/ccr-get-follow-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrFollowStatsRequest, options?): Promise +---- + +[discrete] +===== `CcrFollowStatsRequest` + +[source,ts] +---- +interface CcrFollowStatsRequest extends <> { + index: <> +} +---- + +[discrete] +===== `CcrFollowStatsResponse` + +[source,ts] +---- +interface CcrFollowStatsResponse { + indices: CcrFollowIndexStats[] +} +---- + diff --git a/docs/reference-ccr-forget_follower.asciidoc b/docs/reference-ccr-forget_follower.asciidoc new file mode 100644 index 000000000..4911dcc35 --- /dev/null +++ b/docs/reference-ccr-forget_follower.asciidoc @@ -0,0 +1,66 @@ +[[reference-ccr-forget_follower]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.forgetFollower + +Removes the follower retention leases from the leader. + +{ref}/ccr-post-forget-follower.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrForgetFollowerRequest, options?): Promise +---- + +[discrete] +===== `CcrForgetFollowerRequest` + +[source,ts] +---- +interface CcrForgetFollowerRequest extends <> { + index: <> + follower_cluster?: string + follower_index?: <> + follower_index_uuid?: <> + leader_remote_cluster?: string +} +---- + +[discrete] +===== `CcrForgetFollowerResponse` + +[source,ts] +---- +interface CcrForgetFollowerResponse { + _shards: <> +} +---- + diff --git a/docs/reference-ccr-get_auto_follow_pattern.asciidoc b/docs/reference-ccr-get_auto_follow_pattern.asciidoc new file mode 100644 index 000000000..ed4e5e43e --- /dev/null +++ b/docs/reference-ccr-get_auto_follow_pattern.asciidoc @@ -0,0 +1,62 @@ +[[reference-ccr-get_auto_follow_pattern]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.getAutoFollowPattern + +Gets configured auto-follow patterns. Returns the specified auto-follow pattern collection. + +{ref}/ccr-get-auto-follow-pattern.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrGetAutoFollowPatternRequest, options?): Promise +---- + +[discrete] +===== `CcrGetAutoFollowPatternRequest` + +[source,ts] +---- +interface CcrGetAutoFollowPatternRequest extends <> { + name?: <> +} +---- + +[discrete] +===== `CcrGetAutoFollowPatternResponse` + +[source,ts] +---- +interface CcrGetAutoFollowPatternResponse { + patterns: CcrGetAutoFollowPatternAutoFollowPattern[] +} +---- + diff --git a/docs/reference-ccr-pause_auto_follow_pattern.asciidoc b/docs/reference-ccr-pause_auto_follow_pattern.asciidoc new file mode 100644 index 000000000..8824b2124 --- /dev/null +++ b/docs/reference-ccr-pause_auto_follow_pattern.asciidoc @@ -0,0 +1,60 @@ +[[reference-ccr-pause_auto_follow_pattern]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.pauseAutoFollowPattern + +Pauses an auto-follow pattern + +{ref}/ccr-pause-auto-follow-pattern.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrPauseAutoFollowPatternRequest, options?): Promise +---- + +[discrete] +===== `CcrPauseAutoFollowPatternRequest` + +[source,ts] +---- +interface CcrPauseAutoFollowPatternRequest extends <> { + name: <> +} +---- + +[discrete] +===== `CcrPauseAutoFollowPatternResponse` + +[source,ts] +---- +type CcrPauseAutoFollowPatternResponse = <> +---- + diff --git a/docs/reference-ccr-pause_follow.asciidoc b/docs/reference-ccr-pause_follow.asciidoc new file mode 100644 index 000000000..5dbee490b --- /dev/null +++ b/docs/reference-ccr-pause_follow.asciidoc @@ -0,0 +1,60 @@ +[[reference-ccr-pause_follow]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.pauseFollow + +Pauses a follower index. The follower index will not fetch any additional operations from the leader index. + +{ref}/ccr-post-pause-follow.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrPauseFollowRequest, options?): Promise +---- + +[discrete] +===== `CcrPauseFollowRequest` + +[source,ts] +---- +interface CcrPauseFollowRequest extends <> { + index: <> +} +---- + +[discrete] +===== `CcrPauseFollowResponse` + +[source,ts] +---- +type CcrPauseFollowResponse = <> +---- + diff --git a/docs/reference-ccr-put_auto_follow_pattern.asciidoc b/docs/reference-ccr-put_auto_follow_pattern.asciidoc new file mode 100644 index 000000000..b4b5f6585 --- /dev/null +++ b/docs/reference-ccr-put_auto_follow_pattern.asciidoc @@ -0,0 +1,75 @@ +[[reference-ccr-put_auto_follow_pattern]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.putAutoFollowPattern + +Creates a new named collection of auto-follow patterns against a specified remote cluster. Newly created indices on the remote cluster matching any of the specified patterns will be automatically configured as follower indices. + +{ref}/ccr-put-auto-follow-pattern.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrPutAutoFollowPatternRequest, options?): Promise +---- + +[discrete] +===== `CcrPutAutoFollowPatternRequest` + +[source,ts] +---- +interface CcrPutAutoFollowPatternRequest extends <> { + name: <> + remote_cluster: string + follow_index_pattern?: <> + leader_index_patterns?: <> + leader_index_exclusion_patterns?: <> + max_outstanding_read_requests?: <> + settings?: Record + max_outstanding_write_requests?: <> + read_poll_timeout?: <> + max_read_request_operation_count?: <> + max_read_request_size?: <> + max_retry_delay?: <> + max_write_buffer_count?: <> + max_write_buffer_size?: <> + max_write_request_operation_count?: <> + max_write_request_size?: <> +} +---- + +[discrete] +===== `CcrPutAutoFollowPatternResponse` + +[source,ts] +---- +type CcrPutAutoFollowPatternResponse = <> +---- + diff --git a/docs/reference-ccr-resume_auto_follow_pattern.asciidoc b/docs/reference-ccr-resume_auto_follow_pattern.asciidoc new file mode 100644 index 000000000..7e73fae09 --- /dev/null +++ b/docs/reference-ccr-resume_auto_follow_pattern.asciidoc @@ -0,0 +1,60 @@ +[[reference-ccr-resume_auto_follow_pattern]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.resumeAutoFollowPattern + +Resumes an auto-follow pattern that has been paused + +{ref}/ccr-resume-auto-follow-pattern.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrResumeAutoFollowPatternRequest, options?): Promise +---- + +[discrete] +===== `CcrResumeAutoFollowPatternRequest` + +[source,ts] +---- +interface CcrResumeAutoFollowPatternRequest extends <> { + name: <> +} +---- + +[discrete] +===== `CcrResumeAutoFollowPatternResponse` + +[source,ts] +---- +type CcrResumeAutoFollowPatternResponse = <> +---- + diff --git a/docs/reference-ccr-resume_follow.asciidoc b/docs/reference-ccr-resume_follow.asciidoc new file mode 100644 index 000000000..5b25b4678 --- /dev/null +++ b/docs/reference-ccr-resume_follow.asciidoc @@ -0,0 +1,70 @@ +[[reference-ccr-resume_follow]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.resumeFollow + +Resumes a follower index that has been paused + +{ref}/ccr-post-resume-follow.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrResumeFollowRequest, options?): Promise +---- + +[discrete] +===== `CcrResumeFollowRequest` + +[source,ts] +---- +interface CcrResumeFollowRequest extends <> { + index: <> + max_outstanding_read_requests?: <> + max_outstanding_write_requests?: <> + max_read_request_operation_count?: <> + max_read_request_size?: string + max_retry_delay?: <> + max_write_buffer_count?: <> + max_write_buffer_size?: string + max_write_request_operation_count?: <> + max_write_request_size?: string + read_poll_timeout?: <> +} +---- + +[discrete] +===== `CcrResumeFollowResponse` + +[source,ts] +---- +type CcrResumeFollowResponse = <> +---- + diff --git a/docs/reference-ccr-stats.asciidoc b/docs/reference-ccr-stats.asciidoc new file mode 100644 index 000000000..9ecb48733 --- /dev/null +++ b/docs/reference-ccr-stats.asciidoc @@ -0,0 +1,62 @@ +[[reference-ccr-stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.stats + +Gets all stats related to cross-cluster replication. + +{ref}/ccr-get-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrStatsRequest, options?): Promise +---- + +[discrete] +===== `CcrStatsRequest` + +[source,ts] +---- +interface CcrStatsRequest extends <> { +} +---- + +[discrete] +===== `CcrStatsResponse` + +[source,ts] +---- +interface CcrStatsResponse { + auto_follow_stats: CcrStatsAutoFollowStats + follow_stats: CcrStatsFollowStats +} +---- + diff --git a/docs/reference-ccr-unfollow.asciidoc b/docs/reference-ccr-unfollow.asciidoc new file mode 100644 index 000000000..1a5e41e28 --- /dev/null +++ b/docs/reference-ccr-unfollow.asciidoc @@ -0,0 +1,60 @@ +[[reference-ccr-unfollow]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ccr.unfollow + +Stops the following task associated with a follower index and removes index metadata and settings associated with cross-cluster replication. + +{ref}/ccr-post-unfollow.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CcrUnfollowRequest, options?): Promise +---- + +[discrete] +===== `CcrUnfollowRequest` + +[source,ts] +---- +interface CcrUnfollowRequest extends <> { + index: <> +} +---- + +[discrete] +===== `CcrUnfollowResponse` + +[source,ts] +---- +type CcrUnfollowResponse = <> +---- + diff --git a/docs/reference-clear_scroll.asciidoc b/docs/reference-clear_scroll.asciidoc new file mode 100644 index 000000000..72e66fdda --- /dev/null +++ b/docs/reference-clear_scroll.asciidoc @@ -0,0 +1,63 @@ +[[reference-clear_scroll]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.clearScroll + +Clear a scrolling search. Clear the search context and results for a scrolling search. + +{ref}/clear-scroll-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClearScrollRequest, options?): Promise +---- + +[discrete] +===== `ClearScrollRequest` + +[source,ts] +---- +interface ClearScrollRequest extends <> { + scroll_id?: <> +} +---- + +[discrete] +===== `ClearScrollResponse` + +[source,ts] +---- +interface ClearScrollResponse { + succeeded: boolean + num_freed: <> +} +---- + diff --git a/docs/reference-close_point_in_time.asciidoc b/docs/reference-close_point_in_time.asciidoc new file mode 100644 index 000000000..f126c1243 --- /dev/null +++ b/docs/reference-close_point_in_time.asciidoc @@ -0,0 +1,63 @@ +[[reference-close_point_in_time]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.closePointInTime + +Close a point in time. A point in time must be opened explicitly before being used in search requests. The `keep_alive` parameter tells Elasticsearch how long it should persist. A point in time is automatically closed when the `keep_alive` period has elapsed. However, keeping points in time has a cost; close them as soon as they are no longer required for search requests. + +{ref}/point-in-time-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClosePointInTimeRequest, options?): Promise +---- + +[discrete] +===== `ClosePointInTimeRequest` + +[source,ts] +---- +interface ClosePointInTimeRequest extends <> { + id: <> +} +---- + +[discrete] +===== `ClosePointInTimeResponse` + +[source,ts] +---- +interface ClosePointInTimeResponse { + succeeded: boolean + num_freed: <> +} +---- + diff --git a/docs/reference-cluster-allocation_explain.asciidoc b/docs/reference-cluster-allocation_explain.asciidoc new file mode 100644 index 000000000..89f1655d0 --- /dev/null +++ b/docs/reference-cluster-allocation_explain.asciidoc @@ -0,0 +1,91 @@ +[[reference-cluster-allocation_explain]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.allocationExplain + +Provides explanations for shard allocations in the cluster. + +{ref}/cluster-allocation-explain.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterAllocationExplainRequest, options?): Promise +---- + +[discrete] +===== `ClusterAllocationExplainRequest` + +[source,ts] +---- +interface ClusterAllocationExplainRequest extends <> { + include_disk_info?: boolean + include_yes_decisions?: boolean + current_node?: string + index?: <> + primary?: boolean + shard?: <> +} +---- + +[discrete] +===== `ClusterAllocationExplainResponse` + +[source,ts] +---- +interface ClusterAllocationExplainResponse { + allocate_explanation?: string + allocation_delay?: <> + allocation_delay_in_millis?: <><<>> + can_allocate?: ClusterAllocationExplainDecision + can_move_to_other_node?: ClusterAllocationExplainDecision + can_rebalance_cluster?: ClusterAllocationExplainDecision + can_rebalance_cluster_decisions?: ClusterAllocationExplainAllocationDecision[] + can_rebalance_to_other_node?: ClusterAllocationExplainDecision + can_remain_decisions?: ClusterAllocationExplainAllocationDecision[] + can_remain_on_current_node?: ClusterAllocationExplainDecision + cluster_info?: ClusterAllocationExplainClusterInfo + configured_delay?: <> + configured_delay_in_millis?: <><<>> + current_node?: ClusterAllocationExplainCurrentNode + current_state: string + index: <> + move_explanation?: string + node_allocation_decisions?: ClusterAllocationExplainNodeAllocationExplanation[] + primary: boolean + rebalance_explanation?: string + remaining_delay?: <> + remaining_delay_in_millis?: <><<>> + shard: <> + unassigned_info?: ClusterAllocationExplainUnassignedInformation + note?: string +} +---- + diff --git a/docs/reference-cluster-delete_component_template.asciidoc b/docs/reference-cluster-delete_component_template.asciidoc new file mode 100644 index 000000000..9bd68791d --- /dev/null +++ b/docs/reference-cluster-delete_component_template.asciidoc @@ -0,0 +1,62 @@ +[[reference-cluster-delete_component_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.deleteComponentTemplate + +Delete component templates. Deletes component templates. Component templates are building blocks for constructing index templates that specify index mappings, settings, and aliases. + +{ref}/indices-component-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterDeleteComponentTemplateRequest, options?): Promise +---- + +[discrete] +===== `ClusterDeleteComponentTemplateRequest` + +[source,ts] +---- +interface ClusterDeleteComponentTemplateRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `ClusterDeleteComponentTemplateResponse` + +[source,ts] +---- +type ClusterDeleteComponentTemplateResponse = <> +---- + diff --git a/docs/reference-cluster-delete_voting_config_exclusions.asciidoc b/docs/reference-cluster-delete_voting_config_exclusions.asciidoc new file mode 100644 index 000000000..210c6054e --- /dev/null +++ b/docs/reference-cluster-delete_voting_config_exclusions.asciidoc @@ -0,0 +1,60 @@ +[[reference-cluster-delete_voting_config_exclusions]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.deleteVotingConfigExclusions + +Clears cluster voting config exclusions. + +{ref}/voting-config-exclusions.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterDeleteVotingConfigExclusionsRequest, options?): Promise +---- + +[discrete] +===== `ClusterDeleteVotingConfigExclusionsRequest` + +[source,ts] +---- +interface ClusterDeleteVotingConfigExclusionsRequest extends <> { + wait_for_removal?: boolean +} +---- + +[discrete] +===== `ClusterDeleteVotingConfigExclusionsResponse` + +[source,ts] +---- +type ClusterDeleteVotingConfigExclusionsResponse = boolean +---- + diff --git a/docs/reference-cluster-exists_component_template.asciidoc b/docs/reference-cluster-exists_component_template.asciidoc new file mode 100644 index 000000000..1ccb0a92d --- /dev/null +++ b/docs/reference-cluster-exists_component_template.asciidoc @@ -0,0 +1,62 @@ +[[reference-cluster-exists_component_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.existsComponentTemplate + +Check component templates. Returns information about whether a particular component template exists. + +{ref}/indices-component-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterExistsComponentTemplateRequest, options?): Promise +---- + +[discrete] +===== `ClusterExistsComponentTemplateRequest` + +[source,ts] +---- +interface ClusterExistsComponentTemplateRequest extends <> { + name: <> + master_timeout?: <> + local?: boolean +} +---- + +[discrete] +===== `ClusterExistsComponentTemplateResponse` + +[source,ts] +---- +type ClusterExistsComponentTemplateResponse = boolean +---- + diff --git a/docs/reference-cluster-get_component_template.asciidoc b/docs/reference-cluster-get_component_template.asciidoc new file mode 100644 index 000000000..88c229597 --- /dev/null +++ b/docs/reference-cluster-get_component_template.asciidoc @@ -0,0 +1,66 @@ +[[reference-cluster-get_component_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.getComponentTemplate + +Get component templates. Retrieves information about component templates. + +{ref}/indices-component-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterGetComponentTemplateRequest, options?): Promise +---- + +[discrete] +===== `ClusterGetComponentTemplateRequest` + +[source,ts] +---- +interface ClusterGetComponentTemplateRequest extends <> { + name?: <> + flat_settings?: boolean + include_defaults?: boolean + local?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `ClusterGetComponentTemplateResponse` + +[source,ts] +---- +interface ClusterGetComponentTemplateResponse { + component_templates: ClusterComponentTemplate[] +} +---- + diff --git a/docs/reference-cluster-get_settings.asciidoc b/docs/reference-cluster-get_settings.asciidoc new file mode 100644 index 000000000..40ab9b33e --- /dev/null +++ b/docs/reference-cluster-get_settings.asciidoc @@ -0,0 +1,67 @@ +[[reference-cluster-get_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.getSettings + +Returns cluster-wide settings. By default, it returns only settings that have been explicitly defined. + +{ref}/cluster-get-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterGetSettingsRequest, options?): Promise +---- + +[discrete] +===== `ClusterGetSettingsRequest` + +[source,ts] +---- +interface ClusterGetSettingsRequest extends <> { + flat_settings?: boolean + include_defaults?: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `ClusterGetSettingsResponse` + +[source,ts] +---- +interface ClusterGetSettingsResponse { + persistent: Record + transient: Record + defaults?: Record +} +---- + diff --git a/docs/reference-cluster-health.asciidoc b/docs/reference-cluster-health.asciidoc new file mode 100644 index 000000000..2988c1668 --- /dev/null +++ b/docs/reference-cluster-health.asciidoc @@ -0,0 +1,71 @@ +[[reference-cluster-health]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.health + +The cluster health API returns a simple status on the health of the cluster. You can also use the API to get the health status of only specified data streams and indices. For data streams, the API retrieves the health status of the stream’s backing indices. The cluster health status is: green, yellow or red. On the shard level, a red status indicates that the specific shard is not allocated in the cluster, yellow means that the primary shard is allocated but replicas are not, and green means that all shards are allocated. The index level status is controlled by the worst shard status. The cluster status is controlled by the worst index status. + +{ref}/cluster-health.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterHealthRequest, options?): Promise +---- + +[discrete] +===== `ClusterHealthRequest` + +[source,ts] +---- +interface ClusterHealthRequest extends <> { + index?: <> + expand_wildcards?: <> + level?: <> + local?: boolean + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> + wait_for_events?: <> + wait_for_nodes?: string | <> + wait_for_no_initializing_shards?: boolean + wait_for_no_relocating_shards?: boolean + wait_for_status?: <> +} +---- + +[discrete] +===== `ClusterHealthResponse` + +[source,ts] +---- +type ClusterHealthResponse = ClusterHealthHealthResponseBody +---- + diff --git a/docs/reference-cluster-info.asciidoc b/docs/reference-cluster-info.asciidoc new file mode 100644 index 000000000..d0535babc --- /dev/null +++ b/docs/reference-cluster-info.asciidoc @@ -0,0 +1,66 @@ +[[reference-cluster-info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.info + +Get cluster info. Returns basic information about the cluster. + +{ref}/cluster-info.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterInfoRequest, options?): Promise +---- + +[discrete] +===== `ClusterInfoRequest` + +[source,ts] +---- +interface ClusterInfoRequest extends <> { + target: <> +} +---- + +[discrete] +===== `ClusterInfoResponse` + +[source,ts] +---- +interface ClusterInfoResponse { + cluster_name: <> + http?: NodesHttp + ingest?: NodesIngest + thread_pool?: Record + script?: NodesScripting +} +---- + diff --git a/docs/reference-cluster-pending_tasks.asciidoc b/docs/reference-cluster-pending_tasks.asciidoc new file mode 100644 index 000000000..ec9b75aeb --- /dev/null +++ b/docs/reference-cluster-pending_tasks.asciidoc @@ -0,0 +1,63 @@ +[[reference-cluster-pending_tasks]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.pendingTasks + +Returns cluster-level changes (such as create index, update mapping, allocate or fail shard) that have not yet been executed. NOTE: This API returns a list of any pending updates to the cluster state. These are distinct from the tasks reported by the Task Management API which include periodic tasks and tasks initiated by the user, such as node stats, search queries, or create index requests. However, if a user-initiated task such as a create index command causes a cluster state update, the activity of this task might be reported by both task api and pending cluster tasks API. + +{ref}/cluster-pending.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterPendingTasksRequest, options?): Promise +---- + +[discrete] +===== `ClusterPendingTasksRequest` + +[source,ts] +---- +interface ClusterPendingTasksRequest extends <> { + local?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `ClusterPendingTasksResponse` + +[source,ts] +---- +interface ClusterPendingTasksResponse { + tasks: ClusterPendingTasksPendingTask[] +} +---- + diff --git a/docs/reference-cluster-post_voting_config_exclusions.asciidoc b/docs/reference-cluster-post_voting_config_exclusions.asciidoc new file mode 100644 index 000000000..e4f372ae4 --- /dev/null +++ b/docs/reference-cluster-post_voting_config_exclusions.asciidoc @@ -0,0 +1,62 @@ +[[reference-cluster-post_voting_config_exclusions]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.postVotingConfigExclusions + +Updates the cluster voting config exclusions by node ids or node names. + +{ref}/voting-config-exclusions.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterPostVotingConfigExclusionsRequest, options?): Promise +---- + +[discrete] +===== `ClusterPostVotingConfigExclusionsRequest` + +[source,ts] +---- +interface ClusterPostVotingConfigExclusionsRequest extends <> { + node_names?: <> + node_ids?: <> + timeout?: <> +} +---- + +[discrete] +===== `ClusterPostVotingConfigExclusionsResponse` + +[source,ts] +---- +type ClusterPostVotingConfigExclusionsResponse = boolean +---- + diff --git a/docs/reference-cluster-put_component_template.asciidoc b/docs/reference-cluster-put_component_template.asciidoc new file mode 100644 index 000000000..fc5aa4a7b --- /dev/null +++ b/docs/reference-cluster-put_component_template.asciidoc @@ -0,0 +1,66 @@ +[[reference-cluster-put_component_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.putComponentTemplate + +Create or update a component template. Creates or updates a component template. Component templates are building blocks for constructing index templates that specify index mappings, settings, and aliases. An index template can be composed of multiple component templates. To use a component template, specify it in an index template’s `composed_of` list. Component templates are only applied to new data streams and indices as part of a matching index template. Settings and mappings specified directly in the index template or the create index request override any settings or mappings specified in a component template. Component templates are only used during index creation. For data streams, this includes data stream creation and the creation of a stream’s backing indices. Changes to component templates do not affect existing indices, including a stream’s backing indices. You can use C-style `/* *\/` block comments in component templates. You can include comments anywhere in the request body except before the opening curly bracket. + +{ref}/indices-component-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterPutComponentTemplateRequest, options?): Promise +---- + +[discrete] +===== `ClusterPutComponentTemplateRequest` + +[source,ts] +---- +interface ClusterPutComponentTemplateRequest extends <> { + name: <> + create?: boolean + master_timeout?: <> + template: IndicesIndexState + version?: <> + _meta?: <> + deprecated?: boolean +} +---- + +[discrete] +===== `ClusterPutComponentTemplateResponse` + +[source,ts] +---- +type ClusterPutComponentTemplateResponse = <> +---- + diff --git a/docs/reference-cluster-put_settings.asciidoc b/docs/reference-cluster-put_settings.asciidoc new file mode 100644 index 000000000..6e4069fa3 --- /dev/null +++ b/docs/reference-cluster-put_settings.asciidoc @@ -0,0 +1,68 @@ +[[reference-cluster-put_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.putSettings + +Updates the cluster settings. + +{ref}/cluster-update-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterPutSettingsRequest, options?): Promise +---- + +[discrete] +===== `ClusterPutSettingsRequest` + +[source,ts] +---- +interface ClusterPutSettingsRequest extends <> { + flat_settings?: boolean + master_timeout?: <> + timeout?: <> + persistent?: Record + transient?: Record +} +---- + +[discrete] +===== `ClusterPutSettingsResponse` + +[source,ts] +---- +interface ClusterPutSettingsResponse { + acknowledged: boolean + persistent: Record + transient: Record +} +---- + diff --git a/docs/reference-cluster-remote_info.asciidoc b/docs/reference-cluster-remote_info.asciidoc new file mode 100644 index 000000000..15c44616e --- /dev/null +++ b/docs/reference-cluster-remote_info.asciidoc @@ -0,0 +1,59 @@ +[[reference-cluster-remote_info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.remoteInfo + +The cluster remote info API allows you to retrieve all of the configured remote cluster information. It returns connection and endpoint information keyed by the configured remote cluster alias. + +{ref}/cluster-remote-info.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterRemoteInfoRequest, options?): Promise +---- + +[discrete] +===== `ClusterRemoteInfoRequest` + +[source,ts] +---- +interface ClusterRemoteInfoRequest extends <> { +} +---- + +[discrete] +===== `ClusterRemoteInfoResponse` + +[source,ts] +---- +type ClusterRemoteInfoResponse = Record +---- + diff --git a/docs/reference-cluster-reroute.asciidoc b/docs/reference-cluster-reroute.asciidoc new file mode 100644 index 000000000..1868ff7d9 --- /dev/null +++ b/docs/reference-cluster-reroute.asciidoc @@ -0,0 +1,70 @@ +[[reference-cluster-reroute]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.reroute + +Allows to manually change the allocation of individual shards in the cluster. + +{ref}/cluster-reroute.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterRerouteRequest, options?): Promise +---- + +[discrete] +===== `ClusterRerouteRequest` + +[source,ts] +---- +interface ClusterRerouteRequest extends <> { + dry_run?: boolean + explain?: boolean + metric?: <> + retry_failed?: boolean + master_timeout?: <> + timeout?: <> + commands?: ClusterRerouteCommand[] +} +---- + +[discrete] +===== `ClusterRerouteResponse` + +[source,ts] +---- +interface ClusterRerouteResponse { + acknowledged: boolean + explanations?: ClusterRerouteRerouteExplanation[] + state?: any +} +---- + diff --git a/docs/reference-cluster-state.asciidoc b/docs/reference-cluster-state.asciidoc new file mode 100644 index 000000000..7da73387b --- /dev/null +++ b/docs/reference-cluster-state.asciidoc @@ -0,0 +1,69 @@ +[[reference-cluster-state]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.state + +Returns a comprehensive information about the state of the cluster. + +{ref}/cluster-state.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterStateRequest, options?): Promise +---- + +[discrete] +===== `ClusterStateRequest` + +[source,ts] +---- +interface ClusterStateRequest extends <> { + metric?: <> + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + flat_settings?: boolean + ignore_unavailable?: boolean + local?: boolean + master_timeout?: <> + wait_for_metadata_version?: <> + wait_for_timeout?: <> +} +---- + +[discrete] +===== `ClusterStateResponse` + +[source,ts] +---- +type ClusterStateResponse = any +---- + diff --git a/docs/reference-cluster-stats.asciidoc b/docs/reference-cluster-stats.asciidoc new file mode 100644 index 000000000..3079b88c1 --- /dev/null +++ b/docs/reference-cluster-stats.asciidoc @@ -0,0 +1,62 @@ +[[reference-cluster-stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.cluster.stats + +Returns cluster statistics. It returns basic index metrics (shard numbers, store size, memory usage) and information about the current nodes that form the cluster (number, roles, os, jvm versions, memory usage, cpu and installed plugins). + +{ref}/cluster-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ClusterStatsRequest, options?): Promise +---- + +[discrete] +===== `ClusterStatsRequest` + +[source,ts] +---- +interface ClusterStatsRequest extends <> { + node_id?: <> + include_remotes?: boolean + timeout?: <> +} +---- + +[discrete] +===== `ClusterStatsResponse` + +[source,ts] +---- +type ClusterStatsResponse = ClusterStatsStatsResponseBase +---- + diff --git a/docs/reference-connector-check_in.asciidoc b/docs/reference-connector-check_in.asciidoc new file mode 100644 index 000000000..532ef0cf6 --- /dev/null +++ b/docs/reference-connector-check_in.asciidoc @@ -0,0 +1,62 @@ +[[reference-connector-check_in]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.checkIn + +Check in a connector. Update the `last_seen` field in the connector and set it to the current timestamp. + +{ref}/check-in-connector-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorCheckInRequest, options?): Promise +---- + +[discrete] +===== `ConnectorCheckInRequest` + +[source,ts] +---- +interface ConnectorCheckInRequest extends <> { + connector_id: <> +} +---- + +[discrete] +===== `ConnectorCheckInResponse` + +[source,ts] +---- +interface ConnectorCheckInResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-delete.asciidoc b/docs/reference-connector-delete.asciidoc new file mode 100644 index 000000000..548adc565 --- /dev/null +++ b/docs/reference-connector-delete.asciidoc @@ -0,0 +1,61 @@ +[[reference-connector-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.delete + +Delete a connector. Removes a connector and associated sync jobs. This is a destructive action that is not recoverable. NOTE: This action doesn’t delete any API keys, ingest pipelines, or data indices associated with the connector. These need to be removed manually. + +{ref}/delete-connector-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorDeleteRequest, options?): Promise +---- + +[discrete] +===== `ConnectorDeleteRequest` + +[source,ts] +---- +interface ConnectorDeleteRequest extends <> { + connector_id: <> + delete_sync_jobs?: boolean +} +---- + +[discrete] +===== `ConnectorDeleteResponse` + +[source,ts] +---- +type ConnectorDeleteResponse = <> +---- + diff --git a/docs/reference-connector-get.asciidoc b/docs/reference-connector-get.asciidoc new file mode 100644 index 000000000..67ba6ae6e --- /dev/null +++ b/docs/reference-connector-get.asciidoc @@ -0,0 +1,60 @@ +[[reference-connector-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.get + +Get a connector. Get the details about a connector. + +{ref}/get-connector-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorGetRequest, options?): Promise +---- + +[discrete] +===== `ConnectorGetRequest` + +[source,ts] +---- +interface ConnectorGetRequest extends <> { + connector_id: <> +} +---- + +[discrete] +===== `ConnectorGetResponse` + +[source,ts] +---- +type ConnectorGetResponse = ConnectorConnector +---- + diff --git a/docs/reference-connector-list.asciidoc b/docs/reference-connector-list.asciidoc new file mode 100644 index 000000000..0886ba465 --- /dev/null +++ b/docs/reference-connector-list.asciidoc @@ -0,0 +1,68 @@ +[[reference-connector-list]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.list + +Get all connectors. Get information about all connectors. + +{ref}/list-connector-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorListRequest, options?): Promise +---- + +[discrete] +===== `ConnectorListRequest` + +[source,ts] +---- +interface ConnectorListRequest extends <> { + from?: <> + size?: <> + index_name?: <> + connector_name?: <> + service_type?: <> + query?: string +} +---- + +[discrete] +===== `ConnectorListResponse` + +[source,ts] +---- +interface ConnectorListResponse { + count: <> + results: ConnectorConnector[] +} +---- + diff --git a/docs/reference-connector-post.asciidoc b/docs/reference-connector-post.asciidoc new file mode 100644 index 000000000..9e847e9cd --- /dev/null +++ b/docs/reference-connector-post.asciidoc @@ -0,0 +1,68 @@ +[[reference-connector-post]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.post + +Create a connector. Connectors are Elasticsearch integrations that bring content from third-party data sources, which can be deployed on Elastic Cloud or hosted on your own infrastructure. Elastic managed connectors (Native connectors) are a managed service on Elastic Cloud. Self-managed connectors (Connector clients) are self-managed on your infrastructure. + +{ref}/create-connector-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorPostRequest, options?): Promise +---- + +[discrete] +===== `ConnectorPostRequest` + +[source,ts] +---- +interface ConnectorPostRequest extends <> { + description?: string + index_name?: <> + is_native?: boolean + language?: string + name?: string + service_type?: string +} +---- + +[discrete] +===== `ConnectorPostResponse` + +[source,ts] +---- +interface ConnectorPostResponse { + result: <> + id: <> +} +---- + diff --git a/docs/reference-connector-put.asciidoc b/docs/reference-connector-put.asciidoc new file mode 100644 index 000000000..3ff54c951 --- /dev/null +++ b/docs/reference-connector-put.asciidoc @@ -0,0 +1,69 @@ +[[reference-connector-put]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.put + +Create or update a connector. + +{ref}/create-connector-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorPutRequest, options?): Promise +---- + +[discrete] +===== `ConnectorPutRequest` + +[source,ts] +---- +interface ConnectorPutRequest extends <> { + connector_id?: <> + description?: string + index_name?: <> + is_native?: boolean + language?: string + name?: string + service_type?: string +} +---- + +[discrete] +===== `ConnectorPutResponse` + +[source,ts] +---- +interface ConnectorPutResponse { + result: <> + id: <> +} +---- + diff --git a/docs/reference-connector-sync_job_cancel.asciidoc b/docs/reference-connector-sync_job_cancel.asciidoc new file mode 100644 index 000000000..397dced52 --- /dev/null +++ b/docs/reference-connector-sync_job_cancel.asciidoc @@ -0,0 +1,62 @@ +[[reference-connector-sync_job_cancel]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobCancel + +Cancel a connector sync job. Cancel a connector sync job, which sets the status to cancelling and updates `cancellation_requested_at` to the current time. The connector service is then responsible for setting the status of connector sync jobs to cancelled. + +{ref}/cancel-connector-sync-job-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobCancelRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobCancelRequest` + +[source,ts] +---- +interface ConnectorSyncJobCancelRequest extends <> { + connector_sync_job_id: <> +} +---- + +[discrete] +===== `ConnectorSyncJobCancelResponse` + +[source,ts] +---- +interface ConnectorSyncJobCancelResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-sync_job_check_in.asciidoc b/docs/reference-connector-sync_job_check_in.asciidoc new file mode 100644 index 000000000..e10c2eaf7 --- /dev/null +++ b/docs/reference-connector-sync_job_check_in.asciidoc @@ -0,0 +1,59 @@ +[[reference-connector-sync_job_check_in]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobCheckIn + +Checks in a connector sync job (refreshes 'last_seen'). + +{ref}/check-in-connector-sync-job-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobCheckInRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobCheckInRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `ConnectorSyncJobCheckInResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-connector-sync_job_claim.asciidoc b/docs/reference-connector-sync_job_claim.asciidoc new file mode 100644 index 000000000..889dfb29e --- /dev/null +++ b/docs/reference-connector-sync_job_claim.asciidoc @@ -0,0 +1,57 @@ +[[reference-connector-sync_job_claim]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobClaim + +Claims a connector sync job. + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobClaimRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobClaimRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `ConnectorSyncJobClaimResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-connector-sync_job_delete.asciidoc b/docs/reference-connector-sync_job_delete.asciidoc new file mode 100644 index 000000000..f98d5d947 --- /dev/null +++ b/docs/reference-connector-sync_job_delete.asciidoc @@ -0,0 +1,60 @@ +[[reference-connector-sync_job_delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobDelete + +Delete a connector sync job. Remove a connector sync job and its associated data. This is a destructive action that is not recoverable. + +{ref}/delete-connector-sync-job-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobDeleteRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobDeleteRequest` + +[source,ts] +---- +interface ConnectorSyncJobDeleteRequest extends <> { + connector_sync_job_id: <> +} +---- + +[discrete] +===== `ConnectorSyncJobDeleteResponse` + +[source,ts] +---- +type ConnectorSyncJobDeleteResponse = <> +---- + diff --git a/docs/reference-connector-sync_job_error.asciidoc b/docs/reference-connector-sync_job_error.asciidoc new file mode 100644 index 000000000..aba697d1c --- /dev/null +++ b/docs/reference-connector-sync_job_error.asciidoc @@ -0,0 +1,59 @@ +[[reference-connector-sync_job_error]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobError + +Sets an error for a connector sync job. + +{ref}/set-connector-sync-job-error-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobErrorRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobErrorRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `ConnectorSyncJobErrorResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-connector-sync_job_get.asciidoc b/docs/reference-connector-sync_job_get.asciidoc new file mode 100644 index 000000000..3439c1200 --- /dev/null +++ b/docs/reference-connector-sync_job_get.asciidoc @@ -0,0 +1,60 @@ +[[reference-connector-sync_job_get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobGet + +Get a connector sync job. + +{ref}/get-connector-sync-job-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobGetRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobGetRequest` + +[source,ts] +---- +interface ConnectorSyncJobGetRequest extends <> { + connector_sync_job_id: <> +} +---- + +[discrete] +===== `ConnectorSyncJobGetResponse` + +[source,ts] +---- +type ConnectorSyncJobGetResponse = ConnectorConnectorSyncJob +---- + diff --git a/docs/reference-connector-sync_job_list.asciidoc b/docs/reference-connector-sync_job_list.asciidoc new file mode 100644 index 000000000..0f2c9ffbf --- /dev/null +++ b/docs/reference-connector-sync_job_list.asciidoc @@ -0,0 +1,67 @@ +[[reference-connector-sync_job_list]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobList + +Get all connector sync jobs. Get information about all stored connector sync jobs listed by their creation date in ascending order. + +{ref}/list-connector-sync-jobs-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobListRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobListRequest` + +[source,ts] +---- +interface ConnectorSyncJobListRequest extends <> { + from?: <> + size?: <> + status?: ConnectorSyncStatus + connector_id?: <> + job_type?: ConnectorSyncJobType | ConnectorSyncJobType[] +} +---- + +[discrete] +===== `ConnectorSyncJobListResponse` + +[source,ts] +---- +interface ConnectorSyncJobListResponse { + count: <> + results: ConnectorConnectorSyncJob[] +} +---- + diff --git a/docs/reference-connector-sync_job_post.asciidoc b/docs/reference-connector-sync_job_post.asciidoc new file mode 100644 index 000000000..6dc0597e0 --- /dev/null +++ b/docs/reference-connector-sync_job_post.asciidoc @@ -0,0 +1,64 @@ +[[reference-connector-sync_job_post]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobPost + +Create a connector sync job. Create a connector sync job document in the internal index and initialize its counters and timestamps with default values. + +{ref}/create-connector-sync-job-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobPostRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobPostRequest` + +[source,ts] +---- +interface ConnectorSyncJobPostRequest extends <> { + id: <> + job_type?: ConnectorSyncJobType + trigger_method?: ConnectorSyncJobTriggerMethod +} +---- + +[discrete] +===== `ConnectorSyncJobPostResponse` + +[source,ts] +---- +interface ConnectorSyncJobPostResponse { + id: <> +} +---- + diff --git a/docs/reference-connector-sync_job_update_stats.asciidoc b/docs/reference-connector-sync_job_update_stats.asciidoc new file mode 100644 index 000000000..8ef50dd09 --- /dev/null +++ b/docs/reference-connector-sync_job_update_stats.asciidoc @@ -0,0 +1,59 @@ +[[reference-connector-sync_job_update_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.syncJobUpdateStats + +Updates the stats fields in the connector sync job document. + +{ref}/set-connector-sync-job-stats-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorSyncJobUpdateStatsRequest, options?): Promise +---- + +[discrete] +===== `ConnectorSyncJobUpdateStatsRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `ConnectorSyncJobUpdateStatsResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-connector-update_active_filtering.asciidoc b/docs/reference-connector-update_active_filtering.asciidoc new file mode 100644 index 000000000..2830c9f78 --- /dev/null +++ b/docs/reference-connector-update_active_filtering.asciidoc @@ -0,0 +1,62 @@ +[[reference-connector-update_active_filtering]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateActiveFiltering + +Activate the connector draft filter. Activates the valid draft filtering for a connector. + +{ref}/update-connector-filtering-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateActiveFilteringRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateActiveFilteringRequest` + +[source,ts] +---- +interface ConnectorUpdateActiveFilteringRequest extends <> { + connector_id: <> +} +---- + +[discrete] +===== `ConnectorUpdateActiveFilteringResponse` + +[source,ts] +---- +interface ConnectorUpdateActiveFilteringResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_api_key_id.asciidoc b/docs/reference-connector-update_api_key_id.asciidoc new file mode 100644 index 000000000..1ca5ef059 --- /dev/null +++ b/docs/reference-connector-update_api_key_id.asciidoc @@ -0,0 +1,64 @@ +[[reference-connector-update_api_key_id]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateApiKeyId + +Update the connector API key ID. Update the `api_key_id` and `api_key_secret_id` fields of a connector. You can specify the ID of the API key used for authorization and the ID of the connector secret where the API key is stored. The connector secret ID is required only for Elastic managed (native) connectors. Self-managed connectors (connector clients) do not use this field. + +{ref}/update-connector-api-key-id-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateApiKeyIdRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateApiKeyIdRequest` + +[source,ts] +---- +interface ConnectorUpdateApiKeyIdRequest extends <> { + connector_id: <> + api_key_id?: string + api_key_secret_id?: string +} +---- + +[discrete] +===== `ConnectorUpdateApiKeyIdResponse` + +[source,ts] +---- +interface ConnectorUpdateApiKeyIdResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_configuration.asciidoc b/docs/reference-connector-update_configuration.asciidoc new file mode 100644 index 000000000..f08862717 --- /dev/null +++ b/docs/reference-connector-update_configuration.asciidoc @@ -0,0 +1,64 @@ +[[reference-connector-update_configuration]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateConfiguration + +Update the connector configuration. Update the configuration field in the connector document. + +{ref}/update-connector-configuration-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateConfigurationRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateConfigurationRequest` + +[source,ts] +---- +interface ConnectorUpdateConfigurationRequest extends <> { + connector_id: <> + configuration?: ConnectorConnectorConfiguration + values?: Record +} +---- + +[discrete] +===== `ConnectorUpdateConfigurationResponse` + +[source,ts] +---- +interface ConnectorUpdateConfigurationResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_error.asciidoc b/docs/reference-connector-update_error.asciidoc new file mode 100644 index 000000000..d3dcc566a --- /dev/null +++ b/docs/reference-connector-update_error.asciidoc @@ -0,0 +1,63 @@ +[[reference-connector-update_error]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateError + +Update the connector error field. Set the error field for the connector. If the error provided in the request body is non-null, the connector’s status is updated to error. Otherwise, if the error is reset to null, the connector status is updated to connected. + +{ref}/update-connector-error-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateErrorRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateErrorRequest` + +[source,ts] +---- +interface ConnectorUpdateErrorRequest extends <> { + connector_id: <> + error: SpecUtilsWithNullValue +} +---- + +[discrete] +===== `ConnectorUpdateErrorResponse` + +[source,ts] +---- +interface ConnectorUpdateErrorResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_features.asciidoc b/docs/reference-connector-update_features.asciidoc new file mode 100644 index 000000000..ceb4f10b4 --- /dev/null +++ b/docs/reference-connector-update_features.asciidoc @@ -0,0 +1,59 @@ +[[reference-connector-update_features]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateFeatures + +Updates the connector features in the connector document. + +{ref}/update-connector-features-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateFeaturesRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateFeaturesRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `ConnectorUpdateFeaturesResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-connector-update_filtering.asciidoc b/docs/reference-connector-update_filtering.asciidoc new file mode 100644 index 000000000..2fab8b40b --- /dev/null +++ b/docs/reference-connector-update_filtering.asciidoc @@ -0,0 +1,65 @@ +[[reference-connector-update_filtering]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateFiltering + +Update the connector filtering. Update the draft filtering configuration of a connector and marks the draft validation state as edited. The filtering draft is activated once validated by the running Elastic connector service. The filtering property is used to configure sync rules (both basic and advanced) for a connector. + +{ref}/update-connector-filtering-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateFilteringRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateFilteringRequest` + +[source,ts] +---- +interface ConnectorUpdateFilteringRequest extends <> { + connector_id: <> + filtering?: ConnectorFilteringConfig[] + rules?: ConnectorFilteringRule[] + advanced_snippet?: ConnectorFilteringAdvancedSnippet +} +---- + +[discrete] +===== `ConnectorUpdateFilteringResponse` + +[source,ts] +---- +interface ConnectorUpdateFilteringResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_filtering_validation.asciidoc b/docs/reference-connector-update_filtering_validation.asciidoc new file mode 100644 index 000000000..877d76682 --- /dev/null +++ b/docs/reference-connector-update_filtering_validation.asciidoc @@ -0,0 +1,61 @@ +[[reference-connector-update_filtering_validation]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateFilteringValidation + +Update the connector draft filtering validation. Update the draft filtering validation info for a connector. + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateFilteringValidationRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateFilteringValidationRequest` + +[source,ts] +---- +interface ConnectorUpdateFilteringValidationRequest extends <> { + connector_id: <> + validation: ConnectorFilteringRulesValidation +} +---- + +[discrete] +===== `ConnectorUpdateFilteringValidationResponse` + +[source,ts] +---- +interface ConnectorUpdateFilteringValidationResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_index_name.asciidoc b/docs/reference-connector-update_index_name.asciidoc new file mode 100644 index 000000000..e13f2d775 --- /dev/null +++ b/docs/reference-connector-update_index_name.asciidoc @@ -0,0 +1,63 @@ +[[reference-connector-update_index_name]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateIndexName + +Update the connector index name. Update the `index_name` field of a connector, specifying the index where the data ingested by the connector is stored. + +{ref}/update-connector-index-name-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateIndexNameRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateIndexNameRequest` + +[source,ts] +---- +interface ConnectorUpdateIndexNameRequest extends <> { + connector_id: <> + index_name: SpecUtilsWithNullValue<<>> +} +---- + +[discrete] +===== `ConnectorUpdateIndexNameResponse` + +[source,ts] +---- +interface ConnectorUpdateIndexNameResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_name.asciidoc b/docs/reference-connector-update_name.asciidoc new file mode 100644 index 000000000..c1716c5b6 --- /dev/null +++ b/docs/reference-connector-update_name.asciidoc @@ -0,0 +1,64 @@ +[[reference-connector-update_name]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateName + +Update the connector name and description. + +{ref}/update-connector-name-description-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateNameRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateNameRequest` + +[source,ts] +---- +interface ConnectorUpdateNameRequest extends <> { + connector_id: <> + name?: string + description?: string +} +---- + +[discrete] +===== `ConnectorUpdateNameResponse` + +[source,ts] +---- +interface ConnectorUpdateNameResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_native.asciidoc b/docs/reference-connector-update_native.asciidoc new file mode 100644 index 000000000..288b88827 --- /dev/null +++ b/docs/reference-connector-update_native.asciidoc @@ -0,0 +1,61 @@ +[[reference-connector-update_native]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateNative + +Update the connector is_native flag. + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateNativeRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateNativeRequest` + +[source,ts] +---- +interface ConnectorUpdateNativeRequest extends <> { + connector_id: <> + is_native: boolean +} +---- + +[discrete] +===== `ConnectorUpdateNativeResponse` + +[source,ts] +---- +interface ConnectorUpdateNativeResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_pipeline.asciidoc b/docs/reference-connector-update_pipeline.asciidoc new file mode 100644 index 000000000..37911dd56 --- /dev/null +++ b/docs/reference-connector-update_pipeline.asciidoc @@ -0,0 +1,63 @@ +[[reference-connector-update_pipeline]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updatePipeline + +Update the connector pipeline. When you create a new connector, the configuration of an ingest pipeline is populated with default settings. + +{ref}/update-connector-pipeline-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdatePipelineRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdatePipelineRequest` + +[source,ts] +---- +interface ConnectorUpdatePipelineRequest extends <> { + connector_id: <> + pipeline: ConnectorIngestPipelineParams +} +---- + +[discrete] +===== `ConnectorUpdatePipelineResponse` + +[source,ts] +---- +interface ConnectorUpdatePipelineResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_scheduling.asciidoc b/docs/reference-connector-update_scheduling.asciidoc new file mode 100644 index 000000000..7eaca3c4d --- /dev/null +++ b/docs/reference-connector-update_scheduling.asciidoc @@ -0,0 +1,63 @@ +[[reference-connector-update_scheduling]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateScheduling + +Update the connector scheduling. + +{ref}/update-connector-scheduling-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateSchedulingRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateSchedulingRequest` + +[source,ts] +---- +interface ConnectorUpdateSchedulingRequest extends <> { + connector_id: <> + scheduling: ConnectorSchedulingConfiguration +} +---- + +[discrete] +===== `ConnectorUpdateSchedulingResponse` + +[source,ts] +---- +interface ConnectorUpdateSchedulingResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_service_type.asciidoc b/docs/reference-connector-update_service_type.asciidoc new file mode 100644 index 000000000..e82725586 --- /dev/null +++ b/docs/reference-connector-update_service_type.asciidoc @@ -0,0 +1,63 @@ +[[reference-connector-update_service_type]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateServiceType + +Update the connector service type. + +{ref}/update-connector-service-type-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateServiceTypeRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateServiceTypeRequest` + +[source,ts] +---- +interface ConnectorUpdateServiceTypeRequest extends <> { + connector_id: <> + service_type: string +} +---- + +[discrete] +===== `ConnectorUpdateServiceTypeResponse` + +[source,ts] +---- +interface ConnectorUpdateServiceTypeResponse { + result: <> +} +---- + diff --git a/docs/reference-connector-update_status.asciidoc b/docs/reference-connector-update_status.asciidoc new file mode 100644 index 000000000..f35072c82 --- /dev/null +++ b/docs/reference-connector-update_status.asciidoc @@ -0,0 +1,63 @@ +[[reference-connector-update_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.connector.updateStatus + +Update the connector status. + +{ref}/update-connector-status-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ConnectorUpdateStatusRequest, options?): Promise +---- + +[discrete] +===== `ConnectorUpdateStatusRequest` + +[source,ts] +---- +interface ConnectorUpdateStatusRequest extends <> { + connector_id: <> + status: ConnectorConnectorStatus +} +---- + +[discrete] +===== `ConnectorUpdateStatusResponse` + +[source,ts] +---- +interface ConnectorUpdateStatusResponse { + result: <> +} +---- + diff --git a/docs/reference-count.asciidoc b/docs/reference-count.asciidoc new file mode 100644 index 000000000..12d641929 --- /dev/null +++ b/docs/reference-count.asciidoc @@ -0,0 +1,78 @@ +[[reference-count]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.count + +Returns number of documents matching a query. + +{ref}/search-count.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CountRequest, options?): Promise +---- + +[discrete] +===== `CountRequest` + +[source,ts] +---- +interface CountRequest extends <> { + index?: <> + allow_no_indices?: boolean + analyzer?: string + analyze_wildcard?: boolean + default_operator?: QueryDslOperator + df?: string + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + lenient?: boolean + min_score?: <> + preference?: string + routing?: <> + terminate_after?: <> + q?: string + query?: QueryDslQueryContainer +} +---- + +[discrete] +===== `CountResponse` + +[source,ts] +---- +interface CountResponse { + count: <> + _shards: <> +} +---- + diff --git a/docs/reference-create.asciidoc b/docs/reference-create.asciidoc new file mode 100644 index 000000000..43453e186 --- /dev/null +++ b/docs/reference-create.asciidoc @@ -0,0 +1,69 @@ +[[reference-create]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.create + +Index a document. Adds a JSON document to the specified data stream or index and makes it searchable. If the target is an index and the document already exists, the request updates the document and increments its version. + +{ref}/docs-index_.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(CreateRequest, options?): Promise +---- + +[discrete] +===== `CreateRequest` + +[source,ts] +---- +interface CreateRequest extends <> { + id: <> + index: <> + pipeline?: string + refresh?: <> + routing?: <> + timeout?: <> + version?: <> + version_type?: <> + wait_for_active_shards?: <> + document?: TDocument +} +---- + +[discrete] +===== `CreateResponse` + +[source,ts] +---- +type CreateResponse = <> +---- + diff --git a/docs/reference-dangling_indices-delete_dangling_index.asciidoc b/docs/reference-dangling_indices-delete_dangling_index.asciidoc new file mode 100644 index 000000000..a792988f6 --- /dev/null +++ b/docs/reference-dangling_indices-delete_dangling_index.asciidoc @@ -0,0 +1,63 @@ +[[reference-dangling_indices-delete_dangling_index]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.danglingIndices.deleteDanglingIndex + +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. + +{ref}/modules-gateway-dangling-indices.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(DanglingIndicesDeleteDanglingIndexRequest, options?): Promise +---- + +[discrete] +===== `DanglingIndicesDeleteDanglingIndexRequest` + +[source,ts] +---- +interface DanglingIndicesDeleteDanglingIndexRequest extends <> { + index_uuid: <> + accept_data_loss: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `DanglingIndicesDeleteDanglingIndexResponse` + +[source,ts] +---- +type DanglingIndicesDeleteDanglingIndexResponse = <> +---- + diff --git a/docs/reference-dangling_indices-import_dangling_index.asciidoc b/docs/reference-dangling_indices-import_dangling_index.asciidoc new file mode 100644 index 000000000..8d2af4bf2 --- /dev/null +++ b/docs/reference-dangling_indices-import_dangling_index.asciidoc @@ -0,0 +1,63 @@ +[[reference-dangling_indices-import_dangling_index]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.danglingIndices.importDanglingIndex + +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. + +{ref}/modules-gateway-dangling-indices.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(DanglingIndicesImportDanglingIndexRequest, options?): Promise +---- + +[discrete] +===== `DanglingIndicesImportDanglingIndexRequest` + +[source,ts] +---- +interface DanglingIndicesImportDanglingIndexRequest extends <> { + index_uuid: <> + accept_data_loss: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `DanglingIndicesImportDanglingIndexResponse` + +[source,ts] +---- +type DanglingIndicesImportDanglingIndexResponse = <> +---- + diff --git a/docs/reference-dangling_indices-list_dangling_indices.asciidoc b/docs/reference-dangling_indices-list_dangling_indices.asciidoc new file mode 100644 index 000000000..402e87d46 --- /dev/null +++ b/docs/reference-dangling_indices-list_dangling_indices.asciidoc @@ -0,0 +1,61 @@ +[[reference-dangling_indices-list_dangling_indices]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.danglingIndices.listDanglingIndices + +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. + +{ref}/modules-gateway-dangling-indices.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(DanglingIndicesListDanglingIndicesRequest, options?): Promise +---- + +[discrete] +===== `DanglingIndicesListDanglingIndicesRequest` + +[source,ts] +---- +interface DanglingIndicesListDanglingIndicesRequest extends <> { +} +---- + +[discrete] +===== `DanglingIndicesListDanglingIndicesResponse` + +[source,ts] +---- +interface DanglingIndicesListDanglingIndicesResponse { + dangling_indices: DanglingIndicesListDanglingIndicesDanglingIndex[] +} +---- + diff --git a/docs/reference-delete.asciidoc b/docs/reference-delete.asciidoc new file mode 100644 index 000000000..3476cf1f7 --- /dev/null +++ b/docs/reference-delete.asciidoc @@ -0,0 +1,69 @@ +[[reference-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.delete + +Delete a document. Removes a JSON document from the specified index. + +{ref}/docs-delete.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(DeleteRequest, options?): Promise +---- + +[discrete] +===== `DeleteRequest` + +[source,ts] +---- +interface DeleteRequest extends <> { + id: <> + index: <> + if_primary_term?: <> + if_seq_no?: <> + refresh?: <> + routing?: <> + timeout?: <> + version?: <> + version_type?: <> + wait_for_active_shards?: <> +} +---- + +[discrete] +===== `DeleteResponse` + +[source,ts] +---- +type DeleteResponse = <> +---- + diff --git a/docs/reference-delete_by_query.asciidoc b/docs/reference-delete_by_query.asciidoc new file mode 100644 index 000000000..78c8c75d5 --- /dev/null +++ b/docs/reference-delete_by_query.asciidoc @@ -0,0 +1,108 @@ +[[reference-delete_by_query]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.deleteByQuery + +Delete documents. Deletes documents that match the specified query. + +{ref}/docs-delete-by-query.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(DeleteByQueryRequest, options?): Promise +---- + +[discrete] +===== `DeleteByQueryRequest` + +[source,ts] +---- +interface DeleteByQueryRequest extends <> { + index: <> + allow_no_indices?: boolean + analyzer?: string + analyze_wildcard?: boolean + conflicts?: <> + default_operator?: QueryDslOperator + df?: string + expand_wildcards?: <> + from?: <> + ignore_unavailable?: boolean + lenient?: boolean + preference?: string + refresh?: boolean + request_cache?: boolean + requests_per_second?: <> + routing?: <> + q?: string + scroll?: <> + scroll_size?: <> + search_timeout?: <> + search_type?: <> + slices?: <> + sort?: string[] + stats?: string[] + terminate_after?: <> + timeout?: <> + version?: boolean + wait_for_active_shards?: <> + wait_for_completion?: boolean + max_docs?: <> + query?: QueryDslQueryContainer + slice?: <> +} +---- + +[discrete] +===== `DeleteByQueryResponse` + +[source,ts] +---- +interface DeleteByQueryResponse { + batches?: <> + deleted?: <> + failures?: <>[] + noops?: <> + requests_per_second?: <> + retries?: <> + slice_id?: <> + task?: <> + throttled?: <> + throttled_millis?: <><<>> + throttled_until?: <> + throttled_until_millis?: <><<>> + timed_out?: boolean + took?: <><<>> + total?: <> + version_conflicts?: <> +} +---- + diff --git a/docs/reference-delete_by_query_rethrottle.asciidoc b/docs/reference-delete_by_query_rethrottle.asciidoc new file mode 100644 index 000000000..cb0747ea5 --- /dev/null +++ b/docs/reference-delete_by_query_rethrottle.asciidoc @@ -0,0 +1,61 @@ +[[reference-delete_by_query_rethrottle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.deleteByQueryRethrottle + +Throttle a delete by query operation. Change the number of requests per second for a particular delete 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. + +{ref}/docs-delete-by-query.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(DeleteByQueryRethrottleRequest, options?): Promise +---- + +[discrete] +===== `DeleteByQueryRethrottleRequest` + +[source,ts] +---- +interface DeleteByQueryRethrottleRequest extends <> { + task_id: <> + requests_per_second?: <> +} +---- + +[discrete] +===== `DeleteByQueryRethrottleResponse` + +[source,ts] +---- +type DeleteByQueryRethrottleResponse = TasksTaskListResponseBase +---- + diff --git a/docs/reference-delete_script.asciidoc b/docs/reference-delete_script.asciidoc new file mode 100644 index 000000000..d49c10add --- /dev/null +++ b/docs/reference-delete_script.asciidoc @@ -0,0 +1,62 @@ +[[reference-delete_script]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.deleteScript + +Delete a script or search template. Deletes a stored script or search template. + +{ref}/modules-scripting.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(DeleteScriptRequest, options?): Promise +---- + +[discrete] +===== `DeleteScriptRequest` + +[source,ts] +---- +interface DeleteScriptRequest extends <> { + id: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `DeleteScriptResponse` + +[source,ts] +---- +type DeleteScriptResponse = <> +---- + diff --git a/docs/reference-enrich-delete_policy.asciidoc b/docs/reference-enrich-delete_policy.asciidoc new file mode 100644 index 000000000..e1b5df7d5 --- /dev/null +++ b/docs/reference-enrich-delete_policy.asciidoc @@ -0,0 +1,60 @@ +[[reference-enrich-delete_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.enrich.deletePolicy + +Delete an enrich policy. Deletes an existing enrich policy and its enrich index. + +{ref}/delete-enrich-policy-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EnrichDeletePolicyRequest, options?): Promise +---- + +[discrete] +===== `EnrichDeletePolicyRequest` + +[source,ts] +---- +interface EnrichDeletePolicyRequest extends <> { + name: <> +} +---- + +[discrete] +===== `EnrichDeletePolicyResponse` + +[source,ts] +---- +type EnrichDeletePolicyResponse = <> +---- + diff --git a/docs/reference-enrich-execute_policy.asciidoc b/docs/reference-enrich-execute_policy.asciidoc new file mode 100644 index 000000000..9cd1c6aea --- /dev/null +++ b/docs/reference-enrich-execute_policy.asciidoc @@ -0,0 +1,64 @@ +[[reference-enrich-execute_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.enrich.executePolicy + +Creates the enrich index for an existing enrich policy. + +{ref}/execute-enrich-policy-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EnrichExecutePolicyRequest, options?): Promise +---- + +[discrete] +===== `EnrichExecutePolicyRequest` + +[source,ts] +---- +interface EnrichExecutePolicyRequest extends <> { + name: <> + wait_for_completion?: boolean +} +---- + +[discrete] +===== `EnrichExecutePolicyResponse` + +[source,ts] +---- +interface EnrichExecutePolicyResponse { + status?: EnrichExecutePolicyExecuteEnrichPolicyStatus + task_id?: <> +} +---- + diff --git a/docs/reference-enrich-get_policy.asciidoc b/docs/reference-enrich-get_policy.asciidoc new file mode 100644 index 000000000..b2b818d0c --- /dev/null +++ b/docs/reference-enrich-get_policy.asciidoc @@ -0,0 +1,62 @@ +[[reference-enrich-get_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.enrich.getPolicy + +Get an enrich policy. Returns information about an enrich policy. + +{ref}/get-enrich-policy-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EnrichGetPolicyRequest, options?): Promise +---- + +[discrete] +===== `EnrichGetPolicyRequest` + +[source,ts] +---- +interface EnrichGetPolicyRequest extends <> { + name?: <> +} +---- + +[discrete] +===== `EnrichGetPolicyResponse` + +[source,ts] +---- +interface EnrichGetPolicyResponse { + policies: EnrichSummary[] +} +---- + diff --git a/docs/reference-enrich-put_policy.asciidoc b/docs/reference-enrich-put_policy.asciidoc new file mode 100644 index 000000000..723734465 --- /dev/null +++ b/docs/reference-enrich-put_policy.asciidoc @@ -0,0 +1,63 @@ +[[reference-enrich-put_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.enrich.putPolicy + +Create an enrich policy. Creates an enrich policy. + +{ref}/put-enrich-policy-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EnrichPutPolicyRequest, options?): Promise +---- + +[discrete] +===== `EnrichPutPolicyRequest` + +[source,ts] +---- +interface EnrichPutPolicyRequest extends <> { + name: <> + geo_match?: EnrichPolicy + match?: EnrichPolicy + range?: EnrichPolicy +} +---- + +[discrete] +===== `EnrichPutPolicyResponse` + +[source,ts] +---- +type EnrichPutPolicyResponse = <> +---- + diff --git a/docs/reference-enrich-stats.asciidoc b/docs/reference-enrich-stats.asciidoc new file mode 100644 index 000000000..9ff421709 --- /dev/null +++ b/docs/reference-enrich-stats.asciidoc @@ -0,0 +1,63 @@ +[[reference-enrich-stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.enrich.stats + +Get enrich stats. Returns enrich coordinator statistics and information about enrich policies that are currently executing. + +{ref}/enrich-stats-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EnrichStatsRequest, options?): Promise +---- + +[discrete] +===== `EnrichStatsRequest` + +[source,ts] +---- +interface EnrichStatsRequest extends <> { +} +---- + +[discrete] +===== `EnrichStatsResponse` + +[source,ts] +---- +interface EnrichStatsResponse { + coordinator_stats: EnrichStatsCoordinatorStats[] + executing_policies: EnrichStatsExecutingPolicy[] + cache_stats?: EnrichStatsCacheStats[] +} +---- + diff --git a/docs/reference-eql-delete.asciidoc b/docs/reference-eql-delete.asciidoc new file mode 100644 index 000000000..d2260e2f9 --- /dev/null +++ b/docs/reference-eql-delete.asciidoc @@ -0,0 +1,60 @@ +[[reference-eql-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.eql.delete + +Deletes an async EQL search or a stored synchronous EQL search. The API also deletes results for the search. + +{ref}/eql-search-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EqlDeleteRequest, options?): Promise +---- + +[discrete] +===== `EqlDeleteRequest` + +[source,ts] +---- +interface EqlDeleteRequest extends <> { + id: <> +} +---- + +[discrete] +===== `EqlDeleteResponse` + +[source,ts] +---- +type EqlDeleteResponse = <> +---- + diff --git a/docs/reference-eql-get.asciidoc b/docs/reference-eql-get.asciidoc new file mode 100644 index 000000000..202618cfd --- /dev/null +++ b/docs/reference-eql-get.asciidoc @@ -0,0 +1,62 @@ +[[reference-eql-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.eql.get + +Returns the current status and available results for an async EQL search or a stored synchronous EQL search. + +{ref}/get-async-eql-search-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EqlGetRequest, options?): Promise +---- + +[discrete] +===== `EqlGetRequest` + +[source,ts] +---- +interface EqlGetRequest extends <> { + id: <> + keep_alive?: <> + wait_for_completion_timeout?: <> +} +---- + +[discrete] +===== `EqlGetResponse` + +[source,ts] +---- +type EqlGetResponse = EqlEqlSearchResponseBase +---- + diff --git a/docs/reference-eql-get_status.asciidoc b/docs/reference-eql-get_status.asciidoc new file mode 100644 index 000000000..7fe4ca200 --- /dev/null +++ b/docs/reference-eql-get_status.asciidoc @@ -0,0 +1,67 @@ +[[reference-eql-get_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.eql.getStatus + +Returns the current status for an async EQL search or a stored synchronous EQL search without returning results. + +{ref}/get-async-eql-status-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EqlGetStatusRequest, options?): Promise +---- + +[discrete] +===== `EqlGetStatusRequest` + +[source,ts] +---- +interface EqlGetStatusRequest extends <> { + id: <> +} +---- + +[discrete] +===== `EqlGetStatusResponse` + +[source,ts] +---- +interface EqlGetStatusResponse { + id: <> + is_partial: boolean + is_running: boolean + start_time_in_millis?: <><<>> + expiration_time_in_millis?: <><<>> + completion_status?: <> +} +---- + diff --git a/docs/reference-eql-search.asciidoc b/docs/reference-eql-search.asciidoc new file mode 100644 index 000000000..3354f26e2 --- /dev/null +++ b/docs/reference-eql-search.asciidoc @@ -0,0 +1,77 @@ +[[reference-eql-search]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.eql.search + +Returns results matching a query expressed in Event Query Language (EQL) + +{ref}/eql-search-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EqlSearchRequest, options?): Promise +---- + +[discrete] +===== `EqlSearchRequest` + +[source,ts] +---- +interface EqlSearchRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + query: string + case_sensitive?: boolean + event_category_field?: <> + tiebreaker_field?: <> + timestamp_field?: <> + fetch_size?: <> + filter?: QueryDslQueryContainer | QueryDslQueryContainer[] + keep_alive?: <> + keep_on_completion?: boolean + wait_for_completion_timeout?: <> + size?: <> + fields?: QueryDslFieldAndFormat | <> | (QueryDslFieldAndFormat | <>)[] + result_position?: EqlSearchResultPosition + runtime_mappings?: MappingRuntimeFields +} +---- + +[discrete] +===== `EqlSearchResponse` + +[source,ts] +---- +type EqlSearchResponse = EqlEqlSearchResponseBase +---- + diff --git a/docs/reference-esql-async_query.asciidoc b/docs/reference-esql-async_query.asciidoc new file mode 100644 index 000000000..0cc9bcb65 --- /dev/null +++ b/docs/reference-esql-async_query.asciidoc @@ -0,0 +1,59 @@ +[[reference-esql-async_query]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.esql.asyncQuery + +Executes an ESQL request asynchronously + +{ref}/esql-async-query-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EsqlAsyncQueryRequest, options?): Promise +---- + +[discrete] +===== `EsqlAsyncQueryRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `EsqlAsyncQueryResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-esql-async_query_get.asciidoc b/docs/reference-esql-async_query_get.asciidoc new file mode 100644 index 000000000..ffd187289 --- /dev/null +++ b/docs/reference-esql-async_query_get.asciidoc @@ -0,0 +1,59 @@ +[[reference-esql-async_query_get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.esql.asyncQueryGet + +Retrieves the results of a previously submitted async query request given its ID. + +{ref}/esql-async-query-get-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EsqlAsyncQueryGetRequest, options?): Promise +---- + +[discrete] +===== `EsqlAsyncQueryGetRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `EsqlAsyncQueryGetResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-esql-query.asciidoc b/docs/reference-esql-query.asciidoc new file mode 100644 index 000000000..30586cffd --- /dev/null +++ b/docs/reference-esql-query.asciidoc @@ -0,0 +1,69 @@ +[[reference-esql-query]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.esql.query + +Executes an ES|QL request + +{ref}/esql-rest.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(EsqlQueryRequest, options?): Promise +---- + +[discrete] +===== `EsqlQueryRequest` + +[source,ts] +---- +interface EsqlQueryRequest extends <> { + format?: EsqlQueryEsqlFormat + delimiter?: string + drop_null_columns?: boolean + columnar?: boolean + filter?: QueryDslQueryContainer + locale?: string + params?: <>[] + profile?: boolean + query: string + tables?: Record> +} +---- + +[discrete] +===== `EsqlQueryResponse` + +[source,ts] +---- +type EsqlQueryResponse = <> +---- + diff --git a/docs/reference-exists.asciidoc b/docs/reference-exists.asciidoc new file mode 100644 index 000000000..d16504355 --- /dev/null +++ b/docs/reference-exists.asciidoc @@ -0,0 +1,71 @@ +[[reference-exists]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.exists + +Check a document. Checks if a specified document exists. + +{ref}/docs-get.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ExistsRequest, options?): Promise +---- + +[discrete] +===== `ExistsRequest` + +[source,ts] +---- +interface ExistsRequest extends <> { + id: <> + index: <> + preference?: string + realtime?: boolean + refresh?: boolean + routing?: <> + _source?: SearchSourceConfigParam + _source_excludes?: <> + _source_includes?: <> + stored_fields?: <> + version?: <> + version_type?: <> +} +---- + +[discrete] +===== `ExistsResponse` + +[source,ts] +---- +type ExistsResponse = boolean +---- + diff --git a/docs/reference-exists_source.asciidoc b/docs/reference-exists_source.asciidoc new file mode 100644 index 000000000..e07df6f88 --- /dev/null +++ b/docs/reference-exists_source.asciidoc @@ -0,0 +1,70 @@ +[[reference-exists_source]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.existsSource + +Check for a document source. Checks if a document's `_source` is stored. + +{ref}/docs-get.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ExistsSourceRequest, options?): Promise +---- + +[discrete] +===== `ExistsSourceRequest` + +[source,ts] +---- +interface ExistsSourceRequest extends <> { + id: <> + index: <> + preference?: string + realtime?: boolean + refresh?: boolean + routing?: <> + _source?: SearchSourceConfigParam + _source_excludes?: <> + _source_includes?: <> + version?: <> + version_type?: <> +} +---- + +[discrete] +===== `ExistsSourceResponse` + +[source,ts] +---- +type ExistsSourceResponse = boolean +---- + diff --git a/docs/reference-explain.asciidoc b/docs/reference-explain.asciidoc new file mode 100644 index 000000000..04a5a4d11 --- /dev/null +++ b/docs/reference-explain.asciidoc @@ -0,0 +1,80 @@ +[[reference-explain]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.explain + +Explain a document match result. Returns information about why a specific document matches, or doesn’t match, a query. + +{ref}/search-explain.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ExplainRequest, options?): Promise +---- + +[discrete] +===== `ExplainRequest` + +[source,ts] +---- +interface ExplainRequest extends <> { + id: <> + index: <> + analyzer?: string + analyze_wildcard?: boolean + default_operator?: QueryDslOperator + df?: string + lenient?: boolean + preference?: string + routing?: <> + _source?: SearchSourceConfigParam + _source_excludes?: <> + _source_includes?: <> + stored_fields?: <> + q?: string + query?: QueryDslQueryContainer +} +---- + +[discrete] +===== `ExplainResponse` + +[source,ts] +---- +interface ExplainResponse { + _index: <> + _id: <> + matched: boolean + explanation?: ExplainExplanationDetail + get?: <> +} +---- + diff --git a/docs/reference-features-get_features.asciidoc b/docs/reference-features-get_features.asciidoc new file mode 100644 index 000000000..b30187fac --- /dev/null +++ b/docs/reference-features-get_features.asciidoc @@ -0,0 +1,61 @@ +[[reference-features-get_features]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.features.getFeatures + +Gets a list of features which can be included in snapshots using the feature_states field when creating a snapshot + +{ref}/get-features-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(FeaturesGetFeaturesRequest, options?): Promise +---- + +[discrete] +===== `FeaturesGetFeaturesRequest` + +[source,ts] +---- +interface FeaturesGetFeaturesRequest extends <> { +} +---- + +[discrete] +===== `FeaturesGetFeaturesResponse` + +[source,ts] +---- +interface FeaturesGetFeaturesResponse { + features: FeaturesFeature[] +} +---- + diff --git a/docs/reference-features-reset_features.asciidoc b/docs/reference-features-reset_features.asciidoc new file mode 100644 index 000000000..9839a20de --- /dev/null +++ b/docs/reference-features-reset_features.asciidoc @@ -0,0 +1,61 @@ +[[reference-features-reset_features]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.features.resetFeatures + +Resets the internal state of features, usually by deleting system indices + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(FeaturesResetFeaturesRequest, options?): Promise +---- + +[discrete] +===== `FeaturesResetFeaturesRequest` + +[source,ts] +---- +interface FeaturesResetFeaturesRequest extends <> { +} +---- + +[discrete] +===== `FeaturesResetFeaturesResponse` + +[source,ts] +---- +interface FeaturesResetFeaturesResponse { + features: FeaturesFeature[] +} +---- + diff --git a/docs/reference-field_caps.asciidoc b/docs/reference-field_caps.asciidoc new file mode 100644 index 000000000..8df5df73b --- /dev/null +++ b/docs/reference-field_caps.asciidoc @@ -0,0 +1,73 @@ +[[reference-field_caps]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.fieldCaps + +Get the field capabilities. Get information about the capabilities of fields among multiple indices. For data streams, the API returns field capabilities among the stream’s backing indices. It returns runtime fields like any other field. For example, a runtime field with a type of keyword is returned the same as any other field that belongs to the `keyword` family. + +{ref}/search-field-caps.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(FieldCapsRequest, options?): Promise +---- + +[discrete] +===== `FieldCapsRequest` + +[source,ts] +---- +interface FieldCapsRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + include_unmapped?: boolean + filters?: string + types?: string[] + include_empty_fields?: boolean + fields?: <> + index_filter?: QueryDslQueryContainer + runtime_mappings?: MappingRuntimeFields +} +---- + +[discrete] +===== `FieldCapsResponse` + +[source,ts] +---- +interface FieldCapsResponse { + indices: <> + fields: Record<<>, Record> +} +---- + diff --git a/docs/reference-fleet-global_checkpoints.asciidoc b/docs/reference-fleet-global_checkpoints.asciidoc new file mode 100644 index 000000000..26a0921c1 --- /dev/null +++ b/docs/reference-fleet-global_checkpoints.asciidoc @@ -0,0 +1,67 @@ +[[reference-fleet-global_checkpoints]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.fleet.globalCheckpoints + +Returns the current global checkpoints for an index. This API is design for internal use by the fleet server project. + +{ref}/get-global-checkpoints.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(FleetGlobalCheckpointsRequest, options?): Promise +---- + +[discrete] +===== `FleetGlobalCheckpointsRequest` + +[source,ts] +---- +interface FleetGlobalCheckpointsRequest extends <> { + index: <> | <> + wait_for_advance?: boolean + wait_for_index?: boolean + checkpoints?: FleetCheckpoint[] + timeout?: <> +} +---- + +[discrete] +===== `FleetGlobalCheckpointsResponse` + +[source,ts] +---- +interface FleetGlobalCheckpointsResponse { + global_checkpoints: FleetCheckpoint[] + timed_out: boolean +} +---- + diff --git a/docs/reference-fleet-msearch.asciidoc b/docs/reference-fleet-msearch.asciidoc new file mode 100644 index 000000000..d5377d798 --- /dev/null +++ b/docs/reference-fleet-msearch.asciidoc @@ -0,0 +1,74 @@ +[[reference-fleet-msearch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.fleet.msearch + +Executes several [fleet searches](https://www.elastic.co/guide/en/elasticsearch/reference/current/fleet-search.html) with a single API request. The API follows the same structure as the [multi search](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-multi-search.html) API. However, similar to the fleet search API, it supports the wait_for_checkpoints parameter. + +[discrete] +==== Function signature + +[source,ts] +---- +(FleetMsearchRequest, options?): Promise +---- + +[discrete] +===== `FleetMsearchRequest` + +[source,ts] +---- +interface FleetMsearchRequest extends <> { + index?: <> | <> + allow_no_indices?: boolean + ccs_minimize_roundtrips?: boolean + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + max_concurrent_searches?: <> + max_concurrent_shard_requests?: <> + pre_filter_shard_size?: <> + search_type?: <> + rest_total_hits_as_int?: boolean + typed_keys?: boolean + wait_for_checkpoints?: FleetCheckpoint[] + allow_partial_search_results?: boolean + searches?: MsearchRequestItem[] +} +---- + +[discrete] +===== `FleetMsearchResponse` + +[source,ts] +---- +interface FleetMsearchResponse { + docs: MsearchResponseItem[] +} +---- + diff --git a/docs/reference-fleet-search.asciidoc b/docs/reference-fleet-search.asciidoc new file mode 100644 index 000000000..9f2cb2fc9 --- /dev/null +++ b/docs/reference-fleet-search.asciidoc @@ -0,0 +1,136 @@ +[[reference-fleet-search]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.fleet.search + +The purpose of the fleet search api is to provide a search api where the search will only be executed after provided checkpoint has been processed and is visible for searches inside of Elasticsearch. + +[discrete] +==== Function signature + +[source,ts] +---- +(FleetSearchRequest, options?): Promise +---- + +[discrete] +===== `FleetSearchRequest` + +[source,ts] +---- +interface FleetSearchRequest extends <> { + index: <> | <> + allow_no_indices?: boolean + analyzer?: string + analyze_wildcard?: boolean + batched_reduce_size?: <> + ccs_minimize_roundtrips?: boolean + default_operator?: QueryDslOperator + df?: string + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + lenient?: boolean + max_concurrent_shard_requests?: <> + min_compatible_shard_node?: <> + preference?: string + pre_filter_shard_size?: <> + request_cache?: boolean + routing?: <> + scroll?: <> + search_type?: <> + suggest_field?: <> + suggest_mode?: <> + suggest_size?: <> + suggest_text?: string + typed_keys?: boolean + rest_total_hits_as_int?: boolean + _source_excludes?: <> + _source_includes?: <> + q?: string + wait_for_checkpoints?: FleetCheckpoint[] + allow_partial_search_results?: boolean + aggregations?: Record + /** @alias aggregations */ + aggs?: Record + collapse?: SearchFieldCollapse + explain?: boolean + ext?: Record + from?: <> + highlight?: SearchHighlight + track_total_hits?: SearchTrackHits + indices_boost?: Record<<>, <>>[] + docvalue_fields?: (QueryDslFieldAndFormat | <>)[] + min_score?: <> + post_filter?: QueryDslQueryContainer + profile?: boolean + query?: QueryDslQueryContainer + rescore?: SearchRescore | SearchRescore[] + script_fields?: Record>> + search_after?: <> + size?: <> + slice?: <> + sort?: <> + _source?: SearchSourceConfig + fields?: (QueryDslFieldAndFormat | <>)[] + suggest?: SearchSuggester + terminate_after?: <> + timeout?: string + track_scores?: boolean + version?: boolean + seq_no_primary_term?: boolean + stored_fields?: <> + pit?: SearchPointInTimeReference + runtime_mappings?: MappingRuntimeFields + stats?: string[] +} +---- + +[discrete] +===== `FleetSearchResponse` + +[source,ts] +---- +interface FleetSearchResponse { + took: <> + timed_out: boolean + _shards: <> + hits: SearchHitsMetadata + aggregations?: Record<<>, AggregationsAggregate> + _clusters?: <> + fields?: Record + max_score?: <> + num_reduce_phases?: <> + profile?: SearchProfile + pit_id?: <> + _scroll_id?: <> + suggest?: Record<<>, SearchSuggest[]> + terminated_early?: boolean +} +---- + diff --git a/docs/reference-get.asciidoc b/docs/reference-get.asciidoc new file mode 100644 index 000000000..72ac6f1a0 --- /dev/null +++ b/docs/reference-get.asciidoc @@ -0,0 +1,72 @@ +[[reference-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.get + +Get a document by its ID. Retrieves the document with the specified ID from an index. + +{ref}/docs-get.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(GetRequest, options?): Promise +---- + +[discrete] +===== `GetRequest` + +[source,ts] +---- +interface GetRequest extends <> { + id: <> + index: <> + force_synthetic_source?: boolean + preference?: string + realtime?: boolean + refresh?: boolean + routing?: <> + _source?: SearchSourceConfigParam + _source_excludes?: <> + _source_includes?: <> + stored_fields?: <> + version?: <> + version_type?: <> +} +---- + +[discrete] +===== `GetResponse` + +[source,ts] +---- +type GetResponse = GetGetResult +---- + diff --git a/docs/reference-get_script.asciidoc b/docs/reference-get_script.asciidoc new file mode 100644 index 000000000..0c912e325 --- /dev/null +++ b/docs/reference-get_script.asciidoc @@ -0,0 +1,65 @@ +[[reference-get_script]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.getScript + +Get a script or search template. Retrieves a stored script or search template. + +{ref}/modules-scripting.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(GetScriptRequest, options?): Promise +---- + +[discrete] +===== `GetScriptRequest` + +[source,ts] +---- +interface GetScriptRequest extends <> { + id: <> + master_timeout?: <> +} +---- + +[discrete] +===== `GetScriptResponse` + +[source,ts] +---- +interface GetScriptResponse { + _id: <> + found: boolean + script?: <> +} +---- + diff --git a/docs/reference-get_script_context.asciidoc b/docs/reference-get_script_context.asciidoc new file mode 100644 index 000000000..2eb64c789 --- /dev/null +++ b/docs/reference-get_script_context.asciidoc @@ -0,0 +1,61 @@ +[[reference-get_script_context]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.getScriptContext + +Get script contexts. Get a list of supported script contexts and their methods. + +{painless}/painless-contexts.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(GetScriptContextRequest, options?): Promise +---- + +[discrete] +===== `GetScriptContextRequest` + +[source,ts] +---- +interface GetScriptContextRequest extends <> { +} +---- + +[discrete] +===== `GetScriptContextResponse` + +[source,ts] +---- +interface GetScriptContextResponse { + contexts: GetScriptContextContext[] +} +---- + diff --git a/docs/reference-get_script_languages.asciidoc b/docs/reference-get_script_languages.asciidoc new file mode 100644 index 000000000..86a71f2f1 --- /dev/null +++ b/docs/reference-get_script_languages.asciidoc @@ -0,0 +1,62 @@ +[[reference-get_script_languages]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.getScriptLanguages + +Get script languages. Get a list of available script types, languages, and contexts. + +{ref}/modules-scripting.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(GetScriptLanguagesRequest, options?): Promise +---- + +[discrete] +===== `GetScriptLanguagesRequest` + +[source,ts] +---- +interface GetScriptLanguagesRequest extends <> { +} +---- + +[discrete] +===== `GetScriptLanguagesResponse` + +[source,ts] +---- +interface GetScriptLanguagesResponse { + language_contexts: GetScriptLanguagesLanguageContext[] + types_allowed: string[] +} +---- + diff --git a/docs/reference-get_source.asciidoc b/docs/reference-get_source.asciidoc new file mode 100644 index 000000000..b5c13c3ee --- /dev/null +++ b/docs/reference-get_source.asciidoc @@ -0,0 +1,71 @@ +[[reference-get_source]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.getSource + +Get a document's source. Returns the source of a document. + +{ref}/docs-get.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(GetSourceRequest, options?): Promise +---- + +[discrete] +===== `GetSourceRequest` + +[source,ts] +---- +interface GetSourceRequest extends <> { + id: <> + index: <> + preference?: string + realtime?: boolean + refresh?: boolean + routing?: <> + _source?: SearchSourceConfigParam + _source_excludes?: <> + _source_includes?: <> + stored_fields?: <> + version?: <> + version_type?: <> +} +---- + +[discrete] +===== `GetSourceResponse` + +[source,ts] +---- +type GetSourceResponse = TDocument +---- + diff --git a/docs/reference-graph-explore.asciidoc b/docs/reference-graph-explore.asciidoc new file mode 100644 index 000000000..835e03fd6 --- /dev/null +++ b/docs/reference-graph-explore.asciidoc @@ -0,0 +1,72 @@ +[[reference-graph-explore]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.graph.explore + +Extracts and summarizes information about the documents and terms in an Elasticsearch data stream or index. + +{ref}/graph-explore-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(GraphExploreRequest, options?): Promise +---- + +[discrete] +===== `GraphExploreRequest` + +[source,ts] +---- +interface GraphExploreRequest extends <> { + index: <> + routing?: <> + timeout?: <> + connections?: GraphHop + controls?: GraphExploreControls + query?: QueryDslQueryContainer + vertices?: GraphVertexDefinition[] +} +---- + +[discrete] +===== `GraphExploreResponse` + +[source,ts] +---- +interface GraphExploreResponse { + connections: GraphConnection[] + failures: <>[] + timed_out: boolean + took: <> + vertices: GraphVertex[] +} +---- + diff --git a/docs/reference-health_report.asciidoc b/docs/reference-health_report.asciidoc new file mode 100644 index 000000000..a19de2289 --- /dev/null +++ b/docs/reference-health_report.asciidoc @@ -0,0 +1,67 @@ +[[reference-health_report]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.healthReport + +Returns the health of the cluster. + +{ref}/health-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(HealthReportRequest, options?): Promise +---- + +[discrete] +===== `HealthReportRequest` + +[source,ts] +---- +interface HealthReportRequest extends <> { + feature?: string | string[] + timeout?: <> + verbose?: boolean + size?: <> +} +---- + +[discrete] +===== `HealthReportResponse` + +[source,ts] +---- +interface HealthReportResponse { + cluster_name: string + indicators: HealthReportIndicators + status?: HealthReportIndicatorHealthStatus +} +---- + diff --git a/docs/reference-ilm-delete_lifecycle.asciidoc b/docs/reference-ilm-delete_lifecycle.asciidoc new file mode 100644 index 000000000..925734546 --- /dev/null +++ b/docs/reference-ilm-delete_lifecycle.asciidoc @@ -0,0 +1,62 @@ +[[reference-ilm-delete_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.deleteLifecycle + +Deletes the specified lifecycle policy definition. You cannot delete policies that are currently in use. If the policy is being used to manage any indices, the request fails and returns an error. + +{ref}/ilm-delete-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmDeleteLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IlmDeleteLifecycleRequest` + +[source,ts] +---- +interface IlmDeleteLifecycleRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IlmDeleteLifecycleResponse` + +[source,ts] +---- +type IlmDeleteLifecycleResponse = <> +---- + diff --git a/docs/reference-ilm-explain_lifecycle.asciidoc b/docs/reference-ilm-explain_lifecycle.asciidoc new file mode 100644 index 000000000..239d89476 --- /dev/null +++ b/docs/reference-ilm-explain_lifecycle.asciidoc @@ -0,0 +1,66 @@ +[[reference-ilm-explain_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.explainLifecycle + +Retrieves information about the index’s current lifecycle state, such as the currently executing phase, action, and step. Shows when the index entered each one, the definition of the running phase, and information about any failures. + +{ref}/ilm-explain-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmExplainLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IlmExplainLifecycleRequest` + +[source,ts] +---- +interface IlmExplainLifecycleRequest extends <> { + index: <> + only_errors?: boolean + only_managed?: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IlmExplainLifecycleResponse` + +[source,ts] +---- +interface IlmExplainLifecycleResponse { + indices: Record<<>, IlmExplainLifecycleLifecycleExplain> +} +---- + diff --git a/docs/reference-ilm-get_lifecycle.asciidoc b/docs/reference-ilm-get_lifecycle.asciidoc new file mode 100644 index 000000000..96bcc871d --- /dev/null +++ b/docs/reference-ilm-get_lifecycle.asciidoc @@ -0,0 +1,62 @@ +[[reference-ilm-get_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.getLifecycle + +Retrieves a lifecycle policy. + +{ref}/ilm-get-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmGetLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IlmGetLifecycleRequest` + +[source,ts] +---- +interface IlmGetLifecycleRequest extends <> { + name?: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IlmGetLifecycleResponse` + +[source,ts] +---- +type IlmGetLifecycleResponse = Record +---- + diff --git a/docs/reference-ilm-get_status.asciidoc b/docs/reference-ilm-get_status.asciidoc new file mode 100644 index 000000000..f50cff97e --- /dev/null +++ b/docs/reference-ilm-get_status.asciidoc @@ -0,0 +1,61 @@ +[[reference-ilm-get_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.getStatus + +Retrieves the current index lifecycle management (ILM) status. + +{ref}/ilm-get-status.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmGetStatusRequest, options?): Promise +---- + +[discrete] +===== `IlmGetStatusRequest` + +[source,ts] +---- +interface IlmGetStatusRequest extends <> { +} +---- + +[discrete] +===== `IlmGetStatusResponse` + +[source,ts] +---- +interface IlmGetStatusResponse { + operation_mode: <> +} +---- + diff --git a/docs/reference-ilm-migrate_to_data_tiers.asciidoc b/docs/reference-ilm-migrate_to_data_tiers.asciidoc new file mode 100644 index 000000000..d52f80cd1 --- /dev/null +++ b/docs/reference-ilm-migrate_to_data_tiers.asciidoc @@ -0,0 +1,70 @@ +[[reference-ilm-migrate_to_data_tiers]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.migrateToDataTiers + +Switches the indices, ILM policies, and legacy, composable and component templates from using custom node attributes and attribute-based allocation filters to using data tiers, and optionally deletes one legacy index template.+ Using node roles enables ILM to automatically move the indices between data tiers. + +{ref}/ilm-migrate-to-data-tiers.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmMigrateToDataTiersRequest, options?): Promise +---- + +[discrete] +===== `IlmMigrateToDataTiersRequest` + +[source,ts] +---- +interface IlmMigrateToDataTiersRequest extends <> { + dry_run?: boolean + legacy_template_to_delete?: string + node_attribute?: string +} +---- + +[discrete] +===== `IlmMigrateToDataTiersResponse` + +[source,ts] +---- +interface IlmMigrateToDataTiersResponse { + dry_run: boolean + removed_legacy_template: string + migrated_ilm_policies: string[] + migrated_indices: <> + migrated_legacy_templates: string[] + migrated_composable_templates: string[] + migrated_component_templates: string[] +} +---- + diff --git a/docs/reference-ilm-move_to_step.asciidoc b/docs/reference-ilm-move_to_step.asciidoc new file mode 100644 index 000000000..6115d6857 --- /dev/null +++ b/docs/reference-ilm-move_to_step.asciidoc @@ -0,0 +1,62 @@ +[[reference-ilm-move_to_step]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.moveToStep + +Manually moves an index into the specified step and executes that step. + +{ref}/ilm-move-to-step.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmMoveToStepRequest, options?): Promise +---- + +[discrete] +===== `IlmMoveToStepRequest` + +[source,ts] +---- +interface IlmMoveToStepRequest extends <> { + index: <> + current_step: IlmMoveToStepStepKey + next_step: IlmMoveToStepStepKey +} +---- + +[discrete] +===== `IlmMoveToStepResponse` + +[source,ts] +---- +type IlmMoveToStepResponse = <> +---- + diff --git a/docs/reference-ilm-put_lifecycle.asciidoc b/docs/reference-ilm-put_lifecycle.asciidoc new file mode 100644 index 000000000..9b24ba0ca --- /dev/null +++ b/docs/reference-ilm-put_lifecycle.asciidoc @@ -0,0 +1,63 @@ +[[reference-ilm-put_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.putLifecycle + +Creates a lifecycle policy. If the specified policy exists, the policy is replaced and the policy version is incremented. + +{ref}/ilm-put-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmPutLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IlmPutLifecycleRequest` + +[source,ts] +---- +interface IlmPutLifecycleRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> + policy?: IlmPolicy +} +---- + +[discrete] +===== `IlmPutLifecycleResponse` + +[source,ts] +---- +type IlmPutLifecycleResponse = <> +---- + diff --git a/docs/reference-ilm-remove_policy.asciidoc b/docs/reference-ilm-remove_policy.asciidoc new file mode 100644 index 000000000..8bddad3d3 --- /dev/null +++ b/docs/reference-ilm-remove_policy.asciidoc @@ -0,0 +1,63 @@ +[[reference-ilm-remove_policy]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.removePolicy + +Removes the assigned lifecycle policy and stops managing the specified index + +{ref}/ilm-remove-policy.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmRemovePolicyRequest, options?): Promise +---- + +[discrete] +===== `IlmRemovePolicyRequest` + +[source,ts] +---- +interface IlmRemovePolicyRequest extends <> { + index: <> +} +---- + +[discrete] +===== `IlmRemovePolicyResponse` + +[source,ts] +---- +interface IlmRemovePolicyResponse { + failed_indexes: <>[] + has_failures: boolean +} +---- + diff --git a/docs/reference-ilm-retry.asciidoc b/docs/reference-ilm-retry.asciidoc new file mode 100644 index 000000000..6370b4858 --- /dev/null +++ b/docs/reference-ilm-retry.asciidoc @@ -0,0 +1,60 @@ +[[reference-ilm-retry]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.retry + +Retries executing the policy for an index that is in the ERROR step. + +{ref}/ilm-retry-policy.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmRetryRequest, options?): Promise +---- + +[discrete] +===== `IlmRetryRequest` + +[source,ts] +---- +interface IlmRetryRequest extends <> { + index: <> +} +---- + +[discrete] +===== `IlmRetryResponse` + +[source,ts] +---- +type IlmRetryResponse = <> +---- + diff --git a/docs/reference-ilm-start.asciidoc b/docs/reference-ilm-start.asciidoc new file mode 100644 index 000000000..b0f3cb7a4 --- /dev/null +++ b/docs/reference-ilm-start.asciidoc @@ -0,0 +1,61 @@ +[[reference-ilm-start]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.start + +Start the index lifecycle management (ILM) plugin. + +{ref}/ilm-start.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmStartRequest, options?): Promise +---- + +[discrete] +===== `IlmStartRequest` + +[source,ts] +---- +interface IlmStartRequest extends <> { + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IlmStartResponse` + +[source,ts] +---- +type IlmStartResponse = <> +---- + diff --git a/docs/reference-ilm-stop.asciidoc b/docs/reference-ilm-stop.asciidoc new file mode 100644 index 000000000..41233ac6a --- /dev/null +++ b/docs/reference-ilm-stop.asciidoc @@ -0,0 +1,61 @@ +[[reference-ilm-stop]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ilm.stop + +Halts all lifecycle management operations and stops the index lifecycle management (ILM) plugin + +{ref}/ilm-stop.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IlmStopRequest, options?): Promise +---- + +[discrete] +===== `IlmStopRequest` + +[source,ts] +---- +interface IlmStopRequest extends <> { + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IlmStopResponse` + +[source,ts] +---- +type IlmStopResponse = <> +---- + diff --git a/docs/reference-index.asciidoc b/docs/reference-index.asciidoc new file mode 100644 index 000000000..ca4d09d09 --- /dev/null +++ b/docs/reference-index.asciidoc @@ -0,0 +1,73 @@ +[[reference-index]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.index + +Index a document. Adds a JSON document to the specified data stream or index and makes it searchable. If the target is an index and the document already exists, the request updates the document and increments its version. + +{ref}/docs-index_.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndexRequest, options?): Promise +---- + +[discrete] +===== `IndexRequest` + +[source,ts] +---- +interface IndexRequest extends <> { + id?: <> + index: <> + if_primary_term?: <> + if_seq_no?: <> + op_type?: <> + pipeline?: string + refresh?: <> + routing?: <> + timeout?: <> + version?: <> + version_type?: <> + wait_for_active_shards?: <> + require_alias?: boolean + document?: TDocument +} +---- + +[discrete] +===== `IndexResponse` + +[source,ts] +---- +type IndexResponse = <> +---- + diff --git a/docs/reference-indices-add_block.asciidoc b/docs/reference-indices-add_block.asciidoc new file mode 100644 index 000000000..9d5747755 --- /dev/null +++ b/docs/reference-indices-add_block.asciidoc @@ -0,0 +1,70 @@ +[[reference-indices-add_block]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.addBlock + +Add an index block. Limits the operations allowed on an index by blocking specific operation types. + +{ref}/index-modules-blocks.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesAddBlockRequest, options?): Promise +---- + +[discrete] +===== `IndicesAddBlockRequest` + +[source,ts] +---- +interface IndicesAddBlockRequest extends <> { + index: <> + block: IndicesAddBlockIndicesBlockOptions + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesAddBlockResponse` + +[source,ts] +---- +interface IndicesAddBlockResponse { + acknowledged: boolean + shards_acknowledged: boolean + indices: IndicesAddBlockIndicesBlockStatus[] +} +---- + diff --git a/docs/reference-indices-analyze.asciidoc b/docs/reference-indices-analyze.asciidoc new file mode 100644 index 000000000..f64be70ec --- /dev/null +++ b/docs/reference-indices-analyze.asciidoc @@ -0,0 +1,72 @@ +[[reference-indices-analyze]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.analyze + +Get tokens from text analysis. The analyze API performs [analysis](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis.html) on a text string and returns the resulting tokens. + +{ref}/indices-analyze.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesAnalyzeRequest, options?): Promise +---- + +[discrete] +===== `IndicesAnalyzeRequest` + +[source,ts] +---- +interface IndicesAnalyzeRequest extends <> { + index?: <> + analyzer?: string + attributes?: string[] + char_filter?: AnalysisCharFilter[] + explain?: boolean + field?: <> + filter?: AnalysisTokenFilter[] + normalizer?: string + text?: IndicesAnalyzeTextToAnalyze + tokenizer?: AnalysisTokenizer +} +---- + +[discrete] +===== `IndicesAnalyzeResponse` + +[source,ts] +---- +interface IndicesAnalyzeResponse { + detail?: IndicesAnalyzeAnalyzeDetail + tokens?: IndicesAnalyzeAnalyzeToken[] +} +---- + diff --git a/docs/reference-indices-clear_cache.asciidoc b/docs/reference-indices-clear_cache.asciidoc new file mode 100644 index 000000000..7ca4affcf --- /dev/null +++ b/docs/reference-indices-clear_cache.asciidoc @@ -0,0 +1,67 @@ +[[reference-indices-clear_cache]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.clearCache + +Clears the caches of one or more indices. For data streams, the API clears the caches of the stream’s backing indices. + +{ref}/indices-clearcache.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesClearCacheRequest, options?): Promise +---- + +[discrete] +===== `IndicesClearCacheRequest` + +[source,ts] +---- +interface IndicesClearCacheRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + fielddata?: boolean + fields?: <> + ignore_unavailable?: boolean + query?: boolean + request?: boolean +} +---- + +[discrete] +===== `IndicesClearCacheResponse` + +[source,ts] +---- +type IndicesClearCacheResponse = <> +---- + diff --git a/docs/reference-indices-clone.asciidoc b/docs/reference-indices-clone.asciidoc new file mode 100644 index 000000000..ab43ec562 --- /dev/null +++ b/docs/reference-indices-clone.asciidoc @@ -0,0 +1,70 @@ +[[reference-indices-clone]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.clone + +Clones an existing index. + +{ref}/indices-clone-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesCloneRequest, options?): Promise +---- + +[discrete] +===== `IndicesCloneRequest` + +[source,ts] +---- +interface IndicesCloneRequest extends <> { + index: <> + target: <> + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> + aliases?: Record<<>, IndicesAlias> + settings?: Record +} +---- + +[discrete] +===== `IndicesCloneResponse` + +[source,ts] +---- +interface IndicesCloneResponse { + acknowledged: boolean + index: <> + shards_acknowledged: boolean +} +---- + diff --git a/docs/reference-indices-close.asciidoc b/docs/reference-indices-close.asciidoc new file mode 100644 index 000000000..469eec0d1 --- /dev/null +++ b/docs/reference-indices-close.asciidoc @@ -0,0 +1,70 @@ +[[reference-indices-close]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.close + +Closes an index. + +{ref}/indices-close.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesCloseRequest, options?): Promise +---- + +[discrete] +===== `IndicesCloseRequest` + +[source,ts] +---- +interface IndicesCloseRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> +} +---- + +[discrete] +===== `IndicesCloseResponse` + +[source,ts] +---- +interface IndicesCloseResponse { + acknowledged: boolean + indices: Record<<>, IndicesCloseCloseIndexResult> + shards_acknowledged: boolean +} +---- + diff --git a/docs/reference-indices-create.asciidoc b/docs/reference-indices-create.asciidoc new file mode 100644 index 000000000..608828168 --- /dev/null +++ b/docs/reference-indices-create.asciidoc @@ -0,0 +1,70 @@ +[[reference-indices-create]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.create + +Create an index. Creates a new index. + +{ref}/indices-create-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesCreateRequest, options?): Promise +---- + +[discrete] +===== `IndicesCreateRequest` + +[source,ts] +---- +interface IndicesCreateRequest extends <> { + index: <> + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> + aliases?: Record<<>, IndicesAlias> + mappings?: MappingTypeMapping + settings?: IndicesIndexSettings +} +---- + +[discrete] +===== `IndicesCreateResponse` + +[source,ts] +---- +interface IndicesCreateResponse { + index: <> + shards_acknowledged: boolean + acknowledged: boolean +} +---- + diff --git a/docs/reference-indices-create_data_stream.asciidoc b/docs/reference-indices-create_data_stream.asciidoc new file mode 100644 index 000000000..0465ed99b --- /dev/null +++ b/docs/reference-indices-create_data_stream.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-create_data_stream]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.createDataStream + +Create a data stream. Creates a data stream. You must have a matching index template with data stream enabled. + +{ref}/data-streams.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesCreateDataStreamRequest, options?): Promise +---- + +[discrete] +===== `IndicesCreateDataStreamRequest` + +[source,ts] +---- +interface IndicesCreateDataStreamRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesCreateDataStreamResponse` + +[source,ts] +---- +type IndicesCreateDataStreamResponse = <> +---- + diff --git a/docs/reference-indices-data_streams_stats.asciidoc b/docs/reference-indices-data_streams_stats.asciidoc new file mode 100644 index 000000000..25f0b5028 --- /dev/null +++ b/docs/reference-indices-data_streams_stats.asciidoc @@ -0,0 +1,68 @@ +[[reference-indices-data_streams_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.dataStreamsStats + +Get data stream stats. Retrieves statistics for one or more data streams. + +{ref}/data-streams.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDataStreamsStatsRequest, options?): Promise +---- + +[discrete] +===== `IndicesDataStreamsStatsRequest` + +[source,ts] +---- +interface IndicesDataStreamsStatsRequest extends <> { + name?: <> + expand_wildcards?: <> +} +---- + +[discrete] +===== `IndicesDataStreamsStatsResponse` + +[source,ts] +---- +interface IndicesDataStreamsStatsResponse { + _shards: <> + backing_indices: <> + data_stream_count: <> + data_streams: IndicesDataStreamsStatsDataStreamsStatsItem[] + total_store_sizes?: <> + total_store_size_bytes: <> +} +---- + diff --git a/docs/reference-indices-delete.asciidoc b/docs/reference-indices-delete.asciidoc new file mode 100644 index 000000000..f135f3a89 --- /dev/null +++ b/docs/reference-indices-delete.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.delete + +Delete indices. Deletes one or more indices. + +{ref}/indices-delete-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDeleteRequest, options?): Promise +---- + +[discrete] +===== `IndicesDeleteRequest` + +[source,ts] +---- +interface IndicesDeleteRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesDeleteResponse` + +[source,ts] +---- +type IndicesDeleteResponse = <> +---- + diff --git a/docs/reference-indices-delete_alias.asciidoc b/docs/reference-indices-delete_alias.asciidoc new file mode 100644 index 000000000..b49895eb1 --- /dev/null +++ b/docs/reference-indices-delete_alias.asciidoc @@ -0,0 +1,63 @@ +[[reference-indices-delete_alias]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.deleteAlias + +Delete an alias. Removes a data stream or index from an alias. + +{ref}/indices-aliases.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDeleteAliasRequest, options?): Promise +---- + +[discrete] +===== `IndicesDeleteAliasRequest` + +[source,ts] +---- +interface IndicesDeleteAliasRequest extends <> { + index: <> + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesDeleteAliasResponse` + +[source,ts] +---- +type IndicesDeleteAliasResponse = <> +---- + diff --git a/docs/reference-indices-delete_data_lifecycle.asciidoc b/docs/reference-indices-delete_data_lifecycle.asciidoc new file mode 100644 index 000000000..07e8c3a33 --- /dev/null +++ b/docs/reference-indices-delete_data_lifecycle.asciidoc @@ -0,0 +1,63 @@ +[[reference-indices-delete_data_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.deleteDataLifecycle + +Delete data stream lifecycles. Removes the data stream lifecycle from a data stream, rendering it not managed by the data stream lifecycle. + +{ref}/data-streams-delete-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDeleteDataLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IndicesDeleteDataLifecycleRequest` + +[source,ts] +---- +interface IndicesDeleteDataLifecycleRequest extends <> { + name: <> + expand_wildcards?: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesDeleteDataLifecycleResponse` + +[source,ts] +---- +type IndicesDeleteDataLifecycleResponse = <> +---- + diff --git a/docs/reference-indices-delete_data_stream.asciidoc b/docs/reference-indices-delete_data_stream.asciidoc new file mode 100644 index 000000000..aedd05612 --- /dev/null +++ b/docs/reference-indices-delete_data_stream.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-delete_data_stream]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.deleteDataStream + +Delete data streams. Deletes one or more data streams and their backing indices. + +{ref}/data-streams.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDeleteDataStreamRequest, options?): Promise +---- + +[discrete] +===== `IndicesDeleteDataStreamRequest` + +[source,ts] +---- +interface IndicesDeleteDataStreamRequest extends <> { + name: <> + master_timeout?: <> + expand_wildcards?: <> +} +---- + +[discrete] +===== `IndicesDeleteDataStreamResponse` + +[source,ts] +---- +type IndicesDeleteDataStreamResponse = <> +---- + diff --git a/docs/reference-indices-delete_index_template.asciidoc b/docs/reference-indices-delete_index_template.asciidoc new file mode 100644 index 000000000..72d258219 --- /dev/null +++ b/docs/reference-indices-delete_index_template.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-delete_index_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.deleteIndexTemplate + +Delete an index template. The provided may contain multiple template names separated by a comma. If multiple template names are specified then there is no wildcard support and the provided names should match completely with existing templates. + +{ref}/indices-delete-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDeleteIndexTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesDeleteIndexTemplateRequest` + +[source,ts] +---- +interface IndicesDeleteIndexTemplateRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesDeleteIndexTemplateResponse` + +[source,ts] +---- +type IndicesDeleteIndexTemplateResponse = <> +---- + diff --git a/docs/reference-indices-delete_template.asciidoc b/docs/reference-indices-delete_template.asciidoc new file mode 100644 index 000000000..049f04d30 --- /dev/null +++ b/docs/reference-indices-delete_template.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-delete_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.deleteTemplate + +Deletes a legacy index template. + +{ref}/indices-delete-template-v1.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDeleteTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesDeleteTemplateRequest` + +[source,ts] +---- +interface IndicesDeleteTemplateRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesDeleteTemplateResponse` + +[source,ts] +---- +type IndicesDeleteTemplateResponse = <> +---- + diff --git a/docs/reference-indices-disk_usage.asciidoc b/docs/reference-indices-disk_usage.asciidoc new file mode 100644 index 000000000..5e10b0728 --- /dev/null +++ b/docs/reference-indices-disk_usage.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-disk_usage]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.diskUsage + +Analyzes the disk usage of each field of an index or data stream. + +{ref}/indices-disk-usage.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDiskUsageRequest, options?): Promise +---- + +[discrete] +===== `IndicesDiskUsageRequest` + +[source,ts] +---- +interface IndicesDiskUsageRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + flush?: boolean + ignore_unavailable?: boolean + run_expensive_tasks?: boolean +} +---- + +[discrete] +===== `IndicesDiskUsageResponse` + +[source,ts] +---- +type IndicesDiskUsageResponse = any +---- + diff --git a/docs/reference-indices-downsample.asciidoc b/docs/reference-indices-downsample.asciidoc new file mode 100644 index 000000000..61589e167 --- /dev/null +++ b/docs/reference-indices-downsample.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-downsample]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.downsample + +Aggregates a time series (TSDS) index and stores pre-computed statistical summaries (`min`, `max`, `sum`, `value_count` and `avg`) for each metric field grouped by a configured time interval. + +{ref}/indices-downsample-data-stream.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesDownsampleRequest, options?): Promise +---- + +[discrete] +===== `IndicesDownsampleRequest` + +[source,ts] +---- +interface IndicesDownsampleRequest extends <> { + index: <> + target_index: <> + config?: IndicesDownsampleConfig +} +---- + +[discrete] +===== `IndicesDownsampleResponse` + +[source,ts] +---- +type IndicesDownsampleResponse = any +---- + diff --git a/docs/reference-indices-exists.asciidoc b/docs/reference-indices-exists.asciidoc new file mode 100644 index 000000000..ffdf4691f --- /dev/null +++ b/docs/reference-indices-exists.asciidoc @@ -0,0 +1,66 @@ +[[reference-indices-exists]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.exists + +Check indices. Checks if one or more indices, index aliases, or data streams exist. + +{ref}/indices-exists.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesExistsRequest, options?): Promise +---- + +[discrete] +===== `IndicesExistsRequest` + +[source,ts] +---- +interface IndicesExistsRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + flat_settings?: boolean + ignore_unavailable?: boolean + include_defaults?: boolean + local?: boolean +} +---- + +[discrete] +===== `IndicesExistsResponse` + +[source,ts] +---- +type IndicesExistsResponse = boolean +---- + diff --git a/docs/reference-indices-exists_alias.asciidoc b/docs/reference-indices-exists_alias.asciidoc new file mode 100644 index 000000000..5e262cc86 --- /dev/null +++ b/docs/reference-indices-exists_alias.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-exists_alias]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.existsAlias + +Check aliases. Checks if one or more data stream or index aliases exist. + +{ref}/indices-aliases.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesExistsAliasRequest, options?): Promise +---- + +[discrete] +===== `IndicesExistsAliasRequest` + +[source,ts] +---- +interface IndicesExistsAliasRequest extends <> { + name: <> + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + local?: boolean +} +---- + +[discrete] +===== `IndicesExistsAliasResponse` + +[source,ts] +---- +type IndicesExistsAliasResponse = boolean +---- + diff --git a/docs/reference-indices-exists_index_template.asciidoc b/docs/reference-indices-exists_index_template.asciidoc new file mode 100644 index 000000000..ea8105dac --- /dev/null +++ b/docs/reference-indices-exists_index_template.asciidoc @@ -0,0 +1,61 @@ +[[reference-indices-exists_index_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.existsIndexTemplate + +Returns information about whether a particular index template exists. + +{ref}/index-templates.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesExistsIndexTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesExistsIndexTemplateRequest` + +[source,ts] +---- +interface IndicesExistsIndexTemplateRequest extends <> { + name: <> + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesExistsIndexTemplateResponse` + +[source,ts] +---- +type IndicesExistsIndexTemplateResponse = boolean +---- + diff --git a/docs/reference-indices-exists_template.asciidoc b/docs/reference-indices-exists_template.asciidoc new file mode 100644 index 000000000..e9179a65c --- /dev/null +++ b/docs/reference-indices-exists_template.asciidoc @@ -0,0 +1,63 @@ +[[reference-indices-exists_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.existsTemplate + +Check existence of index templates. Returns information about whether a particular index template exists. + +{ref}/indices-template-exists-v1.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesExistsTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesExistsTemplateRequest` + +[source,ts] +---- +interface IndicesExistsTemplateRequest extends <> { + name: <> + flat_settings?: boolean + local?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesExistsTemplateResponse` + +[source,ts] +---- +type IndicesExistsTemplateResponse = boolean +---- + diff --git a/docs/reference-indices-explain_data_lifecycle.asciidoc b/docs/reference-indices-explain_data_lifecycle.asciidoc new file mode 100644 index 000000000..bda3ecf8f --- /dev/null +++ b/docs/reference-indices-explain_data_lifecycle.asciidoc @@ -0,0 +1,64 @@ +[[reference-indices-explain_data_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.explainDataLifecycle + +Get the status for a data stream lifecycle. Retrieves information about an index or data stream’s current data stream lifecycle status, such as time since index creation, time since rollover, the lifecycle configuration managing the index, or any errors encountered during lifecycle execution. + +{ref}/data-streams-explain-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesExplainDataLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IndicesExplainDataLifecycleRequest` + +[source,ts] +---- +interface IndicesExplainDataLifecycleRequest extends <> { + index: <> + include_defaults?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesExplainDataLifecycleResponse` + +[source,ts] +---- +interface IndicesExplainDataLifecycleResponse { + indices: Record<<>, IndicesExplainDataLifecycleDataStreamLifecycleExplain> +} +---- + diff --git a/docs/reference-indices-field_usage_stats.asciidoc b/docs/reference-indices-field_usage_stats.asciidoc new file mode 100644 index 000000000..3f03c310d --- /dev/null +++ b/docs/reference-indices-field_usage_stats.asciidoc @@ -0,0 +1,67 @@ +[[reference-indices-field_usage_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.fieldUsageStats + +Returns field usage information for each shard and field of an index. + +{ref}/field-usage-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesFieldUsageStatsRequest, options?): Promise +---- + +[discrete] +===== `IndicesFieldUsageStatsRequest` + +[source,ts] +---- +interface IndicesFieldUsageStatsRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + fields?: <> + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> +} +---- + +[discrete] +===== `IndicesFieldUsageStatsResponse` + +[source,ts] +---- +type IndicesFieldUsageStatsResponse = IndicesFieldUsageStatsFieldsUsageBody +---- + diff --git a/docs/reference-indices-flush.asciidoc b/docs/reference-indices-flush.asciidoc new file mode 100644 index 000000000..5176d9909 --- /dev/null +++ b/docs/reference-indices-flush.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-flush]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.flush + +Flushes one or more data streams or indices. + +{ref}/indices-flush.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesFlushRequest, options?): Promise +---- + +[discrete] +===== `IndicesFlushRequest` + +[source,ts] +---- +interface IndicesFlushRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + force?: boolean + ignore_unavailable?: boolean + wait_if_ongoing?: boolean +} +---- + +[discrete] +===== `IndicesFlushResponse` + +[source,ts] +---- +type IndicesFlushResponse = <> +---- + diff --git a/docs/reference-indices-forcemerge.asciidoc b/docs/reference-indices-forcemerge.asciidoc new file mode 100644 index 000000000..2c72626f0 --- /dev/null +++ b/docs/reference-indices-forcemerge.asciidoc @@ -0,0 +1,67 @@ +[[reference-indices-forcemerge]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.forcemerge + +Performs the force merge operation on one or more indices. + +{ref}/indices-forcemerge.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesForcemergeRequest, options?): Promise +---- + +[discrete] +===== `IndicesForcemergeRequest` + +[source,ts] +---- +interface IndicesForcemergeRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + flush?: boolean + ignore_unavailable?: boolean + max_num_segments?: <> + only_expunge_deletes?: boolean + wait_for_completion?: boolean +} +---- + +[discrete] +===== `IndicesForcemergeResponse` + +[source,ts] +---- +type IndicesForcemergeResponse = IndicesForcemergeForceMergeResponseBody +---- + diff --git a/docs/reference-indices-get.asciidoc b/docs/reference-indices-get.asciidoc new file mode 100644 index 000000000..48301abd8 --- /dev/null +++ b/docs/reference-indices-get.asciidoc @@ -0,0 +1,68 @@ +[[reference-indices-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.get + +Get index information. Returns information about one or more indices. For data streams, the API returns information about the stream’s backing indices. + +{ref}/indices-get-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetRequest` + +[source,ts] +---- +interface IndicesGetRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + flat_settings?: boolean + ignore_unavailable?: boolean + include_defaults?: boolean + local?: boolean + master_timeout?: <> + features?: IndicesGetFeatures +} +---- + +[discrete] +===== `IndicesGetResponse` + +[source,ts] +---- +type IndicesGetResponse = Record<<>, IndicesIndexState> +---- + diff --git a/docs/reference-indices-get_alias.asciidoc b/docs/reference-indices-get_alias.asciidoc new file mode 100644 index 000000000..6c68ec26c --- /dev/null +++ b/docs/reference-indices-get_alias.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-get_alias]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getAlias + +Get aliases. Retrieves information for one or more data stream or index aliases. + +{ref}/indices-aliases.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetAliasRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetAliasRequest` + +[source,ts] +---- +interface IndicesGetAliasRequest extends <> { + name?: <> + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + local?: boolean +} +---- + +[discrete] +===== `IndicesGetAliasResponse` + +[source,ts] +---- +type IndicesGetAliasResponse = Record<<>, IndicesGetAliasIndexAliases> +---- + diff --git a/docs/reference-indices-get_data_lifecycle.asciidoc b/docs/reference-indices-get_data_lifecycle.asciidoc new file mode 100644 index 000000000..72044e8b3 --- /dev/null +++ b/docs/reference-indices-get_data_lifecycle.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-get_data_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getDataLifecycle + +Get data stream lifecycles. Retrieves the data stream lifecycle configuration of one or more data streams. + +{ref}/data-streams-get-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetDataLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetDataLifecycleRequest` + +[source,ts] +---- +interface IndicesGetDataLifecycleRequest extends <> { + name: <> + expand_wildcards?: <> + include_defaults?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesGetDataLifecycleResponse` + +[source,ts] +---- +interface IndicesGetDataLifecycleResponse { + data_streams: IndicesGetDataLifecycleDataStreamWithLifecycle[] +} +---- + diff --git a/docs/reference-indices-get_data_stream.asciidoc b/docs/reference-indices-get_data_stream.asciidoc new file mode 100644 index 000000000..12f4796c1 --- /dev/null +++ b/docs/reference-indices-get_data_stream.asciidoc @@ -0,0 +1,66 @@ +[[reference-indices-get_data_stream]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getDataStream + +Get data streams. Retrieves information about one or more data streams. + +{ref}/data-streams.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetDataStreamRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetDataStreamRequest` + +[source,ts] +---- +interface IndicesGetDataStreamRequest extends <> { + name?: <> + expand_wildcards?: <> + include_defaults?: boolean + master_timeout?: <> + verbose?: boolean +} +---- + +[discrete] +===== `IndicesGetDataStreamResponse` + +[source,ts] +---- +interface IndicesGetDataStreamResponse { + data_streams: IndicesDataStream[] +} +---- + diff --git a/docs/reference-indices-get_field_mapping.asciidoc b/docs/reference-indices-get_field_mapping.asciidoc new file mode 100644 index 000000000..e3075f196 --- /dev/null +++ b/docs/reference-indices-get_field_mapping.asciidoc @@ -0,0 +1,66 @@ +[[reference-indices-get_field_mapping]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getFieldMapping + +Get mapping definitions. Retrieves mapping definitions for one or more fields. For data streams, the API retrieves field mappings for the stream’s backing indices. + +{ref}/indices-get-field-mapping.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetFieldMappingRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetFieldMappingRequest` + +[source,ts] +---- +interface IndicesGetFieldMappingRequest extends <> { + fields: <> + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + include_defaults?: boolean + local?: boolean +} +---- + +[discrete] +===== `IndicesGetFieldMappingResponse` + +[source,ts] +---- +type IndicesGetFieldMappingResponse = Record<<>, IndicesGetFieldMappingTypeFieldMappings> +---- + diff --git a/docs/reference-indices-get_index_template.asciidoc b/docs/reference-indices-get_index_template.asciidoc new file mode 100644 index 000000000..ade7d6aaa --- /dev/null +++ b/docs/reference-indices-get_index_template.asciidoc @@ -0,0 +1,66 @@ +[[reference-indices-get_index_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getIndexTemplate + +Get index templates. Returns information about one or more index templates. + +{ref}/indices-get-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetIndexTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetIndexTemplateRequest` + +[source,ts] +---- +interface IndicesGetIndexTemplateRequest extends <> { + name?: <> + local?: boolean + flat_settings?: boolean + master_timeout?: <> + include_defaults?: boolean +} +---- + +[discrete] +===== `IndicesGetIndexTemplateResponse` + +[source,ts] +---- +interface IndicesGetIndexTemplateResponse { + index_templates: IndicesGetIndexTemplateIndexTemplateItem[] +} +---- + diff --git a/docs/reference-indices-get_mapping.asciidoc b/docs/reference-indices-get_mapping.asciidoc new file mode 100644 index 000000000..b7cf4441d --- /dev/null +++ b/docs/reference-indices-get_mapping.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-get_mapping]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getMapping + +Get mapping definitions. Retrieves mapping definitions for one or more indices. For data streams, the API retrieves mappings for the stream’s backing indices. + +{ref}/indices-get-mapping.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetMappingRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetMappingRequest` + +[source,ts] +---- +interface IndicesGetMappingRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + local?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesGetMappingResponse` + +[source,ts] +---- +type IndicesGetMappingResponse = Record<<>, IndicesGetMappingIndexMappingRecord> +---- + diff --git a/docs/reference-indices-get_settings.asciidoc b/docs/reference-indices-get_settings.asciidoc new file mode 100644 index 000000000..d39fb0708 --- /dev/null +++ b/docs/reference-indices-get_settings.asciidoc @@ -0,0 +1,68 @@ +[[reference-indices-get_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getSettings + +Get index settings. Returns setting information for one or more indices. For data streams, returns setting information for the stream’s backing indices. + +{ref}/indices-get-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetSettingsRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetSettingsRequest` + +[source,ts] +---- +interface IndicesGetSettingsRequest extends <> { + index?: <> + name?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + flat_settings?: boolean + ignore_unavailable?: boolean + include_defaults?: boolean + local?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesGetSettingsResponse` + +[source,ts] +---- +type IndicesGetSettingsResponse = Record<<>, IndicesIndexState> +---- + diff --git a/docs/reference-indices-get_template.asciidoc b/docs/reference-indices-get_template.asciidoc new file mode 100644 index 000000000..aed4e1f2d --- /dev/null +++ b/docs/reference-indices-get_template.asciidoc @@ -0,0 +1,63 @@ +[[reference-indices-get_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.getTemplate + +Get index templates. Retrieves information about one or more index templates. + +{ref}/indices-get-template-v1.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesGetTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesGetTemplateRequest` + +[source,ts] +---- +interface IndicesGetTemplateRequest extends <> { + name?: <> + flat_settings?: boolean + local?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesGetTemplateResponse` + +[source,ts] +---- +type IndicesGetTemplateResponse = Record +---- + diff --git a/docs/reference-indices-migrate_to_data_stream.asciidoc b/docs/reference-indices-migrate_to_data_stream.asciidoc new file mode 100644 index 000000000..a12cd72f2 --- /dev/null +++ b/docs/reference-indices-migrate_to_data_stream.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-migrate_to_data_stream]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.migrateToDataStream + +Convert an index alias to a data stream. Converts an index alias to a data stream. You must have a matching index template that is data stream enabled. The alias must meet the following criteria: The alias must have a write index; All indices for the alias must have a `@timestamp` field mapping of a `date` or `date_nanos` field type; The alias must not have any filters; The alias must not use custom routing. If successful, the request removes the alias and creates a data stream with the same name. The indices for the alias become hidden backing indices for the stream. The write index for the alias becomes the write index for the stream. + +{ref}/data-streams.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesMigrateToDataStreamRequest, options?): Promise +---- + +[discrete] +===== `IndicesMigrateToDataStreamRequest` + +[source,ts] +---- +interface IndicesMigrateToDataStreamRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IndicesMigrateToDataStreamResponse` + +[source,ts] +---- +type IndicesMigrateToDataStreamResponse = <> +---- + diff --git a/docs/reference-indices-modify_data_stream.asciidoc b/docs/reference-indices-modify_data_stream.asciidoc new file mode 100644 index 000000000..0f3f14e81 --- /dev/null +++ b/docs/reference-indices-modify_data_stream.asciidoc @@ -0,0 +1,60 @@ +[[reference-indices-modify_data_stream]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.modifyDataStream + +Update data streams. Performs one or more data stream modification actions in a single atomic operation. + +{ref}/data-streams.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesModifyDataStreamRequest, options?): Promise +---- + +[discrete] +===== `IndicesModifyDataStreamRequest` + +[source,ts] +---- +interface IndicesModifyDataStreamRequest extends <> { + actions: IndicesModifyDataStreamAction[] +} +---- + +[discrete] +===== `IndicesModifyDataStreamResponse` + +[source,ts] +---- +type IndicesModifyDataStreamResponse = <> +---- + diff --git a/docs/reference-indices-open.asciidoc b/docs/reference-indices-open.asciidoc new file mode 100644 index 000000000..a2cde94a7 --- /dev/null +++ b/docs/reference-indices-open.asciidoc @@ -0,0 +1,69 @@ +[[reference-indices-open]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.open + +Opens a closed index. For data streams, the API opens any closed backing indices. + +{ref}/indices-open-close.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesOpenRequest, options?): Promise +---- + +[discrete] +===== `IndicesOpenRequest` + +[source,ts] +---- +interface IndicesOpenRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> +} +---- + +[discrete] +===== `IndicesOpenResponse` + +[source,ts] +---- +interface IndicesOpenResponse { + acknowledged: boolean + shards_acknowledged: boolean +} +---- + diff --git a/docs/reference-indices-promote_data_stream.asciidoc b/docs/reference-indices-promote_data_stream.asciidoc new file mode 100644 index 000000000..1d1f918c9 --- /dev/null +++ b/docs/reference-indices-promote_data_stream.asciidoc @@ -0,0 +1,61 @@ +[[reference-indices-promote_data_stream]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.promoteDataStream + +Promotes a data stream from a replicated data stream managed by CCR to a regular data stream + +{ref}/data-streams.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesPromoteDataStreamRequest, options?): Promise +---- + +[discrete] +===== `IndicesPromoteDataStreamRequest` + +[source,ts] +---- +interface IndicesPromoteDataStreamRequest extends <> { + name: <> + master_timeout?: <> +} +---- + +[discrete] +===== `IndicesPromoteDataStreamResponse` + +[source,ts] +---- +type IndicesPromoteDataStreamResponse = any +---- + diff --git a/docs/reference-indices-put_alias.asciidoc b/docs/reference-indices-put_alias.asciidoc new file mode 100644 index 000000000..a273d8e66 --- /dev/null +++ b/docs/reference-indices-put_alias.asciidoc @@ -0,0 +1,68 @@ +[[reference-indices-put_alias]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.putAlias + +Create or update an alias. Adds a data stream or index to an alias. + +{ref}/indices-aliases.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesPutAliasRequest, options?): Promise +---- + +[discrete] +===== `IndicesPutAliasRequest` + +[source,ts] +---- +interface IndicesPutAliasRequest extends <> { + index: <> + name: <> + master_timeout?: <> + timeout?: <> + filter?: QueryDslQueryContainer + index_routing?: <> + is_write_index?: boolean + routing?: <> + search_routing?: <> +} +---- + +[discrete] +===== `IndicesPutAliasResponse` + +[source,ts] +---- +type IndicesPutAliasResponse = <> +---- + diff --git a/docs/reference-indices-put_data_lifecycle.asciidoc b/docs/reference-indices-put_data_lifecycle.asciidoc new file mode 100644 index 000000000..02129034c --- /dev/null +++ b/docs/reference-indices-put_data_lifecycle.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-put_data_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.putDataLifecycle + +Update data stream lifecycles. Update the data stream lifecycle of the specified data streams. + +{ref}/data-streams-put-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesPutDataLifecycleRequest, options?): Promise +---- + +[discrete] +===== `IndicesPutDataLifecycleRequest` + +[source,ts] +---- +interface IndicesPutDataLifecycleRequest extends <> { + name: <> + expand_wildcards?: <> + master_timeout?: <> + timeout?: <> + data_retention?: <> + downsampling?: IndicesDataStreamLifecycleDownsampling +} +---- + +[discrete] +===== `IndicesPutDataLifecycleResponse` + +[source,ts] +---- +type IndicesPutDataLifecycleResponse = <> +---- + diff --git a/docs/reference-indices-put_index_template.asciidoc b/docs/reference-indices-put_index_template.asciidoc new file mode 100644 index 000000000..994c31846 --- /dev/null +++ b/docs/reference-indices-put_index_template.asciidoc @@ -0,0 +1,73 @@ +[[reference-indices-put_index_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.putIndexTemplate + +Create or update an index template. Index templates define settings, mappings, and aliases that can be applied automatically to new indices. + +{ref}/indices-put-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesPutIndexTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesPutIndexTemplateRequest` + +[source,ts] +---- +interface IndicesPutIndexTemplateRequest extends <> { + name: <> + create?: boolean + master_timeout?: <> + cause?: string + index_patterns?: <> + composed_of?: <>[] + template?: IndicesPutIndexTemplateIndexTemplateMapping + data_stream?: IndicesDataStreamVisibility + priority?: <> + version?: <> + _meta?: <> + allow_auto_create?: boolean + ignore_missing_component_templates?: string[] + deprecated?: boolean +} +---- + +[discrete] +===== `IndicesPutIndexTemplateResponse` + +[source,ts] +---- +type IndicesPutIndexTemplateResponse = <> +---- + diff --git a/docs/reference-indices-put_mapping.asciidoc b/docs/reference-indices-put_mapping.asciidoc new file mode 100644 index 000000000..ada522272 --- /dev/null +++ b/docs/reference-indices-put_mapping.asciidoc @@ -0,0 +1,77 @@ +[[reference-indices-put_mapping]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.putMapping + +Update field mappings. Adds new fields to an existing data stream or index. You can also use this API to change the search settings of existing fields. For data streams, these changes are applied to all backing indices by default. + +{ref}/indices-put-mapping.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesPutMappingRequest, options?): Promise +---- + +[discrete] +===== `IndicesPutMappingRequest` + +[source,ts] +---- +interface IndicesPutMappingRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + master_timeout?: <> + timeout?: <> + write_index_only?: boolean + date_detection?: boolean + dynamic?: MappingDynamicMapping + dynamic_date_formats?: string[] + dynamic_templates?: Record | Record[] + _field_names?: MappingFieldNamesField + _meta?: <> + numeric_detection?: boolean + properties?: Record<<>, MappingProperty> + _routing?: MappingRoutingField + _source?: MappingSourceField + runtime?: MappingRuntimeFields +} +---- + +[discrete] +===== `IndicesPutMappingResponse` + +[source,ts] +---- +type IndicesPutMappingResponse = <> +---- + diff --git a/docs/reference-indices-put_settings.asciidoc b/docs/reference-indices-put_settings.asciidoc new file mode 100644 index 000000000..2feb47509 --- /dev/null +++ b/docs/reference-indices-put_settings.asciidoc @@ -0,0 +1,68 @@ +[[reference-indices-put_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.putSettings + +Update index settings. Changes dynamic index settings in real time. For data streams, index setting changes are applied to all backing indices by default. + +{ref}/indices-update-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesPutSettingsRequest, options?): Promise +---- + +[discrete] +===== `IndicesPutSettingsRequest` + +[source,ts] +---- +interface IndicesPutSettingsRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + flat_settings?: boolean + ignore_unavailable?: boolean + master_timeout?: <> + preserve_existing?: boolean + timeout?: <> + settings?: IndicesIndexSettings +} +---- + +[discrete] +===== `IndicesPutSettingsResponse` + +[source,ts] +---- +type IndicesPutSettingsResponse = <> +---- + diff --git a/docs/reference-indices-put_template.asciidoc b/docs/reference-indices-put_template.asciidoc new file mode 100644 index 000000000..93585b789 --- /dev/null +++ b/docs/reference-indices-put_template.asciidoc @@ -0,0 +1,69 @@ +[[reference-indices-put_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.putTemplate + +Create or update an index template. Index templates define settings, mappings, and aliases that can be applied automatically to new indices. + +{ref}/indices-templates-v1.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesPutTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesPutTemplateRequest` + +[source,ts] +---- +interface IndicesPutTemplateRequest extends <> { + name: <> + create?: boolean + master_timeout?: <> + cause?: string + aliases?: Record<<>, IndicesAlias> + index_patterns?: string | string[] + mappings?: MappingTypeMapping + order?: <> + settings?: IndicesIndexSettings + version?: <> +} +---- + +[discrete] +===== `IndicesPutTemplateResponse` + +[source,ts] +---- +type IndicesPutTemplateResponse = <> +---- + diff --git a/docs/reference-indices-recovery.asciidoc b/docs/reference-indices-recovery.asciidoc new file mode 100644 index 000000000..5a282890b --- /dev/null +++ b/docs/reference-indices-recovery.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-recovery]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.recovery + +Returns information about ongoing and completed shard recoveries for one or more indices. For data streams, the API returns information for the stream’s backing indices. + +{ref}/indices-recovery.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesRecoveryRequest, options?): Promise +---- + +[discrete] +===== `IndicesRecoveryRequest` + +[source,ts] +---- +interface IndicesRecoveryRequest extends <> { + index?: <> + active_only?: boolean + detailed?: boolean +} +---- + +[discrete] +===== `IndicesRecoveryResponse` + +[source,ts] +---- +type IndicesRecoveryResponse = Record<<>, IndicesRecoveryRecoveryStatus> +---- + diff --git a/docs/reference-indices-refresh.asciidoc b/docs/reference-indices-refresh.asciidoc new file mode 100644 index 000000000..66741cd93 --- /dev/null +++ b/docs/reference-indices-refresh.asciidoc @@ -0,0 +1,63 @@ +[[reference-indices-refresh]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.refresh + +Refresh an index. A refresh makes recent operations performed on one or more indices available for search. For data streams, the API runs the refresh operation on the stream’s backing indices. + +{ref}/indices-refresh.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesRefreshRequest, options?): Promise +---- + +[discrete] +===== `IndicesRefreshRequest` + +[source,ts] +---- +interface IndicesRefreshRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean +} +---- + +[discrete] +===== `IndicesRefreshResponse` + +[source,ts] +---- +type IndicesRefreshResponse = <> +---- + diff --git a/docs/reference-indices-reload_search_analyzers.asciidoc b/docs/reference-indices-reload_search_analyzers.asciidoc new file mode 100644 index 000000000..7f651255c --- /dev/null +++ b/docs/reference-indices-reload_search_analyzers.asciidoc @@ -0,0 +1,63 @@ +[[reference-indices-reload_search_analyzers]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.reloadSearchAnalyzers + +Reloads an index's search analyzers and their resources. + +{ref}/indices-reload-analyzers.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesReloadSearchAnalyzersRequest, options?): Promise +---- + +[discrete] +===== `IndicesReloadSearchAnalyzersRequest` + +[source,ts] +---- +interface IndicesReloadSearchAnalyzersRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean +} +---- + +[discrete] +===== `IndicesReloadSearchAnalyzersResponse` + +[source,ts] +---- +type IndicesReloadSearchAnalyzersResponse = IndicesReloadSearchAnalyzersReloadResult +---- + diff --git a/docs/reference-indices-resolve_cluster.asciidoc b/docs/reference-indices-resolve_cluster.asciidoc new file mode 100644 index 000000000..91064c85c --- /dev/null +++ b/docs/reference-indices-resolve_cluster.asciidoc @@ -0,0 +1,64 @@ +[[reference-indices-resolve_cluster]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.resolveCluster + +Resolves the specified index expressions to return information about each cluster, including the local cluster, if included. Multiple patterns and remote clusters are supported. + +{ref}/indices-resolve-cluster-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesResolveClusterRequest, options?): Promise +---- + +[discrete] +===== `IndicesResolveClusterRequest` + +[source,ts] +---- +interface IndicesResolveClusterRequest extends <> { + name: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean +} +---- + +[discrete] +===== `IndicesResolveClusterResponse` + +[source,ts] +---- +type IndicesResolveClusterResponse = Record<<>, IndicesResolveClusterResolveClusterInfo> +---- + diff --git a/docs/reference-indices-resolve_index.asciidoc b/docs/reference-indices-resolve_index.asciidoc new file mode 100644 index 000000000..b4056a287 --- /dev/null +++ b/docs/reference-indices-resolve_index.asciidoc @@ -0,0 +1,67 @@ +[[reference-indices-resolve_index]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.resolveIndex + +Resolves the specified name(s) and/or index patterns for indices, aliases, and data streams. Multiple patterns and remote clusters are supported. + +{ref}/indices-resolve-index-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesResolveIndexRequest, options?): Promise +---- + +[discrete] +===== `IndicesResolveIndexRequest` + +[source,ts] +---- +interface IndicesResolveIndexRequest extends <> { + name: <> + expand_wildcards?: <> + ignore_unavailable?: boolean + allow_no_indices?: boolean +} +---- + +[discrete] +===== `IndicesResolveIndexResponse` + +[source,ts] +---- +interface IndicesResolveIndexResponse { + indices: IndicesResolveIndexResolveIndexItem[] + aliases: IndicesResolveIndexResolveIndexAliasItem[] + data_streams: IndicesResolveIndexResolveIndexDataStreamsItem[] +} +---- + diff --git a/docs/reference-indices-rollover.asciidoc b/docs/reference-indices-rollover.asciidoc new file mode 100644 index 000000000..113be318e --- /dev/null +++ b/docs/reference-indices-rollover.asciidoc @@ -0,0 +1,77 @@ +[[reference-indices-rollover]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.rollover + +Roll over to a new index. Creates a new index for a data stream or index alias. + +{ref}/indices-rollover-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesRolloverRequest, options?): Promise +---- + +[discrete] +===== `IndicesRolloverRequest` + +[source,ts] +---- +interface IndicesRolloverRequest extends <> { + alias: <> + new_index?: <> + dry_run?: boolean + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> + aliases?: Record<<>, IndicesAlias> + conditions?: IndicesRolloverRolloverConditions + mappings?: MappingTypeMapping + settings?: Record +} +---- + +[discrete] +===== `IndicesRolloverResponse` + +[source,ts] +---- +interface IndicesRolloverResponse { + acknowledged: boolean + conditions: Record + dry_run: boolean + new_index: string + old_index: string + rolled_over: boolean + shards_acknowledged: boolean +} +---- + diff --git a/docs/reference-indices-segments.asciidoc b/docs/reference-indices-segments.asciidoc new file mode 100644 index 000000000..35a3c805d --- /dev/null +++ b/docs/reference-indices-segments.asciidoc @@ -0,0 +1,67 @@ +[[reference-indices-segments]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.segments + +Returns low-level information about the Lucene segments in index shards. For data streams, the API returns information about the stream’s backing indices. + +{ref}/indices-segments.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesSegmentsRequest, options?): Promise +---- + +[discrete] +===== `IndicesSegmentsRequest` + +[source,ts] +---- +interface IndicesSegmentsRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + verbose?: boolean +} +---- + +[discrete] +===== `IndicesSegmentsResponse` + +[source,ts] +---- +interface IndicesSegmentsResponse { + indices: Record + _shards: <> +} +---- + diff --git a/docs/reference-indices-shard_stores.asciidoc b/docs/reference-indices-shard_stores.asciidoc new file mode 100644 index 000000000..519ab965a --- /dev/null +++ b/docs/reference-indices-shard_stores.asciidoc @@ -0,0 +1,66 @@ +[[reference-indices-shard_stores]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.shardStores + +Retrieves store information about replica shards in one or more indices. For data streams, the API retrieves store information for the stream’s backing indices. + +{ref}/indices-shards-stores.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesShardStoresRequest, options?): Promise +---- + +[discrete] +===== `IndicesShardStoresRequest` + +[source,ts] +---- +interface IndicesShardStoresRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + status?: IndicesShardStoresShardStoreStatus | IndicesShardStoresShardStoreStatus[] +} +---- + +[discrete] +===== `IndicesShardStoresResponse` + +[source,ts] +---- +interface IndicesShardStoresResponse { + indices: Record<<>, IndicesShardStoresIndicesShardStores> +} +---- + diff --git a/docs/reference-indices-shrink.asciidoc b/docs/reference-indices-shrink.asciidoc new file mode 100644 index 000000000..758a8452f --- /dev/null +++ b/docs/reference-indices-shrink.asciidoc @@ -0,0 +1,70 @@ +[[reference-indices-shrink]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.shrink + +Shrinks an existing index into a new index with fewer primary shards. + +{ref}/indices-shrink-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesShrinkRequest, options?): Promise +---- + +[discrete] +===== `IndicesShrinkRequest` + +[source,ts] +---- +interface IndicesShrinkRequest extends <> { + index: <> + target: <> + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> + aliases?: Record<<>, IndicesAlias> + settings?: Record +} +---- + +[discrete] +===== `IndicesShrinkResponse` + +[source,ts] +---- +interface IndicesShrinkResponse { + acknowledged: boolean + shards_acknowledged: boolean + index: <> +} +---- + diff --git a/docs/reference-indices-simulate_index_template.asciidoc b/docs/reference-indices-simulate_index_template.asciidoc new file mode 100644 index 000000000..71a79e085 --- /dev/null +++ b/docs/reference-indices-simulate_index_template.asciidoc @@ -0,0 +1,65 @@ +[[reference-indices-simulate_index_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.simulateIndexTemplate + +Simulate an index. Returns the index configuration that would be applied to the specified index from an existing index template. + +{ref}/indices-simulate-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesSimulateIndexTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesSimulateIndexTemplateRequest` + +[source,ts] +---- +interface IndicesSimulateIndexTemplateRequest extends <> { + name: <> + master_timeout?: <> + include_defaults?: boolean +} +---- + +[discrete] +===== `IndicesSimulateIndexTemplateResponse` + +[source,ts] +---- +interface IndicesSimulateIndexTemplateResponse { + overlapping?: IndicesSimulateTemplateOverlapping[] + template: IndicesSimulateTemplateTemplate +} +---- + diff --git a/docs/reference-indices-simulate_template.asciidoc b/docs/reference-indices-simulate_template.asciidoc new file mode 100644 index 000000000..674399345 --- /dev/null +++ b/docs/reference-indices-simulate_template.asciidoc @@ -0,0 +1,76 @@ +[[reference-indices-simulate_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.simulateTemplate + +Simulate an index template. Returns the index configuration that would be applied by a particular index template. + +{ref}/indices-simulate-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesSimulateTemplateRequest, options?): Promise +---- + +[discrete] +===== `IndicesSimulateTemplateRequest` + +[source,ts] +---- +interface IndicesSimulateTemplateRequest extends <> { + name?: <> + create?: boolean + master_timeout?: <> + include_defaults?: boolean + allow_auto_create?: boolean + index_patterns?: <> + composed_of?: <>[] + template?: IndicesPutIndexTemplateIndexTemplateMapping + data_stream?: IndicesDataStreamVisibility + priority?: <> + version?: <> + _meta?: <> + ignore_missing_component_templates?: string[] + deprecated?: boolean +} +---- + +[discrete] +===== `IndicesSimulateTemplateResponse` + +[source,ts] +---- +interface IndicesSimulateTemplateResponse { + overlapping?: IndicesSimulateTemplateOverlapping[] + template: IndicesSimulateTemplateTemplate +} +---- + diff --git a/docs/reference-indices-split.asciidoc b/docs/reference-indices-split.asciidoc new file mode 100644 index 000000000..3154d23aa --- /dev/null +++ b/docs/reference-indices-split.asciidoc @@ -0,0 +1,70 @@ +[[reference-indices-split]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.split + +Splits an existing index into a new index with more primary shards. + +{ref}/indices-split-index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesSplitRequest, options?): Promise +---- + +[discrete] +===== `IndicesSplitRequest` + +[source,ts] +---- +interface IndicesSplitRequest extends <> { + index: <> + target: <> + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: <> + aliases?: Record<<>, IndicesAlias> + settings?: Record +} +---- + +[discrete] +===== `IndicesSplitResponse` + +[source,ts] +---- +interface IndicesSplitResponse { + acknowledged: boolean + shards_acknowledged: boolean + index: <> +} +---- + diff --git a/docs/reference-indices-stats.asciidoc b/docs/reference-indices-stats.asciidoc new file mode 100644 index 000000000..107414a33 --- /dev/null +++ b/docs/reference-indices-stats.asciidoc @@ -0,0 +1,74 @@ +[[reference-indices-stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.stats + +Returns statistics for one or more indices. For data streams, the API retrieves statistics for the stream’s backing indices. + +{ref}/indices-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesStatsRequest, options?): Promise +---- + +[discrete] +===== `IndicesStatsRequest` + +[source,ts] +---- +interface IndicesStatsRequest extends <> { + metric?: <> + index?: <> + completion_fields?: <> + expand_wildcards?: <> + fielddata_fields?: <> + fields?: <> + forbid_closed_indices?: boolean + groups?: string | string[] + include_segment_file_sizes?: boolean + include_unloaded_segments?: boolean + level?: <> +} +---- + +[discrete] +===== `IndicesStatsResponse` + +[source,ts] +---- +interface IndicesStatsResponse { + indices?: Record + _shards: <> + _all: IndicesStatsIndicesStats +} +---- + diff --git a/docs/reference-indices-unfreeze.asciidoc b/docs/reference-indices-unfreeze.asciidoc new file mode 100644 index 000000000..b046d7607 --- /dev/null +++ b/docs/reference-indices-unfreeze.asciidoc @@ -0,0 +1,69 @@ +[[reference-indices-unfreeze]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.unfreeze + +Unfreezes an index. + +{ref}/unfreeze-index-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesUnfreezeRequest, options?): Promise +---- + +[discrete] +===== `IndicesUnfreezeRequest` + +[source,ts] +---- +interface IndicesUnfreezeRequest extends <> { + index: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + master_timeout?: <> + timeout?: <> + wait_for_active_shards?: string +} +---- + +[discrete] +===== `IndicesUnfreezeResponse` + +[source,ts] +---- +interface IndicesUnfreezeResponse { + acknowledged: boolean + shards_acknowledged: boolean +} +---- + diff --git a/docs/reference-indices-update_aliases.asciidoc b/docs/reference-indices-update_aliases.asciidoc new file mode 100644 index 000000000..39ef67f5b --- /dev/null +++ b/docs/reference-indices-update_aliases.asciidoc @@ -0,0 +1,62 @@ +[[reference-indices-update_aliases]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.updateAliases + +Create or update an alias. Adds a data stream or index to an alias. + +{ref}/indices-aliases.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesUpdateAliasesRequest, options?): Promise +---- + +[discrete] +===== `IndicesUpdateAliasesRequest` + +[source,ts] +---- +interface IndicesUpdateAliasesRequest extends <> { + master_timeout?: <> + timeout?: <> + actions?: IndicesUpdateAliasesAction[] +} +---- + +[discrete] +===== `IndicesUpdateAliasesResponse` + +[source,ts] +---- +type IndicesUpdateAliasesResponse = <> +---- + diff --git a/docs/reference-indices-validate_query.asciidoc b/docs/reference-indices-validate_query.asciidoc new file mode 100644 index 000000000..c12320340 --- /dev/null +++ b/docs/reference-indices-validate_query.asciidoc @@ -0,0 +1,78 @@ +[[reference-indices-validate_query]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.indices.validateQuery + +Validate a query. Validates a query without running it. + +{ref}/search-validate.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IndicesValidateQueryRequest, options?): Promise +---- + +[discrete] +===== `IndicesValidateQueryRequest` + +[source,ts] +---- +interface IndicesValidateQueryRequest extends <> { + index?: <> + allow_no_indices?: boolean + all_shards?: boolean + analyzer?: string + analyze_wildcard?: boolean + default_operator?: QueryDslOperator + df?: string + expand_wildcards?: <> + explain?: boolean + ignore_unavailable?: boolean + lenient?: boolean + rewrite?: boolean + q?: string + query?: QueryDslQueryContainer +} +---- + +[discrete] +===== `IndicesValidateQueryResponse` + +[source,ts] +---- +interface IndicesValidateQueryResponse { + explanations?: IndicesValidateQueryIndicesValidationExplanation[] + _shards?: <> + valid: boolean + error?: string +} +---- + diff --git a/docs/reference-inference-delete.asciidoc b/docs/reference-inference-delete.asciidoc new file mode 100644 index 000000000..27505ec59 --- /dev/null +++ b/docs/reference-inference-delete.asciidoc @@ -0,0 +1,63 @@ +[[reference-inference-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.inference.delete + +Delete an inference endpoint + +{ref}/delete-inference-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(InferenceDeleteRequest, options?): Promise +---- + +[discrete] +===== `InferenceDeleteRequest` + +[source,ts] +---- +interface InferenceDeleteRequest extends <> { + task_type?: InferenceTaskType + inference_id: <> + dry_run?: boolean + force?: boolean +} +---- + +[discrete] +===== `InferenceDeleteResponse` + +[source,ts] +---- +type InferenceDeleteResponse = InferenceDeleteInferenceEndpointResult +---- + diff --git a/docs/reference-inference-get.asciidoc b/docs/reference-inference-get.asciidoc new file mode 100644 index 000000000..1c597151c --- /dev/null +++ b/docs/reference-inference-get.asciidoc @@ -0,0 +1,63 @@ +[[reference-inference-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.inference.get + +Get an inference endpoint + +{ref}/get-inference-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(InferenceGetRequest, options?): Promise +---- + +[discrete] +===== `InferenceGetRequest` + +[source,ts] +---- +interface InferenceGetRequest extends <> { + task_type?: InferenceTaskType + inference_id?: <> +} +---- + +[discrete] +===== `InferenceGetResponse` + +[source,ts] +---- +interface InferenceGetResponse { + endpoints: InferenceInferenceEndpointInfo[] +} +---- + diff --git a/docs/reference-inference-inference.asciidoc b/docs/reference-inference-inference.asciidoc new file mode 100644 index 000000000..775e01e79 --- /dev/null +++ b/docs/reference-inference-inference.asciidoc @@ -0,0 +1,65 @@ +[[reference-inference-inference]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.inference.inference + +Perform inference on the service + +{ref}/post-inference-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(InferenceInferenceRequest, options?): Promise +---- + +[discrete] +===== `InferenceInferenceRequest` + +[source,ts] +---- +interface InferenceInferenceRequest extends <> { + task_type?: InferenceTaskType + inference_id: <> + timeout?: <> + query?: string + input: string | string[] + task_settings?: InferenceTaskSettings +} +---- + +[discrete] +===== `InferenceInferenceResponse` + +[source,ts] +---- +type InferenceInferenceResponse = InferenceInferenceResult +---- + diff --git a/docs/reference-inference-put.asciidoc b/docs/reference-inference-put.asciidoc new file mode 100644 index 000000000..fb557926b --- /dev/null +++ b/docs/reference-inference-put.asciidoc @@ -0,0 +1,62 @@ +[[reference-inference-put]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.inference.put + +Create an inference endpoint + +{ref}/put-inference-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(InferencePutRequest, options?): Promise +---- + +[discrete] +===== `InferencePutRequest` + +[source,ts] +---- +interface InferencePutRequest extends <> { + task_type?: InferenceTaskType + inference_id: <> + inference_config?: InferenceInferenceEndpoint +} +---- + +[discrete] +===== `InferencePutResponse` + +[source,ts] +---- +type InferencePutResponse = InferenceInferenceEndpointInfo +---- + diff --git a/docs/reference-inference-stream_inference.asciidoc b/docs/reference-inference-stream_inference.asciidoc new file mode 100644 index 000000000..184054640 --- /dev/null +++ b/docs/reference-inference-stream_inference.asciidoc @@ -0,0 +1,57 @@ +[[reference-inference-stream_inference]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.inference.streamInference + +Perform streaming inference + +[discrete] +==== Function signature + +[source,ts] +---- +(InferenceStreamInferenceRequest, options?): Promise +---- + +[discrete] +===== `InferenceStreamInferenceRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `InferenceStreamInferenceResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-info.asciidoc b/docs/reference-info.asciidoc new file mode 100644 index 000000000..b3df99b09 --- /dev/null +++ b/docs/reference-info.asciidoc @@ -0,0 +1,65 @@ +[[reference-info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.info + +Get cluster info. Returns basic information about the cluster. + +{ref}/index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(InfoRequest, options?): Promise +---- + +[discrete] +===== `InfoRequest` + +[source,ts] +---- +interface InfoRequest extends <> { +} +---- + +[discrete] +===== `InfoResponse` + +[source,ts] +---- +interface InfoResponse { + cluster_name: <> + cluster_uuid: <> + name: <> + tagline: string + version: <> +} +---- + diff --git a/docs/reference-ingest-delete_geoip_database.asciidoc b/docs/reference-ingest-delete_geoip_database.asciidoc new file mode 100644 index 000000000..98885cec5 --- /dev/null +++ b/docs/reference-ingest-delete_geoip_database.asciidoc @@ -0,0 +1,62 @@ +[[reference-ingest-delete_geoip_database]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.deleteGeoipDatabase + +Deletes a geoip database configuration. + +{ref}/delete-geoip-database-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestDeleteGeoipDatabaseRequest, options?): Promise +---- + +[discrete] +===== `IngestDeleteGeoipDatabaseRequest` + +[source,ts] +---- +interface IngestDeleteGeoipDatabaseRequest extends <> { + id: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IngestDeleteGeoipDatabaseResponse` + +[source,ts] +---- +type IngestDeleteGeoipDatabaseResponse = <> +---- + diff --git a/docs/reference-ingest-delete_pipeline.asciidoc b/docs/reference-ingest-delete_pipeline.asciidoc new file mode 100644 index 000000000..6d847e69f --- /dev/null +++ b/docs/reference-ingest-delete_pipeline.asciidoc @@ -0,0 +1,62 @@ +[[reference-ingest-delete_pipeline]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.deletePipeline + +Deletes one or more existing ingest pipeline. + +{ref}/delete-pipeline-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestDeletePipelineRequest, options?): Promise +---- + +[discrete] +===== `IngestDeletePipelineRequest` + +[source,ts] +---- +interface IngestDeletePipelineRequest extends <> { + id: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `IngestDeletePipelineResponse` + +[source,ts] +---- +type IngestDeletePipelineResponse = <> +---- + diff --git a/docs/reference-ingest-geo_ip_stats.asciidoc b/docs/reference-ingest-geo_ip_stats.asciidoc new file mode 100644 index 000000000..af336c446 --- /dev/null +++ b/docs/reference-ingest-geo_ip_stats.asciidoc @@ -0,0 +1,62 @@ +[[reference-ingest-geo_ip_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.geoIpStats + +Gets download statistics for GeoIP2 databases used with the geoip processor. + +{ref}/geoip-processor.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestGeoIpStatsRequest, options?): Promise +---- + +[discrete] +===== `IngestGeoIpStatsRequest` + +[source,ts] +---- +interface IngestGeoIpStatsRequest extends <> { +} +---- + +[discrete] +===== `IngestGeoIpStatsResponse` + +[source,ts] +---- +interface IngestGeoIpStatsResponse { + stats: IngestGeoIpStatsGeoIpDownloadStatistics + nodes: Record<<>, IngestGeoIpStatsGeoIpNodeDatabases> +} +---- + diff --git a/docs/reference-ingest-get_geoip_database.asciidoc b/docs/reference-ingest-get_geoip_database.asciidoc new file mode 100644 index 000000000..387ef7f3f --- /dev/null +++ b/docs/reference-ingest-get_geoip_database.asciidoc @@ -0,0 +1,63 @@ +[[reference-ingest-get_geoip_database]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.getGeoipDatabase + +Returns information about one or more geoip database configurations. + +{ref}/get-geoip-database-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestGetGeoipDatabaseRequest, options?): Promise +---- + +[discrete] +===== `IngestGetGeoipDatabaseRequest` + +[source,ts] +---- +interface IngestGetGeoipDatabaseRequest extends <> { + id?: <> + master_timeout?: <> +} +---- + +[discrete] +===== `IngestGetGeoipDatabaseResponse` + +[source,ts] +---- +interface IngestGetGeoipDatabaseResponse { + databases: IngestGetGeoipDatabaseDatabaseConfigurationMetadata[] +} +---- + diff --git a/docs/reference-ingest-get_pipeline.asciidoc b/docs/reference-ingest-get_pipeline.asciidoc new file mode 100644 index 000000000..5173a9226 --- /dev/null +++ b/docs/reference-ingest-get_pipeline.asciidoc @@ -0,0 +1,62 @@ +[[reference-ingest-get_pipeline]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.getPipeline + +Returns information about one or more ingest pipelines. This API returns a local reference of the pipeline. + +{ref}/get-pipeline-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestGetPipelineRequest, options?): Promise +---- + +[discrete] +===== `IngestGetPipelineRequest` + +[source,ts] +---- +interface IngestGetPipelineRequest extends <> { + id?: <> + master_timeout?: <> + summary?: boolean +} +---- + +[discrete] +===== `IngestGetPipelineResponse` + +[source,ts] +---- +type IngestGetPipelineResponse = Record +---- + diff --git a/docs/reference-ingest-processor_grok.asciidoc b/docs/reference-ingest-processor_grok.asciidoc new file mode 100644 index 000000000..dc69b7f05 --- /dev/null +++ b/docs/reference-ingest-processor_grok.asciidoc @@ -0,0 +1,61 @@ +[[reference-ingest-processor_grok]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.processorGrok + +Extracts structured fields out of a single text field within a document. You choose which field to extract matched fields from, as well as the grok pattern you expect will match. A grok pattern is like a regular expression that supports aliased expressions that can be reused. + +{ref}/grok-processor.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestProcessorGrokRequest, options?): Promise +---- + +[discrete] +===== `IngestProcessorGrokRequest` + +[source,ts] +---- +interface IngestProcessorGrokRequest extends <> { +} +---- + +[discrete] +===== `IngestProcessorGrokResponse` + +[source,ts] +---- +interface IngestProcessorGrokResponse { + patterns: Record +} +---- + diff --git a/docs/reference-ingest-put_geoip_database.asciidoc b/docs/reference-ingest-put_geoip_database.asciidoc new file mode 100644 index 000000000..dffb38cf2 --- /dev/null +++ b/docs/reference-ingest-put_geoip_database.asciidoc @@ -0,0 +1,64 @@ +[[reference-ingest-put_geoip_database]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.putGeoipDatabase + +Returns information about one or more geoip database configurations. + +{ref}/put-geoip-database-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestPutGeoipDatabaseRequest, options?): Promise +---- + +[discrete] +===== `IngestPutGeoipDatabaseRequest` + +[source,ts] +---- +interface IngestPutGeoipDatabaseRequest extends <> { + id: <> + master_timeout?: <> + timeout?: <> + name: <> + maxmind: IngestMaxmind +} +---- + +[discrete] +===== `IngestPutGeoipDatabaseResponse` + +[source,ts] +---- +type IngestPutGeoipDatabaseResponse = <> +---- + diff --git a/docs/reference-ingest-put_pipeline.asciidoc b/docs/reference-ingest-put_pipeline.asciidoc new file mode 100644 index 000000000..f0a1c7e62 --- /dev/null +++ b/docs/reference-ingest-put_pipeline.asciidoc @@ -0,0 +1,69 @@ +[[reference-ingest-put_pipeline]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.putPipeline + +Creates or updates an ingest pipeline. Changes made using this API take effect immediately. + +{ref}/ingest.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestPutPipelineRequest, options?): Promise +---- + +[discrete] +===== `IngestPutPipelineRequest` + +[source,ts] +---- +interface IngestPutPipelineRequest extends <> { + id: <> + master_timeout?: <> + timeout?: <> + if_version?: <> + _meta?: <> + description?: string + on_failure?: IngestProcessorContainer[] + processors?: IngestProcessorContainer[] + version?: <> + deprecated?: boolean +} +---- + +[discrete] +===== `IngestPutPipelineResponse` + +[source,ts] +---- +type IngestPutPipelineResponse = <> +---- + diff --git a/docs/reference-ingest-simulate.asciidoc b/docs/reference-ingest-simulate.asciidoc new file mode 100644 index 000000000..74a6cd0ef --- /dev/null +++ b/docs/reference-ingest-simulate.asciidoc @@ -0,0 +1,65 @@ +[[reference-ingest-simulate]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ingest.simulate + +Executes an ingest pipeline against a set of provided documents. + +{ref}/simulate-pipeline-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(IngestSimulateRequest, options?): Promise +---- + +[discrete] +===== `IngestSimulateRequest` + +[source,ts] +---- +interface IngestSimulateRequest extends <> { + id?: <> + verbose?: boolean + docs: IngestSimulateDocument[] + pipeline?: IngestPipeline +} +---- + +[discrete] +===== `IngestSimulateResponse` + +[source,ts] +---- +interface IngestSimulateResponse { + docs: IngestSimulateSimulateDocumentResult[] +} +---- + diff --git a/docs/reference-knn_search.asciidoc b/docs/reference-knn_search.asciidoc new file mode 100644 index 000000000..a5217d330 --- /dev/null +++ b/docs/reference-knn_search.asciidoc @@ -0,0 +1,74 @@ +[[reference-knn_search]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.knnSearch + +Run a knn search. NOTE: The kNN search API has been replaced by the `knn` option in the search API. Perform a k-nearest neighbor (kNN) search on a dense_vector field and return the matching documents. Given a query vector, the API finds the k closest vectors and returns those documents as search hits. Elasticsearch uses the HNSW algorithm to support efficient kNN search. Like most kNN algorithms, HNSW is an approximate method that sacrifices result accuracy for improved search speed. This means the results returned are not always the true k closest neighbors. The kNN search API supports restricting the search using a filter. The search will return the top k documents that also match the filter query. + +{ref}/search-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(KnnSearchRequest, options?): Promise +---- + +[discrete] +===== `KnnSearchRequest` + +[source,ts] +---- +interface KnnSearchRequest extends <> { + index: <> + routing?: <> + _source?: SearchSourceConfig + docvalue_fields?: (QueryDslFieldAndFormat | <>)[] + stored_fields?: <> + fields?: <> + filter?: QueryDslQueryContainer | QueryDslQueryContainer[] + knn: KnnSearchQuery +} +---- + +[discrete] +===== `KnnSearchResponse` + +[source,ts] +---- +interface KnnSearchResponse { + took: <> + timed_out: boolean + _shards: <> + hits: SearchHitsMetadata + fields?: Record + max_score?: <> +} +---- + diff --git a/docs/reference-license-delete.asciidoc b/docs/reference-license-delete.asciidoc new file mode 100644 index 000000000..a554a92d5 --- /dev/null +++ b/docs/reference-license-delete.asciidoc @@ -0,0 +1,59 @@ +[[reference-license-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.license.delete + +Deletes licensing information for the cluster + +{ref}/delete-license.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LicenseDeleteRequest, options?): Promise +---- + +[discrete] +===== `LicenseDeleteRequest` + +[source,ts] +---- +interface LicenseDeleteRequest extends <> { +} +---- + +[discrete] +===== `LicenseDeleteResponse` + +[source,ts] +---- +type LicenseDeleteResponse = <> +---- + diff --git a/docs/reference-license-get.asciidoc b/docs/reference-license-get.asciidoc new file mode 100644 index 000000000..c8ec99e8c --- /dev/null +++ b/docs/reference-license-get.asciidoc @@ -0,0 +1,63 @@ +[[reference-license-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.license.get + +Get license information. Returns information about your Elastic license, including its type, its status, when it was issued, and when it expires. For more information about the different types of licenses, refer to [Elastic Stack subscriptions](https://www.elastic.co/subscriptions). + +{ref}/get-license.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LicenseGetRequest, options?): Promise +---- + +[discrete] +===== `LicenseGetRequest` + +[source,ts] +---- +interface LicenseGetRequest extends <> { + accept_enterprise?: boolean + local?: boolean +} +---- + +[discrete] +===== `LicenseGetResponse` + +[source,ts] +---- +interface LicenseGetResponse { + license: LicenseGetLicenseInformation +} +---- + diff --git a/docs/reference-license-get_basic_status.asciidoc b/docs/reference-license-get_basic_status.asciidoc new file mode 100644 index 000000000..8bcf35017 --- /dev/null +++ b/docs/reference-license-get_basic_status.asciidoc @@ -0,0 +1,61 @@ +[[reference-license-get_basic_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.license.getBasicStatus + +Retrieves information about the status of the basic license. + +{ref}/get-basic-status.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LicenseGetBasicStatusRequest, options?): Promise +---- + +[discrete] +===== `LicenseGetBasicStatusRequest` + +[source,ts] +---- +interface LicenseGetBasicStatusRequest extends <> { +} +---- + +[discrete] +===== `LicenseGetBasicStatusResponse` + +[source,ts] +---- +interface LicenseGetBasicStatusResponse { + eligible_to_start_basic: boolean +} +---- + diff --git a/docs/reference-license-get_trial_status.asciidoc b/docs/reference-license-get_trial_status.asciidoc new file mode 100644 index 000000000..d96178efb --- /dev/null +++ b/docs/reference-license-get_trial_status.asciidoc @@ -0,0 +1,61 @@ +[[reference-license-get_trial_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.license.getTrialStatus + +Retrieves information about the status of the trial license. + +{ref}/get-trial-status.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LicenseGetTrialStatusRequest, options?): Promise +---- + +[discrete] +===== `LicenseGetTrialStatusRequest` + +[source,ts] +---- +interface LicenseGetTrialStatusRequest extends <> { +} +---- + +[discrete] +===== `LicenseGetTrialStatusResponse` + +[source,ts] +---- +interface LicenseGetTrialStatusResponse { + eligible_to_start_trial: boolean +} +---- + diff --git a/docs/reference-license-post.asciidoc b/docs/reference-license-post.asciidoc new file mode 100644 index 000000000..0a3f779fb --- /dev/null +++ b/docs/reference-license-post.asciidoc @@ -0,0 +1,66 @@ +[[reference-license-post]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.license.post + +Updates the license for the cluster. + +{ref}/update-license.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LicensePostRequest, options?): Promise +---- + +[discrete] +===== `LicensePostRequest` + +[source,ts] +---- +interface LicensePostRequest extends <> { + acknowledge?: boolean + license?: LicenseLicense + licenses?: LicenseLicense[] +} +---- + +[discrete] +===== `LicensePostResponse` + +[source,ts] +---- +interface LicensePostResponse { + acknowledge?: LicensePostAcknowledgement + acknowledged: boolean + license_status: LicenseLicenseStatus +} +---- + diff --git a/docs/reference-license-post_start_basic.asciidoc b/docs/reference-license-post_start_basic.asciidoc new file mode 100644 index 000000000..bc0a74a38 --- /dev/null +++ b/docs/reference-license-post_start_basic.asciidoc @@ -0,0 +1,66 @@ +[[reference-license-post_start_basic]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.license.postStartBasic + +The start basic API enables you to initiate an indefinite basic license, which gives access to all the basic features. If the basic license does not support all of the features that are available with your current license, however, you are notified in the response. You must then re-submit the API request with the acknowledge parameter set to true. To check the status of your basic license, use the following API: [Get basic status](https://www.elastic.co/guide/en/elasticsearch/reference/current/get-basic-status.html). + +{ref}/start-basic.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LicensePostStartBasicRequest, options?): Promise +---- + +[discrete] +===== `LicensePostStartBasicRequest` + +[source,ts] +---- +interface LicensePostStartBasicRequest extends <> { + acknowledge?: boolean +} +---- + +[discrete] +===== `LicensePostStartBasicResponse` + +[source,ts] +---- +interface LicensePostStartBasicResponse { + acknowledged: boolean + basic_was_started: boolean + error_message?: string + type?: LicenseLicenseType + acknowledge?: Record +} +---- + diff --git a/docs/reference-license-post_start_trial.asciidoc b/docs/reference-license-post_start_trial.asciidoc new file mode 100644 index 000000000..7e7b1d363 --- /dev/null +++ b/docs/reference-license-post_start_trial.asciidoc @@ -0,0 +1,66 @@ +[[reference-license-post_start_trial]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.license.postStartTrial + +The start trial API enables you to start a 30-day trial, which gives access to all subscription features. + +{ref}/start-trial.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LicensePostStartTrialRequest, options?): Promise +---- + +[discrete] +===== `LicensePostStartTrialRequest` + +[source,ts] +---- +interface LicensePostStartTrialRequest extends <> { + acknowledge?: boolean + type_query_string?: string +} +---- + +[discrete] +===== `LicensePostStartTrialResponse` + +[source,ts] +---- +interface LicensePostStartTrialResponse { + acknowledged: boolean + error_message?: string + trial_was_started: boolean + type?: LicenseLicenseType +} +---- + diff --git a/docs/reference-logstash-delete_pipeline.asciidoc b/docs/reference-logstash-delete_pipeline.asciidoc new file mode 100644 index 000000000..320cc9769 --- /dev/null +++ b/docs/reference-logstash-delete_pipeline.asciidoc @@ -0,0 +1,60 @@ +[[reference-logstash-delete_pipeline]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.logstash.deletePipeline + +Deletes a pipeline used for Logstash Central Management. + +{ref}/logstash-api-delete-pipeline.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LogstashDeletePipelineRequest, options?): Promise +---- + +[discrete] +===== `LogstashDeletePipelineRequest` + +[source,ts] +---- +interface LogstashDeletePipelineRequest extends <> { + id: <> +} +---- + +[discrete] +===== `LogstashDeletePipelineResponse` + +[source,ts] +---- +type LogstashDeletePipelineResponse = boolean +---- + diff --git a/docs/reference-logstash-get_pipeline.asciidoc b/docs/reference-logstash-get_pipeline.asciidoc new file mode 100644 index 000000000..2acbb3deb --- /dev/null +++ b/docs/reference-logstash-get_pipeline.asciidoc @@ -0,0 +1,60 @@ +[[reference-logstash-get_pipeline]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.logstash.getPipeline + +Retrieves pipelines used for Logstash Central Management. + +{ref}/logstash-api-get-pipeline.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LogstashGetPipelineRequest, options?): Promise +---- + +[discrete] +===== `LogstashGetPipelineRequest` + +[source,ts] +---- +interface LogstashGetPipelineRequest extends <> { + id?: <> +} +---- + +[discrete] +===== `LogstashGetPipelineResponse` + +[source,ts] +---- +type LogstashGetPipelineResponse = Record<<>, LogstashPipeline> +---- + diff --git a/docs/reference-logstash-put_pipeline.asciidoc b/docs/reference-logstash-put_pipeline.asciidoc new file mode 100644 index 000000000..d4f510249 --- /dev/null +++ b/docs/reference-logstash-put_pipeline.asciidoc @@ -0,0 +1,61 @@ +[[reference-logstash-put_pipeline]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.logstash.putPipeline + +Creates or updates a pipeline used for Logstash Central Management. + +{ref}/logstash-api-put-pipeline.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(LogstashPutPipelineRequest, options?): Promise +---- + +[discrete] +===== `LogstashPutPipelineRequest` + +[source,ts] +---- +interface LogstashPutPipelineRequest extends <> { + id: <> + pipeline?: LogstashPipeline +} +---- + +[discrete] +===== `LogstashPutPipelineResponse` + +[source,ts] +---- +type LogstashPutPipelineResponse = boolean +---- + diff --git a/docs/reference-main-index.asciidoc b/docs/reference-main-index.asciidoc new file mode 100644 index 000000000..c3ddb5c91 --- /dev/null +++ b/docs/reference-main-index.asciidoc @@ -0,0 +1,1004 @@ +[[reference-main-index]] += API reference + +include::reference-shared-types.asciidoc[] +include::reference-async_search-delete.asciidoc[] +include::reference-async_search-get.asciidoc[] +include::reference-async_search-status.asciidoc[] +include::reference-async_search-submit.asciidoc[] +include::reference-autoscaling-delete_autoscaling_policy.asciidoc[] +include::reference-autoscaling-get_autoscaling_capacity.asciidoc[] +include::reference-autoscaling-get_autoscaling_policy.asciidoc[] +include::reference-autoscaling-put_autoscaling_policy.asciidoc[] +include::reference-bulk.asciidoc[] +include::reference-cat-aliases.asciidoc[] +include::reference-cat-allocation.asciidoc[] +include::reference-cat-component_templates.asciidoc[] +include::reference-cat-count.asciidoc[] +include::reference-cat-fielddata.asciidoc[] +include::reference-cat-health.asciidoc[] +include::reference-cat-help.asciidoc[] +include::reference-cat-indices.asciidoc[] +include::reference-cat-master.asciidoc[] +include::reference-cat-ml_data_frame_analytics.asciidoc[] +include::reference-cat-ml_datafeeds.asciidoc[] +include::reference-cat-ml_jobs.asciidoc[] +include::reference-cat-ml_trained_models.asciidoc[] +include::reference-cat-nodeattrs.asciidoc[] +include::reference-cat-nodes.asciidoc[] +include::reference-cat-pending_tasks.asciidoc[] +include::reference-cat-plugins.asciidoc[] +include::reference-cat-recovery.asciidoc[] +include::reference-cat-repositories.asciidoc[] +include::reference-cat-segments.asciidoc[] +include::reference-cat-shards.asciidoc[] +include::reference-cat-snapshots.asciidoc[] +include::reference-cat-tasks.asciidoc[] +include::reference-cat-templates.asciidoc[] +include::reference-cat-thread_pool.asciidoc[] +include::reference-cat-transforms.asciidoc[] +include::reference-ccr-delete_auto_follow_pattern.asciidoc[] +include::reference-ccr-follow.asciidoc[] +include::reference-ccr-follow_info.asciidoc[] +include::reference-ccr-follow_stats.asciidoc[] +include::reference-ccr-forget_follower.asciidoc[] +include::reference-ccr-get_auto_follow_pattern.asciidoc[] +include::reference-ccr-pause_auto_follow_pattern.asciidoc[] +include::reference-ccr-pause_follow.asciidoc[] +include::reference-ccr-put_auto_follow_pattern.asciidoc[] +include::reference-ccr-resume_auto_follow_pattern.asciidoc[] +include::reference-ccr-resume_follow.asciidoc[] +include::reference-ccr-stats.asciidoc[] +include::reference-ccr-unfollow.asciidoc[] +include::reference-clear_scroll.asciidoc[] +include::reference-close_point_in_time.asciidoc[] +include::reference-cluster-allocation_explain.asciidoc[] +include::reference-cluster-delete_component_template.asciidoc[] +include::reference-cluster-delete_voting_config_exclusions.asciidoc[] +include::reference-cluster-exists_component_template.asciidoc[] +include::reference-cluster-get_component_template.asciidoc[] +include::reference-cluster-get_settings.asciidoc[] +include::reference-cluster-health.asciidoc[] +include::reference-cluster-info.asciidoc[] +include::reference-cluster-pending_tasks.asciidoc[] +include::reference-cluster-post_voting_config_exclusions.asciidoc[] +include::reference-cluster-put_component_template.asciidoc[] +include::reference-cluster-put_settings.asciidoc[] +include::reference-cluster-remote_info.asciidoc[] +include::reference-cluster-reroute.asciidoc[] +include::reference-cluster-state.asciidoc[] +include::reference-cluster-stats.asciidoc[] +include::reference-connector-check_in.asciidoc[] +include::reference-connector-delete.asciidoc[] +include::reference-connector-get.asciidoc[] +include::reference-connector-list.asciidoc[] +include::reference-connector-post.asciidoc[] +include::reference-connector-put.asciidoc[] +include::reference-connector-sync_job_cancel.asciidoc[] +include::reference-connector-sync_job_check_in.asciidoc[] +include::reference-connector-sync_job_claim.asciidoc[] +include::reference-connector-sync_job_delete.asciidoc[] +include::reference-connector-sync_job_error.asciidoc[] +include::reference-connector-sync_job_get.asciidoc[] +include::reference-connector-sync_job_list.asciidoc[] +include::reference-connector-sync_job_post.asciidoc[] +include::reference-connector-sync_job_update_stats.asciidoc[] +include::reference-connector-update_active_filtering.asciidoc[] +include::reference-connector-update_api_key_id.asciidoc[] +include::reference-connector-update_configuration.asciidoc[] +include::reference-connector-update_error.asciidoc[] +include::reference-connector-update_features.asciidoc[] +include::reference-connector-update_filtering.asciidoc[] +include::reference-connector-update_filtering_validation.asciidoc[] +include::reference-connector-update_index_name.asciidoc[] +include::reference-connector-update_name.asciidoc[] +include::reference-connector-update_native.asciidoc[] +include::reference-connector-update_pipeline.asciidoc[] +include::reference-connector-update_scheduling.asciidoc[] +include::reference-connector-update_service_type.asciidoc[] +include::reference-connector-update_status.asciidoc[] +include::reference-count.asciidoc[] +include::reference-create.asciidoc[] +include::reference-dangling_indices-delete_dangling_index.asciidoc[] +include::reference-dangling_indices-import_dangling_index.asciidoc[] +include::reference-dangling_indices-list_dangling_indices.asciidoc[] +include::reference-delete.asciidoc[] +include::reference-delete_by_query.asciidoc[] +include::reference-delete_by_query_rethrottle.asciidoc[] +include::reference-delete_script.asciidoc[] +include::reference-enrich-delete_policy.asciidoc[] +include::reference-enrich-execute_policy.asciidoc[] +include::reference-enrich-get_policy.asciidoc[] +include::reference-enrich-put_policy.asciidoc[] +include::reference-enrich-stats.asciidoc[] +include::reference-eql-delete.asciidoc[] +include::reference-eql-get.asciidoc[] +include::reference-eql-get_status.asciidoc[] +include::reference-eql-search.asciidoc[] +include::reference-esql-async_query.asciidoc[] +include::reference-esql-async_query_get.asciidoc[] +include::reference-esql-query.asciidoc[] +include::reference-exists.asciidoc[] +include::reference-exists_source.asciidoc[] +include::reference-explain.asciidoc[] +include::reference-features-get_features.asciidoc[] +include::reference-features-reset_features.asciidoc[] +include::reference-field_caps.asciidoc[] +include::reference-fleet-global_checkpoints.asciidoc[] +include::reference-fleet-msearch.asciidoc[] +include::reference-fleet-search.asciidoc[] +include::reference-get.asciidoc[] +include::reference-get_script.asciidoc[] +include::reference-get_script_context.asciidoc[] +include::reference-get_script_languages.asciidoc[] +include::reference-get_source.asciidoc[] +include::reference-graph-explore.asciidoc[] +include::reference-health_report.asciidoc[] +include::reference-ilm-delete_lifecycle.asciidoc[] +include::reference-ilm-explain_lifecycle.asciidoc[] +include::reference-ilm-get_lifecycle.asciidoc[] +include::reference-ilm-get_status.asciidoc[] +include::reference-ilm-migrate_to_data_tiers.asciidoc[] +include::reference-ilm-move_to_step.asciidoc[] +include::reference-ilm-put_lifecycle.asciidoc[] +include::reference-ilm-remove_policy.asciidoc[] +include::reference-ilm-retry.asciidoc[] +include::reference-ilm-start.asciidoc[] +include::reference-ilm-stop.asciidoc[] +include::reference-index.asciidoc[] +include::reference-indices-add_block.asciidoc[] +include::reference-indices-analyze.asciidoc[] +include::reference-indices-clear_cache.asciidoc[] +include::reference-indices-clone.asciidoc[] +include::reference-indices-close.asciidoc[] +include::reference-indices-create.asciidoc[] +include::reference-indices-create_data_stream.asciidoc[] +include::reference-indices-data_streams_stats.asciidoc[] +include::reference-indices-delete.asciidoc[] +include::reference-indices-delete_alias.asciidoc[] +include::reference-indices-delete_data_lifecycle.asciidoc[] +include::reference-indices-delete_data_stream.asciidoc[] +include::reference-indices-delete_index_template.asciidoc[] +include::reference-indices-delete_template.asciidoc[] +include::reference-indices-disk_usage.asciidoc[] +include::reference-indices-downsample.asciidoc[] +include::reference-indices-exists.asciidoc[] +include::reference-indices-exists_alias.asciidoc[] +include::reference-indices-exists_index_template.asciidoc[] +include::reference-indices-exists_template.asciidoc[] +include::reference-indices-explain_data_lifecycle.asciidoc[] +include::reference-indices-field_usage_stats.asciidoc[] +include::reference-indices-flush.asciidoc[] +include::reference-indices-forcemerge.asciidoc[] +include::reference-indices-get.asciidoc[] +include::reference-indices-get_alias.asciidoc[] +include::reference-indices-get_data_lifecycle.asciidoc[] +include::reference-indices-get_data_stream.asciidoc[] +include::reference-indices-get_field_mapping.asciidoc[] +include::reference-indices-get_index_template.asciidoc[] +include::reference-indices-get_mapping.asciidoc[] +include::reference-indices-get_settings.asciidoc[] +include::reference-indices-get_template.asciidoc[] +include::reference-indices-migrate_to_data_stream.asciidoc[] +include::reference-indices-modify_data_stream.asciidoc[] +include::reference-indices-open.asciidoc[] +include::reference-indices-promote_data_stream.asciidoc[] +include::reference-indices-put_alias.asciidoc[] +include::reference-indices-put_data_lifecycle.asciidoc[] +include::reference-indices-put_index_template.asciidoc[] +include::reference-indices-put_mapping.asciidoc[] +include::reference-indices-put_settings.asciidoc[] +include::reference-indices-put_template.asciidoc[] +include::reference-indices-recovery.asciidoc[] +include::reference-indices-refresh.asciidoc[] +include::reference-indices-reload_search_analyzers.asciidoc[] +include::reference-indices-resolve_cluster.asciidoc[] +include::reference-indices-resolve_index.asciidoc[] +include::reference-indices-rollover.asciidoc[] +include::reference-indices-segments.asciidoc[] +include::reference-indices-shard_stores.asciidoc[] +include::reference-indices-shrink.asciidoc[] +include::reference-indices-simulate_index_template.asciidoc[] +include::reference-indices-simulate_template.asciidoc[] +include::reference-indices-split.asciidoc[] +include::reference-indices-stats.asciidoc[] +include::reference-indices-unfreeze.asciidoc[] +include::reference-indices-update_aliases.asciidoc[] +include::reference-indices-validate_query.asciidoc[] +include::reference-inference-delete.asciidoc[] +include::reference-inference-get.asciidoc[] +include::reference-inference-inference.asciidoc[] +include::reference-inference-put.asciidoc[] +include::reference-inference-stream_inference.asciidoc[] +include::reference-info.asciidoc[] +include::reference-ingest-delete_geoip_database.asciidoc[] +include::reference-ingest-delete_pipeline.asciidoc[] +include::reference-ingest-geo_ip_stats.asciidoc[] +include::reference-ingest-get_geoip_database.asciidoc[] +include::reference-ingest-get_pipeline.asciidoc[] +include::reference-ingest-processor_grok.asciidoc[] +include::reference-ingest-put_geoip_database.asciidoc[] +include::reference-ingest-put_pipeline.asciidoc[] +include::reference-ingest-simulate.asciidoc[] +include::reference-knn_search.asciidoc[] +include::reference-license-delete.asciidoc[] +include::reference-license-get.asciidoc[] +include::reference-license-get_basic_status.asciidoc[] +include::reference-license-get_trial_status.asciidoc[] +include::reference-license-post.asciidoc[] +include::reference-license-post_start_basic.asciidoc[] +include::reference-license-post_start_trial.asciidoc[] +include::reference-logstash-delete_pipeline.asciidoc[] +include::reference-logstash-get_pipeline.asciidoc[] +include::reference-logstash-put_pipeline.asciidoc[] +include::reference-mget.asciidoc[] +include::reference-migration-deprecations.asciidoc[] +include::reference-migration-get_feature_upgrade_status.asciidoc[] +include::reference-migration-post_feature_upgrade.asciidoc[] +include::reference-ml-clear_trained_model_deployment_cache.asciidoc[] +include::reference-ml-close_job.asciidoc[] +include::reference-ml-delete_calendar.asciidoc[] +include::reference-ml-delete_calendar_event.asciidoc[] +include::reference-ml-delete_calendar_job.asciidoc[] +include::reference-ml-delete_data_frame_analytics.asciidoc[] +include::reference-ml-delete_datafeed.asciidoc[] +include::reference-ml-delete_expired_data.asciidoc[] +include::reference-ml-delete_filter.asciidoc[] +include::reference-ml-delete_forecast.asciidoc[] +include::reference-ml-delete_job.asciidoc[] +include::reference-ml-delete_model_snapshot.asciidoc[] +include::reference-ml-delete_trained_model.asciidoc[] +include::reference-ml-delete_trained_model_alias.asciidoc[] +include::reference-ml-estimate_model_memory.asciidoc[] +include::reference-ml-evaluate_data_frame.asciidoc[] +include::reference-ml-explain_data_frame_analytics.asciidoc[] +include::reference-ml-flush_job.asciidoc[] +include::reference-ml-forecast.asciidoc[] +include::reference-ml-get_buckets.asciidoc[] +include::reference-ml-get_calendar_events.asciidoc[] +include::reference-ml-get_calendars.asciidoc[] +include::reference-ml-get_categories.asciidoc[] +include::reference-ml-get_data_frame_analytics.asciidoc[] +include::reference-ml-get_data_frame_analytics_stats.asciidoc[] +include::reference-ml-get_datafeed_stats.asciidoc[] +include::reference-ml-get_datafeeds.asciidoc[] +include::reference-ml-get_filters.asciidoc[] +include::reference-ml-get_influencers.asciidoc[] +include::reference-ml-get_job_stats.asciidoc[] +include::reference-ml-get_jobs.asciidoc[] +include::reference-ml-get_memory_stats.asciidoc[] +include::reference-ml-get_model_snapshot_upgrade_stats.asciidoc[] +include::reference-ml-get_model_snapshots.asciidoc[] +include::reference-ml-get_overall_buckets.asciidoc[] +include::reference-ml-get_records.asciidoc[] +include::reference-ml-get_trained_models.asciidoc[] +include::reference-ml-get_trained_models_stats.asciidoc[] +include::reference-ml-infer_trained_model.asciidoc[] +include::reference-ml-info.asciidoc[] +include::reference-ml-open_job.asciidoc[] +include::reference-ml-post_calendar_events.asciidoc[] +include::reference-ml-post_data.asciidoc[] +include::reference-ml-preview_data_frame_analytics.asciidoc[] +include::reference-ml-preview_datafeed.asciidoc[] +include::reference-ml-put_calendar.asciidoc[] +include::reference-ml-put_calendar_job.asciidoc[] +include::reference-ml-put_data_frame_analytics.asciidoc[] +include::reference-ml-put_datafeed.asciidoc[] +include::reference-ml-put_filter.asciidoc[] +include::reference-ml-put_job.asciidoc[] +include::reference-ml-put_trained_model.asciidoc[] +include::reference-ml-put_trained_model_alias.asciidoc[] +include::reference-ml-put_trained_model_definition_part.asciidoc[] +include::reference-ml-put_trained_model_vocabulary.asciidoc[] +include::reference-ml-reset_job.asciidoc[] +include::reference-ml-revert_model_snapshot.asciidoc[] +include::reference-ml-set_upgrade_mode.asciidoc[] +include::reference-ml-start_data_frame_analytics.asciidoc[] +include::reference-ml-start_datafeed.asciidoc[] +include::reference-ml-start_trained_model_deployment.asciidoc[] +include::reference-ml-stop_data_frame_analytics.asciidoc[] +include::reference-ml-stop_datafeed.asciidoc[] +include::reference-ml-stop_trained_model_deployment.asciidoc[] +include::reference-ml-update_data_frame_analytics.asciidoc[] +include::reference-ml-update_datafeed.asciidoc[] +include::reference-ml-update_filter.asciidoc[] +include::reference-ml-update_job.asciidoc[] +include::reference-ml-update_model_snapshot.asciidoc[] +include::reference-ml-update_trained_model_deployment.asciidoc[] +include::reference-ml-upgrade_job_snapshot.asciidoc[] +include::reference-monitoring-bulk.asciidoc[] +include::reference-msearch.asciidoc[] +include::reference-msearch_template.asciidoc[] +include::reference-mtermvectors.asciidoc[] +include::reference-nodes-clear_repositories_metering_archive.asciidoc[] +include::reference-nodes-get_repositories_metering_info.asciidoc[] +include::reference-nodes-hot_threads.asciidoc[] +include::reference-nodes-info.asciidoc[] +include::reference-nodes-reload_secure_settings.asciidoc[] +include::reference-nodes-stats.asciidoc[] +include::reference-nodes-usage.asciidoc[] +include::reference-open_point_in_time.asciidoc[] +include::reference-ping.asciidoc[] +include::reference-put_script.asciidoc[] +include::reference-query_rules-delete_rule.asciidoc[] +include::reference-query_rules-delete_ruleset.asciidoc[] +include::reference-query_rules-get_rule.asciidoc[] +include::reference-query_rules-get_ruleset.asciidoc[] +include::reference-query_rules-list_rulesets.asciidoc[] +include::reference-query_rules-put_rule.asciidoc[] +include::reference-query_rules-put_ruleset.asciidoc[] +include::reference-query_rules-test.asciidoc[] +include::reference-rank_eval.asciidoc[] +include::reference-reindex.asciidoc[] +include::reference-reindex_rethrottle.asciidoc[] +include::reference-render_search_template.asciidoc[] +include::reference-rollup-delete_job.asciidoc[] +include::reference-rollup-get_jobs.asciidoc[] +include::reference-rollup-get_rollup_caps.asciidoc[] +include::reference-rollup-get_rollup_index_caps.asciidoc[] +include::reference-rollup-put_job.asciidoc[] +include::reference-rollup-rollup_search.asciidoc[] +include::reference-rollup-start_job.asciidoc[] +include::reference-rollup-stop_job.asciidoc[] +include::reference-scripts_painless_execute.asciidoc[] +include::reference-scroll.asciidoc[] +include::reference-search.asciidoc[] +include::reference-search_application-delete.asciidoc[] +include::reference-search_application-delete_behavioral_analytics.asciidoc[] +include::reference-search_application-get.asciidoc[] +include::reference-search_application-get_behavioral_analytics.asciidoc[] +include::reference-search_application-list.asciidoc[] +include::reference-search_application-post_behavioral_analytics_event.asciidoc[] +include::reference-search_application-put.asciidoc[] +include::reference-search_application-put_behavioral_analytics.asciidoc[] +include::reference-search_application-render_query.asciidoc[] +include::reference-search_application-search.asciidoc[] +include::reference-search_mvt.asciidoc[] +include::reference-search_shards.asciidoc[] +include::reference-search_template.asciidoc[] +include::reference-searchable_snapshots-cache_stats.asciidoc[] +include::reference-searchable_snapshots-clear_cache.asciidoc[] +include::reference-searchable_snapshots-mount.asciidoc[] +include::reference-searchable_snapshots-stats.asciidoc[] +include::reference-security-activate_user_profile.asciidoc[] +include::reference-security-authenticate.asciidoc[] +include::reference-security-bulk_delete_role.asciidoc[] +include::reference-security-bulk_put_role.asciidoc[] +include::reference-security-bulk_update_api_keys.asciidoc[] +include::reference-security-change_password.asciidoc[] +include::reference-security-clear_api_key_cache.asciidoc[] +include::reference-security-clear_cached_privileges.asciidoc[] +include::reference-security-clear_cached_realms.asciidoc[] +include::reference-security-clear_cached_roles.asciidoc[] +include::reference-security-clear_cached_service_tokens.asciidoc[] +include::reference-security-create_api_key.asciidoc[] +include::reference-security-create_cross_cluster_api_key.asciidoc[] +include::reference-security-create_service_token.asciidoc[] +include::reference-security-delete_privileges.asciidoc[] +include::reference-security-delete_role.asciidoc[] +include::reference-security-delete_role_mapping.asciidoc[] +include::reference-security-delete_service_token.asciidoc[] +include::reference-security-delete_user.asciidoc[] +include::reference-security-disable_user.asciidoc[] +include::reference-security-disable_user_profile.asciidoc[] +include::reference-security-enable_user.asciidoc[] +include::reference-security-enable_user_profile.asciidoc[] +include::reference-security-enroll_kibana.asciidoc[] +include::reference-security-enroll_node.asciidoc[] +include::reference-security-get_api_key.asciidoc[] +include::reference-security-get_builtin_privileges.asciidoc[] +include::reference-security-get_privileges.asciidoc[] +include::reference-security-get_role.asciidoc[] +include::reference-security-get_role_mapping.asciidoc[] +include::reference-security-get_service_accounts.asciidoc[] +include::reference-security-get_service_credentials.asciidoc[] +include::reference-security-get_settings.asciidoc[] +include::reference-security-get_token.asciidoc[] +include::reference-security-get_user.asciidoc[] +include::reference-security-get_user_privileges.asciidoc[] +include::reference-security-get_user_profile.asciidoc[] +include::reference-security-grant_api_key.asciidoc[] +include::reference-security-has_privileges.asciidoc[] +include::reference-security-has_privileges_user_profile.asciidoc[] +include::reference-security-invalidate_api_key.asciidoc[] +include::reference-security-invalidate_token.asciidoc[] +include::reference-security-oidc_authenticate.asciidoc[] +include::reference-security-oidc_logout.asciidoc[] +include::reference-security-oidc_prepare_authentication.asciidoc[] +include::reference-security-put_privileges.asciidoc[] +include::reference-security-put_role.asciidoc[] +include::reference-security-put_role_mapping.asciidoc[] +include::reference-security-put_user.asciidoc[] +include::reference-security-query_api_keys.asciidoc[] +include::reference-security-query_role.asciidoc[] +include::reference-security-query_user.asciidoc[] +include::reference-security-saml_authenticate.asciidoc[] +include::reference-security-saml_complete_logout.asciidoc[] +include::reference-security-saml_invalidate.asciidoc[] +include::reference-security-saml_logout.asciidoc[] +include::reference-security-saml_prepare_authentication.asciidoc[] +include::reference-security-saml_service_provider_metadata.asciidoc[] +include::reference-security-suggest_user_profiles.asciidoc[] +include::reference-security-update_api_key.asciidoc[] +include::reference-security-update_cross_cluster_api_key.asciidoc[] +include::reference-security-update_settings.asciidoc[] +include::reference-security-update_user_profile_data.asciidoc[] +include::reference-shutdown-delete_node.asciidoc[] +include::reference-shutdown-get_node.asciidoc[] +include::reference-shutdown-put_node.asciidoc[] +include::reference-simulate-ingest.asciidoc[] +include::reference-slm-delete_lifecycle.asciidoc[] +include::reference-slm-execute_lifecycle.asciidoc[] +include::reference-slm-execute_retention.asciidoc[] +include::reference-slm-get_lifecycle.asciidoc[] +include::reference-slm-get_stats.asciidoc[] +include::reference-slm-get_status.asciidoc[] +include::reference-slm-put_lifecycle.asciidoc[] +include::reference-slm-start.asciidoc[] +include::reference-slm-stop.asciidoc[] +include::reference-snapshot-cleanup_repository.asciidoc[] +include::reference-snapshot-clone.asciidoc[] +include::reference-snapshot-create.asciidoc[] +include::reference-snapshot-create_repository.asciidoc[] +include::reference-snapshot-delete.asciidoc[] +include::reference-snapshot-delete_repository.asciidoc[] +include::reference-snapshot-get.asciidoc[] +include::reference-snapshot-get_repository.asciidoc[] +include::reference-snapshot-repository_analyze.asciidoc[] +include::reference-snapshot-restore.asciidoc[] +include::reference-snapshot-status.asciidoc[] +include::reference-snapshot-verify_repository.asciidoc[] +include::reference-sql-clear_cursor.asciidoc[] +include::reference-sql-delete_async.asciidoc[] +include::reference-sql-get_async.asciidoc[] +include::reference-sql-get_async_status.asciidoc[] +include::reference-sql-query.asciidoc[] +include::reference-sql-translate.asciidoc[] +include::reference-ssl-certificates.asciidoc[] +include::reference-synonyms-delete_synonym.asciidoc[] +include::reference-synonyms-delete_synonym_rule.asciidoc[] +include::reference-synonyms-get_synonym.asciidoc[] +include::reference-synonyms-get_synonym_rule.asciidoc[] +include::reference-synonyms-get_synonyms_sets.asciidoc[] +include::reference-synonyms-put_synonym.asciidoc[] +include::reference-synonyms-put_synonym_rule.asciidoc[] +include::reference-tasks-cancel.asciidoc[] +include::reference-tasks-get.asciidoc[] +include::reference-tasks-list.asciidoc[] +include::reference-terms_enum.asciidoc[] +include::reference-termvectors.asciidoc[] +include::reference-text_structure-find_field_structure.asciidoc[] +include::reference-text_structure-find_message_structure.asciidoc[] +include::reference-text_structure-find_structure.asciidoc[] +include::reference-text_structure-test_grok_pattern.asciidoc[] +include::reference-transform-delete_transform.asciidoc[] +include::reference-transform-get_node_stats.asciidoc[] +include::reference-transform-get_transform.asciidoc[] +include::reference-transform-get_transform_stats.asciidoc[] +include::reference-transform-preview_transform.asciidoc[] +include::reference-transform-put_transform.asciidoc[] +include::reference-transform-reset_transform.asciidoc[] +include::reference-transform-schedule_now_transform.asciidoc[] +include::reference-transform-start_transform.asciidoc[] +include::reference-transform-stop_transform.asciidoc[] +include::reference-transform-update_transform.asciidoc[] +include::reference-transform-upgrade_transforms.asciidoc[] +include::reference-update.asciidoc[] +include::reference-update_by_query.asciidoc[] +include::reference-update_by_query_rethrottle.asciidoc[] +include::reference-watcher-ack_watch.asciidoc[] +include::reference-watcher-activate_watch.asciidoc[] +include::reference-watcher-deactivate_watch.asciidoc[] +include::reference-watcher-delete_watch.asciidoc[] +include::reference-watcher-execute_watch.asciidoc[] +include::reference-watcher-get_settings.asciidoc[] +include::reference-watcher-get_watch.asciidoc[] +include::reference-watcher-put_watch.asciidoc[] +include::reference-watcher-query_watches.asciidoc[] +include::reference-watcher-start.asciidoc[] +include::reference-watcher-stats.asciidoc[] +include::reference-watcher-stop.asciidoc[] +include::reference-watcher-update_settings.asciidoc[] +include::reference-xpack-info.asciidoc[] +include::reference-xpack-usage.asciidoc[] + + +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> +<> diff --git a/docs/reference-mget.asciidoc b/docs/reference-mget.asciidoc new file mode 100644 index 000000000..a60c7cfce --- /dev/null +++ b/docs/reference-mget.asciidoc @@ -0,0 +1,73 @@ +[[reference-mget]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.mget + +Get multiple documents. Get multiple JSON documents by ID from one or more indices. If you specify an index in the request URI, you only need to specify the document IDs in the request body. To ensure fast responses, this multi get (mget) API responds with partial results if one or more shards fail. + +{ref}/docs-multi-get.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MgetRequest, options?): Promise +---- + +[discrete] +===== `MgetRequest` + +[source,ts] +---- +interface MgetRequest extends <> { + index?: <> + force_synthetic_source?: boolean + preference?: string + realtime?: boolean + refresh?: boolean + routing?: <> + _source?: SearchSourceConfigParam + _source_excludes?: <> + _source_includes?: <> + stored_fields?: <> + docs?: MgetOperation[] + ids?: <> +} +---- + +[discrete] +===== `MgetResponse` + +[source,ts] +---- +interface MgetResponse { + docs: MgetResponseItem[] +} +---- + diff --git a/docs/reference-migration-deprecations.asciidoc b/docs/reference-migration-deprecations.asciidoc new file mode 100644 index 000000000..106e34fed --- /dev/null +++ b/docs/reference-migration-deprecations.asciidoc @@ -0,0 +1,65 @@ +[[reference-migration-deprecations]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.migration.deprecations + +Retrieves information about different cluster, node, and index level settings that use deprecated features that will be removed or changed in the next major version. + +{ref}/migration-api-deprecation.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MigrationDeprecationsRequest, options?): Promise +---- + +[discrete] +===== `MigrationDeprecationsRequest` + +[source,ts] +---- +interface MigrationDeprecationsRequest extends <> { + index?: <> +} +---- + +[discrete] +===== `MigrationDeprecationsResponse` + +[source,ts] +---- +interface MigrationDeprecationsResponse { + cluster_settings: MigrationDeprecationsDeprecation[] + index_settings: Record + node_settings: MigrationDeprecationsDeprecation[] + ml_settings: MigrationDeprecationsDeprecation[] +} +---- + diff --git a/docs/reference-migration-get_feature_upgrade_status.asciidoc b/docs/reference-migration-get_feature_upgrade_status.asciidoc new file mode 100644 index 000000000..ef53d79ea --- /dev/null +++ b/docs/reference-migration-get_feature_upgrade_status.asciidoc @@ -0,0 +1,62 @@ +[[reference-migration-get_feature_upgrade_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.migration.getFeatureUpgradeStatus + +Find out whether system features need to be upgraded or not + +{ref}/migration-api-feature-upgrade.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MigrationGetFeatureUpgradeStatusRequest, options?): Promise +---- + +[discrete] +===== `MigrationGetFeatureUpgradeStatusRequest` + +[source,ts] +---- +interface MigrationGetFeatureUpgradeStatusRequest extends <> { +} +---- + +[discrete] +===== `MigrationGetFeatureUpgradeStatusResponse` + +[source,ts] +---- +interface MigrationGetFeatureUpgradeStatusResponse { + features: MigrationGetFeatureUpgradeStatusMigrationFeature[] + migration_status: MigrationGetFeatureUpgradeStatusMigrationStatus +} +---- + diff --git a/docs/reference-migration-post_feature_upgrade.asciidoc b/docs/reference-migration-post_feature_upgrade.asciidoc new file mode 100644 index 000000000..3a2124f31 --- /dev/null +++ b/docs/reference-migration-post_feature_upgrade.asciidoc @@ -0,0 +1,62 @@ +[[reference-migration-post_feature_upgrade]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.migration.postFeatureUpgrade + +Begin upgrades for system features + +{ref}/migration-api-feature-upgrade.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MigrationPostFeatureUpgradeRequest, options?): Promise +---- + +[discrete] +===== `MigrationPostFeatureUpgradeRequest` + +[source,ts] +---- +interface MigrationPostFeatureUpgradeRequest extends <> { +} +---- + +[discrete] +===== `MigrationPostFeatureUpgradeResponse` + +[source,ts] +---- +interface MigrationPostFeatureUpgradeResponse { + accepted: boolean + features: MigrationPostFeatureUpgradeMigrationFeature[] +} +---- + diff --git a/docs/reference-ml-clear_trained_model_deployment_cache.asciidoc b/docs/reference-ml-clear_trained_model_deployment_cache.asciidoc new file mode 100644 index 000000000..84926e56a --- /dev/null +++ b/docs/reference-ml-clear_trained_model_deployment_cache.asciidoc @@ -0,0 +1,62 @@ +[[reference-ml-clear_trained_model_deployment_cache]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.clearTrainedModelDeploymentCache + +Clear trained model deployment cache. Cache will be cleared on all nodes where the trained model is assigned. A trained model deployment may have an inference cache enabled. As requests are handled by each allocated node, their responses may be cached on that individual node. Calling this API clears the caches without restarting the deployment. + +{ref}/clear-trained-model-deployment-cache.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlClearTrainedModelDeploymentCacheRequest, options?): Promise +---- + +[discrete] +===== `MlClearTrainedModelDeploymentCacheRequest` + +[source,ts] +---- +interface MlClearTrainedModelDeploymentCacheRequest extends <> { + model_id: <> +} +---- + +[discrete] +===== `MlClearTrainedModelDeploymentCacheResponse` + +[source,ts] +---- +interface MlClearTrainedModelDeploymentCacheResponse { + cleared: boolean +} +---- + diff --git a/docs/reference-ml-close_job.asciidoc b/docs/reference-ml-close_job.asciidoc new file mode 100644 index 000000000..de16526f2 --- /dev/null +++ b/docs/reference-ml-close_job.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-close_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.closeJob + +Close anomaly detection jobs. A job can be opened and closed multiple times throughout its lifecycle. A closed job cannot receive data or perform analysis operations, but you can still explore and navigate results. When you close a job, it runs housekeeping tasks such as pruning the model history, flushing buffers, calculating final results and persisting the model snapshots. Depending upon the size of the job, it could take several minutes to close and the equivalent time to re-open. After it is closed, the job has a minimal overhead on the cluster except for maintaining its meta data. Therefore it is a best practice to close jobs that are no longer required to process data. If you close an anomaly detection job whose datafeed is running, the request first tries to stop the datafeed. This behavior is equivalent to calling stop datafeed API with the same timeout and force parameters as the close job request. When a datafeed that has a specified end date stops, it automatically closes its associated job. + +{ref}/ml-close-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlCloseJobRequest, options?): Promise +---- + +[discrete] +===== `MlCloseJobRequest` + +[source,ts] +---- +interface MlCloseJobRequest extends <> { + job_id: <> + allow_no_match?: boolean + force?: boolean + timeout?: <> +} +---- + +[discrete] +===== `MlCloseJobResponse` + +[source,ts] +---- +interface MlCloseJobResponse { + closed: boolean +} +---- + diff --git a/docs/reference-ml-delete_calendar.asciidoc b/docs/reference-ml-delete_calendar.asciidoc new file mode 100644 index 000000000..d34bc3d20 --- /dev/null +++ b/docs/reference-ml-delete_calendar.asciidoc @@ -0,0 +1,60 @@ +[[reference-ml-delete_calendar]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteCalendar + +Delete a calendar. Removes all scheduled events from a calendar, then deletes it. + +{ref}/ml-delete-calendar.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteCalendarRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteCalendarRequest` + +[source,ts] +---- +interface MlDeleteCalendarRequest extends <> { + calendar_id: <> +} +---- + +[discrete] +===== `MlDeleteCalendarResponse` + +[source,ts] +---- +type MlDeleteCalendarResponse = <> +---- + diff --git a/docs/reference-ml-delete_calendar_event.asciidoc b/docs/reference-ml-delete_calendar_event.asciidoc new file mode 100644 index 000000000..f61df27fd --- /dev/null +++ b/docs/reference-ml-delete_calendar_event.asciidoc @@ -0,0 +1,61 @@ +[[reference-ml-delete_calendar_event]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteCalendarEvent + +Delete events from a calendar. + +{ref}/ml-delete-calendar-event.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteCalendarEventRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteCalendarEventRequest` + +[source,ts] +---- +interface MlDeleteCalendarEventRequest extends <> { + calendar_id: <> + event_id: <> +} +---- + +[discrete] +===== `MlDeleteCalendarEventResponse` + +[source,ts] +---- +type MlDeleteCalendarEventResponse = <> +---- + diff --git a/docs/reference-ml-delete_calendar_job.asciidoc b/docs/reference-ml-delete_calendar_job.asciidoc new file mode 100644 index 000000000..5b8dba08d --- /dev/null +++ b/docs/reference-ml-delete_calendar_job.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-delete_calendar_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteCalendarJob + +Delete anomaly jobs from a calendar. + +{ref}/ml-delete-calendar-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteCalendarJobRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteCalendarJobRequest` + +[source,ts] +---- +interface MlDeleteCalendarJobRequest extends <> { + calendar_id: <> + job_id: <> +} +---- + +[discrete] +===== `MlDeleteCalendarJobResponse` + +[source,ts] +---- +interface MlDeleteCalendarJobResponse { + calendar_id: <> + description?: string + job_ids: <> +} +---- + diff --git a/docs/reference-ml-delete_data_frame_analytics.asciidoc b/docs/reference-ml-delete_data_frame_analytics.asciidoc new file mode 100644 index 000000000..7d16b5eb5 --- /dev/null +++ b/docs/reference-ml-delete_data_frame_analytics.asciidoc @@ -0,0 +1,62 @@ +[[reference-ml-delete_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteDataFrameAnalytics + +Delete a data frame analytics job. + +{ref}/delete-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlDeleteDataFrameAnalyticsRequest extends <> { + id: <> + force?: boolean + timeout?: <> +} +---- + +[discrete] +===== `MlDeleteDataFrameAnalyticsResponse` + +[source,ts] +---- +type MlDeleteDataFrameAnalyticsResponse = <> +---- + diff --git a/docs/reference-ml-delete_datafeed.asciidoc b/docs/reference-ml-delete_datafeed.asciidoc new file mode 100644 index 000000000..afd67bf7a --- /dev/null +++ b/docs/reference-ml-delete_datafeed.asciidoc @@ -0,0 +1,61 @@ +[[reference-ml-delete_datafeed]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteDatafeed + +Delete a datafeed. + +{ref}/ml-delete-datafeed.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteDatafeedRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteDatafeedRequest` + +[source,ts] +---- +interface MlDeleteDatafeedRequest extends <> { + datafeed_id: <> + force?: boolean +} +---- + +[discrete] +===== `MlDeleteDatafeedResponse` + +[source,ts] +---- +type MlDeleteDatafeedResponse = <> +---- + diff --git a/docs/reference-ml-delete_expired_data.asciidoc b/docs/reference-ml-delete_expired_data.asciidoc new file mode 100644 index 000000000..c6c86799c --- /dev/null +++ b/docs/reference-ml-delete_expired_data.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-delete_expired_data]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteExpiredData + +Delete expired ML data. Deletes all job results, model snapshots and forecast data that have exceeded their retention days period. Machine learning state documents that are not associated with any job are also deleted. You can limit the request to a single or set of anomaly detection jobs by using a job identifier, a group name, a comma-separated list of jobs, or a wildcard expression. You can delete expired data for all anomaly detection jobs by using _all, by specifying * as the , or by omitting the . + +{ref}/ml-delete-expired-data.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteExpiredDataRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteExpiredDataRequest` + +[source,ts] +---- +interface MlDeleteExpiredDataRequest extends <> { + job_id?: <> + requests_per_second?: <> + timeout?: <> +} +---- + +[discrete] +===== `MlDeleteExpiredDataResponse` + +[source,ts] +---- +interface MlDeleteExpiredDataResponse { + deleted: boolean +} +---- + diff --git a/docs/reference-ml-delete_filter.asciidoc b/docs/reference-ml-delete_filter.asciidoc new file mode 100644 index 000000000..3feabc61b --- /dev/null +++ b/docs/reference-ml-delete_filter.asciidoc @@ -0,0 +1,60 @@ +[[reference-ml-delete_filter]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteFilter + +Delete a filter. If an anomaly detection job references the filter, you cannot delete the filter. You must update or delete the job before you can delete the filter. + +{ref}/ml-delete-filter.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteFilterRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteFilterRequest` + +[source,ts] +---- +interface MlDeleteFilterRequest extends <> { + filter_id: <> +} +---- + +[discrete] +===== `MlDeleteFilterResponse` + +[source,ts] +---- +type MlDeleteFilterResponse = <> +---- + diff --git a/docs/reference-ml-delete_forecast.asciidoc b/docs/reference-ml-delete_forecast.asciidoc new file mode 100644 index 000000000..65ef02743 --- /dev/null +++ b/docs/reference-ml-delete_forecast.asciidoc @@ -0,0 +1,63 @@ +[[reference-ml-delete_forecast]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteForecast + +Delete forecasts from a job. By default, forecasts are retained for 14 days. You can specify a different retention period with the `expires_in` parameter in the forecast jobs API. The delete forecast API enables you to delete one or more forecasts before they expire. + +{ref}/ml-delete-forecast.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteForecastRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteForecastRequest` + +[source,ts] +---- +interface MlDeleteForecastRequest extends <> { + job_id: <> + forecast_id?: <> + allow_no_forecasts?: boolean + timeout?: <> +} +---- + +[discrete] +===== `MlDeleteForecastResponse` + +[source,ts] +---- +type MlDeleteForecastResponse = <> +---- + diff --git a/docs/reference-ml-delete_job.asciidoc b/docs/reference-ml-delete_job.asciidoc new file mode 100644 index 000000000..6d6305b7a --- /dev/null +++ b/docs/reference-ml-delete_job.asciidoc @@ -0,0 +1,63 @@ +[[reference-ml-delete_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteJob + +Delete an anomaly detection job. All job configuration, model state and results are deleted. It is not currently possible to delete multiple jobs using wildcards or a comma separated list. If you delete a job that has a datafeed, the request first tries to delete the datafeed. This behavior is equivalent to calling the delete datafeed API with the same timeout and force parameters as the delete job request. + +{ref}/ml-delete-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteJobRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteJobRequest` + +[source,ts] +---- +interface MlDeleteJobRequest extends <> { + job_id: <> + force?: boolean + delete_user_annotations?: boolean + wait_for_completion?: boolean +} +---- + +[discrete] +===== `MlDeleteJobResponse` + +[source,ts] +---- +type MlDeleteJobResponse = <> +---- + diff --git a/docs/reference-ml-delete_model_snapshot.asciidoc b/docs/reference-ml-delete_model_snapshot.asciidoc new file mode 100644 index 000000000..a24cda942 --- /dev/null +++ b/docs/reference-ml-delete_model_snapshot.asciidoc @@ -0,0 +1,61 @@ +[[reference-ml-delete_model_snapshot]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteModelSnapshot + +Delete a model snapshot. You cannot delete the active model snapshot. To delete that snapshot, first revert to a different one. To identify the active model snapshot, refer to the `model_snapshot_id` in the results from the get jobs API. + +{ref}/ml-delete-snapshot.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteModelSnapshotRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteModelSnapshotRequest` + +[source,ts] +---- +interface MlDeleteModelSnapshotRequest extends <> { + job_id: <> + snapshot_id: <> +} +---- + +[discrete] +===== `MlDeleteModelSnapshotResponse` + +[source,ts] +---- +type MlDeleteModelSnapshotResponse = <> +---- + diff --git a/docs/reference-ml-delete_trained_model.asciidoc b/docs/reference-ml-delete_trained_model.asciidoc new file mode 100644 index 000000000..8608c6b75 --- /dev/null +++ b/docs/reference-ml-delete_trained_model.asciidoc @@ -0,0 +1,61 @@ +[[reference-ml-delete_trained_model]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteTrainedModel + +Delete an unreferenced trained model. The request deletes a trained inference model that is not referenced by an ingest pipeline. + +{ref}/delete-trained-models.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteTrainedModelRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteTrainedModelRequest` + +[source,ts] +---- +interface MlDeleteTrainedModelRequest extends <> { + model_id: <> + force?: boolean +} +---- + +[discrete] +===== `MlDeleteTrainedModelResponse` + +[source,ts] +---- +type MlDeleteTrainedModelResponse = <> +---- + diff --git a/docs/reference-ml-delete_trained_model_alias.asciidoc b/docs/reference-ml-delete_trained_model_alias.asciidoc new file mode 100644 index 000000000..1256897e3 --- /dev/null +++ b/docs/reference-ml-delete_trained_model_alias.asciidoc @@ -0,0 +1,61 @@ +[[reference-ml-delete_trained_model_alias]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.deleteTrainedModelAlias + +Delete a trained model alias. This API deletes an existing model alias that refers to a trained model. If the model alias is missing or refers to a model other than the one identified by the `model_id`, this API returns an error. + +{ref}/delete-trained-models-aliases.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlDeleteTrainedModelAliasRequest, options?): Promise +---- + +[discrete] +===== `MlDeleteTrainedModelAliasRequest` + +[source,ts] +---- +interface MlDeleteTrainedModelAliasRequest extends <> { + model_alias: <> + model_id: <> +} +---- + +[discrete] +===== `MlDeleteTrainedModelAliasResponse` + +[source,ts] +---- +type MlDeleteTrainedModelAliasResponse = <> +---- + diff --git a/docs/reference-ml-estimate_model_memory.asciidoc b/docs/reference-ml-estimate_model_memory.asciidoc new file mode 100644 index 000000000..6be238f1f --- /dev/null +++ b/docs/reference-ml-estimate_model_memory.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-estimate_model_memory]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.estimateModelMemory + +Estimate job model memory usage. Makes an estimation of the memory usage for an anomaly detection job model. It is based on analysis configuration details for the job and cardinality estimates for the fields it references. + +{ref}/ml-apis.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlEstimateModelMemoryRequest, options?): Promise +---- + +[discrete] +===== `MlEstimateModelMemoryRequest` + +[source,ts] +---- +interface MlEstimateModelMemoryRequest extends <> { + analysis_config?: MlAnalysisConfig + max_bucket_cardinality?: Record<<>, <>> + overall_cardinality?: Record<<>, <>> +} +---- + +[discrete] +===== `MlEstimateModelMemoryResponse` + +[source,ts] +---- +interface MlEstimateModelMemoryResponse { + model_memory_estimate: string +} +---- + diff --git a/docs/reference-ml-evaluate_data_frame.asciidoc b/docs/reference-ml-evaluate_data_frame.asciidoc new file mode 100644 index 000000000..b53b2c0b6 --- /dev/null +++ b/docs/reference-ml-evaluate_data_frame.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-evaluate_data_frame]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.evaluateDataFrame + +Evaluate data frame analytics. The API packages together commonly used evaluation metrics for various types of machine learning features. This has been designed for use on indexes created by data frame analytics. Evaluation requires both a ground truth field and an analytics result field to be present. + +{ref}/evaluate-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlEvaluateDataFrameRequest, options?): Promise +---- + +[discrete] +===== `MlEvaluateDataFrameRequest` + +[source,ts] +---- +interface MlEvaluateDataFrameRequest extends <> { + evaluation: MlDataframeEvaluationContainer + index: <> + query?: QueryDslQueryContainer +} +---- + +[discrete] +===== `MlEvaluateDataFrameResponse` + +[source,ts] +---- +interface MlEvaluateDataFrameResponse { + classification?: MlEvaluateDataFrameDataframeClassificationSummary + outlier_detection?: MlEvaluateDataFrameDataframeOutlierDetectionSummary + regression?: MlEvaluateDataFrameDataframeRegressionSummary +} +---- + diff --git a/docs/reference-ml-explain_data_frame_analytics.asciidoc b/docs/reference-ml-explain_data_frame_analytics.asciidoc new file mode 100644 index 000000000..27e616595 --- /dev/null +++ b/docs/reference-ml-explain_data_frame_analytics.asciidoc @@ -0,0 +1,71 @@ +[[reference-ml-explain_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.explainDataFrameAnalytics + +Explain data frame analytics config. This API provides explanations for a data frame analytics config that either exists already or one that has not been created yet. The following explanations are provided: * which fields are included or not in the analysis and why, * how much memory is estimated to be required. The estimate can be used when deciding the appropriate value for model_memory_limit setting later on. If you have object fields or fields that are excluded via source filtering, they are not included in the explanation. + +{ref}/explain-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlExplainDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlExplainDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlExplainDataFrameAnalyticsRequest extends <> { + id?: <> + source?: MlDataframeAnalyticsSource + dest?: MlDataframeAnalyticsDestination + analysis?: MlDataframeAnalysisContainer + description?: string + model_memory_limit?: string + max_num_threads?: <> + analyzed_fields?: MlDataframeAnalysisAnalyzedFields | string[] + allow_lazy_start?: boolean +} +---- + +[discrete] +===== `MlExplainDataFrameAnalyticsResponse` + +[source,ts] +---- +interface MlExplainDataFrameAnalyticsResponse { + field_selection: MlDataframeAnalyticsFieldSelection[] + memory_estimation: MlDataframeAnalyticsMemoryEstimation +} +---- + diff --git a/docs/reference-ml-flush_job.asciidoc b/docs/reference-ml-flush_job.asciidoc new file mode 100644 index 000000000..c4cda17fa --- /dev/null +++ b/docs/reference-ml-flush_job.asciidoc @@ -0,0 +1,68 @@ +[[reference-ml-flush_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.flushJob + +Force buffered data to be processed. The flush jobs API is only applicable when sending data for analysis using the post data API. Depending on the content of the buffer, then it might additionally calculate new results. Both flush and close operations are similar, however the flush is more efficient if you are expecting to send more data for analysis. When flushing, the job remains open and is available to continue analyzing data. A close operation additionally prunes and persists the model state to disk and the job must be opened again before analyzing further data. + +{ref}/ml-flush-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlFlushJobRequest, options?): Promise +---- + +[discrete] +===== `MlFlushJobRequest` + +[source,ts] +---- +interface MlFlushJobRequest extends <> { + job_id: <> + advance_time?: <> + calc_interim?: boolean + end?: <> + skip_time?: <> + start?: <> +} +---- + +[discrete] +===== `MlFlushJobResponse` + +[source,ts] +---- +interface MlFlushJobResponse { + flushed: boolean + last_finalized_bucket_end?: <> +} +---- + diff --git a/docs/reference-ml-forecast.asciidoc b/docs/reference-ml-forecast.asciidoc new file mode 100644 index 000000000..a225cabea --- /dev/null +++ b/docs/reference-ml-forecast.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-forecast]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.forecast + +Predict future behavior of a time series. Forecasts are not supported for jobs that perform population analysis; an error occurs if you try to create a forecast for a job that has an `over_field_name` in its configuration. Forcasts predict future behavior based on historical data. + +{ref}/ml-forecast.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlForecastRequest, options?): Promise +---- + +[discrete] +===== `MlForecastRequest` + +[source,ts] +---- +interface MlForecastRequest extends <> { + job_id: <> + duration?: <> + expires_in?: <> + max_model_memory?: string +} +---- + +[discrete] +===== `MlForecastResponse` + +[source,ts] +---- +interface MlForecastResponse { + acknowledged: boolean + forecast_id: <> +} +---- + diff --git a/docs/reference-ml-get_buckets.asciidoc b/docs/reference-ml-get_buckets.asciidoc new file mode 100644 index 000000000..ad5203ee7 --- /dev/null +++ b/docs/reference-ml-get_buckets.asciidoc @@ -0,0 +1,74 @@ +[[reference-ml-get_buckets]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getBuckets + +Get anomaly detection job results for buckets. The API presents a chronological view of the records, grouped by bucket. + +{ref}/ml-get-bucket.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetBucketsRequest, options?): Promise +---- + +[discrete] +===== `MlGetBucketsRequest` + +[source,ts] +---- +interface MlGetBucketsRequest extends <> { + job_id: <> + timestamp?: <> + from?: <> + size?: <> + anomaly_score?: <> + desc?: boolean + end?: <> + exclude_interim?: boolean + expand?: boolean + page?: MlPage + sort?: <> + start?: <> +} +---- + +[discrete] +===== `MlGetBucketsResponse` + +[source,ts] +---- +interface MlGetBucketsResponse { + buckets: MlBucketSummary[] + count: <> +} +---- + diff --git a/docs/reference-ml-get_calendar_events.asciidoc b/docs/reference-ml-get_calendar_events.asciidoc new file mode 100644 index 000000000..6653c89cf --- /dev/null +++ b/docs/reference-ml-get_calendar_events.asciidoc @@ -0,0 +1,68 @@ +[[reference-ml-get_calendar_events]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getCalendarEvents + +Get info about events in calendars. + +{ref}/ml-get-calendar-event.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetCalendarEventsRequest, options?): Promise +---- + +[discrete] +===== `MlGetCalendarEventsRequest` + +[source,ts] +---- +interface MlGetCalendarEventsRequest extends <> { + calendar_id: <> + end?: <> + from?: <> + job_id?: <> + size?: <> + start?: <> +} +---- + +[discrete] +===== `MlGetCalendarEventsResponse` + +[source,ts] +---- +interface MlGetCalendarEventsResponse { + count: <> + events: MlCalendarEvent[] +} +---- + diff --git a/docs/reference-ml-get_calendars.asciidoc b/docs/reference-ml-get_calendars.asciidoc new file mode 100644 index 000000000..3cbd709e3 --- /dev/null +++ b/docs/reference-ml-get_calendars.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-get_calendars]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getCalendars + +Get calendar configuration info. + +{ref}/ml-get-calendar.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetCalendarsRequest, options?): Promise +---- + +[discrete] +===== `MlGetCalendarsRequest` + +[source,ts] +---- +interface MlGetCalendarsRequest extends <> { + calendar_id?: <> + from?: <> + size?: <> + page?: MlPage +} +---- + +[discrete] +===== `MlGetCalendarsResponse` + +[source,ts] +---- +interface MlGetCalendarsResponse { + calendars: MlGetCalendarsCalendar[] + count: <> +} +---- + diff --git a/docs/reference-ml-get_categories.asciidoc b/docs/reference-ml-get_categories.asciidoc new file mode 100644 index 000000000..c73e98855 --- /dev/null +++ b/docs/reference-ml-get_categories.asciidoc @@ -0,0 +1,68 @@ +[[reference-ml-get_categories]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getCategories + +Get anomaly detection job results for categories. + +{ref}/ml-get-category.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetCategoriesRequest, options?): Promise +---- + +[discrete] +===== `MlGetCategoriesRequest` + +[source,ts] +---- +interface MlGetCategoriesRequest extends <> { + job_id: <> + category_id?: <> + from?: <> + partition_field_value?: string + size?: <> + page?: MlPage +} +---- + +[discrete] +===== `MlGetCategoriesResponse` + +[source,ts] +---- +interface MlGetCategoriesResponse { + categories: MlCategory[] + count: <> +} +---- + diff --git a/docs/reference-ml-get_data_frame_analytics.asciidoc b/docs/reference-ml-get_data_frame_analytics.asciidoc new file mode 100644 index 000000000..0d47532be --- /dev/null +++ b/docs/reference-ml-get_data_frame_analytics.asciidoc @@ -0,0 +1,67 @@ +[[reference-ml-get_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getDataFrameAnalytics + +Get data frame analytics job configuration info. You can get information for multiple data frame analytics jobs in a single API request by using a comma-separated list of data frame analytics jobs or a wildcard expression. + +{ref}/get-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlGetDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlGetDataFrameAnalyticsRequest extends <> { + id?: <> + allow_no_match?: boolean + from?: <> + size?: <> + exclude_generated?: boolean +} +---- + +[discrete] +===== `MlGetDataFrameAnalyticsResponse` + +[source,ts] +---- +interface MlGetDataFrameAnalyticsResponse { + count: <> + data_frame_analytics: MlDataframeAnalyticsSummary[] +} +---- + diff --git a/docs/reference-ml-get_data_frame_analytics_stats.asciidoc b/docs/reference-ml-get_data_frame_analytics_stats.asciidoc new file mode 100644 index 000000000..54770a6f8 --- /dev/null +++ b/docs/reference-ml-get_data_frame_analytics_stats.asciidoc @@ -0,0 +1,67 @@ +[[reference-ml-get_data_frame_analytics_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getDataFrameAnalyticsStats + +Get data frame analytics jobs usage info. + +{ref}/get-dfanalytics-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetDataFrameAnalyticsStatsRequest, options?): Promise +---- + +[discrete] +===== `MlGetDataFrameAnalyticsStatsRequest` + +[source,ts] +---- +interface MlGetDataFrameAnalyticsStatsRequest extends <> { + id?: <> + allow_no_match?: boolean + from?: <> + size?: <> + verbose?: boolean +} +---- + +[discrete] +===== `MlGetDataFrameAnalyticsStatsResponse` + +[source,ts] +---- +interface MlGetDataFrameAnalyticsStatsResponse { + count: <> + data_frame_analytics: MlDataframeAnalytics[] +} +---- + diff --git a/docs/reference-ml-get_datafeed_stats.asciidoc b/docs/reference-ml-get_datafeed_stats.asciidoc new file mode 100644 index 000000000..13725b348 --- /dev/null +++ b/docs/reference-ml-get_datafeed_stats.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-get_datafeed_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getDatafeedStats + +Get datafeeds usage info. You can get statistics for multiple datafeeds in a single API request by using a comma-separated list of datafeeds or a wildcard expression. You can get statistics for all datafeeds by using `_all`, by specifying `*` as the ``, or by omitting the ``. If the datafeed is stopped, the only information you receive is the `datafeed_id` and the `state`. This API returns a maximum of 10,000 datafeeds. + +{ref}/ml-get-datafeed-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetDatafeedStatsRequest, options?): Promise +---- + +[discrete] +===== `MlGetDatafeedStatsRequest` + +[source,ts] +---- +interface MlGetDatafeedStatsRequest extends <> { + datafeed_id?: <> + allow_no_match?: boolean +} +---- + +[discrete] +===== `MlGetDatafeedStatsResponse` + +[source,ts] +---- +interface MlGetDatafeedStatsResponse { + count: <> + datafeeds: MlDatafeedStats[] +} +---- + diff --git a/docs/reference-ml-get_datafeeds.asciidoc b/docs/reference-ml-get_datafeeds.asciidoc new file mode 100644 index 000000000..e9fb19ecc --- /dev/null +++ b/docs/reference-ml-get_datafeeds.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-get_datafeeds]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getDatafeeds + +Get datafeeds configuration info. You can get information for multiple datafeeds in a single API request by using a comma-separated list of datafeeds or a wildcard expression. You can get information for all datafeeds by using `_all`, by specifying `*` as the ``, or by omitting the ``. This API returns a maximum of 10,000 datafeeds. + +{ref}/ml-get-datafeed.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetDatafeedsRequest, options?): Promise +---- + +[discrete] +===== `MlGetDatafeedsRequest` + +[source,ts] +---- +interface MlGetDatafeedsRequest extends <> { + datafeed_id?: <> + allow_no_match?: boolean + exclude_generated?: boolean +} +---- + +[discrete] +===== `MlGetDatafeedsResponse` + +[source,ts] +---- +interface MlGetDatafeedsResponse { + count: <> + datafeeds: MlDatafeed[] +} +---- + diff --git a/docs/reference-ml-get_filters.asciidoc b/docs/reference-ml-get_filters.asciidoc new file mode 100644 index 000000000..29ae571a5 --- /dev/null +++ b/docs/reference-ml-get_filters.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-get_filters]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getFilters + +Get filters. You can get a single filter or all filters. + +{ref}/ml-get-filter.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetFiltersRequest, options?): Promise +---- + +[discrete] +===== `MlGetFiltersRequest` + +[source,ts] +---- +interface MlGetFiltersRequest extends <> { + filter_id?: <> + from?: <> + size?: <> +} +---- + +[discrete] +===== `MlGetFiltersResponse` + +[source,ts] +---- +interface MlGetFiltersResponse { + count: <> + filters: MlFilter[] +} +---- + diff --git a/docs/reference-ml-get_influencers.asciidoc b/docs/reference-ml-get_influencers.asciidoc new file mode 100644 index 000000000..5d131f19a --- /dev/null +++ b/docs/reference-ml-get_influencers.asciidoc @@ -0,0 +1,72 @@ +[[reference-ml-get_influencers]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getInfluencers + +Get anomaly detection job results for influencers. Influencers are the entities that have contributed to, or are to blame for, the anomalies. Influencer results are available only if an `influencer_field_name` is specified in the job configuration. + +{ref}/ml-get-influencer.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetInfluencersRequest, options?): Promise +---- + +[discrete] +===== `MlGetInfluencersRequest` + +[source,ts] +---- +interface MlGetInfluencersRequest extends <> { + job_id: <> + desc?: boolean + end?: <> + exclude_interim?: boolean + influencer_score?: <> + from?: <> + size?: <> + sort?: <> + start?: <> + page?: MlPage +} +---- + +[discrete] +===== `MlGetInfluencersResponse` + +[source,ts] +---- +interface MlGetInfluencersResponse { + count: <> + influencers: MlInfluencer[] +} +---- + diff --git a/docs/reference-ml-get_job_stats.asciidoc b/docs/reference-ml-get_job_stats.asciidoc new file mode 100644 index 000000000..8ab82d55e --- /dev/null +++ b/docs/reference-ml-get_job_stats.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-get_job_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getJobStats + +Get anomaly detection jobs usage info. + +{ref}/ml-get-job-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetJobStatsRequest, options?): Promise +---- + +[discrete] +===== `MlGetJobStatsRequest` + +[source,ts] +---- +interface MlGetJobStatsRequest extends <> { + job_id?: <> + allow_no_match?: boolean +} +---- + +[discrete] +===== `MlGetJobStatsResponse` + +[source,ts] +---- +interface MlGetJobStatsResponse { + count: <> + jobs: MlJobStats[] +} +---- + diff --git a/docs/reference-ml-get_jobs.asciidoc b/docs/reference-ml-get_jobs.asciidoc new file mode 100644 index 000000000..fab7b5654 --- /dev/null +++ b/docs/reference-ml-get_jobs.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-get_jobs]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getJobs + +Get anomaly detection jobs configuration info. You can get information for multiple anomaly detection jobs in a single API request by using a group name, a comma-separated list of jobs, or a wildcard expression. You can get information for all anomaly detection jobs by using `_all`, by specifying `*` as the ``, or by omitting the ``. + +{ref}/ml-get-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetJobsRequest, options?): Promise +---- + +[discrete] +===== `MlGetJobsRequest` + +[source,ts] +---- +interface MlGetJobsRequest extends <> { + job_id?: <> + allow_no_match?: boolean + exclude_generated?: boolean +} +---- + +[discrete] +===== `MlGetJobsResponse` + +[source,ts] +---- +interface MlGetJobsResponse { + count: <> + jobs: MlJob[] +} +---- + diff --git a/docs/reference-ml-get_memory_stats.asciidoc b/docs/reference-ml-get_memory_stats.asciidoc new file mode 100644 index 000000000..68353dab1 --- /dev/null +++ b/docs/reference-ml-get_memory_stats.asciidoc @@ -0,0 +1,67 @@ +[[reference-ml-get_memory_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getMemoryStats + +Get machine learning memory usage info. Get information about how machine learning jobs and trained models are using memory, on each node, both within the JVM heap, and natively, outside of the JVM. + +{ref}/get-ml-memory.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetMemoryStatsRequest, options?): Promise +---- + +[discrete] +===== `MlGetMemoryStatsRequest` + +[source,ts] +---- +interface MlGetMemoryStatsRequest extends <> { + node_id?: <> + human?: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `MlGetMemoryStatsResponse` + +[source,ts] +---- +interface MlGetMemoryStatsResponse { + _nodes: <> + cluster_name: <> + nodes: Record<<>, MlGetMemoryStatsMemory> +} +---- + diff --git a/docs/reference-ml-get_model_snapshot_upgrade_stats.asciidoc b/docs/reference-ml-get_model_snapshot_upgrade_stats.asciidoc new file mode 100644 index 000000000..8aba7ef1a --- /dev/null +++ b/docs/reference-ml-get_model_snapshot_upgrade_stats.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-get_model_snapshot_upgrade_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getModelSnapshotUpgradeStats + +Get anomaly detection job model snapshot upgrade usage info. + +{ref}/ml-get-job-model-snapshot-upgrade-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetModelSnapshotUpgradeStatsRequest, options?): Promise +---- + +[discrete] +===== `MlGetModelSnapshotUpgradeStatsRequest` + +[source,ts] +---- +interface MlGetModelSnapshotUpgradeStatsRequest extends <> { + job_id: <> + snapshot_id: <> + allow_no_match?: boolean +} +---- + +[discrete] +===== `MlGetModelSnapshotUpgradeStatsResponse` + +[source,ts] +---- +interface MlGetModelSnapshotUpgradeStatsResponse { + count: <> + model_snapshot_upgrades: MlModelSnapshotUpgrade[] +} +---- + diff --git a/docs/reference-ml-get_model_snapshots.asciidoc b/docs/reference-ml-get_model_snapshots.asciidoc new file mode 100644 index 000000000..80ae35a49 --- /dev/null +++ b/docs/reference-ml-get_model_snapshots.asciidoc @@ -0,0 +1,71 @@ +[[reference-ml-get_model_snapshots]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getModelSnapshots + +Get model snapshots info. + +{ref}/ml-get-snapshot.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetModelSnapshotsRequest, options?): Promise +---- + +[discrete] +===== `MlGetModelSnapshotsRequest` + +[source,ts] +---- +interface MlGetModelSnapshotsRequest extends <> { + job_id: <> + snapshot_id?: <> + from?: <> + size?: <> + desc?: boolean + end?: <> + page?: MlPage + sort?: <> + start?: <> +} +---- + +[discrete] +===== `MlGetModelSnapshotsResponse` + +[source,ts] +---- +interface MlGetModelSnapshotsResponse { + count: <> + model_snapshots: MlModelSnapshot[] +} +---- + diff --git a/docs/reference-ml-get_overall_buckets.asciidoc b/docs/reference-ml-get_overall_buckets.asciidoc new file mode 100644 index 000000000..81ac4f7dd --- /dev/null +++ b/docs/reference-ml-get_overall_buckets.asciidoc @@ -0,0 +1,70 @@ +[[reference-ml-get_overall_buckets]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getOverallBuckets + +Get overall bucket results. Retrievs overall bucket results that summarize the bucket results of multiple anomaly detection jobs. The `overall_score` is calculated by combining the scores of all the buckets within the overall bucket span. First, the maximum `anomaly_score` per anomaly detection job in the overall bucket is calculated. Then the `top_n` of those scores are averaged to result in the `overall_score`. This means that you can fine-tune the `overall_score` so that it is more or less sensitive to the number of jobs that detect an anomaly at the same time. For example, if you set `top_n` to `1`, the `overall_score` is the maximum bucket score in the overall bucket. Alternatively, if you set `top_n` to the number of jobs, the `overall_score` is high only when all jobs detect anomalies in that overall bucket. If you set the `bucket_span` parameter (to a value greater than its default), the `overall_score` is the maximum `overall_score` of the overall buckets that have a span equal to the jobs' largest bucket span. + +{ref}/ml-get-overall-buckets.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetOverallBucketsRequest, options?): Promise +---- + +[discrete] +===== `MlGetOverallBucketsRequest` + +[source,ts] +---- +interface MlGetOverallBucketsRequest extends <> { + job_id: <> + allow_no_match?: boolean + bucket_span?: <> + end?: <> + exclude_interim?: boolean + overall_score?: <> | string + start?: <> + top_n?: <> +} +---- + +[discrete] +===== `MlGetOverallBucketsResponse` + +[source,ts] +---- +interface MlGetOverallBucketsResponse { + count: <> + overall_buckets: MlOverallBucket[] +} +---- + diff --git a/docs/reference-ml-get_records.asciidoc b/docs/reference-ml-get_records.asciidoc new file mode 100644 index 000000000..56a4351ff --- /dev/null +++ b/docs/reference-ml-get_records.asciidoc @@ -0,0 +1,72 @@ +[[reference-ml-get_records]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getRecords + +Get anomaly records for an anomaly detection job. Records contain the detailed analytical results. They describe the anomalous activity that has been identified in the input data based on the detector configuration. There can be many anomaly records depending on the characteristics and size of the input data. In practice, there are often too many to be able to manually process them. The machine learning features therefore perform a sophisticated aggregation of the anomaly records into buckets. The number of record results depends on the number of anomalies found in each bucket, which relates to the number of time series being modeled and the number of detectors. + +{ref}/ml-get-record.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetRecordsRequest, options?): Promise +---- + +[discrete] +===== `MlGetRecordsRequest` + +[source,ts] +---- +interface MlGetRecordsRequest extends <> { + job_id: <> + from?: <> + size?: <> + desc?: boolean + end?: <> + exclude_interim?: boolean + page?: MlPage + record_score?: <> + sort?: <> + start?: <> +} +---- + +[discrete] +===== `MlGetRecordsResponse` + +[source,ts] +---- +interface MlGetRecordsResponse { + count: <> + records: MlAnomaly[] +} +---- + diff --git a/docs/reference-ml-get_trained_models.asciidoc b/docs/reference-ml-get_trained_models.asciidoc new file mode 100644 index 000000000..f9751b925 --- /dev/null +++ b/docs/reference-ml-get_trained_models.asciidoc @@ -0,0 +1,70 @@ +[[reference-ml-get_trained_models]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getTrainedModels + +Get trained model configuration info. + +{ref}/get-trained-models.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetTrainedModelsRequest, options?): Promise +---- + +[discrete] +===== `MlGetTrainedModelsRequest` + +[source,ts] +---- +interface MlGetTrainedModelsRequest extends <> { + model_id?: <> + allow_no_match?: boolean + decompress_definition?: boolean + exclude_generated?: boolean + from?: <> + include?: MlInclude + size?: <> + tags?: string | string[] +} +---- + +[discrete] +===== `MlGetTrainedModelsResponse` + +[source,ts] +---- +interface MlGetTrainedModelsResponse { + count: <> + trained_model_configs: MlTrainedModelConfig[] +} +---- + diff --git a/docs/reference-ml-get_trained_models_stats.asciidoc b/docs/reference-ml-get_trained_models_stats.asciidoc new file mode 100644 index 000000000..2fa3cb1cd --- /dev/null +++ b/docs/reference-ml-get_trained_models_stats.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-get_trained_models_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.getTrainedModelsStats + +Get trained models usage info. You can get usage information for multiple trained models in a single API request by using a comma-separated list of model IDs or a wildcard expression. + +{ref}/get-trained-models-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlGetTrainedModelsStatsRequest, options?): Promise +---- + +[discrete] +===== `MlGetTrainedModelsStatsRequest` + +[source,ts] +---- +interface MlGetTrainedModelsStatsRequest extends <> { + model_id?: <> + allow_no_match?: boolean + from?: <> + size?: <> +} +---- + +[discrete] +===== `MlGetTrainedModelsStatsResponse` + +[source,ts] +---- +interface MlGetTrainedModelsStatsResponse { + count: <> + trained_model_stats: MlTrainedModelStats[] +} +---- + diff --git a/docs/reference-ml-infer_trained_model.asciidoc b/docs/reference-ml-infer_trained_model.asciidoc new file mode 100644 index 000000000..d76a02095 --- /dev/null +++ b/docs/reference-ml-infer_trained_model.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-infer_trained_model]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.inferTrainedModel + +Evaluate a trained model. + +{ref}/infer-trained-model.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlInferTrainedModelRequest, options?): Promise +---- + +[discrete] +===== `MlInferTrainedModelRequest` + +[source,ts] +---- +interface MlInferTrainedModelRequest extends <> { + model_id: <> + timeout?: <> + docs: Record[] + inference_config?: MlInferenceConfigUpdateContainer +} +---- + +[discrete] +===== `MlInferTrainedModelResponse` + +[source,ts] +---- +interface MlInferTrainedModelResponse { + inference_results: MlInferenceResponseResult[] +} +---- + diff --git a/docs/reference-ml-info.asciidoc b/docs/reference-ml-info.asciidoc new file mode 100644 index 000000000..320785add --- /dev/null +++ b/docs/reference-ml-info.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.info + +Return ML defaults and limits. Returns defaults and limits used by machine learning. This endpoint is designed to be used by a user interface that needs to fully understand machine learning configurations where some options are not specified, meaning that the defaults should be used. This endpoint may be used to find out what those defaults are. It also provides information about the maximum size of machine learning jobs that could run in the current cluster configuration. + +{ref}/get-ml-info.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlInfoRequest, options?): Promise +---- + +[discrete] +===== `MlInfoRequest` + +[source,ts] +---- +interface MlInfoRequest extends <> { +} +---- + +[discrete] +===== `MlInfoResponse` + +[source,ts] +---- +interface MlInfoResponse { + defaults: MlInfoDefaults + limits: MlInfoLimits + upgrade_mode: boolean + native_code: MlInfoNativeCode +} +---- + diff --git a/docs/reference-ml-open_job.asciidoc b/docs/reference-ml-open_job.asciidoc new file mode 100644 index 000000000..28a6b475e --- /dev/null +++ b/docs/reference-ml-open_job.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-open_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.openJob + +Open anomaly detection jobs. An anomaly detection job must be opened to be ready to receive and analyze data. It can be opened and closed multiple times throughout its lifecycle. When you open a new job, it starts with an empty model. When you open an existing job, the most recent model state is automatically loaded. The job is ready to resume its analysis from where it left off, once new data is received. + +{ref}/ml-open-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlOpenJobRequest, options?): Promise +---- + +[discrete] +===== `MlOpenJobRequest` + +[source,ts] +---- +interface MlOpenJobRequest extends <> { + job_id: <> + timeout?: <> +} +---- + +[discrete] +===== `MlOpenJobResponse` + +[source,ts] +---- +interface MlOpenJobResponse { + opened: boolean + node: <> +} +---- + diff --git a/docs/reference-ml-post_calendar_events.asciidoc b/docs/reference-ml-post_calendar_events.asciidoc new file mode 100644 index 000000000..74852be25 --- /dev/null +++ b/docs/reference-ml-post_calendar_events.asciidoc @@ -0,0 +1,63 @@ +[[reference-ml-post_calendar_events]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.postCalendarEvents + +Add scheduled events to the calendar. + +{ref}/ml-post-calendar-event.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPostCalendarEventsRequest, options?): Promise +---- + +[discrete] +===== `MlPostCalendarEventsRequest` + +[source,ts] +---- +interface MlPostCalendarEventsRequest extends <> { + calendar_id: <> + events: MlCalendarEvent[] +} +---- + +[discrete] +===== `MlPostCalendarEventsResponse` + +[source,ts] +---- +interface MlPostCalendarEventsResponse { + events: MlCalendarEvent[] +} +---- + diff --git a/docs/reference-ml-post_data.asciidoc b/docs/reference-ml-post_data.asciidoc new file mode 100644 index 000000000..d76e2ce1c --- /dev/null +++ b/docs/reference-ml-post_data.asciidoc @@ -0,0 +1,79 @@ +[[reference-ml-post_data]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.postData + +Send data to an anomaly detection job for analysis. IMPORTANT: For each job, data can be accepted from only a single connection at a time. It is not currently possible to post data to multiple jobs using wildcards or a comma-separated list. + +{ref}/ml-post-data.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPostDataRequest, options?): Promise +---- + +[discrete] +===== `MlPostDataRequest` + +[source,ts] +---- +interface MlPostDataRequest extends <> { + job_id: <> + reset_end?: <> + reset_start?: <> + data?: TData[] +} +---- + +[discrete] +===== `MlPostDataResponse` + +[source,ts] +---- +interface MlPostDataResponse { + bucket_count: <> + earliest_record_timestamp: <> + empty_bucket_count: <> + input_bytes: <> + input_field_count: <> + input_record_count: <> + invalid_date_count: <> + job_id: <> + last_data_time: <> + latest_record_timestamp: <> + missing_field_count: <> + out_of_order_timestamp_count: <> + processed_field_count: <> + processed_record_count: <> + sparse_bucket_count: <> +} +---- + diff --git a/docs/reference-ml-preview_data_frame_analytics.asciidoc b/docs/reference-ml-preview_data_frame_analytics.asciidoc new file mode 100644 index 000000000..608f67f1a --- /dev/null +++ b/docs/reference-ml-preview_data_frame_analytics.asciidoc @@ -0,0 +1,63 @@ +[[reference-ml-preview_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.previewDataFrameAnalytics + +Preview features used by data frame analytics. Previews the extracted features used by a data frame analytics config. + +{ref}/preview-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPreviewDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlPreviewDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlPreviewDataFrameAnalyticsRequest extends <> { + id?: <> + config?: MlPreviewDataFrameAnalyticsDataframePreviewConfig +} +---- + +[discrete] +===== `MlPreviewDataFrameAnalyticsResponse` + +[source,ts] +---- +interface MlPreviewDataFrameAnalyticsResponse { + feature_values: Record<<>, string>[] +} +---- + diff --git a/docs/reference-ml-preview_datafeed.asciidoc b/docs/reference-ml-preview_datafeed.asciidoc new file mode 100644 index 000000000..8b8b16cf8 --- /dev/null +++ b/docs/reference-ml-preview_datafeed.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-preview_datafeed]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.previewDatafeed + +Preview a datafeed. This API returns the first "page" of search results from a datafeed. You can preview an existing datafeed or provide configuration details for a datafeed and anomaly detection job in the API. The preview shows the structure of the data that will be passed to the anomaly detection engine. IMPORTANT: When Elasticsearch security features are enabled, the preview uses the credentials of the user that called the API. However, when the datafeed starts it uses the roles of the last user that created or updated the datafeed. To get a preview that accurately reflects the behavior of the datafeed, use the appropriate credentials. You can also use secondary authorization headers to supply the credentials. + +{ref}/ml-preview-datafeed.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPreviewDatafeedRequest, options?): Promise +---- + +[discrete] +===== `MlPreviewDatafeedRequest` + +[source,ts] +---- +interface MlPreviewDatafeedRequest extends <> { + datafeed_id?: <> + start?: <> + end?: <> + datafeed_config?: MlDatafeedConfig + job_config?: MlJobConfig +} +---- + +[discrete] +===== `MlPreviewDatafeedResponse` + +[source,ts] +---- +type MlPreviewDatafeedResponse = TDocument[] +---- + diff --git a/docs/reference-ml-put_calendar.asciidoc b/docs/reference-ml-put_calendar.asciidoc new file mode 100644 index 000000000..7304b4edb --- /dev/null +++ b/docs/reference-ml-put_calendar.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-put_calendar]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putCalendar + +Create a calendar. + +{ref}/ml-put-calendar.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutCalendarRequest, options?): Promise +---- + +[discrete] +===== `MlPutCalendarRequest` + +[source,ts] +---- +interface MlPutCalendarRequest extends <> { + calendar_id: <> + job_ids?: <>[] + description?: string +} +---- + +[discrete] +===== `MlPutCalendarResponse` + +[source,ts] +---- +interface MlPutCalendarResponse { + calendar_id: <> + description?: string + job_ids: <> +} +---- + diff --git a/docs/reference-ml-put_calendar_job.asciidoc b/docs/reference-ml-put_calendar_job.asciidoc new file mode 100644 index 000000000..47fa104e8 --- /dev/null +++ b/docs/reference-ml-put_calendar_job.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-put_calendar_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putCalendarJob + +Add anomaly detection job to calendar. + +{ref}/ml-put-calendar-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutCalendarJobRequest, options?): Promise +---- + +[discrete] +===== `MlPutCalendarJobRequest` + +[source,ts] +---- +interface MlPutCalendarJobRequest extends <> { + calendar_id: <> + job_id: <> +} +---- + +[discrete] +===== `MlPutCalendarJobResponse` + +[source,ts] +---- +interface MlPutCalendarJobResponse { + calendar_id: <> + description?: string + job_ids: <> +} +---- + diff --git a/docs/reference-ml-put_data_frame_analytics.asciidoc b/docs/reference-ml-put_data_frame_analytics.asciidoc new file mode 100644 index 000000000..e860dacf3 --- /dev/null +++ b/docs/reference-ml-put_data_frame_analytics.asciidoc @@ -0,0 +1,83 @@ +[[reference-ml-put_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putDataFrameAnalytics + +Create a data frame analytics job. This API creates a data frame analytics job that performs an analysis on the source indices and stores the outcome in a destination index. + +{ref}/put-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlPutDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlPutDataFrameAnalyticsRequest extends <> { + id: <> + allow_lazy_start?: boolean + analysis: MlDataframeAnalysisContainer + analyzed_fields?: MlDataframeAnalysisAnalyzedFields | string[] + description?: string + dest: MlDataframeAnalyticsDestination + max_num_threads?: <> + model_memory_limit?: string + source: MlDataframeAnalyticsSource + headers?: <> + version?: <> +} +---- + +[discrete] +===== `MlPutDataFrameAnalyticsResponse` + +[source,ts] +---- +interface MlPutDataFrameAnalyticsResponse { + authorization?: MlDataframeAnalyticsAuthorization + allow_lazy_start: boolean + analysis: MlDataframeAnalysisContainer + analyzed_fields?: MlDataframeAnalysisAnalyzedFields | string[] + create_time: <><<>> + description?: string + dest: MlDataframeAnalyticsDestination + id: <> + max_num_threads: <> + model_memory_limit: string + source: MlDataframeAnalyticsSource + version: <> +} +---- + diff --git a/docs/reference-ml-put_datafeed.asciidoc b/docs/reference-ml-put_datafeed.asciidoc new file mode 100644 index 000000000..acfe59bbe --- /dev/null +++ b/docs/reference-ml-put_datafeed.asciidoc @@ -0,0 +1,96 @@ +[[reference-ml-put_datafeed]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putDatafeed + +Create a datafeed. Datafeeds retrieve data from Elasticsearch for analysis by an anomaly detection job. You can associate only one datafeed with each anomaly detection job. The datafeed contains a query that runs at a defined interval (`frequency`). If you are concerned about delayed data, you can add a delay (`query_delay') at each interval. When Elasticsearch security features are enabled, your datafeed remembers which roles the user who created it had at the time of creation and runs the query using those same roles. If you provide secondary authorization headers, those credentials are used instead. You must use Kibana, this API, or the create anomaly detection jobs API to create a datafeed. Do not add a datafeed directly to the `.ml-config` index. Do not give users `write` privileges on the `.ml-config` index. + +{ref}/ml-put-datafeed.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutDatafeedRequest, options?): Promise +---- + +[discrete] +===== `MlPutDatafeedRequest` + +[source,ts] +---- +interface MlPutDatafeedRequest extends <> { + datafeed_id: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + aggregations?: Record + chunking_config?: MlChunkingConfig + delayed_data_check_config?: MlDelayedDataCheckConfig + frequency?: <> + indices?: <> + /** @alias indices */ + indexes?: <> + indices_options?: <> + job_id?: <> + max_empty_searches?: <> + query?: QueryDslQueryContainer + query_delay?: <> + runtime_mappings?: MappingRuntimeFields + script_fields?: Record>> + scroll_size?: <> + headers?: <> +} +---- + +[discrete] +===== `MlPutDatafeedResponse` + +[source,ts] +---- +interface MlPutDatafeedResponse { + aggregations?: Record + authorization?: MlDatafeedAuthorization + chunking_config: MlChunkingConfig + delayed_data_check_config?: MlDelayedDataCheckConfig + datafeed_id: <> + frequency?: <> + indices: string[] + job_id: <> + indices_options?: <> + max_empty_searches?: <> + query: QueryDslQueryContainer + query_delay: <> + runtime_mappings?: MappingRuntimeFields + script_fields?: Record>> + scroll_size: <> +} +---- + diff --git a/docs/reference-ml-put_filter.asciidoc b/docs/reference-ml-put_filter.asciidoc new file mode 100644 index 000000000..5c0b3dbfa --- /dev/null +++ b/docs/reference-ml-put_filter.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-put_filter]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putFilter + +Create a filter. A filter contains a list of strings. It can be used by one or more anomaly detection jobs. Specifically, filters are referenced in the `custom_rules` property of detector configuration objects. + +{ref}/ml-put-filter.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutFilterRequest, options?): Promise +---- + +[discrete] +===== `MlPutFilterRequest` + +[source,ts] +---- +interface MlPutFilterRequest extends <> { + filter_id: <> + description?: string + items?: string[] +} +---- + +[discrete] +===== `MlPutFilterResponse` + +[source,ts] +---- +interface MlPutFilterResponse { + description: string + filter_id: <> + items: string[] +} +---- + diff --git a/docs/reference-ml-put_job.asciidoc b/docs/reference-ml-put_job.asciidoc new file mode 100644 index 000000000..f80e42b19 --- /dev/null +++ b/docs/reference-ml-put_job.asciidoc @@ -0,0 +1,96 @@ +[[reference-ml-put_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putJob + +Create an anomaly detection job. If you include a `datafeed_config`, you must have read index privileges on the source index. + +{ref}/ml-put-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutJobRequest, options?): Promise +---- + +[discrete] +===== `MlPutJobRequest` + +[source,ts] +---- +interface MlPutJobRequest extends <> { + job_id: <> + allow_lazy_open?: boolean + analysis_config: MlAnalysisConfig + analysis_limits?: MlAnalysisLimits + background_persist_interval?: <> + custom_settings?: MlCustomSettings + daily_model_snapshot_retention_after_days?: <> + data_description: MlDataDescription + datafeed_config?: MlDatafeedConfig + description?: string + groups?: string[] + model_plot_config?: MlModelPlotConfig + model_snapshot_retention_days?: <> + renormalization_window_days?: <> + results_index_name?: <> + results_retention_days?: <> +} +---- + +[discrete] +===== `MlPutJobResponse` + +[source,ts] +---- +interface MlPutJobResponse { + allow_lazy_open: boolean + analysis_config: MlAnalysisConfigRead + analysis_limits: MlAnalysisLimits + background_persist_interval?: <> + create_time: <> + custom_settings?: MlCustomSettings + daily_model_snapshot_retention_after_days: <> + data_description: MlDataDescription + datafeed_config?: MlDatafeed + description?: string + groups?: string[] + job_id: <> + job_type: string + job_version: string + model_plot_config?: MlModelPlotConfig + model_snapshot_id?: <> + model_snapshot_retention_days: <> + renormalization_window_days?: <> + results_index_name: string + results_retention_days?: <> +} +---- + diff --git a/docs/reference-ml-put_trained_model.asciidoc b/docs/reference-ml-put_trained_model.asciidoc new file mode 100644 index 000000000..a6b75d56a --- /dev/null +++ b/docs/reference-ml-put_trained_model.asciidoc @@ -0,0 +1,73 @@ +[[reference-ml-put_trained_model]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putTrainedModel + +Create a trained model. Enable you to supply a trained model that is not created by data frame analytics. + +{ref}/put-trained-models.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutTrainedModelRequest, options?): Promise +---- + +[discrete] +===== `MlPutTrainedModelRequest` + +[source,ts] +---- +interface MlPutTrainedModelRequest extends <> { + model_id: <> + defer_definition_decompression?: boolean + wait_for_completion?: boolean + compressed_definition?: string + definition?: MlPutTrainedModelDefinition + description?: string + inference_config?: MlInferenceConfigCreateContainer + input?: MlPutTrainedModelInput + metadata?: any + model_type?: MlTrainedModelType + model_size_bytes?: <> + platform_architecture?: string + tags?: string[] + prefix_strings?: MlTrainedModelPrefixStrings +} +---- + +[discrete] +===== `MlPutTrainedModelResponse` + +[source,ts] +---- +type MlPutTrainedModelResponse = MlTrainedModelConfig +---- + diff --git a/docs/reference-ml-put_trained_model_alias.asciidoc b/docs/reference-ml-put_trained_model_alias.asciidoc new file mode 100644 index 000000000..c80e5a514 --- /dev/null +++ b/docs/reference-ml-put_trained_model_alias.asciidoc @@ -0,0 +1,62 @@ +[[reference-ml-put_trained_model_alias]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putTrainedModelAlias + +Create or update a trained model alias. A trained model alias is a logical name used to reference a single trained model. You can use aliases instead of trained model identifiers to make it easier to reference your models. For example, you can use aliases in inference aggregations and processors. An alias must be unique and refer to only a single trained model. However, you can have multiple aliases for each trained model. If you use this API to update an alias such that it references a different trained model ID and the model uses a different type of data frame analytics, an error occurs. For example, this situation occurs if you have a trained model for regression analysis and a trained model for classification analysis; you cannot reassign an alias from one type of trained model to another. If you use this API to update an alias and there are very few input fields in common between the old and new trained models for the model alias, the API returns a warning. + +{ref}/put-trained-models-aliases.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutTrainedModelAliasRequest, options?): Promise +---- + +[discrete] +===== `MlPutTrainedModelAliasRequest` + +[source,ts] +---- +interface MlPutTrainedModelAliasRequest extends <> { + model_alias: <> + model_id: <> + reassign?: boolean +} +---- + +[discrete] +===== `MlPutTrainedModelAliasResponse` + +[source,ts] +---- +type MlPutTrainedModelAliasResponse = <> +---- + diff --git a/docs/reference-ml-put_trained_model_definition_part.asciidoc b/docs/reference-ml-put_trained_model_definition_part.asciidoc new file mode 100644 index 000000000..f8be8ae79 --- /dev/null +++ b/docs/reference-ml-put_trained_model_definition_part.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-put_trained_model_definition_part]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putTrainedModelDefinitionPart + +Create part of a trained model definition. + +{ref}/put-trained-model-definition-part.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutTrainedModelDefinitionPartRequest, options?): Promise +---- + +[discrete] +===== `MlPutTrainedModelDefinitionPartRequest` + +[source,ts] +---- +interface MlPutTrainedModelDefinitionPartRequest extends <> { + model_id: <> + part: <> + definition: string + total_definition_length: <> + total_parts: <> +} +---- + +[discrete] +===== `MlPutTrainedModelDefinitionPartResponse` + +[source,ts] +---- +type MlPutTrainedModelDefinitionPartResponse = <> +---- + diff --git a/docs/reference-ml-put_trained_model_vocabulary.asciidoc b/docs/reference-ml-put_trained_model_vocabulary.asciidoc new file mode 100644 index 000000000..5329b54f2 --- /dev/null +++ b/docs/reference-ml-put_trained_model_vocabulary.asciidoc @@ -0,0 +1,63 @@ +[[reference-ml-put_trained_model_vocabulary]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.putTrainedModelVocabulary + +Create a trained model vocabulary. This API is supported only for natural language processing (NLP) models. The vocabulary is stored in the index as described in `inference_config.*.vocabulary` of the trained model definition. + +{ref}/put-trained-model-vocabulary.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlPutTrainedModelVocabularyRequest, options?): Promise +---- + +[discrete] +===== `MlPutTrainedModelVocabularyRequest` + +[source,ts] +---- +interface MlPutTrainedModelVocabularyRequest extends <> { + model_id: <> + vocabulary: string[] + merges?: string[] + scores?: <>[] +} +---- + +[discrete] +===== `MlPutTrainedModelVocabularyResponse` + +[source,ts] +---- +type MlPutTrainedModelVocabularyResponse = <> +---- + diff --git a/docs/reference-ml-reset_job.asciidoc b/docs/reference-ml-reset_job.asciidoc new file mode 100644 index 000000000..ac42867b0 --- /dev/null +++ b/docs/reference-ml-reset_job.asciidoc @@ -0,0 +1,62 @@ +[[reference-ml-reset_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.resetJob + +Reset an anomaly detection job. All model state and results are deleted. The job is ready to start over as if it had just been created. It is not currently possible to reset multiple jobs using wildcards or a comma separated list. + +{ref}/ml-reset-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlResetJobRequest, options?): Promise +---- + +[discrete] +===== `MlResetJobRequest` + +[source,ts] +---- +interface MlResetJobRequest extends <> { + job_id: <> + wait_for_completion?: boolean + delete_user_annotations?: boolean +} +---- + +[discrete] +===== `MlResetJobResponse` + +[source,ts] +---- +type MlResetJobResponse = <> +---- + diff --git a/docs/reference-ml-revert_model_snapshot.asciidoc b/docs/reference-ml-revert_model_snapshot.asciidoc new file mode 100644 index 000000000..81b3db7be --- /dev/null +++ b/docs/reference-ml-revert_model_snapshot.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-revert_model_snapshot]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.revertModelSnapshot + +Revert to a snapshot. The machine learning features react quickly to anomalous input, learning new behaviors in data. Highly anomalous input increases the variance in the models whilst the system learns whether this is a new step-change in behavior or a one-off event. In the case where this anomalous input is known to be a one-off, then it might be appropriate to reset the model state to a time before this event. For example, you might consider reverting to a saved snapshot after Black Friday or a critical system failure. + +{ref}/ml-revert-snapshot.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlRevertModelSnapshotRequest, options?): Promise +---- + +[discrete] +===== `MlRevertModelSnapshotRequest` + +[source,ts] +---- +interface MlRevertModelSnapshotRequest extends <> { + job_id: <> + snapshot_id: <> + delete_intervening_results?: boolean +} +---- + +[discrete] +===== `MlRevertModelSnapshotResponse` + +[source,ts] +---- +interface MlRevertModelSnapshotResponse { + model: MlModelSnapshot +} +---- + diff --git a/docs/reference-ml-set_upgrade_mode.asciidoc b/docs/reference-ml-set_upgrade_mode.asciidoc new file mode 100644 index 000000000..703f766a4 --- /dev/null +++ b/docs/reference-ml-set_upgrade_mode.asciidoc @@ -0,0 +1,61 @@ +[[reference-ml-set_upgrade_mode]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.setUpgradeMode + +Set upgrade_mode for ML indices. Sets a cluster wide upgrade_mode setting that prepares machine learning indices for an upgrade. When upgrading your cluster, in some circumstances you must restart your nodes and reindex your machine learning indices. In those circumstances, there must be no machine learning jobs running. You can close the machine learning jobs, do the upgrade, then open all the jobs again. Alternatively, you can use this API to temporarily halt tasks associated with the jobs and datafeeds and prevent new jobs from opening. You can also use this API during upgrades that do not require you to reindex your machine learning indices, though stopping jobs is not a requirement in that case. You can see the current value for the upgrade_mode setting by using the get machine learning info API. + +{ref}/ml-set-upgrade-mode.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlSetUpgradeModeRequest, options?): Promise +---- + +[discrete] +===== `MlSetUpgradeModeRequest` + +[source,ts] +---- +interface MlSetUpgradeModeRequest extends <> { + enabled?: boolean + timeout?: <> +} +---- + +[discrete] +===== `MlSetUpgradeModeResponse` + +[source,ts] +---- +type MlSetUpgradeModeResponse = <> +---- + diff --git a/docs/reference-ml-start_data_frame_analytics.asciidoc b/docs/reference-ml-start_data_frame_analytics.asciidoc new file mode 100644 index 000000000..90cc02f0a --- /dev/null +++ b/docs/reference-ml-start_data_frame_analytics.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-start_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.startDataFrameAnalytics + +Start a data frame analytics job. A data frame analytics job can be started and stopped multiple times throughout its lifecycle. If the destination index does not exist, it is created automatically the first time you start the data frame analytics job. The `index.number_of_shards` and `index.number_of_replicas` settings for the destination index are copied from the source index. If there are multiple source indices, the destination index copies the highest setting values. The mappings for the destination index are also copied from the source indices. If there are any mapping conflicts, the job fails to start. If the destination index exists, it is used as is. You can therefore set up the destination index in advance with custom settings and mappings. + +{ref}/start-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlStartDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlStartDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlStartDataFrameAnalyticsRequest extends <> { + id: <> + timeout?: <> +} +---- + +[discrete] +===== `MlStartDataFrameAnalyticsResponse` + +[source,ts] +---- +interface MlStartDataFrameAnalyticsResponse { + acknowledged: boolean + node: <> +} +---- + diff --git a/docs/reference-ml-start_datafeed.asciidoc b/docs/reference-ml-start_datafeed.asciidoc new file mode 100644 index 000000000..5ac0a4d2b --- /dev/null +++ b/docs/reference-ml-start_datafeed.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-start_datafeed]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.startDatafeed + +Start datafeeds. A datafeed must be started in order to retrieve data from Elasticsearch. A datafeed can be started and stopped multiple times throughout its lifecycle. Before you can start a datafeed, the anomaly detection job must be open. Otherwise, an error occurs. If you restart a stopped datafeed, it continues processing input data from the next millisecond after it was stopped. If new data was indexed for that exact millisecond between stopping and starting, it will be ignored. When Elasticsearch security features are enabled, your datafeed remembers which roles the last user to create or update it had at the time of creation or update and runs the query using those same roles. If you provided secondary authorization headers when you created or updated the datafeed, those credentials are used instead. + +{ref}/ml-start-datafeed.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlStartDatafeedRequest, options?): Promise +---- + +[discrete] +===== `MlStartDatafeedRequest` + +[source,ts] +---- +interface MlStartDatafeedRequest extends <> { + datafeed_id: <> + end?: <> + start?: <> + timeout?: <> +} +---- + +[discrete] +===== `MlStartDatafeedResponse` + +[source,ts] +---- +interface MlStartDatafeedResponse { + node: <> + started: boolean +} +---- + diff --git a/docs/reference-ml-start_trained_model_deployment.asciidoc b/docs/reference-ml-start_trained_model_deployment.asciidoc new file mode 100644 index 000000000..cad79365f --- /dev/null +++ b/docs/reference-ml-start_trained_model_deployment.asciidoc @@ -0,0 +1,70 @@ +[[reference-ml-start_trained_model_deployment]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.startTrainedModelDeployment + +Start a trained model deployment. It allocates the model to every machine learning node. + +{ref}/start-trained-model-deployment.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlStartTrainedModelDeploymentRequest, options?): Promise +---- + +[discrete] +===== `MlStartTrainedModelDeploymentRequest` + +[source,ts] +---- +interface MlStartTrainedModelDeploymentRequest extends <> { + model_id: <> + cache_size?: <> + deployment_id?: string + number_of_allocations?: <> + priority?: MlTrainingPriority + queue_capacity?: <> + threads_per_allocation?: <> + timeout?: <> + wait_for?: MlDeploymentAllocationState +} +---- + +[discrete] +===== `MlStartTrainedModelDeploymentResponse` + +[source,ts] +---- +interface MlStartTrainedModelDeploymentResponse { + assignment: MlTrainedModelAssignment +} +---- + diff --git a/docs/reference-ml-stop_data_frame_analytics.asciidoc b/docs/reference-ml-stop_data_frame_analytics.asciidoc new file mode 100644 index 000000000..63849165f --- /dev/null +++ b/docs/reference-ml-stop_data_frame_analytics.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-stop_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.stopDataFrameAnalytics + +Stop data frame analytics jobs. A data frame analytics job can be started and stopped multiple times throughout its lifecycle. + +{ref}/stop-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlStopDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlStopDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlStopDataFrameAnalyticsRequest extends <> { + id: <> + allow_no_match?: boolean + force?: boolean + timeout?: <> +} +---- + +[discrete] +===== `MlStopDataFrameAnalyticsResponse` + +[source,ts] +---- +interface MlStopDataFrameAnalyticsResponse { + stopped: boolean +} +---- + diff --git a/docs/reference-ml-stop_datafeed.asciidoc b/docs/reference-ml-stop_datafeed.asciidoc new file mode 100644 index 000000000..3d609c3f7 --- /dev/null +++ b/docs/reference-ml-stop_datafeed.asciidoc @@ -0,0 +1,65 @@ +[[reference-ml-stop_datafeed]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.stopDatafeed + +Stop datafeeds. A datafeed that is stopped ceases to retrieve data from Elasticsearch. A datafeed can be started and stopped multiple times throughout its lifecycle. + +{ref}/ml-stop-datafeed.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlStopDatafeedRequest, options?): Promise +---- + +[discrete] +===== `MlStopDatafeedRequest` + +[source,ts] +---- +interface MlStopDatafeedRequest extends <> { + datafeed_id: <> + allow_no_match?: boolean + force?: boolean + timeout?: <> +} +---- + +[discrete] +===== `MlStopDatafeedResponse` + +[source,ts] +---- +interface MlStopDatafeedResponse { + stopped: boolean +} +---- + diff --git a/docs/reference-ml-stop_trained_model_deployment.asciidoc b/docs/reference-ml-stop_trained_model_deployment.asciidoc new file mode 100644 index 000000000..0e4741c66 --- /dev/null +++ b/docs/reference-ml-stop_trained_model_deployment.asciidoc @@ -0,0 +1,64 @@ +[[reference-ml-stop_trained_model_deployment]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.stopTrainedModelDeployment + +Stop a trained model deployment. + +{ref}/stop-trained-model-deployment.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlStopTrainedModelDeploymentRequest, options?): Promise +---- + +[discrete] +===== `MlStopTrainedModelDeploymentRequest` + +[source,ts] +---- +interface MlStopTrainedModelDeploymentRequest extends <> { + model_id: <> + allow_no_match?: boolean + force?: boolean +} +---- + +[discrete] +===== `MlStopTrainedModelDeploymentResponse` + +[source,ts] +---- +interface MlStopTrainedModelDeploymentResponse { + stopped: boolean +} +---- + diff --git a/docs/reference-ml-update_data_frame_analytics.asciidoc b/docs/reference-ml-update_data_frame_analytics.asciidoc new file mode 100644 index 000000000..333700a67 --- /dev/null +++ b/docs/reference-ml-update_data_frame_analytics.asciidoc @@ -0,0 +1,77 @@ +[[reference-ml-update_data_frame_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.updateDataFrameAnalytics + +Update a data frame analytics job. + +{ref}/update-dfanalytics.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlUpdateDataFrameAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `MlUpdateDataFrameAnalyticsRequest` + +[source,ts] +---- +interface MlUpdateDataFrameAnalyticsRequest extends <> { + id: <> + description?: string + model_memory_limit?: string + max_num_threads?: <> + allow_lazy_start?: boolean +} +---- + +[discrete] +===== `MlUpdateDataFrameAnalyticsResponse` + +[source,ts] +---- +interface MlUpdateDataFrameAnalyticsResponse { + authorization?: MlDataframeAnalyticsAuthorization + allow_lazy_start: boolean + analysis: MlDataframeAnalysisContainer + analyzed_fields?: MlDataframeAnalysisAnalyzedFields | string[] + create_time: <> + description?: string + dest: MlDataframeAnalyticsDestination + id: <> + max_num_threads: <> + model_memory_limit: string + source: MlDataframeAnalyticsSource + version: <> +} +---- + diff --git a/docs/reference-ml-update_datafeed.asciidoc b/docs/reference-ml-update_datafeed.asciidoc new file mode 100644 index 000000000..5c5491812 --- /dev/null +++ b/docs/reference-ml-update_datafeed.asciidoc @@ -0,0 +1,95 @@ +[[reference-ml-update_datafeed]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.updateDatafeed + +Update a datafeed. You must stop and start the datafeed for the changes to be applied. When Elasticsearch security features are enabled, your datafeed remembers which roles the user who updated it had at the time of the update and runs the query using those same roles. If you provide secondary authorization headers, those credentials are used instead. + +{ref}/ml-update-datafeed.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlUpdateDatafeedRequest, options?): Promise +---- + +[discrete] +===== `MlUpdateDatafeedRequest` + +[source,ts] +---- +interface MlUpdateDatafeedRequest extends <> { + datafeed_id: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + aggregations?: Record + chunking_config?: MlChunkingConfig + delayed_data_check_config?: MlDelayedDataCheckConfig + frequency?: <> + indices?: string[] + /** @alias indices */ + indexes?: string[] + indices_options?: <> + job_id?: <> + max_empty_searches?: <> + query?: QueryDslQueryContainer + query_delay?: <> + runtime_mappings?: MappingRuntimeFields + script_fields?: Record>> + scroll_size?: <> +} +---- + +[discrete] +===== `MlUpdateDatafeedResponse` + +[source,ts] +---- +interface MlUpdateDatafeedResponse { + authorization?: MlDatafeedAuthorization + aggregations?: Record + chunking_config: MlChunkingConfig + delayed_data_check_config?: MlDelayedDataCheckConfig + datafeed_id: <> + frequency?: <> + indices: string[] + indices_options?: <> + job_id: <> + max_empty_searches?: <> + query: QueryDslQueryContainer + query_delay: <> + runtime_mappings?: MappingRuntimeFields + script_fields?: Record>> + scroll_size: <> +} +---- + diff --git a/docs/reference-ml-update_filter.asciidoc b/docs/reference-ml-update_filter.asciidoc new file mode 100644 index 000000000..844720385 --- /dev/null +++ b/docs/reference-ml-update_filter.asciidoc @@ -0,0 +1,67 @@ +[[reference-ml-update_filter]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.updateFilter + +Update a filter. Updates the description of a filter, adds items, or removes items from the list. + +{ref}/ml-update-filter.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlUpdateFilterRequest, options?): Promise +---- + +[discrete] +===== `MlUpdateFilterRequest` + +[source,ts] +---- +interface MlUpdateFilterRequest extends <> { + filter_id: <> + add_items?: string[] + description?: string + remove_items?: string[] +} +---- + +[discrete] +===== `MlUpdateFilterResponse` + +[source,ts] +---- +interface MlUpdateFilterResponse { + description: string + filter_id: <> + items: string[] +} +---- + diff --git a/docs/reference-ml-update_job.asciidoc b/docs/reference-ml-update_job.asciidoc new file mode 100644 index 000000000..ce235cc6d --- /dev/null +++ b/docs/reference-ml-update_job.asciidoc @@ -0,0 +1,97 @@ +[[reference-ml-update_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.updateJob + +Update an anomaly detection job. Updates certain properties of an anomaly detection job. + +{ref}/ml-update-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlUpdateJobRequest, options?): Promise +---- + +[discrete] +===== `MlUpdateJobRequest` + +[source,ts] +---- +interface MlUpdateJobRequest extends <> { + job_id: <> + allow_lazy_open?: boolean + analysis_limits?: MlAnalysisMemoryLimit + background_persist_interval?: <> + custom_settings?: Record + categorization_filters?: string[] + description?: string + model_plot_config?: MlModelPlotConfig + model_prune_window?: <> + daily_model_snapshot_retention_after_days?: <> + model_snapshot_retention_days?: <> + renormalization_window_days?: <> + results_retention_days?: <> + groups?: string[] + detectors?: MlDetector[] + per_partition_categorization?: MlPerPartitionCategorization +} +---- + +[discrete] +===== `MlUpdateJobResponse` + +[source,ts] +---- +interface MlUpdateJobResponse { + allow_lazy_open: boolean + analysis_config: MlAnalysisConfigRead + analysis_limits: MlAnalysisLimits + background_persist_interval?: <> + create_time: <><<>> + finished_time?: <><<>> + custom_settings?: Record + daily_model_snapshot_retention_after_days: <> + data_description: MlDataDescription + datafeed_config?: MlDatafeed + description?: string + groups?: string[] + job_id: <> + job_type: string + job_version: <> + model_plot_config?: MlModelPlotConfig + model_snapshot_id?: <> + model_snapshot_retention_days: <> + renormalization_window_days?: <> + results_index_name: <> + results_retention_days?: <> +} +---- + diff --git a/docs/reference-ml-update_model_snapshot.asciidoc b/docs/reference-ml-update_model_snapshot.asciidoc new file mode 100644 index 000000000..b03c3d71f --- /dev/null +++ b/docs/reference-ml-update_model_snapshot.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-update_model_snapshot]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.updateModelSnapshot + +Update a snapshot. Updates certain properties of a snapshot. + +{ref}/ml-update-snapshot.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlUpdateModelSnapshotRequest, options?): Promise +---- + +[discrete] +===== `MlUpdateModelSnapshotRequest` + +[source,ts] +---- +interface MlUpdateModelSnapshotRequest extends <> { + job_id: <> + snapshot_id: <> + description?: string + retain?: boolean +} +---- + +[discrete] +===== `MlUpdateModelSnapshotResponse` + +[source,ts] +---- +interface MlUpdateModelSnapshotResponse { + acknowledged: boolean + model: MlModelSnapshot +} +---- + diff --git a/docs/reference-ml-update_trained_model_deployment.asciidoc b/docs/reference-ml-update_trained_model_deployment.asciidoc new file mode 100644 index 000000000..ad9121193 --- /dev/null +++ b/docs/reference-ml-update_trained_model_deployment.asciidoc @@ -0,0 +1,63 @@ +[[reference-ml-update_trained_model_deployment]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.updateTrainedModelDeployment + +Update a trained model deployment. + +{ref}/update-trained-model-deployment.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlUpdateTrainedModelDeploymentRequest, options?): Promise +---- + +[discrete] +===== `MlUpdateTrainedModelDeploymentRequest` + +[source,ts] +---- +interface MlUpdateTrainedModelDeploymentRequest extends <> { + model_id: <> + number_of_allocations?: <> +} +---- + +[discrete] +===== `MlUpdateTrainedModelDeploymentResponse` + +[source,ts] +---- +interface MlUpdateTrainedModelDeploymentResponse { + assignment: MlTrainedModelAssignment +} +---- + diff --git a/docs/reference-ml-upgrade_job_snapshot.asciidoc b/docs/reference-ml-upgrade_job_snapshot.asciidoc new file mode 100644 index 000000000..7c8d0ae0c --- /dev/null +++ b/docs/reference-ml-upgrade_job_snapshot.asciidoc @@ -0,0 +1,66 @@ +[[reference-ml-upgrade_job_snapshot]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ml.upgradeJobSnapshot + +Upgrade a snapshot. Upgrades an anomaly detection model snapshot to the latest major version. Over time, older snapshot formats are deprecated and removed. Anomaly detection jobs support only snapshots that are from the current or previous major version. This API provides a means to upgrade a snapshot to the current major version. This aids in preparing the cluster for an upgrade to the next major version. Only one snapshot per anomaly detection job can be upgraded at a time and the upgraded snapshot cannot be the current snapshot of the anomaly detection job. + +{ref}/ml-upgrade-job-model-snapshot.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MlUpgradeJobSnapshotRequest, options?): Promise +---- + +[discrete] +===== `MlUpgradeJobSnapshotRequest` + +[source,ts] +---- +interface MlUpgradeJobSnapshotRequest extends <> { + job_id: <> + snapshot_id: <> + wait_for_completion?: boolean + timeout?: <> +} +---- + +[discrete] +===== `MlUpgradeJobSnapshotResponse` + +[source,ts] +---- +interface MlUpgradeJobSnapshotResponse { + node: <> + completed: boolean +} +---- + diff --git a/docs/reference-monitoring-bulk.asciidoc b/docs/reference-monitoring-bulk.asciidoc new file mode 100644 index 000000000..071ba92ba --- /dev/null +++ b/docs/reference-monitoring-bulk.asciidoc @@ -0,0 +1,69 @@ +[[reference-monitoring-bulk]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.monitoring.bulk + +Used by the monitoring features to send monitoring data. + +{ref}/monitor-elasticsearch-cluster.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MonitoringBulkRequest, options?): Promise +---- + +[discrete] +===== `MonitoringBulkRequest` + +[source,ts] +---- +interface MonitoringBulkRequest extends <> { + type?: string + system_id: string + system_api_version: string + interval: <> + operations?: (BulkOperationContainer | BulkUpdateAction | TDocument)[] +} +---- + +[discrete] +===== `MonitoringBulkResponse` + +[source,ts] +---- +interface MonitoringBulkResponse { + error?: <> + errors: boolean + ignored: boolean + took: <> +} +---- + diff --git a/docs/reference-msearch.asciidoc b/docs/reference-msearch.asciidoc new file mode 100644 index 000000000..e1f2a89ca --- /dev/null +++ b/docs/reference-msearch.asciidoc @@ -0,0 +1,74 @@ +[[reference-msearch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.msearch + +Run multiple searches. The format of the request is similar to the bulk API format and makes use of the newline delimited JSON (NDJSON) format. The structure is as follows: ``` header\n body\n header\n body\n ``` This structure is specifically optimized to reduce parsing if a specific search ends up redirected to another node. IMPORTANT: The final line of data must end with a newline character `\n`. Each newline character may be preceded by a carriage return `\r`. When sending requests to this endpoint the `Content-Type` header should be set to `application/x-ndjson`. + +{ref}/search-multi-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MsearchRequest, options?): Promise +---- + +[discrete] +===== `MsearchRequest` + +[source,ts] +---- +interface MsearchRequest extends <> { + index?: <> + allow_no_indices?: boolean + ccs_minimize_roundtrips?: boolean + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + include_named_queries_score?: boolean + max_concurrent_searches?: <> + max_concurrent_shard_requests?: <> + pre_filter_shard_size?: <> + rest_total_hits_as_int?: boolean + routing?: <> + search_type?: <> + typed_keys?: boolean + searches?: MsearchRequestItem[] +} +---- + +[discrete] +===== `MsearchResponse` + +[source,ts] +---- +type MsearchResponse>, AggregationsAggregate>> = MsearchMultiSearchResult +---- + diff --git a/docs/reference-msearch_template.asciidoc b/docs/reference-msearch_template.asciidoc new file mode 100644 index 000000000..ae866f2cf --- /dev/null +++ b/docs/reference-msearch_template.asciidoc @@ -0,0 +1,66 @@ +[[reference-msearch_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.msearchTemplate + +Run multiple templated searches. + +{ref}/search-multi-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MsearchTemplateRequest, options?): Promise +---- + +[discrete] +===== `MsearchTemplateRequest` + +[source,ts] +---- +interface MsearchTemplateRequest extends <> { + index?: <> + ccs_minimize_roundtrips?: boolean + max_concurrent_searches?: <> + search_type?: <> + rest_total_hits_as_int?: boolean + typed_keys?: boolean + search_templates?: MsearchTemplateRequestItem[] +} +---- + +[discrete] +===== `MsearchTemplateResponse` + +[source,ts] +---- +type MsearchTemplateResponse>, AggregationsAggregate>> = MsearchMultiSearchResult +---- + diff --git a/docs/reference-mtermvectors.asciidoc b/docs/reference-mtermvectors.asciidoc new file mode 100644 index 000000000..9485d37a0 --- /dev/null +++ b/docs/reference-mtermvectors.asciidoc @@ -0,0 +1,75 @@ +[[reference-mtermvectors]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.mtermvectors + +Get multiple term vectors. You can specify existing documents by index and ID or provide artificial documents in the body of the request. You can specify the index in the request body or request URI. The response contains a `docs` array with all the fetched termvectors. Each element has the structure provided by the termvectors API. + +{ref}/docs-multi-termvectors.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(MtermvectorsRequest, options?): Promise +---- + +[discrete] +===== `MtermvectorsRequest` + +[source,ts] +---- +interface MtermvectorsRequest extends <> { + index?: <> + fields?: <> + field_statistics?: boolean + offsets?: boolean + payloads?: boolean + positions?: boolean + preference?: string + realtime?: boolean + routing?: <> + term_statistics?: boolean + version?: <> + version_type?: <> + docs?: MtermvectorsOperation[] + ids?: <>[] +} +---- + +[discrete] +===== `MtermvectorsResponse` + +[source,ts] +---- +interface MtermvectorsResponse { + docs: MtermvectorsTermVectorsResult[] +} +---- + diff --git a/docs/reference-nodes-clear_repositories_metering_archive.asciidoc b/docs/reference-nodes-clear_repositories_metering_archive.asciidoc new file mode 100644 index 000000000..43d8f0b8d --- /dev/null +++ b/docs/reference-nodes-clear_repositories_metering_archive.asciidoc @@ -0,0 +1,61 @@ +[[reference-nodes-clear_repositories_metering_archive]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.nodes.clearRepositoriesMeteringArchive + +You can use this API to clear the archived repositories metering information in the cluster. + +{ref}/clear-repositories-metering-archive-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(NodesClearRepositoriesMeteringArchiveRequest, options?): Promise +---- + +[discrete] +===== `NodesClearRepositoriesMeteringArchiveRequest` + +[source,ts] +---- +interface NodesClearRepositoriesMeteringArchiveRequest extends <> { + node_id: <> + max_archive_version: <> +} +---- + +[discrete] +===== `NodesClearRepositoriesMeteringArchiveResponse` + +[source,ts] +---- +type NodesClearRepositoriesMeteringArchiveResponse = NodesClearRepositoriesMeteringArchiveResponseBase +---- + diff --git a/docs/reference-nodes-get_repositories_metering_info.asciidoc b/docs/reference-nodes-get_repositories_metering_info.asciidoc new file mode 100644 index 000000000..9aead8537 --- /dev/null +++ b/docs/reference-nodes-get_repositories_metering_info.asciidoc @@ -0,0 +1,60 @@ +[[reference-nodes-get_repositories_metering_info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.nodes.getRepositoriesMeteringInfo + +You can use the cluster repositories metering API to retrieve repositories metering information in a cluster. This API exposes monotonically non-decreasing counters and it’s expected that clients would durably store the information needed to compute aggregations over a period of time. Additionally, the information exposed by this API is volatile, meaning that it won’t be present after node restarts. + +{ref}/get-repositories-metering-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(NodesGetRepositoriesMeteringInfoRequest, options?): Promise +---- + +[discrete] +===== `NodesGetRepositoriesMeteringInfoRequest` + +[source,ts] +---- +interface NodesGetRepositoriesMeteringInfoRequest extends <> { + node_id: <> +} +---- + +[discrete] +===== `NodesGetRepositoriesMeteringInfoResponse` + +[source,ts] +---- +type NodesGetRepositoriesMeteringInfoResponse = NodesGetRepositoriesMeteringInfoResponseBase +---- + diff --git a/docs/reference-nodes-hot_threads.asciidoc b/docs/reference-nodes-hot_threads.asciidoc new file mode 100644 index 000000000..8e4460b14 --- /dev/null +++ b/docs/reference-nodes-hot_threads.asciidoc @@ -0,0 +1,69 @@ +[[reference-nodes-hot_threads]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.nodes.hotThreads + +This API yields a breakdown of the hot threads on each selected node in the cluster. The output is plain text with a breakdown of each node’s top hot threads. + +{ref}/cluster-nodes-hot-threads.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(NodesHotThreadsRequest, options?): Promise +---- + +[discrete] +===== `NodesHotThreadsRequest` + +[source,ts] +---- +interface NodesHotThreadsRequest extends <> { + node_id?: <> + ignore_idle_threads?: boolean + interval?: <> + snapshots?: <> + master_timeout?: <> + threads?: <> + timeout?: <> + type?: <> + sort?: <> +} +---- + +[discrete] +===== `NodesHotThreadsResponse` + +[source,ts] +---- +interface NodesHotThreadsResponse { +} +---- + diff --git a/docs/reference-nodes-info.asciidoc b/docs/reference-nodes-info.asciidoc new file mode 100644 index 000000000..3aa5ec737 --- /dev/null +++ b/docs/reference-nodes-info.asciidoc @@ -0,0 +1,64 @@ +[[reference-nodes-info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.nodes.info + +Returns cluster nodes information. + +{ref}/cluster-nodes-info.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(NodesInfoRequest, options?): Promise +---- + +[discrete] +===== `NodesInfoRequest` + +[source,ts] +---- +interface NodesInfoRequest extends <> { + node_id?: <> + metric?: <> + flat_settings?: boolean + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `NodesInfoResponse` + +[source,ts] +---- +type NodesInfoResponse = NodesInfoResponseBase +---- + diff --git a/docs/reference-nodes-reload_secure_settings.asciidoc b/docs/reference-nodes-reload_secure_settings.asciidoc new file mode 100644 index 000000000..5f8575c89 --- /dev/null +++ b/docs/reference-nodes-reload_secure_settings.asciidoc @@ -0,0 +1,62 @@ +[[reference-nodes-reload_secure_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.nodes.reloadSecureSettings + +Reloads the keystore on nodes in the cluster. + +{ref}/secure-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(NodesReloadSecureSettingsRequest, options?): Promise +---- + +[discrete] +===== `NodesReloadSecureSettingsRequest` + +[source,ts] +---- +interface NodesReloadSecureSettingsRequest extends <> { + node_id?: <> + timeout?: <> + secure_settings_password?: <> +} +---- + +[discrete] +===== `NodesReloadSecureSettingsResponse` + +[source,ts] +---- +type NodesReloadSecureSettingsResponse = NodesReloadSecureSettingsResponseBase +---- + diff --git a/docs/reference-nodes-stats.asciidoc b/docs/reference-nodes-stats.asciidoc new file mode 100644 index 000000000..93fe3f660 --- /dev/null +++ b/docs/reference-nodes-stats.asciidoc @@ -0,0 +1,72 @@ +[[reference-nodes-stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.nodes.stats + +Returns cluster nodes statistics. + +{ref}/cluster-nodes-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(NodesStatsRequest, options?): Promise +---- + +[discrete] +===== `NodesStatsRequest` + +[source,ts] +---- +interface NodesStatsRequest extends <> { + node_id?: <> + metric?: <> + index_metric?: <> + completion_fields?: <> + fielddata_fields?: <> + fields?: <> + groups?: boolean + include_segment_file_sizes?: boolean + level?: <> + master_timeout?: <> + timeout?: <> + types?: string[] + include_unloaded_segments?: boolean +} +---- + +[discrete] +===== `NodesStatsResponse` + +[source,ts] +---- +type NodesStatsResponse = NodesStatsResponseBase +---- + diff --git a/docs/reference-nodes-usage.asciidoc b/docs/reference-nodes-usage.asciidoc new file mode 100644 index 000000000..33bb7ae2c --- /dev/null +++ b/docs/reference-nodes-usage.asciidoc @@ -0,0 +1,62 @@ +[[reference-nodes-usage]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.nodes.usage + +Returns information on the usage of features. + +{ref}/cluster-nodes-usage.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(NodesUsageRequest, options?): Promise +---- + +[discrete] +===== `NodesUsageRequest` + +[source,ts] +---- +interface NodesUsageRequest extends <> { + node_id?: <> + metric?: <> + timeout?: <> +} +---- + +[discrete] +===== `NodesUsageResponse` + +[source,ts] +---- +type NodesUsageResponse = NodesUsageResponseBase +---- + diff --git a/docs/reference-open_point_in_time.asciidoc b/docs/reference-open_point_in_time.asciidoc new file mode 100644 index 000000000..34810c53a --- /dev/null +++ b/docs/reference-open_point_in_time.asciidoc @@ -0,0 +1,69 @@ +[[reference-open_point_in_time]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.openPointInTime + +Open a point in time. A search request by default runs against the most recent visible data of the target indices, which is called point in time. Elasticsearch pit (point in time) is a lightweight view into the state of the data as it existed when initiated. In some cases, it’s preferred to perform multiple search requests using the same point in time. For example, if refreshes happen between `search_after` requests, then the results of those requests might not be consistent as changes happening between searches are only visible to the more recent point in time. A point in time must be opened explicitly before being used in search requests. The `keep_alive` parameter tells Elasticsearch how long it should persist. + +{ref}/point-in-time-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(OpenPointInTimeRequest, options?): Promise +---- + +[discrete] +===== `OpenPointInTimeRequest` + +[source,ts] +---- +interface OpenPointInTimeRequest extends <> { + index: <> + keep_alive: <> + ignore_unavailable?: boolean + preference?: string + routing?: <> + expand_wildcards?: <> + index_filter?: QueryDslQueryContainer +} +---- + +[discrete] +===== `OpenPointInTimeResponse` + +[source,ts] +---- +interface OpenPointInTimeResponse { + _shards: <> + id: <> +} +---- + diff --git a/docs/reference-ping.asciidoc b/docs/reference-ping.asciidoc new file mode 100644 index 000000000..f61278558 --- /dev/null +++ b/docs/reference-ping.asciidoc @@ -0,0 +1,59 @@ +[[reference-ping]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ping + +Ping the cluster. Returns whether the cluster is running. + +{ref}/index.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(PingRequest, options?): Promise +---- + +[discrete] +===== `PingRequest` + +[source,ts] +---- +interface PingRequest extends <> { +} +---- + +[discrete] +===== `PingResponse` + +[source,ts] +---- +type PingResponse = boolean +---- + diff --git a/docs/reference-put_script.asciidoc b/docs/reference-put_script.asciidoc new file mode 100644 index 000000000..c84d0e5c9 --- /dev/null +++ b/docs/reference-put_script.asciidoc @@ -0,0 +1,64 @@ +[[reference-put_script]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.putScript + +Create or update a script or search template. Creates or updates a stored script or search template. + +{ref}/modules-scripting.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(PutScriptRequest, options?): Promise +---- + +[discrete] +===== `PutScriptRequest` + +[source,ts] +---- +interface PutScriptRequest extends <> { + id: <> + context?: <> + master_timeout?: <> + timeout?: <> + script: <> +} +---- + +[discrete] +===== `PutScriptResponse` + +[source,ts] +---- +type PutScriptResponse = <> +---- + diff --git a/docs/reference-query_rules-delete_rule.asciidoc b/docs/reference-query_rules-delete_rule.asciidoc new file mode 100644 index 000000000..0aa7ea40c --- /dev/null +++ b/docs/reference-query_rules-delete_rule.asciidoc @@ -0,0 +1,61 @@ +[[reference-query_rules-delete_rule]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.deleteRule + +Deletes a query rule within a query ruleset. + +{ref}/delete-query-rule.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesDeleteRuleRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesDeleteRuleRequest` + +[source,ts] +---- +interface QueryRulesDeleteRuleRequest extends <> { + ruleset_id: <> + rule_id: <> +} +---- + +[discrete] +===== `QueryRulesDeleteRuleResponse` + +[source,ts] +---- +type QueryRulesDeleteRuleResponse = <> +---- + diff --git a/docs/reference-query_rules-delete_ruleset.asciidoc b/docs/reference-query_rules-delete_ruleset.asciidoc new file mode 100644 index 000000000..79b7accfd --- /dev/null +++ b/docs/reference-query_rules-delete_ruleset.asciidoc @@ -0,0 +1,60 @@ +[[reference-query_rules-delete_ruleset]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.deleteRuleset + +Deletes a query ruleset. + +{ref}/delete-query-ruleset.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesDeleteRulesetRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesDeleteRulesetRequest` + +[source,ts] +---- +interface QueryRulesDeleteRulesetRequest extends <> { + ruleset_id: <> +} +---- + +[discrete] +===== `QueryRulesDeleteRulesetResponse` + +[source,ts] +---- +type QueryRulesDeleteRulesetResponse = <> +---- + diff --git a/docs/reference-query_rules-get_rule.asciidoc b/docs/reference-query_rules-get_rule.asciidoc new file mode 100644 index 000000000..3bfae550c --- /dev/null +++ b/docs/reference-query_rules-get_rule.asciidoc @@ -0,0 +1,61 @@ +[[reference-query_rules-get_rule]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.getRule + +Returns the details about a query rule within a query ruleset + +{ref}/get-query-rule.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesGetRuleRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesGetRuleRequest` + +[source,ts] +---- +interface QueryRulesGetRuleRequest extends <> { + ruleset_id: <> + rule_id: <> +} +---- + +[discrete] +===== `QueryRulesGetRuleResponse` + +[source,ts] +---- +type QueryRulesGetRuleResponse = QueryRulesQueryRule +---- + diff --git a/docs/reference-query_rules-get_ruleset.asciidoc b/docs/reference-query_rules-get_ruleset.asciidoc new file mode 100644 index 000000000..406426fb5 --- /dev/null +++ b/docs/reference-query_rules-get_ruleset.asciidoc @@ -0,0 +1,60 @@ +[[reference-query_rules-get_ruleset]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.getRuleset + +Returns the details about a query ruleset + +{ref}/get-query-ruleset.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesGetRulesetRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesGetRulesetRequest` + +[source,ts] +---- +interface QueryRulesGetRulesetRequest extends <> { + ruleset_id: <> +} +---- + +[discrete] +===== `QueryRulesGetRulesetResponse` + +[source,ts] +---- +type QueryRulesGetRulesetResponse = QueryRulesQueryRuleset +---- + diff --git a/docs/reference-query_rules-list_rulesets.asciidoc b/docs/reference-query_rules-list_rulesets.asciidoc new file mode 100644 index 000000000..aea990d15 --- /dev/null +++ b/docs/reference-query_rules-list_rulesets.asciidoc @@ -0,0 +1,64 @@ +[[reference-query_rules-list_rulesets]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.listRulesets + +Returns summarized information about existing query rulesets. + +{ref}/list-query-rulesets.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesListRulesetsRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesListRulesetsRequest` + +[source,ts] +---- +interface QueryRulesListRulesetsRequest extends <> { + from?: <> + size?: <> +} +---- + +[discrete] +===== `QueryRulesListRulesetsResponse` + +[source,ts] +---- +interface QueryRulesListRulesetsResponse { + count: <> + results: QueryRulesListRulesetsQueryRulesetListItem[] +} +---- + diff --git a/docs/reference-query_rules-put_rule.asciidoc b/docs/reference-query_rules-put_rule.asciidoc new file mode 100644 index 000000000..d029012e6 --- /dev/null +++ b/docs/reference-query_rules-put_rule.asciidoc @@ -0,0 +1,67 @@ +[[reference-query_rules-put_rule]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.putRule + +Creates or updates a query rule within a query ruleset. + +{ref}/put-query-rule.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesPutRuleRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesPutRuleRequest` + +[source,ts] +---- +interface QueryRulesPutRuleRequest extends <> { + ruleset_id: <> + rule_id: <> + type: QueryRulesQueryRuleType + criteria: QueryRulesQueryRuleCriteria | QueryRulesQueryRuleCriteria[] + actions: QueryRulesQueryRuleActions + priority?: <> +} +---- + +[discrete] +===== `QueryRulesPutRuleResponse` + +[source,ts] +---- +interface QueryRulesPutRuleResponse { + result: <> +} +---- + diff --git a/docs/reference-query_rules-put_ruleset.asciidoc b/docs/reference-query_rules-put_ruleset.asciidoc new file mode 100644 index 000000000..ad658c0f5 --- /dev/null +++ b/docs/reference-query_rules-put_ruleset.asciidoc @@ -0,0 +1,63 @@ +[[reference-query_rules-put_ruleset]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.putRuleset + +Creates or updates a query ruleset. + +{ref}/put-query-ruleset.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesPutRulesetRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesPutRulesetRequest` + +[source,ts] +---- +interface QueryRulesPutRulesetRequest extends <> { + ruleset_id: <> + rules: QueryRulesQueryRule | QueryRulesQueryRule[] +} +---- + +[discrete] +===== `QueryRulesPutRulesetResponse` + +[source,ts] +---- +interface QueryRulesPutRulesetResponse { + result: <> +} +---- + diff --git a/docs/reference-query_rules-test.asciidoc b/docs/reference-query_rules-test.asciidoc new file mode 100644 index 000000000..7c9e19a48 --- /dev/null +++ b/docs/reference-query_rules-test.asciidoc @@ -0,0 +1,64 @@ +[[reference-query_rules-test]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.queryRules.test + +Creates or updates a query ruleset. + +{ref}/test-query-ruleset.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(QueryRulesTestRequest, options?): Promise +---- + +[discrete] +===== `QueryRulesTestRequest` + +[source,ts] +---- +interface QueryRulesTestRequest extends <> { + ruleset_id: <> + match_criteria: Record +} +---- + +[discrete] +===== `QueryRulesTestResponse` + +[source,ts] +---- +interface QueryRulesTestResponse { + total_matched_rules: <> + matched_rules: QueryRulesTestQueryRulesetMatchedRule[] +} +---- + diff --git a/docs/reference-rank_eval.asciidoc b/docs/reference-rank_eval.asciidoc new file mode 100644 index 000000000..7c058b90f --- /dev/null +++ b/docs/reference-rank_eval.asciidoc @@ -0,0 +1,70 @@ +[[reference-rank_eval]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rankEval + +Evaluate ranked search results. Evaluate the quality of ranked search results over a set of typical search queries. + +{ref}/search-rank-eval.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RankEvalRequest, options?): Promise +---- + +[discrete] +===== `RankEvalRequest` + +[source,ts] +---- +interface RankEvalRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + search_type?: string + requests: RankEvalRankEvalRequestItem[] + metric?: RankEvalRankEvalMetric +} +---- + +[discrete] +===== `RankEvalResponse` + +[source,ts] +---- +interface RankEvalResponse { + metric_score: <> + details: Record<<>, RankEvalRankEvalMetricDetail> + failures: Record +} +---- + diff --git a/docs/reference-reindex.asciidoc b/docs/reference-reindex.asciidoc new file mode 100644 index 000000000..ff4ac3374 --- /dev/null +++ b/docs/reference-reindex.asciidoc @@ -0,0 +1,90 @@ +[[reference-reindex]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.reindex + +Reindex documents. Copies documents from a source to a destination. The source can be any existing index, alias, or data stream. The destination must differ from the source. For example, you cannot reindex a data stream into itself. + +{ref}/docs-reindex.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ReindexRequest, options?): Promise +---- + +[discrete] +===== `ReindexRequest` + +[source,ts] +---- +interface ReindexRequest extends <> { + refresh?: boolean + requests_per_second?: <> + scroll?: <> + slices?: <> + timeout?: <> + wait_for_active_shards?: <> + wait_for_completion?: boolean + require_alias?: boolean + conflicts?: <> + dest: ReindexDestination + max_docs?: <> + script?: <> | string + size?: <> + source: ReindexSource +} +---- + +[discrete] +===== `ReindexResponse` + +[source,ts] +---- +interface ReindexResponse { + batches?: <> + created?: <> + deleted?: <> + failures?: <>[] + noops?: <> + retries?: <> + requests_per_second?: <> + slice_id?: <> + task?: <> + throttled_millis?: <><<>> + throttled_until_millis?: <><<>> + timed_out?: boolean + took?: <><<>> + total?: <> + updated?: <> + version_conflicts?: <> +} +---- + diff --git a/docs/reference-reindex_rethrottle.asciidoc b/docs/reference-reindex_rethrottle.asciidoc new file mode 100644 index 000000000..de6ee560d --- /dev/null +++ b/docs/reference-reindex_rethrottle.asciidoc @@ -0,0 +1,63 @@ +[[reference-reindex_rethrottle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.reindexRethrottle + +Throttle a reindex operation. Change the number of requests per second for a particular reindex operation. + +{ref}/docs-reindex.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ReindexRethrottleRequest, options?): Promise +---- + +[discrete] +===== `ReindexRethrottleRequest` + +[source,ts] +---- +interface ReindexRethrottleRequest extends <> { + task_id: <> + requests_per_second?: <> +} +---- + +[discrete] +===== `ReindexRethrottleResponse` + +[source,ts] +---- +interface ReindexRethrottleResponse { + nodes: Record +} +---- + diff --git a/docs/reference-render_search_template.asciidoc b/docs/reference-render_search_template.asciidoc new file mode 100644 index 000000000..9ee5d601e --- /dev/null +++ b/docs/reference-render_search_template.asciidoc @@ -0,0 +1,65 @@ +[[reference-render_search_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.renderSearchTemplate + +Render a search template. Render a search template as a search request body. + +{ref}/render-search-template-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RenderSearchTemplateRequest, options?): Promise +---- + +[discrete] +===== `RenderSearchTemplateRequest` + +[source,ts] +---- +interface RenderSearchTemplateRequest extends <> { + id?: <> + file?: string + params?: Record + source?: string +} +---- + +[discrete] +===== `RenderSearchTemplateResponse` + +[source,ts] +---- +interface RenderSearchTemplateResponse { + template_output: Record +} +---- + diff --git a/docs/reference-rollup-delete_job.asciidoc b/docs/reference-rollup-delete_job.asciidoc new file mode 100644 index 000000000..5d9af2be9 --- /dev/null +++ b/docs/reference-rollup-delete_job.asciidoc @@ -0,0 +1,63 @@ +[[reference-rollup-delete_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.deleteJob + +Deletes an existing rollup job. + +{ref}/rollup-delete-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupDeleteJobRequest, options?): Promise +---- + +[discrete] +===== `RollupDeleteJobRequest` + +[source,ts] +---- +interface RollupDeleteJobRequest extends <> { + id: <> +} +---- + +[discrete] +===== `RollupDeleteJobResponse` + +[source,ts] +---- +interface RollupDeleteJobResponse { + acknowledged: boolean + task_failures?: <>[] +} +---- + diff --git a/docs/reference-rollup-get_jobs.asciidoc b/docs/reference-rollup-get_jobs.asciidoc new file mode 100644 index 000000000..f6e31f424 --- /dev/null +++ b/docs/reference-rollup-get_jobs.asciidoc @@ -0,0 +1,62 @@ +[[reference-rollup-get_jobs]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.getJobs + +Retrieves the configuration, stats, and status of rollup jobs. + +{ref}/rollup-get-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupGetJobsRequest, options?): Promise +---- + +[discrete] +===== `RollupGetJobsRequest` + +[source,ts] +---- +interface RollupGetJobsRequest extends <> { + id?: <> +} +---- + +[discrete] +===== `RollupGetJobsResponse` + +[source,ts] +---- +interface RollupGetJobsResponse { + jobs: RollupGetJobsRollupJob[] +} +---- + diff --git a/docs/reference-rollup-get_rollup_caps.asciidoc b/docs/reference-rollup-get_rollup_caps.asciidoc new file mode 100644 index 000000000..58b0431ff --- /dev/null +++ b/docs/reference-rollup-get_rollup_caps.asciidoc @@ -0,0 +1,60 @@ +[[reference-rollup-get_rollup_caps]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.getRollupCaps + +Returns the capabilities of any rollup jobs that have been configured for a specific index or index pattern. + +{ref}/rollup-get-rollup-caps.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupGetRollupCapsRequest, options?): Promise +---- + +[discrete] +===== `RollupGetRollupCapsRequest` + +[source,ts] +---- +interface RollupGetRollupCapsRequest extends <> { + id?: <> +} +---- + +[discrete] +===== `RollupGetRollupCapsResponse` + +[source,ts] +---- +type RollupGetRollupCapsResponse = Record<<>, RollupGetRollupCapsRollupCapabilities> +---- + diff --git a/docs/reference-rollup-get_rollup_index_caps.asciidoc b/docs/reference-rollup-get_rollup_index_caps.asciidoc new file mode 100644 index 000000000..727bf713b --- /dev/null +++ b/docs/reference-rollup-get_rollup_index_caps.asciidoc @@ -0,0 +1,60 @@ +[[reference-rollup-get_rollup_index_caps]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.getRollupIndexCaps + +Returns the rollup capabilities of all jobs inside of a rollup index (for example, the index where rollup data is stored). + +{ref}/rollup-get-rollup-index-caps.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupGetRollupIndexCapsRequest, options?): Promise +---- + +[discrete] +===== `RollupGetRollupIndexCapsRequest` + +[source,ts] +---- +interface RollupGetRollupIndexCapsRequest extends <> { + index: <> +} +---- + +[discrete] +===== `RollupGetRollupIndexCapsResponse` + +[source,ts] +---- +type RollupGetRollupIndexCapsResponse = Record<<>, RollupGetRollupIndexCapsIndexCapabilities> +---- + diff --git a/docs/reference-rollup-put_job.asciidoc b/docs/reference-rollup-put_job.asciidoc new file mode 100644 index 000000000..414e18b67 --- /dev/null +++ b/docs/reference-rollup-put_job.asciidoc @@ -0,0 +1,68 @@ +[[reference-rollup-put_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.putJob + +Creates a rollup job. + +{ref}/rollup-put-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupPutJobRequest, options?): Promise +---- + +[discrete] +===== `RollupPutJobRequest` + +[source,ts] +---- +interface RollupPutJobRequest extends <> { + id: <> + cron: string + groups: RollupGroupings + index_pattern: string + metrics?: RollupFieldMetric[] + page_size: <> + rollup_index: <> + timeout?: <> + headers?: <> +} +---- + +[discrete] +===== `RollupPutJobResponse` + +[source,ts] +---- +type RollupPutJobResponse = <> +---- + diff --git a/docs/reference-rollup-rollup_search.asciidoc b/docs/reference-rollup-rollup_search.asciidoc new file mode 100644 index 000000000..c34e99e02 --- /dev/null +++ b/docs/reference-rollup-rollup_search.asciidoc @@ -0,0 +1,74 @@ +[[reference-rollup-rollup_search]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.rollupSearch + +Enables searching rolled-up data using the standard Query DSL. + +{ref}/rollup-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupRollupSearchRequest, options?): Promise +---- + +[discrete] +===== `RollupRollupSearchRequest` + +[source,ts] +---- +interface RollupRollupSearchRequest extends <> { + index: <> + rest_total_hits_as_int?: boolean + typed_keys?: boolean + aggregations?: Record + /** @alias aggregations */ + aggs?: Record + query?: QueryDslQueryContainer + size?: <> +} +---- + +[discrete] +===== `RollupRollupSearchResponse` + +[source,ts] +---- +interface RollupRollupSearchResponse>, AggregationsAggregate>> { + took: <> + timed_out: boolean + terminated_early?: boolean + _shards: <> + hits: SearchHitsMetadata + aggregations?: TAggregations +} +---- + diff --git a/docs/reference-rollup-start_job.asciidoc b/docs/reference-rollup-start_job.asciidoc new file mode 100644 index 000000000..c6c896d24 --- /dev/null +++ b/docs/reference-rollup-start_job.asciidoc @@ -0,0 +1,62 @@ +[[reference-rollup-start_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.startJob + +Starts an existing, stopped rollup job. + +{ref}/rollup-start-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupStartJobRequest, options?): Promise +---- + +[discrete] +===== `RollupStartJobRequest` + +[source,ts] +---- +interface RollupStartJobRequest extends <> { + id: <> +} +---- + +[discrete] +===== `RollupStartJobResponse` + +[source,ts] +---- +interface RollupStartJobResponse { + started: boolean +} +---- + diff --git a/docs/reference-rollup-stop_job.asciidoc b/docs/reference-rollup-stop_job.asciidoc new file mode 100644 index 000000000..b44e0833d --- /dev/null +++ b/docs/reference-rollup-stop_job.asciidoc @@ -0,0 +1,64 @@ +[[reference-rollup-stop_job]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.rollup.stopJob + +Stops an existing, started rollup job. + +{ref}/rollup-stop-job.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(RollupStopJobRequest, options?): Promise +---- + +[discrete] +===== `RollupStopJobRequest` + +[source,ts] +---- +interface RollupStopJobRequest extends <> { + id: <> + timeout?: <> + wait_for_completion?: boolean +} +---- + +[discrete] +===== `RollupStopJobResponse` + +[source,ts] +---- +interface RollupStopJobResponse { + stopped: boolean +} +---- + diff --git a/docs/reference-scripts_painless_execute.asciidoc b/docs/reference-scripts_painless_execute.asciidoc new file mode 100644 index 000000000..edb5d5c79 --- /dev/null +++ b/docs/reference-scripts_painless_execute.asciidoc @@ -0,0 +1,64 @@ +[[reference-scripts_painless_execute]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.scriptsPainlessExecute + +Run a script. Runs a script and returns a result. + +{painless}/painless-execute-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ScriptsPainlessExecuteRequest, options?): Promise +---- + +[discrete] +===== `ScriptsPainlessExecuteRequest` + +[source,ts] +---- +interface ScriptsPainlessExecuteRequest extends <> { + context?: string + context_setup?: ScriptsPainlessExecutePainlessContextSetup + script?: <> | string +} +---- + +[discrete] +===== `ScriptsPainlessExecuteResponse` + +[source,ts] +---- +interface ScriptsPainlessExecuteResponse { + result: TResult +} +---- + diff --git a/docs/reference-scroll.asciidoc b/docs/reference-scroll.asciidoc new file mode 100644 index 000000000..b9ea019a2 --- /dev/null +++ b/docs/reference-scroll.asciidoc @@ -0,0 +1,62 @@ +[[reference-scroll]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.scroll + +Run a scrolling search. IMPORTANT: The scroll API is no longer recommend for deep pagination. If you need to preserve the index state while paging through more than 10,000 hits, use the `search_after` parameter with a point in time (PIT). The scroll API gets large sets of results from a single scrolling search request. To get the necessary scroll ID, submit a search API request that includes an argument for the `scroll` query parameter. The `scroll` parameter indicates how long Elasticsearch should retain the search context for the request. The search response returns a scroll ID in the `_scroll_id` response body parameter. You can then use the scroll ID with the scroll API to retrieve the next batch of results for the request. If the Elasticsearch security features are enabled, the access to the results of a specific scroll ID is restricted to the user or API key that submitted the search. You can also use the scroll API to specify a new scroll parameter that extends or shortens the retention period for the search context. IMPORTANT: Results from a scrolling search reflect the state of the index at the time of the initial search request. Subsequent indexing or document changes only affect later search and scroll requests. + +{ref}/search-request-body.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ScrollRequest, options?): Promise +---- + +[discrete] +===== `ScrollRequest` + +[source,ts] +---- +interface ScrollRequest extends <> { + scroll_id?: <> + rest_total_hits_as_int?: boolean + scroll?: <> +} +---- + +[discrete] +===== `ScrollResponse` + +[source,ts] +---- +type ScrollResponse>, AggregationsAggregate>> = SearchResponseBody +---- + diff --git a/docs/reference-search.asciidoc b/docs/reference-search.asciidoc new file mode 100644 index 000000000..92fe35d13 --- /dev/null +++ b/docs/reference-search.asciidoc @@ -0,0 +1,127 @@ +[[reference-search]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.search + +Run a search. Get search hits that match the query defined in the request. You can provide search queries using the `q` query string parameter or the request body. If both are specified, only the query parameter is used. + +{ref}/search-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchRequest, options?): Promise +---- + +[discrete] +===== `SearchRequest` + +[source,ts] +---- +interface SearchRequest extends <> { + index?: <> + allow_no_indices?: boolean + allow_partial_search_results?: boolean + analyzer?: string + analyze_wildcard?: boolean + batched_reduce_size?: <> + ccs_minimize_roundtrips?: boolean + default_operator?: QueryDslOperator + df?: string + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + include_named_queries_score?: boolean + lenient?: boolean + max_concurrent_shard_requests?: <> + min_compatible_shard_node?: <> + preference?: string + pre_filter_shard_size?: <> + request_cache?: boolean + routing?: <> + scroll?: <> + search_type?: <> + suggest_field?: <> + suggest_mode?: <> + suggest_size?: <> + suggest_text?: string + typed_keys?: boolean + rest_total_hits_as_int?: boolean + _source_excludes?: <> + _source_includes?: <> + q?: string + force_synthetic_source?: boolean + aggregations?: Record + /** @alias aggregations */ + aggs?: Record + collapse?: SearchFieldCollapse + explain?: boolean + ext?: Record + from?: <> + highlight?: SearchHighlight + track_total_hits?: SearchTrackHits + indices_boost?: Record<<>, <>>[] + docvalue_fields?: (QueryDslFieldAndFormat | <>)[] + knn?: <> | <>[] + rank?: <> + min_score?: <> + post_filter?: QueryDslQueryContainer + profile?: boolean + query?: QueryDslQueryContainer + rescore?: SearchRescore | SearchRescore[] + retriever?: <> + script_fields?: Record>> + search_after?: <> + size?: <> + slice?: <> + sort?: <> + _source?: SearchSourceConfig + fields?: (QueryDslFieldAndFormat | <>)[] + suggest?: SearchSuggester + terminate_after?: <> + timeout?: string + track_scores?: boolean + version?: boolean + seq_no_primary_term?: boolean + stored_fields?: <> + pit?: SearchPointInTimeReference + runtime_mappings?: MappingRuntimeFields + stats?: string[] +} +---- + +[discrete] +===== `SearchResponse` + +[source,ts] +---- +type SearchResponse>, AggregationsAggregate>> = SearchResponseBody +---- + diff --git a/docs/reference-search_application-delete.asciidoc b/docs/reference-search_application-delete.asciidoc new file mode 100644 index 000000000..29b058bf9 --- /dev/null +++ b/docs/reference-search_application-delete.asciidoc @@ -0,0 +1,60 @@ +[[reference-search_application-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.delete + +Delete a search application. Remove a search application and its associated alias. Indices attached to the search application are not removed. + +{ref}/delete-search-application.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationDeleteRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationDeleteRequest` + +[source,ts] +---- +interface SearchApplicationDeleteRequest extends <> { + name: <> +} +---- + +[discrete] +===== `SearchApplicationDeleteResponse` + +[source,ts] +---- +type SearchApplicationDeleteResponse = <> +---- + diff --git a/docs/reference-search_application-delete_behavioral_analytics.asciidoc b/docs/reference-search_application-delete_behavioral_analytics.asciidoc new file mode 100644 index 000000000..95fa6855a --- /dev/null +++ b/docs/reference-search_application-delete_behavioral_analytics.asciidoc @@ -0,0 +1,60 @@ +[[reference-search_application-delete_behavioral_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.deleteBehavioralAnalytics + +Delete a behavioral analytics collection. The associated data stream is also deleted. + +{ref}/delete-analytics-collection.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationDeleteBehavioralAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationDeleteBehavioralAnalyticsRequest` + +[source,ts] +---- +interface SearchApplicationDeleteBehavioralAnalyticsRequest extends <> { + name: <> +} +---- + +[discrete] +===== `SearchApplicationDeleteBehavioralAnalyticsResponse` + +[source,ts] +---- +type SearchApplicationDeleteBehavioralAnalyticsResponse = <> +---- + diff --git a/docs/reference-search_application-get.asciidoc b/docs/reference-search_application-get.asciidoc new file mode 100644 index 000000000..9592b2ba0 --- /dev/null +++ b/docs/reference-search_application-get.asciidoc @@ -0,0 +1,60 @@ +[[reference-search_application-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.get + +Get search application details. + +{ref}/get-search-application.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationGetRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationGetRequest` + +[source,ts] +---- +interface SearchApplicationGetRequest extends <> { + name: <> +} +---- + +[discrete] +===== `SearchApplicationGetResponse` + +[source,ts] +---- +type SearchApplicationGetResponse = SearchApplicationSearchApplication +---- + diff --git a/docs/reference-search_application-get_behavioral_analytics.asciidoc b/docs/reference-search_application-get_behavioral_analytics.asciidoc new file mode 100644 index 000000000..a1a7c4901 --- /dev/null +++ b/docs/reference-search_application-get_behavioral_analytics.asciidoc @@ -0,0 +1,60 @@ +[[reference-search_application-get_behavioral_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.getBehavioralAnalytics + +Get behavioral analytics collections. + +{ref}/list-analytics-collection.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationGetBehavioralAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationGetBehavioralAnalyticsRequest` + +[source,ts] +---- +interface SearchApplicationGetBehavioralAnalyticsRequest extends <> { + name?: <>[] +} +---- + +[discrete] +===== `SearchApplicationGetBehavioralAnalyticsResponse` + +[source,ts] +---- +type SearchApplicationGetBehavioralAnalyticsResponse = Record<<>, SearchApplicationAnalyticsCollection> +---- + diff --git a/docs/reference-search_application-list.asciidoc b/docs/reference-search_application-list.asciidoc new file mode 100644 index 000000000..a97426c01 --- /dev/null +++ b/docs/reference-search_application-list.asciidoc @@ -0,0 +1,65 @@ +[[reference-search_application-list]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.list + +Returns the existing search applications. + +{ref}/list-search-applications.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationListRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationListRequest` + +[source,ts] +---- +interface SearchApplicationListRequest extends <> { + q?: string + from?: <> + size?: <> +} +---- + +[discrete] +===== `SearchApplicationListResponse` + +[source,ts] +---- +interface SearchApplicationListResponse { + count: <> + results: SearchApplicationListSearchApplicationListItem[] +} +---- + diff --git a/docs/reference-search_application-post_behavioral_analytics_event.asciidoc b/docs/reference-search_application-post_behavioral_analytics_event.asciidoc new file mode 100644 index 000000000..f2c641572 --- /dev/null +++ b/docs/reference-search_application-post_behavioral_analytics_event.asciidoc @@ -0,0 +1,59 @@ +[[reference-search_application-post_behavioral_analytics_event]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.postBehavioralAnalyticsEvent + +Creates a behavioral analytics event for existing collection. + +http://todo.com/tbd[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationPostBehavioralAnalyticsEventRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationPostBehavioralAnalyticsEventRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SearchApplicationPostBehavioralAnalyticsEventResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-search_application-put.asciidoc b/docs/reference-search_application-put.asciidoc new file mode 100644 index 000000000..a84a956ac --- /dev/null +++ b/docs/reference-search_application-put.asciidoc @@ -0,0 +1,64 @@ +[[reference-search_application-put]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.put + +Create or update a search application. + +{ref}/put-search-application.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationPutRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationPutRequest` + +[source,ts] +---- +interface SearchApplicationPutRequest extends <> { + name: <> + create?: boolean + search_application?: SearchApplicationSearchApplication +} +---- + +[discrete] +===== `SearchApplicationPutResponse` + +[source,ts] +---- +interface SearchApplicationPutResponse { + result: <> +} +---- + diff --git a/docs/reference-search_application-put_behavioral_analytics.asciidoc b/docs/reference-search_application-put_behavioral_analytics.asciidoc new file mode 100644 index 000000000..2ae7e9e93 --- /dev/null +++ b/docs/reference-search_application-put_behavioral_analytics.asciidoc @@ -0,0 +1,60 @@ +[[reference-search_application-put_behavioral_analytics]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.putBehavioralAnalytics + +Create a behavioral analytics collection. + +{ref}/put-analytics-collection.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationPutBehavioralAnalyticsRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationPutBehavioralAnalyticsRequest` + +[source,ts] +---- +interface SearchApplicationPutBehavioralAnalyticsRequest extends <> { + name: <> +} +---- + +[discrete] +===== `SearchApplicationPutBehavioralAnalyticsResponse` + +[source,ts] +---- +type SearchApplicationPutBehavioralAnalyticsResponse = SearchApplicationPutBehavioralAnalyticsAnalyticsAcknowledgeResponseBase +---- + diff --git a/docs/reference-search_application-render_query.asciidoc b/docs/reference-search_application-render_query.asciidoc new file mode 100644 index 000000000..ba6884172 --- /dev/null +++ b/docs/reference-search_application-render_query.asciidoc @@ -0,0 +1,59 @@ +[[reference-search_application-render_query]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.renderQuery + +Renders a query for given search application search parameters + +{ref}/search-application-render-query.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationRenderQueryRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationRenderQueryRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SearchApplicationRenderQueryResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-search_application-search.asciidoc b/docs/reference-search_application-search.asciidoc new file mode 100644 index 000000000..22a3d599b --- /dev/null +++ b/docs/reference-search_application-search.asciidoc @@ -0,0 +1,62 @@ +[[reference-search_application-search]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchApplication.search + +Run a search application search. Generate and run an Elasticsearch query that uses the specified query parameteter and the search template associated with the search application or default template. Unspecified template parameters are assigned their default values if applicable. + +{ref}/search-application-search.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchApplicationSearchRequest, options?): Promise +---- + +[discrete] +===== `SearchApplicationSearchRequest` + +[source,ts] +---- +interface SearchApplicationSearchRequest extends <> { + name: <> + typed_keys?: boolean + params?: Record +} +---- + +[discrete] +===== `SearchApplicationSearchResponse` + +[source,ts] +---- +type SearchApplicationSearchResponse>, AggregationsAggregate>> = SearchResponseBody +---- + diff --git a/docs/reference-search_mvt.asciidoc b/docs/reference-search_mvt.asciidoc new file mode 100644 index 000000000..adac4c1e1 --- /dev/null +++ b/docs/reference-search_mvt.asciidoc @@ -0,0 +1,78 @@ +[[reference-search_mvt]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchMvt + +Search a vector tile. Search a vector tile for geospatial values. + +{ref}/search-vector-tile-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchMvtRequest, options?): Promise +---- + +[discrete] +===== `SearchMvtRequest` + +[source,ts] +---- +interface SearchMvtRequest extends <> { + index: <> + field: <> + zoom: SearchMvtZoomLevel + x: SearchMvtCoordinate + y: SearchMvtCoordinate + aggs?: Record + buffer?: <> + exact_bounds?: boolean + extent?: <> + fields?: <> + grid_agg?: SearchMvtGridAggregationType + grid_precision?: <> + grid_type?: SearchMvtGridType + query?: QueryDslQueryContainer + runtime_mappings?: MappingRuntimeFields + size?: <> + sort?: <> + track_total_hits?: SearchTrackHits + with_labels?: boolean +} +---- + +[discrete] +===== `SearchMvtResponse` + +[source,ts] +---- +type SearchMvtResponse = <> +---- + diff --git a/docs/reference-search_shards.asciidoc b/docs/reference-search_shards.asciidoc new file mode 100644 index 000000000..fb19ecca0 --- /dev/null +++ b/docs/reference-search_shards.asciidoc @@ -0,0 +1,70 @@ +[[reference-search_shards]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchShards + +Get the search shards. Get the indices and shards that a search request would be run against. This information can be useful for working out issues or planning optimizations with routing and shard preferences. When filtered aliases are used, the filter is returned as part of the indices section. + +{ref}/search-shards.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchShardsRequest, options?): Promise +---- + +[discrete] +===== `SearchShardsRequest` + +[source,ts] +---- +interface SearchShardsRequest extends <> { + index?: <> + allow_no_indices?: boolean + expand_wildcards?: <> + ignore_unavailable?: boolean + local?: boolean + preference?: string + routing?: <> +} +---- + +[discrete] +===== `SearchShardsResponse` + +[source,ts] +---- +interface SearchShardsResponse { + nodes: Record<<>, SearchShardsSearchShardsNodeAttributes> + shards: <>[][] + indices: Record<<>, SearchShardsShardStoreIndex> +} +---- + diff --git a/docs/reference-search_template.asciidoc b/docs/reference-search_template.asciidoc new file mode 100644 index 000000000..74ec1feab --- /dev/null +++ b/docs/reference-search_template.asciidoc @@ -0,0 +1,91 @@ +[[reference-search_template]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchTemplate + +Run a search with a search template. + +{ref}/search-template.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchTemplateRequest, options?): Promise +---- + +[discrete] +===== `SearchTemplateRequest` + +[source,ts] +---- +interface SearchTemplateRequest extends <> { + index?: <> + allow_no_indices?: boolean + ccs_minimize_roundtrips?: boolean + expand_wildcards?: <> + ignore_throttled?: boolean + ignore_unavailable?: boolean + preference?: string + routing?: <> + scroll?: <> + search_type?: <> + rest_total_hits_as_int?: boolean + typed_keys?: boolean + explain?: boolean + id?: <> + params?: Record + profile?: boolean + source?: string +} +---- + +[discrete] +===== `SearchTemplateResponse` + +[source,ts] +---- +interface SearchTemplateResponse { + took: <> + timed_out: boolean + _shards: <> + hits: SearchHitsMetadata + aggregations?: Record<<>, AggregationsAggregate> + _clusters?: <> + fields?: Record + max_score?: <> + num_reduce_phases?: <> + profile?: SearchProfile + pit_id?: <> + _scroll_id?: <> + suggest?: Record<<>, SearchSuggest[]> + terminated_early?: boolean +} +---- + diff --git a/docs/reference-searchable_snapshots-cache_stats.asciidoc b/docs/reference-searchable_snapshots-cache_stats.asciidoc new file mode 100644 index 000000000..472bab97d --- /dev/null +++ b/docs/reference-searchable_snapshots-cache_stats.asciidoc @@ -0,0 +1,63 @@ +[[reference-searchable_snapshots-cache_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchableSnapshots.cacheStats + +Retrieve node-level cache statistics about searchable snapshots. + +{ref}/searchable-snapshots-apis.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchableSnapshotsCacheStatsRequest, options?): Promise +---- + +[discrete] +===== `SearchableSnapshotsCacheStatsRequest` + +[source,ts] +---- +interface SearchableSnapshotsCacheStatsRequest extends <> { + node_id?: <> + master_timeout?: <> +} +---- + +[discrete] +===== `SearchableSnapshotsCacheStatsResponse` + +[source,ts] +---- +interface SearchableSnapshotsCacheStatsResponse { + nodes: Record +} +---- + diff --git a/docs/reference-searchable_snapshots-clear_cache.asciidoc b/docs/reference-searchable_snapshots-clear_cache.asciidoc new file mode 100644 index 000000000..b7eb4a3ac --- /dev/null +++ b/docs/reference-searchable_snapshots-clear_cache.asciidoc @@ -0,0 +1,65 @@ +[[reference-searchable_snapshots-clear_cache]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchableSnapshots.clearCache + +Clear the cache of searchable snapshots. + +{ref}/searchable-snapshots-apis.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchableSnapshotsClearCacheRequest, options?): Promise +---- + +[discrete] +===== `SearchableSnapshotsClearCacheRequest` + +[source,ts] +---- +interface SearchableSnapshotsClearCacheRequest extends <> { + index?: <> + expand_wildcards?: <> + allow_no_indices?: boolean + ignore_unavailable?: boolean + pretty?: boolean + human?: boolean +} +---- + +[discrete] +===== `SearchableSnapshotsClearCacheResponse` + +[source,ts] +---- +type SearchableSnapshotsClearCacheResponse = any +---- + diff --git a/docs/reference-searchable_snapshots-mount.asciidoc b/docs/reference-searchable_snapshots-mount.asciidoc new file mode 100644 index 000000000..e43fdc88b --- /dev/null +++ b/docs/reference-searchable_snapshots-mount.asciidoc @@ -0,0 +1,70 @@ +[[reference-searchable_snapshots-mount]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchableSnapshots.mount + +Mount a snapshot as a searchable index. + +{ref}/searchable-snapshots-api-mount-snapshot.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchableSnapshotsMountRequest, options?): Promise +---- + +[discrete] +===== `SearchableSnapshotsMountRequest` + +[source,ts] +---- +interface SearchableSnapshotsMountRequest extends <> { + repository: <> + snapshot: <> + master_timeout?: <> + wait_for_completion?: boolean + storage?: string + index: <> + renamed_index?: <> + index_settings?: Record + ignore_index_settings?: string[] +} +---- + +[discrete] +===== `SearchableSnapshotsMountResponse` + +[source,ts] +---- +interface SearchableSnapshotsMountResponse { + snapshot: SearchableSnapshotsMountMountedSnapshot +} +---- + diff --git a/docs/reference-searchable_snapshots-stats.asciidoc b/docs/reference-searchable_snapshots-stats.asciidoc new file mode 100644 index 000000000..4c9f6bb7a --- /dev/null +++ b/docs/reference-searchable_snapshots-stats.asciidoc @@ -0,0 +1,64 @@ +[[reference-searchable_snapshots-stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.searchableSnapshots.stats + +Retrieve shard-level statistics about searchable snapshots. + +{ref}/searchable-snapshots-apis.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SearchableSnapshotsStatsRequest, options?): Promise +---- + +[discrete] +===== `SearchableSnapshotsStatsRequest` + +[source,ts] +---- +interface SearchableSnapshotsStatsRequest extends <> { + index?: <> + level?: SearchableSnapshotsStatsLevel +} +---- + +[discrete] +===== `SearchableSnapshotsStatsResponse` + +[source,ts] +---- +interface SearchableSnapshotsStatsResponse { + stats: any + total: any +} +---- + diff --git a/docs/reference-security-activate_user_profile.asciidoc b/docs/reference-security-activate_user_profile.asciidoc new file mode 100644 index 000000000..20a587fdf --- /dev/null +++ b/docs/reference-security-activate_user_profile.asciidoc @@ -0,0 +1,63 @@ +[[reference-security-activate_user_profile]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.activateUserProfile + +Activate a user profile. Create or update a user profile on behalf of another user. + +{ref}/security-api-activate-user-profile.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityActivateUserProfileRequest, options?): Promise +---- + +[discrete] +===== `SecurityActivateUserProfileRequest` + +[source,ts] +---- +interface SecurityActivateUserProfileRequest extends <> { + access_token?: string + grant_type: SecurityGrantType + password?: string + username?: string +} +---- + +[discrete] +===== `SecurityActivateUserProfileResponse` + +[source,ts] +---- +type SecurityActivateUserProfileResponse = SecurityUserProfileWithMetadata +---- + diff --git a/docs/reference-security-authenticate.asciidoc b/docs/reference-security-authenticate.asciidoc new file mode 100644 index 000000000..7c6eba77c --- /dev/null +++ b/docs/reference-security-authenticate.asciidoc @@ -0,0 +1,71 @@ +[[reference-security-authenticate]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.authenticate + +Authenticate a user. Authenticates a user and returns information about the authenticated user. Include the user information in a [basic auth header](https://en.wikipedia.org/wiki/Basic_access_authentication). A successful call returns a JSON structure that shows user information such as their username, the roles that are assigned to the user, any assigned metadata, and information about the realms that authenticated and authorized the user. If the user cannot be authenticated, this API returns a 401 status code. + +{ref}/security-api-authenticate.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityAuthenticateRequest, options?): Promise +---- + +[discrete] +===== `SecurityAuthenticateRequest` + +[source,ts] +---- +interface SecurityAuthenticateRequest extends <> { +} +---- + +[discrete] +===== `SecurityAuthenticateResponse` + +[source,ts] +---- +interface SecurityAuthenticateResponse { + api_key?: SecurityApiKey + authentication_realm: SecurityRealmInfo + email?: string | null + full_name?: <> | null + lookup_realm: SecurityRealmInfo + metadata: <> + roles: string[] + username: <> + enabled: boolean + authentication_type: string + token?: SecurityAuthenticateToken +} +---- + diff --git a/docs/reference-security-bulk_delete_role.asciidoc b/docs/reference-security-bulk_delete_role.asciidoc new file mode 100644 index 000000000..639aff376 --- /dev/null +++ b/docs/reference-security-bulk_delete_role.asciidoc @@ -0,0 +1,65 @@ +[[reference-security-bulk_delete_role]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.bulkDeleteRole + +Bulk delete roles. The role management APIs are generally the preferred way to manage roles, rather than using file-based role management. The bulk delete roles API cannot delete roles that are defined in roles files. + +{ref}/security-api-bulk-delete-role.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityBulkDeleteRoleRequest, options?): Promise +---- + +[discrete] +===== `SecurityBulkDeleteRoleRequest` + +[source,ts] +---- +interface SecurityBulkDeleteRoleRequest extends <> { + refresh?: <> + names: string[] +} +---- + +[discrete] +===== `SecurityBulkDeleteRoleResponse` + +[source,ts] +---- +interface SecurityBulkDeleteRoleResponse { + deleted?: string[] + not_found?: string[] + errors?: SecurityBulkError +} +---- + diff --git a/docs/reference-security-bulk_put_role.asciidoc b/docs/reference-security-bulk_put_role.asciidoc new file mode 100644 index 000000000..b4675ff37 --- /dev/null +++ b/docs/reference-security-bulk_put_role.asciidoc @@ -0,0 +1,66 @@ +[[reference-security-bulk_put_role]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.bulkPutRole + +Bulk create or update roles. The role management APIs are generally the preferred way to manage roles, rather than using file-based role management. The bulk create or update roles API cannot update roles that are defined in roles files. + +{ref}/security-api-bulk-put-role.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityBulkPutRoleRequest, options?): Promise +---- + +[discrete] +===== `SecurityBulkPutRoleRequest` + +[source,ts] +---- +interface SecurityBulkPutRoleRequest extends <> { + refresh?: <> + roles: Record +} +---- + +[discrete] +===== `SecurityBulkPutRoleResponse` + +[source,ts] +---- +interface SecurityBulkPutRoleResponse { + created?: string[] + updated?: string[] + noop?: string[] + errors?: SecurityBulkError +} +---- + diff --git a/docs/reference-security-bulk_update_api_keys.asciidoc b/docs/reference-security-bulk_update_api_keys.asciidoc new file mode 100644 index 000000000..5632d23b4 --- /dev/null +++ b/docs/reference-security-bulk_update_api_keys.asciidoc @@ -0,0 +1,59 @@ +[[reference-security-bulk_update_api_keys]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.bulkUpdateApiKeys + +Updates the attributes of multiple existing API keys. + +{ref}/security-api-bulk-update-api-keys.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityBulkUpdateApiKeysRequest, options?): Promise +---- + +[discrete] +===== `SecurityBulkUpdateApiKeysRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SecurityBulkUpdateApiKeysResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-security-change_password.asciidoc b/docs/reference-security-change_password.asciidoc new file mode 100644 index 000000000..6712af604 --- /dev/null +++ b/docs/reference-security-change_password.asciidoc @@ -0,0 +1,64 @@ +[[reference-security-change_password]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.changePassword + +Change passwords. Change the passwords of users in the native realm and built-in users. + +{ref}/security-api-change-password.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityChangePasswordRequest, options?): Promise +---- + +[discrete] +===== `SecurityChangePasswordRequest` + +[source,ts] +---- +interface SecurityChangePasswordRequest extends <> { + username?: <> + refresh?: <> + password?: <> + password_hash?: string +} +---- + +[discrete] +===== `SecurityChangePasswordResponse` + +[source,ts] +---- +interface SecurityChangePasswordResponse { +} +---- + diff --git a/docs/reference-security-clear_api_key_cache.asciidoc b/docs/reference-security-clear_api_key_cache.asciidoc new file mode 100644 index 000000000..b61eaab56 --- /dev/null +++ b/docs/reference-security-clear_api_key_cache.asciidoc @@ -0,0 +1,64 @@ +[[reference-security-clear_api_key_cache]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.clearApiKeyCache + +Clear the API key cache. Evict a subset of all entries from the API key cache. The cache is also automatically cleared on state changes of the security index. + +{ref}/security-api-clear-api-key-cache.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityClearApiKeyCacheRequest, options?): Promise +---- + +[discrete] +===== `SecurityClearApiKeyCacheRequest` + +[source,ts] +---- +interface SecurityClearApiKeyCacheRequest extends <> { + ids: <> +} +---- + +[discrete] +===== `SecurityClearApiKeyCacheResponse` + +[source,ts] +---- +interface SecurityClearApiKeyCacheResponse { + _nodes: <> + cluster_name: <> + nodes: Record +} +---- + diff --git a/docs/reference-security-clear_cached_privileges.asciidoc b/docs/reference-security-clear_cached_privileges.asciidoc new file mode 100644 index 000000000..00c08ef33 --- /dev/null +++ b/docs/reference-security-clear_cached_privileges.asciidoc @@ -0,0 +1,64 @@ +[[reference-security-clear_cached_privileges]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.clearCachedPrivileges + +Clear the privileges cache. Evict privileges from the native application privilege cache. The cache is also automatically cleared for applications that have their privileges updated. + +{ref}/security-api-clear-privilege-cache.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityClearCachedPrivilegesRequest, options?): Promise +---- + +[discrete] +===== `SecurityClearCachedPrivilegesRequest` + +[source,ts] +---- +interface SecurityClearCachedPrivilegesRequest extends <> { + application: <> +} +---- + +[discrete] +===== `SecurityClearCachedPrivilegesResponse` + +[source,ts] +---- +interface SecurityClearCachedPrivilegesResponse { + _nodes: <> + cluster_name: <> + nodes: Record +} +---- + diff --git a/docs/reference-security-clear_cached_realms.asciidoc b/docs/reference-security-clear_cached_realms.asciidoc new file mode 100644 index 000000000..fd562b07b --- /dev/null +++ b/docs/reference-security-clear_cached_realms.asciidoc @@ -0,0 +1,65 @@ +[[reference-security-clear_cached_realms]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.clearCachedRealms + +Clear the user cache. Evict users from the user cache. You can completely clear the cache or evict specific users. + +{ref}/security-api-clear-cache.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityClearCachedRealmsRequest, options?): Promise +---- + +[discrete] +===== `SecurityClearCachedRealmsRequest` + +[source,ts] +---- +interface SecurityClearCachedRealmsRequest extends <> { + realms: <> + usernames?: string[] +} +---- + +[discrete] +===== `SecurityClearCachedRealmsResponse` + +[source,ts] +---- +interface SecurityClearCachedRealmsResponse { + _nodes: <> + cluster_name: <> + nodes: Record +} +---- + diff --git a/docs/reference-security-clear_cached_roles.asciidoc b/docs/reference-security-clear_cached_roles.asciidoc new file mode 100644 index 000000000..f78a6d6f8 --- /dev/null +++ b/docs/reference-security-clear_cached_roles.asciidoc @@ -0,0 +1,64 @@ +[[reference-security-clear_cached_roles]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.clearCachedRoles + +Clear the roles cache. Evict roles from the native role cache. + +{ref}/security-api-clear-role-cache.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityClearCachedRolesRequest, options?): Promise +---- + +[discrete] +===== `SecurityClearCachedRolesRequest` + +[source,ts] +---- +interface SecurityClearCachedRolesRequest extends <> { + name: <> +} +---- + +[discrete] +===== `SecurityClearCachedRolesResponse` + +[source,ts] +---- +interface SecurityClearCachedRolesResponse { + _nodes: <> + cluster_name: <> + nodes: Record +} +---- + diff --git a/docs/reference-security-clear_cached_service_tokens.asciidoc b/docs/reference-security-clear_cached_service_tokens.asciidoc new file mode 100644 index 000000000..c6962cbe9 --- /dev/null +++ b/docs/reference-security-clear_cached_service_tokens.asciidoc @@ -0,0 +1,66 @@ +[[reference-security-clear_cached_service_tokens]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.clearCachedServiceTokens + +Clear service account token caches. Evict a subset of all entries from the service account token caches. + +{ref}/security-api-clear-service-token-caches.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityClearCachedServiceTokensRequest, options?): Promise +---- + +[discrete] +===== `SecurityClearCachedServiceTokensRequest` + +[source,ts] +---- +interface SecurityClearCachedServiceTokensRequest extends <> { + namespace: <> + service: <> + name: <> +} +---- + +[discrete] +===== `SecurityClearCachedServiceTokensResponse` + +[source,ts] +---- +interface SecurityClearCachedServiceTokensResponse { + _nodes: <> + cluster_name: <> + nodes: Record +} +---- + diff --git a/docs/reference-security-create_api_key.asciidoc b/docs/reference-security-create_api_key.asciidoc new file mode 100644 index 000000000..b01cca084 --- /dev/null +++ b/docs/reference-security-create_api_key.asciidoc @@ -0,0 +1,70 @@ +[[reference-security-create_api_key]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.createApiKey + +Create an API key. Create an API key for access without requiring basic authentication. A successful request returns a JSON structure that contains the API key, its unique id, and its name. If applicable, it also returns expiration information for the API key in milliseconds. NOTE: By default, API keys never expire. You can specify expiration information when you create the API keys. + +{ref}/security-api-create-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityCreateApiKeyRequest, options?): Promise +---- + +[discrete] +===== `SecurityCreateApiKeyRequest` + +[source,ts] +---- +interface SecurityCreateApiKeyRequest extends <> { + refresh?: <> + expiration?: <> + name?: <> + role_descriptors?: Record + metadata?: <> +} +---- + +[discrete] +===== `SecurityCreateApiKeyResponse` + +[source,ts] +---- +interface SecurityCreateApiKeyResponse { + api_key: string + expiration?: <> + id: <> + name: <> + encoded: string +} +---- + diff --git a/docs/reference-security-create_cross_cluster_api_key.asciidoc b/docs/reference-security-create_cross_cluster_api_key.asciidoc new file mode 100644 index 000000000..9ea7eccde --- /dev/null +++ b/docs/reference-security-create_cross_cluster_api_key.asciidoc @@ -0,0 +1,69 @@ +[[reference-security-create_cross_cluster_api_key]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.createCrossClusterApiKey + +Create a cross-cluster API key. Create an API key of the `cross_cluster` type for the API key based remote cluster access. A `cross_cluster` API key cannot be used to authenticate through the REST interface. IMPORTANT: To authenticate this request you must use a credential that is not an API key. Even if you use an API key that has the required privilege, the API returns an error. Cross-cluster API keys are created by the Elasticsearch API key service, which is automatically enabled. NOTE: Unlike REST API keys, a cross-cluster API key does not capture permissions of the authenticated user. The API key’s effective permission is exactly as specified with the `access` property. A successful request returns a JSON structure that contains the API key, its unique ID, and its name. If applicable, it also returns expiration information for the API key in milliseconds. By default, API keys never expire. You can specify expiration information when you create the API keys. Cross-cluster API keys can only be updated with the update cross-cluster API key API. Attempting to update them with the update REST API key API or the bulk update REST API keys API will result in an error. + +{ref}/security-api-create-cross-cluster-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityCreateCrossClusterApiKeyRequest, options?): Promise +---- + +[discrete] +===== `SecurityCreateCrossClusterApiKeyRequest` + +[source,ts] +---- +interface SecurityCreateCrossClusterApiKeyRequest extends <> { + access: SecurityAccess + expiration?: <> + metadata?: <> + name: <> +} +---- + +[discrete] +===== `SecurityCreateCrossClusterApiKeyResponse` + +[source,ts] +---- +interface SecurityCreateCrossClusterApiKeyResponse { + api_key: string + expiration?: <><<>> + id: <> + name: <> + encoded: string +} +---- + diff --git a/docs/reference-security-create_service_token.asciidoc b/docs/reference-security-create_service_token.asciidoc new file mode 100644 index 000000000..d0e5472c7 --- /dev/null +++ b/docs/reference-security-create_service_token.asciidoc @@ -0,0 +1,66 @@ +[[reference-security-create_service_token]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.createServiceToken + +Create a service account token. Create a service accounts token for access without requiring basic authentication. + +{ref}/security-api-create-service-token.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityCreateServiceTokenRequest, options?): Promise +---- + +[discrete] +===== `SecurityCreateServiceTokenRequest` + +[source,ts] +---- +interface SecurityCreateServiceTokenRequest extends <> { + namespace: <> + service: <> + name?: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityCreateServiceTokenResponse` + +[source,ts] +---- +interface SecurityCreateServiceTokenResponse { + created: boolean + token: SecurityCreateServiceTokenToken +} +---- + diff --git a/docs/reference-security-delete_privileges.asciidoc b/docs/reference-security-delete_privileges.asciidoc new file mode 100644 index 000000000..f0193f4ed --- /dev/null +++ b/docs/reference-security-delete_privileges.asciidoc @@ -0,0 +1,62 @@ +[[reference-security-delete_privileges]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.deletePrivileges + +Delete application privileges. + +{ref}/security-api-delete-privilege.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityDeletePrivilegesRequest, options?): Promise +---- + +[discrete] +===== `SecurityDeletePrivilegesRequest` + +[source,ts] +---- +interface SecurityDeletePrivilegesRequest extends <> { + application: <> + name: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityDeletePrivilegesResponse` + +[source,ts] +---- +type SecurityDeletePrivilegesResponse = Record> +---- + diff --git a/docs/reference-security-delete_role.asciidoc b/docs/reference-security-delete_role.asciidoc new file mode 100644 index 000000000..7e685bb7f --- /dev/null +++ b/docs/reference-security-delete_role.asciidoc @@ -0,0 +1,63 @@ +[[reference-security-delete_role]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.deleteRole + +Delete roles. Delete roles in the native realm. + +{ref}/security-api-delete-role.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityDeleteRoleRequest, options?): Promise +---- + +[discrete] +===== `SecurityDeleteRoleRequest` + +[source,ts] +---- +interface SecurityDeleteRoleRequest extends <> { + name: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityDeleteRoleResponse` + +[source,ts] +---- +interface SecurityDeleteRoleResponse { + found: boolean +} +---- + diff --git a/docs/reference-security-delete_role_mapping.asciidoc b/docs/reference-security-delete_role_mapping.asciidoc new file mode 100644 index 000000000..31f6985e7 --- /dev/null +++ b/docs/reference-security-delete_role_mapping.asciidoc @@ -0,0 +1,63 @@ +[[reference-security-delete_role_mapping]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.deleteRoleMapping + +Delete role mappings. + +{ref}/security-api-delete-role-mapping.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityDeleteRoleMappingRequest, options?): Promise +---- + +[discrete] +===== `SecurityDeleteRoleMappingRequest` + +[source,ts] +---- +interface SecurityDeleteRoleMappingRequest extends <> { + name: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityDeleteRoleMappingResponse` + +[source,ts] +---- +interface SecurityDeleteRoleMappingResponse { + found: boolean +} +---- + diff --git a/docs/reference-security-delete_service_token.asciidoc b/docs/reference-security-delete_service_token.asciidoc new file mode 100644 index 000000000..bc79caaf5 --- /dev/null +++ b/docs/reference-security-delete_service_token.asciidoc @@ -0,0 +1,65 @@ +[[reference-security-delete_service_token]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.deleteServiceToken + +Delete service account tokens. Delete service account tokens for a service in a specified namespace. + +{ref}/security-api-delete-service-token.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityDeleteServiceTokenRequest, options?): Promise +---- + +[discrete] +===== `SecurityDeleteServiceTokenRequest` + +[source,ts] +---- +interface SecurityDeleteServiceTokenRequest extends <> { + namespace: <> + service: <> + name: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityDeleteServiceTokenResponse` + +[source,ts] +---- +interface SecurityDeleteServiceTokenResponse { + found: boolean +} +---- + diff --git a/docs/reference-security-delete_user.asciidoc b/docs/reference-security-delete_user.asciidoc new file mode 100644 index 000000000..39c3c0d9c --- /dev/null +++ b/docs/reference-security-delete_user.asciidoc @@ -0,0 +1,63 @@ +[[reference-security-delete_user]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.deleteUser + +Delete users. Delete users from the native realm. + +{ref}/security-api-delete-user.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityDeleteUserRequest, options?): Promise +---- + +[discrete] +===== `SecurityDeleteUserRequest` + +[source,ts] +---- +interface SecurityDeleteUserRequest extends <> { + username: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityDeleteUserResponse` + +[source,ts] +---- +interface SecurityDeleteUserResponse { + found: boolean +} +---- + diff --git a/docs/reference-security-disable_user.asciidoc b/docs/reference-security-disable_user.asciidoc new file mode 100644 index 000000000..183e03279 --- /dev/null +++ b/docs/reference-security-disable_user.asciidoc @@ -0,0 +1,62 @@ +[[reference-security-disable_user]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.disableUser + +Disable users. Disable users in the native realm. + +{ref}/security-api-disable-user.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityDisableUserRequest, options?): Promise +---- + +[discrete] +===== `SecurityDisableUserRequest` + +[source,ts] +---- +interface SecurityDisableUserRequest extends <> { + username: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityDisableUserResponse` + +[source,ts] +---- +interface SecurityDisableUserResponse { +} +---- + diff --git a/docs/reference-security-disable_user_profile.asciidoc b/docs/reference-security-disable_user_profile.asciidoc new file mode 100644 index 000000000..8432ee778 --- /dev/null +++ b/docs/reference-security-disable_user_profile.asciidoc @@ -0,0 +1,61 @@ +[[reference-security-disable_user_profile]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.disableUserProfile + +Disable a user profile. Disable user profiles so that they are not visible in user profile searches. + +{ref}/security-api-disable-user-profile.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityDisableUserProfileRequest, options?): Promise +---- + +[discrete] +===== `SecurityDisableUserProfileRequest` + +[source,ts] +---- +interface SecurityDisableUserProfileRequest extends <> { + uid: SecurityUserProfileId + refresh?: <> +} +---- + +[discrete] +===== `SecurityDisableUserProfileResponse` + +[source,ts] +---- +type SecurityDisableUserProfileResponse = <> +---- + diff --git a/docs/reference-security-enable_user.asciidoc b/docs/reference-security-enable_user.asciidoc new file mode 100644 index 000000000..52c0629ce --- /dev/null +++ b/docs/reference-security-enable_user.asciidoc @@ -0,0 +1,62 @@ +[[reference-security-enable_user]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.enableUser + +Enable users. Enable users in the native realm. + +{ref}/security-api-enable-user.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityEnableUserRequest, options?): Promise +---- + +[discrete] +===== `SecurityEnableUserRequest` + +[source,ts] +---- +interface SecurityEnableUserRequest extends <> { + username: <> + refresh?: <> +} +---- + +[discrete] +===== `SecurityEnableUserResponse` + +[source,ts] +---- +interface SecurityEnableUserResponse { +} +---- + diff --git a/docs/reference-security-enable_user_profile.asciidoc b/docs/reference-security-enable_user_profile.asciidoc new file mode 100644 index 000000000..ba6663a51 --- /dev/null +++ b/docs/reference-security-enable_user_profile.asciidoc @@ -0,0 +1,61 @@ +[[reference-security-enable_user_profile]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.enableUserProfile + +Enable a user profile. Enable user profiles to make them visible in user profile searches. + +{ref}/security-api-enable-user-profile.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityEnableUserProfileRequest, options?): Promise +---- + +[discrete] +===== `SecurityEnableUserProfileRequest` + +[source,ts] +---- +interface SecurityEnableUserProfileRequest extends <> { + uid: SecurityUserProfileId + refresh?: <> +} +---- + +[discrete] +===== `SecurityEnableUserProfileResponse` + +[source,ts] +---- +type SecurityEnableUserProfileResponse = <> +---- + diff --git a/docs/reference-security-enroll_kibana.asciidoc b/docs/reference-security-enroll_kibana.asciidoc new file mode 100644 index 000000000..90da3737b --- /dev/null +++ b/docs/reference-security-enroll_kibana.asciidoc @@ -0,0 +1,62 @@ +[[reference-security-enroll_kibana]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.enrollKibana + +Enroll Kibana. Enable a Kibana instance to configure itself for communication with a secured Elasticsearch cluster. + +{ref}/security-api-kibana-enrollment.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityEnrollKibanaRequest, options?): Promise +---- + +[discrete] +===== `SecurityEnrollKibanaRequest` + +[source,ts] +---- +interface SecurityEnrollKibanaRequest extends <> { +} +---- + +[discrete] +===== `SecurityEnrollKibanaResponse` + +[source,ts] +---- +interface SecurityEnrollKibanaResponse { + token: SecurityEnrollKibanaToken + http_ca: string +} +---- + diff --git a/docs/reference-security-enroll_node.asciidoc b/docs/reference-security-enroll_node.asciidoc new file mode 100644 index 000000000..97d71687a --- /dev/null +++ b/docs/reference-security-enroll_node.asciidoc @@ -0,0 +1,66 @@ +[[reference-security-enroll_node]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.enrollNode + +Enroll a node. Enroll a new node to allow it to join an existing cluster with security features enabled. + +{ref}/security-api-node-enrollment.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityEnrollNodeRequest, options?): Promise +---- + +[discrete] +===== `SecurityEnrollNodeRequest` + +[source,ts] +---- +interface SecurityEnrollNodeRequest extends <> { +} +---- + +[discrete] +===== `SecurityEnrollNodeResponse` + +[source,ts] +---- +interface SecurityEnrollNodeResponse { + http_ca_key: string + http_ca_cert: string + transport_ca_cert: string + transport_key: string + transport_cert: string + nodes_addresses: string[] +} +---- + diff --git a/docs/reference-security-get_api_key.asciidoc b/docs/reference-security-get_api_key.asciidoc new file mode 100644 index 000000000..7eb8af9bd --- /dev/null +++ b/docs/reference-security-get_api_key.asciidoc @@ -0,0 +1,69 @@ +[[reference-security-get_api_key]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getApiKey + +Get API key information. Retrieves information for one or more API keys. NOTE: If you have only the `manage_own_api_key` privilege, this API returns only the API keys that you own. If you have `read_security`, `manage_api_key` or greater privileges (including `manage_security`), this API returns all API keys regardless of ownership. + +{ref}/security-api-get-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetApiKeyRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetApiKeyRequest` + +[source,ts] +---- +interface SecurityGetApiKeyRequest extends <> { + id?: <> + name?: <> + owner?: boolean + realm_name?: <> + username?: <> + with_limited_by?: boolean + active_only?: boolean + with_profile_uid?: boolean +} +---- + +[discrete] +===== `SecurityGetApiKeyResponse` + +[source,ts] +---- +interface SecurityGetApiKeyResponse { + api_keys: SecurityApiKey[] +} +---- + diff --git a/docs/reference-security-get_builtin_privileges.asciidoc b/docs/reference-security-get_builtin_privileges.asciidoc new file mode 100644 index 000000000..97d711107 --- /dev/null +++ b/docs/reference-security-get_builtin_privileges.asciidoc @@ -0,0 +1,62 @@ +[[reference-security-get_builtin_privileges]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getBuiltinPrivileges + +Get builtin privileges. Get the list of cluster privileges and index privileges that are available in this version of Elasticsearch. + +{ref}/security-api-get-builtin-privileges.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetBuiltinPrivilegesRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetBuiltinPrivilegesRequest` + +[source,ts] +---- +interface SecurityGetBuiltinPrivilegesRequest extends <> { +} +---- + +[discrete] +===== `SecurityGetBuiltinPrivilegesResponse` + +[source,ts] +---- +interface SecurityGetBuiltinPrivilegesResponse { + cluster: string[] + index: <> +} +---- + diff --git a/docs/reference-security-get_privileges.asciidoc b/docs/reference-security-get_privileges.asciidoc new file mode 100644 index 000000000..58e6bb1a0 --- /dev/null +++ b/docs/reference-security-get_privileges.asciidoc @@ -0,0 +1,61 @@ +[[reference-security-get_privileges]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getPrivileges + +Get application privileges. + +{ref}/security-api-get-privileges.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetPrivilegesRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetPrivilegesRequest` + +[source,ts] +---- +interface SecurityGetPrivilegesRequest extends <> { + application?: <> + name?: <> +} +---- + +[discrete] +===== `SecurityGetPrivilegesResponse` + +[source,ts] +---- +type SecurityGetPrivilegesResponse = Record> +---- + diff --git a/docs/reference-security-get_role.asciidoc b/docs/reference-security-get_role.asciidoc new file mode 100644 index 000000000..8a45bfae2 --- /dev/null +++ b/docs/reference-security-get_role.asciidoc @@ -0,0 +1,60 @@ +[[reference-security-get_role]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getRole + +Get roles. Get roles in the native realm. The role management APIs are generally the preferred way to manage roles, rather than using file-based role management. The get roles API cannot retrieve roles that are defined in roles files. + +{ref}/security-api-get-role.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetRoleRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetRoleRequest` + +[source,ts] +---- +interface SecurityGetRoleRequest extends <> { + name?: <> +} +---- + +[discrete] +===== `SecurityGetRoleResponse` + +[source,ts] +---- +type SecurityGetRoleResponse = Record +---- + diff --git a/docs/reference-security-get_role_mapping.asciidoc b/docs/reference-security-get_role_mapping.asciidoc new file mode 100644 index 000000000..86f0fd3bf --- /dev/null +++ b/docs/reference-security-get_role_mapping.asciidoc @@ -0,0 +1,60 @@ +[[reference-security-get_role_mapping]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getRoleMapping + +Get role mappings. Role mappings define which roles are assigned to each user. The role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The get role mappings API cannot retrieve role mappings that are defined in role mapping files. + +{ref}/security-api-get-role-mapping.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetRoleMappingRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetRoleMappingRequest` + +[source,ts] +---- +interface SecurityGetRoleMappingRequest extends <> { + name?: <> +} +---- + +[discrete] +===== `SecurityGetRoleMappingResponse` + +[source,ts] +---- +type SecurityGetRoleMappingResponse = Record +---- + diff --git a/docs/reference-security-get_service_accounts.asciidoc b/docs/reference-security-get_service_accounts.asciidoc new file mode 100644 index 000000000..c238d128c --- /dev/null +++ b/docs/reference-security-get_service_accounts.asciidoc @@ -0,0 +1,61 @@ +[[reference-security-get_service_accounts]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getServiceAccounts + +Get service accounts. Get a list of service accounts that match the provided path parameters. + +{ref}/security-api-get-service-accounts.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetServiceAccountsRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetServiceAccountsRequest` + +[source,ts] +---- +interface SecurityGetServiceAccountsRequest extends <> { + namespace?: <> + service?: <> +} +---- + +[discrete] +===== `SecurityGetServiceAccountsResponse` + +[source,ts] +---- +type SecurityGetServiceAccountsResponse = Record +---- + diff --git a/docs/reference-security-get_service_credentials.asciidoc b/docs/reference-security-get_service_credentials.asciidoc new file mode 100644 index 000000000..94b67e9a7 --- /dev/null +++ b/docs/reference-security-get_service_credentials.asciidoc @@ -0,0 +1,66 @@ +[[reference-security-get_service_credentials]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getServiceCredentials + +Get service account credentials. + +{ref}/security-api-get-service-credentials.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetServiceCredentialsRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetServiceCredentialsRequest` + +[source,ts] +---- +interface SecurityGetServiceCredentialsRequest extends <> { + namespace: <> + service: <> +} +---- + +[discrete] +===== `SecurityGetServiceCredentialsResponse` + +[source,ts] +---- +interface SecurityGetServiceCredentialsResponse { + service_account: string + count: <> + tokens: Record>> + nodes_credentials: SecurityGetServiceCredentialsNodesCredentials +} +---- + diff --git a/docs/reference-security-get_settings.asciidoc b/docs/reference-security-get_settings.asciidoc new file mode 100644 index 000000000..729b6aa26 --- /dev/null +++ b/docs/reference-security-get_settings.asciidoc @@ -0,0 +1,59 @@ +[[reference-security-get_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getSettings + +Retrieve settings for the security system indices + +{ref}/security-api-get-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetSettingsRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetSettingsRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SecurityGetSettingsResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-security-get_token.asciidoc b/docs/reference-security-get_token.asciidoc new file mode 100644 index 000000000..4cc9f0f69 --- /dev/null +++ b/docs/reference-security-get_token.asciidoc @@ -0,0 +1,73 @@ +[[reference-security-get_token]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getToken + +Get a token. Create a bearer token for access without requiring basic authentication. + +{ref}/security-api-get-token.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetTokenRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetTokenRequest` + +[source,ts] +---- +interface SecurityGetTokenRequest extends <> { + grant_type?: SecurityGetTokenAccessTokenGrantType + scope?: string + password?: <> + kerberos_ticket?: string + refresh_token?: string + username?: <> +} +---- + +[discrete] +===== `SecurityGetTokenResponse` + +[source,ts] +---- +interface SecurityGetTokenResponse { + access_token: string + expires_in: <> + scope?: string + type: string + refresh_token?: string + kerberos_authentication_response_token?: string + authentication: SecurityGetTokenAuthenticatedUser +} +---- + diff --git a/docs/reference-security-get_user.asciidoc b/docs/reference-security-get_user.asciidoc new file mode 100644 index 000000000..83df8b918 --- /dev/null +++ b/docs/reference-security-get_user.asciidoc @@ -0,0 +1,61 @@ +[[reference-security-get_user]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getUser + +Get users. Get information about users in the native realm and built-in users. + +{ref}/security-api-get-user.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetUserRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetUserRequest` + +[source,ts] +---- +interface SecurityGetUserRequest extends <> { + username?: <> | <>[] + with_profile_uid?: boolean +} +---- + +[discrete] +===== `SecurityGetUserResponse` + +[source,ts] +---- +type SecurityGetUserResponse = Record +---- + diff --git a/docs/reference-security-get_user_privileges.asciidoc b/docs/reference-security-get_user_privileges.asciidoc new file mode 100644 index 000000000..3ba27dfbc --- /dev/null +++ b/docs/reference-security-get_user_privileges.asciidoc @@ -0,0 +1,68 @@ +[[reference-security-get_user_privileges]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getUserPrivileges + +Get user privileges. + +{ref}/security-api-get-user-privileges.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetUserPrivilegesRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetUserPrivilegesRequest` + +[source,ts] +---- +interface SecurityGetUserPrivilegesRequest extends <> { + application?: <> + priviledge?: <> + username?: <> | null +} +---- + +[discrete] +===== `SecurityGetUserPrivilegesResponse` + +[source,ts] +---- +interface SecurityGetUserPrivilegesResponse { + applications: SecurityApplicationPrivileges[] + cluster: string[] + global: SecurityGlobalPrivilege[] + indices: SecurityUserIndicesPrivileges[] + run_as: string[] +} +---- + diff --git a/docs/reference-security-get_user_profile.asciidoc b/docs/reference-security-get_user_profile.asciidoc new file mode 100644 index 000000000..17a1c6048 --- /dev/null +++ b/docs/reference-security-get_user_profile.asciidoc @@ -0,0 +1,64 @@ +[[reference-security-get_user_profile]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.getUserProfile + +Get a user profile. Get a user's profile using the unique profile ID. + +{ref}/security-api-get-user-profile.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGetUserProfileRequest, options?): Promise +---- + +[discrete] +===== `SecurityGetUserProfileRequest` + +[source,ts] +---- +interface SecurityGetUserProfileRequest extends <> { + uid: SecurityUserProfileId | SecurityUserProfileId[] + data?: string | string[] +} +---- + +[discrete] +===== `SecurityGetUserProfileResponse` + +[source,ts] +---- +interface SecurityGetUserProfileResponse { + profiles: SecurityUserProfileWithMetadata[] + errors?: SecurityGetUserProfileGetUserProfileErrors +} +---- + diff --git a/docs/reference-security-grant_api_key.asciidoc b/docs/reference-security-grant_api_key.asciidoc new file mode 100644 index 000000000..d93156b22 --- /dev/null +++ b/docs/reference-security-grant_api_key.asciidoc @@ -0,0 +1,71 @@ +[[reference-security-grant_api_key]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.grantApiKey + +Grant an API key. Create an API key on behalf of another user. This API is similar to the create API keys API, however it creates the API key for a user that is different than the user that runs the API. The caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created. It is not possible to use this API to create an API key without that user’s credentials. The user, for whom the authentication credentials is provided, can optionally "run as" (impersonate) another user. In this case, the API key will be created on behalf of the impersonated user. This API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf. A successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name. If applicable, it also returns expiration information for the API key in milliseconds. By default, API keys never expire. You can specify expiration information when you create the API keys. + +{ref}/security-api-grant-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityGrantApiKeyRequest, options?): Promise +---- + +[discrete] +===== `SecurityGrantApiKeyRequest` + +[source,ts] +---- +interface SecurityGrantApiKeyRequest extends <> { + api_key: SecurityGrantApiKeyGrantApiKey + grant_type: SecurityGrantApiKeyApiKeyGrantType + access_token?: string + username?: <> + password?: <> + run_as?: <> +} +---- + +[discrete] +===== `SecurityGrantApiKeyResponse` + +[source,ts] +---- +interface SecurityGrantApiKeyResponse { + api_key: string + id: <> + name: <> + expiration?: <><<>> + encoded: string +} +---- + diff --git a/docs/reference-security-has_privileges.asciidoc b/docs/reference-security-has_privileges.asciidoc new file mode 100644 index 000000000..21da5545e --- /dev/null +++ b/docs/reference-security-has_privileges.asciidoc @@ -0,0 +1,69 @@ +[[reference-security-has_privileges]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.hasPrivileges + +Check user privileges. Determine whether the specified user has a specified list of privileges. + +{ref}/security-api-has-privileges.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityHasPrivilegesRequest, options?): Promise +---- + +[discrete] +===== `SecurityHasPrivilegesRequest` + +[source,ts] +---- +interface SecurityHasPrivilegesRequest extends <> { + user?: <> + application?: SecurityHasPrivilegesApplicationPrivilegesCheck[] + cluster?: SecurityClusterPrivilege[] + index?: SecurityHasPrivilegesIndexPrivilegesCheck[] +} +---- + +[discrete] +===== `SecurityHasPrivilegesResponse` + +[source,ts] +---- +interface SecurityHasPrivilegesResponse { + application: SecurityHasPrivilegesApplicationsPrivileges + cluster: Record + has_all_requested: boolean + index: Record<<>, SecurityHasPrivilegesPrivileges> + username: <> +} +---- + diff --git a/docs/reference-security-has_privileges_user_profile.asciidoc b/docs/reference-security-has_privileges_user_profile.asciidoc new file mode 100644 index 000000000..5da85a160 --- /dev/null +++ b/docs/reference-security-has_privileges_user_profile.asciidoc @@ -0,0 +1,64 @@ +[[reference-security-has_privileges_user_profile]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.hasPrivilegesUserProfile + +Check user profile privileges. Determine whether the users associated with the specified user profile IDs have all the requested privileges. + +{ref}/security-api-has-privileges-user-profile.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityHasPrivilegesUserProfileRequest, options?): Promise +---- + +[discrete] +===== `SecurityHasPrivilegesUserProfileRequest` + +[source,ts] +---- +interface SecurityHasPrivilegesUserProfileRequest extends <> { + uids: SecurityUserProfileId[] + privileges: SecurityHasPrivilegesUserProfilePrivilegesCheck +} +---- + +[discrete] +===== `SecurityHasPrivilegesUserProfileResponse` + +[source,ts] +---- +interface SecurityHasPrivilegesUserProfileResponse { + has_privilege_uids: SecurityUserProfileId[] + errors?: SecurityHasPrivilegesUserProfileHasPrivilegesUserProfileErrors +} +---- + diff --git a/docs/reference-security-invalidate_api_key.asciidoc b/docs/reference-security-invalidate_api_key.asciidoc new file mode 100644 index 000000000..e10c0b644 --- /dev/null +++ b/docs/reference-security-invalidate_api_key.asciidoc @@ -0,0 +1,70 @@ +[[reference-security-invalidate_api_key]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.invalidateApiKey + +Invalidate API keys. This API invalidates API keys created by the create API key or grant API key APIs. Invalidated API keys fail authentication, but they can still be viewed using the get API key information and query API key information APIs, for at least the configured retention period, until they are automatically deleted. The `manage_api_key` privilege allows deleting any API keys. The `manage_own_api_key` only allows deleting API keys that are owned by the user. In addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats: - Set the parameter `owner=true`. - Or, set both `username` and `realm_name` to match the user’s identity. - Or, if the request is issued by an API key, that is to say an API key invalidates itself, specify its ID in the `ids` field. + +{ref}/security-api-invalidate-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityInvalidateApiKeyRequest, options?): Promise +---- + +[discrete] +===== `SecurityInvalidateApiKeyRequest` + +[source,ts] +---- +interface SecurityInvalidateApiKeyRequest extends <> { + id?: <> + ids?: <>[] + name?: <> + owner?: boolean + realm_name?: string + username?: <> +} +---- + +[discrete] +===== `SecurityInvalidateApiKeyResponse` + +[source,ts] +---- +interface SecurityInvalidateApiKeyResponse { + error_count: <> + error_details?: <>[] + invalidated_api_keys: string[] + previously_invalidated_api_keys: string[] +} +---- + diff --git a/docs/reference-security-invalidate_token.asciidoc b/docs/reference-security-invalidate_token.asciidoc new file mode 100644 index 000000000..268fb78a7 --- /dev/null +++ b/docs/reference-security-invalidate_token.asciidoc @@ -0,0 +1,68 @@ +[[reference-security-invalidate_token]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.invalidateToken + +Invalidate a token. The access tokens returned by the get token API have a finite period of time for which they are valid. After that time period, they can no longer be used. The time period is defined by the `xpack.security.authc.token.timeout` setting. The refresh tokens returned by the get token API are only valid for 24 hours. They can also be used exactly once. If you want to invalidate one or more access or refresh tokens immediately, use this invalidate token API. + +{ref}/security-api-invalidate-token.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityInvalidateTokenRequest, options?): Promise +---- + +[discrete] +===== `SecurityInvalidateTokenRequest` + +[source,ts] +---- +interface SecurityInvalidateTokenRequest extends <> { + token?: string + refresh_token?: string + realm_name?: <> + username?: <> +} +---- + +[discrete] +===== `SecurityInvalidateTokenResponse` + +[source,ts] +---- +interface SecurityInvalidateTokenResponse { + error_count: <> + error_details?: <>[] + invalidated_tokens: <> + previously_invalidated_tokens: <> +} +---- + diff --git a/docs/reference-security-oidc_authenticate.asciidoc b/docs/reference-security-oidc_authenticate.asciidoc new file mode 100644 index 000000000..1573af19b --- /dev/null +++ b/docs/reference-security-oidc_authenticate.asciidoc @@ -0,0 +1,59 @@ +[[reference-security-oidc_authenticate]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.oidcAuthenticate + +Exchanges an OpenID Connection authentication response message for an Elasticsearch access token and refresh token pair + +{ref}/security-api-oidc-authenticate.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityOidcAuthenticateRequest, options?): Promise +---- + +[discrete] +===== `SecurityOidcAuthenticateRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SecurityOidcAuthenticateResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-security-oidc_logout.asciidoc b/docs/reference-security-oidc_logout.asciidoc new file mode 100644 index 000000000..5c8ba0836 --- /dev/null +++ b/docs/reference-security-oidc_logout.asciidoc @@ -0,0 +1,59 @@ +[[reference-security-oidc_logout]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.oidcLogout + +Invalidates a refresh token and access token that was generated from the OpenID Connect Authenticate API + +{ref}/security-api-oidc-logout.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityOidcLogoutRequest, options?): Promise +---- + +[discrete] +===== `SecurityOidcLogoutRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SecurityOidcLogoutResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-security-oidc_prepare_authentication.asciidoc b/docs/reference-security-oidc_prepare_authentication.asciidoc new file mode 100644 index 000000000..de1f491a7 --- /dev/null +++ b/docs/reference-security-oidc_prepare_authentication.asciidoc @@ -0,0 +1,59 @@ +[[reference-security-oidc_prepare_authentication]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.oidcPrepareAuthentication + +Creates an OAuth 2.0 authentication request as a URL string + +{ref}/security-api-oidc-prepare-authentication.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityOidcPrepareAuthenticationRequest, options?): Promise +---- + +[discrete] +===== `SecurityOidcPrepareAuthenticationRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SecurityOidcPrepareAuthenticationResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-security-put_privileges.asciidoc b/docs/reference-security-put_privileges.asciidoc new file mode 100644 index 000000000..9aa2c1063 --- /dev/null +++ b/docs/reference-security-put_privileges.asciidoc @@ -0,0 +1,61 @@ +[[reference-security-put_privileges]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.putPrivileges + +Create or update application privileges. + +{ref}/security-api-put-privileges.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityPutPrivilegesRequest, options?): Promise +---- + +[discrete] +===== `SecurityPutPrivilegesRequest` + +[source,ts] +---- +interface SecurityPutPrivilegesRequest extends <> { + refresh?: <> + privileges?: Record> +} +---- + +[discrete] +===== `SecurityPutPrivilegesResponse` + +[source,ts] +---- +type SecurityPutPrivilegesResponse = Record> +---- + diff --git a/docs/reference-security-put_role.asciidoc b/docs/reference-security-put_role.asciidoc new file mode 100644 index 000000000..3d26f0a73 --- /dev/null +++ b/docs/reference-security-put_role.asciidoc @@ -0,0 +1,72 @@ +[[reference-security-put_role]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.putRole + +Create or update roles. The role management APIs are generally the preferred way to manage roles in the native realm, rather than using file-based role management. The create or update roles API cannot update roles that are defined in roles files. File-based role management is not available in Elastic Serverless. + +{ref}/security-api-put-role.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityPutRoleRequest, options?): Promise +---- + +[discrete] +===== `SecurityPutRoleRequest` + +[source,ts] +---- +interface SecurityPutRoleRequest extends <> { + name: <> + refresh?: <> + applications?: SecurityApplicationPrivileges[] + cluster?: SecurityClusterPrivilege[] + global?: Record + indices?: SecurityIndicesPrivileges[] + remote_indices?: SecurityRemoteIndicesPrivileges[] + metadata?: <> + run_as?: string[] + description?: string + transient_metadata?: Record +} +---- + +[discrete] +===== `SecurityPutRoleResponse` + +[source,ts] +---- +interface SecurityPutRoleResponse { + role: SecurityCreatedStatus +} +---- + diff --git a/docs/reference-security-put_role_mapping.asciidoc b/docs/reference-security-put_role_mapping.asciidoc new file mode 100644 index 000000000..87ddca579 --- /dev/null +++ b/docs/reference-security-put_role_mapping.asciidoc @@ -0,0 +1,70 @@ +[[reference-security-put_role_mapping]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.putRoleMapping + +Create or update role mappings. Role mappings define which roles are assigned to each user. Each mapping has rules that identify users and a list of roles that are granted to those users. The role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The create or update role mappings API cannot update role mappings that are defined in role mapping files. This API does not create roles. Rather, it maps users to existing roles. Roles can be created by using the create or update roles API or roles files. + +{ref}/security-api-put-role-mapping.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityPutRoleMappingRequest, options?): Promise +---- + +[discrete] +===== `SecurityPutRoleMappingRequest` + +[source,ts] +---- +interface SecurityPutRoleMappingRequest extends <> { + name: <> + refresh?: <> + enabled?: boolean + metadata?: <> + roles?: string[] + role_templates?: SecurityRoleTemplate[] + rules?: SecurityRoleMappingRule + run_as?: string[] +} +---- + +[discrete] +===== `SecurityPutRoleMappingResponse` + +[source,ts] +---- +interface SecurityPutRoleMappingResponse { + created?: boolean + role_mapping: SecurityCreatedStatus +} +---- + diff --git a/docs/reference-security-put_user.asciidoc b/docs/reference-security-put_user.asciidoc new file mode 100644 index 000000000..ffecbbcc9 --- /dev/null +++ b/docs/reference-security-put_user.asciidoc @@ -0,0 +1,70 @@ +[[reference-security-put_user]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.putUser + +Create or update users. A password is required for adding a new user but is optional when updating an existing user. To change a user’s password without updating any other fields, use the change password API. + +{ref}/security-api-put-user.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityPutUserRequest, options?): Promise +---- + +[discrete] +===== `SecurityPutUserRequest` + +[source,ts] +---- +interface SecurityPutUserRequest extends <> { + username: <> + refresh?: <> + email?: string | null + full_name?: string | null + metadata?: <> + password?: <> + password_hash?: string + roles?: string[] + enabled?: boolean +} +---- + +[discrete] +===== `SecurityPutUserResponse` + +[source,ts] +---- +interface SecurityPutUserResponse { + created: boolean +} +---- + diff --git a/docs/reference-security-query_api_keys.asciidoc b/docs/reference-security-query_api_keys.asciidoc new file mode 100644 index 000000000..5bdae04d2 --- /dev/null +++ b/docs/reference-security-query_api_keys.asciidoc @@ -0,0 +1,75 @@ +[[reference-security-query_api_keys]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.queryApiKeys + +Find API keys with a query. Get a paginated list of API keys and their information. You can optionally filter the results with a query. + +{ref}/security-api-query-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityQueryApiKeysRequest, options?): Promise +---- + +[discrete] +===== `SecurityQueryApiKeysRequest` + +[source,ts] +---- +interface SecurityQueryApiKeysRequest extends <> { + with_limited_by?: boolean + with_profile_uid?: boolean + typed_keys?: boolean + aggregations?: Record + /** @alias aggregations */ + aggs?: Record + query?: SecurityQueryApiKeysApiKeyQueryContainer + from?: <> + sort?: <> + size?: <> + search_after?: <> +} +---- + +[discrete] +===== `SecurityQueryApiKeysResponse` + +[source,ts] +---- +interface SecurityQueryApiKeysResponse { + total: <> + count: <> + api_keys: SecurityApiKey[] + aggregations?: Record<<>, SecurityQueryApiKeysApiKeyAggregate> +} +---- + diff --git a/docs/reference-security-query_role.asciidoc b/docs/reference-security-query_role.asciidoc new file mode 100644 index 000000000..bf64049ee --- /dev/null +++ b/docs/reference-security-query_role.asciidoc @@ -0,0 +1,68 @@ +[[reference-security-query_role]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.queryRole + +Find roles with a query. Get roles in a paginated manner. You can optionally filter the results with a query. + +{ref}/security-api-query-role.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityQueryRoleRequest, options?): Promise +---- + +[discrete] +===== `SecurityQueryRoleRequest` + +[source,ts] +---- +interface SecurityQueryRoleRequest extends <> { + query?: SecurityQueryRoleRoleQueryContainer + from?: <> + sort?: <> + size?: <> + search_after?: <> +} +---- + +[discrete] +===== `SecurityQueryRoleResponse` + +[source,ts] +---- +interface SecurityQueryRoleResponse { + total: <> + count: <> + roles: SecurityQueryRoleQueryRole[] +} +---- + diff --git a/docs/reference-security-query_user.asciidoc b/docs/reference-security-query_user.asciidoc new file mode 100644 index 000000000..740e3e69d --- /dev/null +++ b/docs/reference-security-query_user.asciidoc @@ -0,0 +1,69 @@ +[[reference-security-query_user]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.queryUser + +Find users with a query. Get information for users in a paginated manner. You can optionally filter the results with a query. + +{ref}/security-api-query-user.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityQueryUserRequest, options?): Promise +---- + +[discrete] +===== `SecurityQueryUserRequest` + +[source,ts] +---- +interface SecurityQueryUserRequest extends <> { + with_profile_uid?: boolean + query?: SecurityQueryUserUserQueryContainer + from?: <> + sort?: <> + size?: <> + search_after?: <> +} +---- + +[discrete] +===== `SecurityQueryUserResponse` + +[source,ts] +---- +interface SecurityQueryUserResponse { + total: <> + count: <> + users: SecurityQueryUserQueryUser[] +} +---- + diff --git a/docs/reference-security-saml_authenticate.asciidoc b/docs/reference-security-saml_authenticate.asciidoc new file mode 100644 index 000000000..4156dc4d1 --- /dev/null +++ b/docs/reference-security-saml_authenticate.asciidoc @@ -0,0 +1,68 @@ +[[reference-security-saml_authenticate]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.samlAuthenticate + +Authenticate SAML. Submits a SAML response message to Elasticsearch for consumption. + +{ref}/security-api-saml-authenticate.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecuritySamlAuthenticateRequest, options?): Promise +---- + +[discrete] +===== `SecuritySamlAuthenticateRequest` + +[source,ts] +---- +interface SecuritySamlAuthenticateRequest extends <> { + content: string + ids: <> + realm?: string +} +---- + +[discrete] +===== `SecuritySamlAuthenticateResponse` + +[source,ts] +---- +interface SecuritySamlAuthenticateResponse { + access_token: string + username: string + expires_in: <> + refresh_token: string + realm: string +} +---- + diff --git a/docs/reference-security-saml_complete_logout.asciidoc b/docs/reference-security-saml_complete_logout.asciidoc new file mode 100644 index 000000000..566f797e2 --- /dev/null +++ b/docs/reference-security-saml_complete_logout.asciidoc @@ -0,0 +1,63 @@ +[[reference-security-saml_complete_logout]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.samlCompleteLogout + +Logout of SAML completely. Verifies the logout response sent from the SAML IdP. + +{ref}/security-api-saml-complete-logout.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecuritySamlCompleteLogoutRequest, options?): Promise +---- + +[discrete] +===== `SecuritySamlCompleteLogoutRequest` + +[source,ts] +---- +interface SecuritySamlCompleteLogoutRequest extends <> { + realm: string + ids: <> + query_string?: string + content?: string +} +---- + +[discrete] +===== `SecuritySamlCompleteLogoutResponse` + +[source,ts] +---- +type SecuritySamlCompleteLogoutResponse = boolean +---- + diff --git a/docs/reference-security-saml_invalidate.asciidoc b/docs/reference-security-saml_invalidate.asciidoc new file mode 100644 index 000000000..a7182d978 --- /dev/null +++ b/docs/reference-security-saml_invalidate.asciidoc @@ -0,0 +1,66 @@ +[[reference-security-saml_invalidate]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.samlInvalidate + +Invalidate SAML. Submits a SAML LogoutRequest message to Elasticsearch for consumption. + +{ref}/security-api-saml-invalidate.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecuritySamlInvalidateRequest, options?): Promise +---- + +[discrete] +===== `SecuritySamlInvalidateRequest` + +[source,ts] +---- +interface SecuritySamlInvalidateRequest extends <> { + acs?: string + query_string: string + realm?: string +} +---- + +[discrete] +===== `SecuritySamlInvalidateResponse` + +[source,ts] +---- +interface SecuritySamlInvalidateResponse { + invalidated: <> + realm: string + redirect: string +} +---- + diff --git a/docs/reference-security-saml_logout.asciidoc b/docs/reference-security-saml_logout.asciidoc new file mode 100644 index 000000000..1d53c6ea2 --- /dev/null +++ b/docs/reference-security-saml_logout.asciidoc @@ -0,0 +1,63 @@ +[[reference-security-saml_logout]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.samlLogout + +Logout of SAML. Submits a request to invalidate an access token and refresh token. + +{ref}/security-api-saml-logout.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecuritySamlLogoutRequest, options?): Promise +---- + +[discrete] +===== `SecuritySamlLogoutRequest` + +[source,ts] +---- +interface SecuritySamlLogoutRequest extends <> { + token: string + refresh_token?: string +} +---- + +[discrete] +===== `SecuritySamlLogoutResponse` + +[source,ts] +---- +interface SecuritySamlLogoutResponse { + redirect: string +} +---- + diff --git a/docs/reference-security-saml_prepare_authentication.asciidoc b/docs/reference-security-saml_prepare_authentication.asciidoc new file mode 100644 index 000000000..144788b4e --- /dev/null +++ b/docs/reference-security-saml_prepare_authentication.asciidoc @@ -0,0 +1,66 @@ +[[reference-security-saml_prepare_authentication]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.samlPrepareAuthentication + +Prepare SAML authentication. Creates a SAML authentication request (``) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch. + +{ref}/security-api-saml-prepare-authentication.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecuritySamlPrepareAuthenticationRequest, options?): Promise +---- + +[discrete] +===== `SecuritySamlPrepareAuthenticationRequest` + +[source,ts] +---- +interface SecuritySamlPrepareAuthenticationRequest extends <> { + acs?: string + realm?: string + relay_state?: string +} +---- + +[discrete] +===== `SecuritySamlPrepareAuthenticationResponse` + +[source,ts] +---- +interface SecuritySamlPrepareAuthenticationResponse { + id: <> + realm: string + redirect: string +} +---- + diff --git a/docs/reference-security-saml_service_provider_metadata.asciidoc b/docs/reference-security-saml_service_provider_metadata.asciidoc new file mode 100644 index 000000000..487223b43 --- /dev/null +++ b/docs/reference-security-saml_service_provider_metadata.asciidoc @@ -0,0 +1,62 @@ +[[reference-security-saml_service_provider_metadata]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.samlServiceProviderMetadata + +Create SAML service provider metadata. Generate SAML metadata for a SAML 2.0 Service Provider. + +{ref}/security-api-saml-sp-metadata.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecuritySamlServiceProviderMetadataRequest, options?): Promise +---- + +[discrete] +===== `SecuritySamlServiceProviderMetadataRequest` + +[source,ts] +---- +interface SecuritySamlServiceProviderMetadataRequest extends <> { + realm_name: <> +} +---- + +[discrete] +===== `SecuritySamlServiceProviderMetadataResponse` + +[source,ts] +---- +interface SecuritySamlServiceProviderMetadataResponse { + metadata: string +} +---- + diff --git a/docs/reference-security-suggest_user_profiles.asciidoc b/docs/reference-security-suggest_user_profiles.asciidoc new file mode 100644 index 000000000..3a9cbaceb --- /dev/null +++ b/docs/reference-security-suggest_user_profiles.asciidoc @@ -0,0 +1,67 @@ +[[reference-security-suggest_user_profiles]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.suggestUserProfiles + +Suggest a user profile. Get suggestions for user profiles that match specified search criteria. + +{ref}/security-api-suggest-user-profile.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecuritySuggestUserProfilesRequest, options?): Promise +---- + +[discrete] +===== `SecuritySuggestUserProfilesRequest` + +[source,ts] +---- +interface SecuritySuggestUserProfilesRequest extends <> { + name?: string + size?: <> + data?: string | string[] + hint?: SecuritySuggestUserProfilesHint +} +---- + +[discrete] +===== `SecuritySuggestUserProfilesResponse` + +[source,ts] +---- +interface SecuritySuggestUserProfilesResponse { + total: SecuritySuggestUserProfilesTotalUserProfiles + took: <> + profiles: SecurityUserProfile[] +} +---- + diff --git a/docs/reference-security-update_api_key.asciidoc b/docs/reference-security-update_api_key.asciidoc new file mode 100644 index 000000000..891d1a67c --- /dev/null +++ b/docs/reference-security-update_api_key.asciidoc @@ -0,0 +1,65 @@ +[[reference-security-update_api_key]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.updateApiKey + +Update an API key. Updates attributes of an existing API key. Users can only update API keys that they created or that were granted to them. Use this API to update API keys created by the create API Key or grant API Key APIs. If you need to apply the same update to many API keys, you can use bulk update API Keys to reduce overhead. It’s not possible to update expired API keys, or API keys that have been invalidated by invalidate API Key. This API supports updates to an API key’s access scope and metadata. The access scope of an API key is derived from the `role_descriptors` you specify in the request, and a snapshot of the owner user’s permissions at the time of the request. The snapshot of the owner’s permissions is updated automatically on every call. If you don’t specify `role_descriptors` in the request, a call to this API might still change the API key’s access scope. This change can occur if the owner user’s permissions have changed since the API key was created or last modified. To update another user’s API key, use the `run_as` feature to submit a request on behalf of another user. IMPORTANT: It’s not possible to use an API key as the authentication credential for this API. To update an API key, the owner user’s credentials are required. + +{ref}/security-api-update-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityUpdateApiKeyRequest, options?): Promise +---- + +[discrete] +===== `SecurityUpdateApiKeyRequest` + +[source,ts] +---- +interface SecurityUpdateApiKeyRequest extends <> { + id: <> + role_descriptors?: Record + metadata?: <> + expiration?: <> +} +---- + +[discrete] +===== `SecurityUpdateApiKeyResponse` + +[source,ts] +---- +interface SecurityUpdateApiKeyResponse { + updated: boolean +} +---- + diff --git a/docs/reference-security-update_cross_cluster_api_key.asciidoc b/docs/reference-security-update_cross_cluster_api_key.asciidoc new file mode 100644 index 000000000..8ba3da305 --- /dev/null +++ b/docs/reference-security-update_cross_cluster_api_key.asciidoc @@ -0,0 +1,65 @@ +[[reference-security-update_cross_cluster_api_key]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.updateCrossClusterApiKey + +Update a cross-cluster API key. Update the attributes of an existing cross-cluster API key, which is used for API key based remote cluster access. + +{ref}/security-api-update-cross-cluster-api-key.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityUpdateCrossClusterApiKeyRequest, options?): Promise +---- + +[discrete] +===== `SecurityUpdateCrossClusterApiKeyRequest` + +[source,ts] +---- +interface SecurityUpdateCrossClusterApiKeyRequest extends <> { + id: <> + access: SecurityAccess + expiration?: <> + metadata?: <> +} +---- + +[discrete] +===== `SecurityUpdateCrossClusterApiKeyResponse` + +[source,ts] +---- +interface SecurityUpdateCrossClusterApiKeyResponse { + updated: boolean +} +---- + diff --git a/docs/reference-security-update_settings.asciidoc b/docs/reference-security-update_settings.asciidoc new file mode 100644 index 000000000..61273c475 --- /dev/null +++ b/docs/reference-security-update_settings.asciidoc @@ -0,0 +1,59 @@ +[[reference-security-update_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.updateSettings + +Update settings for the security system index + +{ref}/security-api-update-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityUpdateSettingsRequest, options?): Promise +---- + +[discrete] +===== `SecurityUpdateSettingsRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SecurityUpdateSettingsResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-security-update_user_profile_data.asciidoc b/docs/reference-security-update_user_profile_data.asciidoc new file mode 100644 index 000000000..c36db3da6 --- /dev/null +++ b/docs/reference-security-update_user_profile_data.asciidoc @@ -0,0 +1,65 @@ +[[reference-security-update_user_profile_data]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.security.updateUserProfileData + +Update user profile data. Update specific data for the user profile that is associated with a unique ID. + +{ref}/security-api-update-user-profile-data.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SecurityUpdateUserProfileDataRequest, options?): Promise +---- + +[discrete] +===== `SecurityUpdateUserProfileDataRequest` + +[source,ts] +---- +interface SecurityUpdateUserProfileDataRequest extends <> { + uid: SecurityUserProfileId + if_seq_no?: <> + if_primary_term?: <> + refresh?: <> + labels?: Record + data?: Record +} +---- + +[discrete] +===== `SecurityUpdateUserProfileDataResponse` + +[source,ts] +---- +type SecurityUpdateUserProfileDataResponse = <> +---- + diff --git a/docs/reference-shared-types.asciidoc b/docs/reference-shared-types.asciidoc new file mode 100644 index 000000000..8f1cabc8a --- /dev/null +++ b/docs/reference-shared-types.asciidoc @@ -0,0 +1,2282 @@ +[[reference-shared-types]] += Types + +[[shared-type-acknowledged-response-base]] +== AcknowledgedResponseBase + +[source,ts] +--- +interface AcknowledgedResponseBase { + /** @property acknowledged For a successful response, this value is always true. On failure, an exception is returned instead. */ + acknowledged: boolean +} +--- + +[[shared-type-aggregate-name]] +== AggregateName + +[source,ts] +--- +type AggregateName = string +--- + +[[shared-type-bulk-index-by-scroll-failure]] +== BulkIndexByScrollFailure + +[source,ts] +--- +interface BulkIndexByScrollFailure { + cause: ErrorCause + id: Id + index: IndexName + status: integer + type: string +} +--- + +[[shared-type-bulk-stats]] +== BulkStats + +[source,ts] +--- +interface BulkStats { + total_operations: long + total_time?: Duration + total_time_in_millis: DurationValue + total_size?: ByteSize + total_size_in_bytes: long + avg_time?: Duration + avg_time_in_millis: DurationValue + avg_size?: ByteSize + avg_size_in_bytes: long +} +--- + +[[shared-type-byte-size]] +== ByteSize + +[source,ts] +--- +type ByteSize = long | string +--- + +[[shared-type-bytes]] +== Bytes + +[source,ts] +--- +type Bytes = 'b' | 'kb' | 'mb' | 'gb' | 'tb' | 'pb' +--- + +[[shared-type-category-id]] +== CategoryId + +[source,ts] +--- +type CategoryId = string +--- + +[[shared-type-cluster-alias]] +== ClusterAlias + +[source,ts] +--- +type ClusterAlias = string +--- + +[[shared-type-cluster-details]] +== ClusterDetails + +[source,ts] +--- +interface ClusterDetails { + status: ClusterSearchStatus + indices: string + took?: DurationValue + timed_out: boolean + _shards?: ShardStatistics + failures?: ShardFailure[] +} +--- + +[[shared-type-cluster-info-target]] +== ClusterInfoTarget + +[source,ts] +--- +type ClusterInfoTarget = '_all' | 'http' | 'ingest' | 'thread_pool' | 'script' +--- + +[[shared-type-cluster-info-targets]] +== ClusterInfoTargets + +[source,ts] +--- +type ClusterInfoTargets = ClusterInfoTarget | ClusterInfoTarget[] +--- + +[[shared-type-cluster-search-status]] +== ClusterSearchStatus + +[source,ts] +--- +type ClusterSearchStatus = 'running' | 'successful' | 'partial' | 'skipped' | 'failed' +--- + +[[shared-type-cluster-statistics]] +== ClusterStatistics + +[source,ts] +--- +interface ClusterStatistics { + skipped: integer + successful: integer + total: integer + running: integer + partial: integer + failed: integer + details?: Record +} +--- + +[[shared-type-completion-stats]] +== CompletionStats + +[source,ts] +--- +interface CompletionStats { + /** @property size_in_bytes Total amount, in bytes, of memory used for completion across all shards assigned to selected nodes. */ + size_in_bytes: long + /** @property size Total amount of memory used for completion across all shards assigned to selected nodes. */ + size?: ByteSize + fields?: Record +} +--- + +[[shared-type-conflicts]] +== Conflicts + +[source,ts] +--- +type Conflicts = 'abort' | 'proceed' +--- + +[[shared-type-coords-geo-bounds]] +== CoordsGeoBounds + +[source,ts] +--- +interface CoordsGeoBounds { + top: double + bottom: double + left: double + right: double +} +--- + +[[shared-type-d-f-i-independence-measure]] +== DFIIndependenceMeasure + +[source,ts] +--- +type DFIIndependenceMeasure = 'standardized' | 'saturated' | 'chisquared' +--- + +[[shared-type-d-f-r-after-effect]] +== DFRAfterEffect + +[source,ts] +--- +type DFRAfterEffect = 'no' | 'b' | 'l' +--- + +[[shared-type-d-f-r-basic-model]] +== DFRBasicModel + +[source,ts] +--- +type DFRBasicModel = 'be' | 'd' | 'g' | 'if' | 'in' | 'ine' | 'p' +--- + +[[shared-type-data-stream-name]] +== DataStreamName + +[source,ts] +--- +type DataStreamName = string +--- + +[[shared-type-data-stream-names]] +== DataStreamNames + +[source,ts] +--- +type DataStreamNames = DataStreamName | DataStreamName[] +--- + +[[shared-type-date-format]] +== DateFormat + +[source,ts] +--- +type DateFormat = string +--- + +[[shared-type-date-math]] +== DateMath + +[source,ts] +--- +type DateMath = string | Date +--- + +[[shared-type-date-time]] +== DateTime + +[source,ts] +--- +type DateTime = string | EpochTime | Date +--- + +[[shared-type-distance]] +== Distance + +[source,ts] +--- +type Distance = string +--- + +[[shared-type-distance-unit]] +== DistanceUnit + +[source,ts] +--- +type DistanceUnit = 'in' | 'ft' | 'yd' | 'mi' | 'nmi' | 'km' | 'm' | 'cm' | 'mm' +--- + +[[shared-type-doc-stats]] +== DocStats + +[source,ts] +--- +interface DocStats { + /** @property count Total number of non-deleted documents across all primary shards assigned to selected nodes. This number is based on documents in Lucene segments and may include documents from nested fields. */ + count: long + /** @property deleted Total number of deleted documents across all primary shards assigned to selected nodes. This number is based on documents in Lucene segments. Elasticsearch reclaims the disk space of deleted Lucene documents when a segment is merged. */ + deleted?: long +} +--- + +[[shared-type-duration]] +== Duration + +[source,ts] +--- +type Duration = string | -1 | 0 +--- + +[[shared-type-duration-large]] +== DurationLarge + +[source,ts] +--- +type DurationLarge = string +--- + +[[shared-type-duration-value]] +== DurationValue + +[source,ts] +--- +type DurationValue = Unit +--- + +[[shared-type-elasticsearch-version-info]] +== ElasticsearchVersionInfo + +[source,ts] +--- +interface ElasticsearchVersionInfo { + build_date: DateTime + build_flavor: string + build_hash: string + build_snapshot: boolean + build_type: string + lucene_version: VersionString + minimum_index_compatibility_version: VersionString + minimum_wire_compatibility_version: VersionString + number: string +} +--- + +[[shared-type-elasticsearch-version-min-info]] +== ElasticsearchVersionMinInfo + +[source,ts] +--- +interface ElasticsearchVersionMinInfo { + build_flavor: string + minimum_index_compatibility_version: VersionString + minimum_wire_compatibility_version: VersionString + number: string +} +--- + +[[shared-type-empty-object]] +== EmptyObject + +[source,ts] +--- +interface EmptyObject { +} +--- + +[[shared-type-epoch-time]] +== EpochTime + +[source,ts] +--- +type EpochTime = Unit +--- + +[[shared-type-error-cause]] +== ErrorCause + +[source,ts] +--- +interface ErrorCauseKeys { + type: string + reason?: string + stack_trace?: string + caused_by?: ErrorCause + root_cause?: ErrorCause[] + suppressed?: ErrorCause[] +} +export type ErrorCause = ErrorCauseKeys + & { [property: string]: any } +--- + +[[shared-type-error-response-base]] +== ErrorResponseBase + +[source,ts] +--- +interface ErrorResponseBase { + error: ErrorCause + status: integer +} +--- + +[[shared-type-esql-columns]] +== EsqlColumns + +[source,ts] +--- +type EsqlColumns = ArrayBuffer +--- + +[[shared-type-expand-wildcard]] +== ExpandWildcard + +[source,ts] +--- +type ExpandWildcard = 'all' | 'open' | 'closed' | 'hidden' | 'none' +--- + +[[shared-type-expand-wildcards]] +== ExpandWildcards + +[source,ts] +--- +type ExpandWildcards = ExpandWildcard | ExpandWildcard[] +--- + +[[shared-type-field]] +== Field + +[source,ts] +--- +type Field = string +--- + +[[shared-type-field-memory-usage]] +== FieldMemoryUsage + +[source,ts] +--- +interface FieldMemoryUsage { + memory_size?: ByteSize + memory_size_in_bytes: long +} +--- + +[[shared-type-field-size-usage]] +== FieldSizeUsage + +[source,ts] +--- +interface FieldSizeUsage { + size?: ByteSize + size_in_bytes: long +} +--- + +[[shared-type-field-sort]] +== FieldSort + +[source,ts] +--- +interface FieldSort { + missing?: AggregationsMissing + mode?: SortMode + nested?: NestedSortValue + order?: SortOrder + unmapped_type?: MappingFieldType + numeric_type?: FieldSortNumericType + format?: string +} +--- + +[[shared-type-field-sort-numeric-type]] +== FieldSortNumericType + +[source,ts] +--- +type FieldSortNumericType = 'long' | 'double' | 'date' | 'date_nanos' +--- + +[[shared-type-field-value]] +== FieldValue + +[source,ts] +--- +type FieldValue = long | double | string | boolean | null | any +--- + +[[shared-type-fielddata-stats]] +== FielddataStats + +[source,ts] +--- +interface FielddataStats { + evictions?: long + memory_size?: ByteSize + memory_size_in_bytes: long + fields?: Record +} +--- + +[[shared-type-fields]] +== Fields + +[source,ts] +--- +type Fields = Field | Field[] +--- + +[[shared-type-flush-stats]] +== FlushStats + +[source,ts] +--- +interface FlushStats { + periodic: long + total: long + total_time?: Duration + total_time_in_millis: DurationValue +} +--- + +[[shared-type-fuzziness]] +== Fuzziness + +[source,ts] +--- +type Fuzziness = string | integer +--- + +[[shared-type-geo-bounds]] +== GeoBounds + +[source,ts] +--- +type GeoBounds = CoordsGeoBounds | TopLeftBottomRightGeoBounds | TopRightBottomLeftGeoBounds | WktGeoBounds +--- + +[[shared-type-geo-distance-sort]] +== GeoDistanceSort + +[source,ts] +--- +interface GeoDistanceSortKeys { + mode?: SortMode + distance_type?: GeoDistanceType + ignore_unmapped?: boolean + order?: SortOrder + unit?: DistanceUnit + nested?: NestedSortValue +} +export type GeoDistanceSort = GeoDistanceSortKeys + & { [property: string]: GeoLocation | GeoLocation[] | SortMode | GeoDistanceType | boolean | SortOrder | DistanceUnit | NestedSortValue } +--- + +[[shared-type-geo-distance-type]] +== GeoDistanceType + +[source,ts] +--- +type GeoDistanceType = 'arc' | 'plane' +--- + +[[shared-type-geo-hash]] +== GeoHash + +[source,ts] +--- +type GeoHash = string +--- + +[[shared-type-geo-hash-location]] +== GeoHashLocation + +[source,ts] +--- +interface GeoHashLocation { + geohash: GeoHash +} +--- + +[[shared-type-geo-hash-precision]] +== GeoHashPrecision + +[source,ts] +--- +type GeoHashPrecision = number | string +--- + +[[shared-type-geo-hex-cell]] +== GeoHexCell + +[source,ts] +--- +type GeoHexCell = string +--- + +[[shared-type-geo-line]] +== GeoLine + +[source,ts] +--- +interface GeoLine { + /** @property type Always `"LineString"` */ + type: string + /** @property coordinates Array of `[lon, lat]` coordinates */ + coordinates: double[][] +} +--- + +[[shared-type-geo-location]] +== GeoLocation + +[source,ts] +--- +type GeoLocation = LatLonGeoLocation | GeoHashLocation | double[] | string +--- + +[[shared-type-geo-shape]] +== GeoShape + +[source,ts] +--- +type GeoShape = any +--- + +[[shared-type-geo-shape-relation]] +== GeoShapeRelation + +[source,ts] +--- +type GeoShapeRelation = 'intersects' | 'disjoint' | 'within' | 'contains' +--- + +[[shared-type-geo-tile]] +== GeoTile + +[source,ts] +--- +type GeoTile = string +--- + +[[shared-type-geo-tile-precision]] +== GeoTilePrecision + +[source,ts] +--- +type GeoTilePrecision = number +--- + +[[shared-type-get-stats]] +== GetStats + +[source,ts] +--- +interface GetStats { + current: long + exists_time?: Duration + exists_time_in_millis: DurationValue + exists_total: long + missing_time?: Duration + missing_time_in_millis: DurationValue + missing_total: long + time?: Duration + time_in_millis: DurationValue + total: long +} +--- + +[[shared-type-grok-pattern]] +== GrokPattern + +[source,ts] +--- +type GrokPattern = string +--- + +[[shared-type-health-status]] +== HealthStatus + +[source,ts] +--- +type HealthStatus = 'green' | 'GREEN' | 'yellow' | 'YELLOW' | 'red' | 'RED' +--- + +[[shared-type-host]] +== Host + +[source,ts] +--- +type Host = string +--- + +[[shared-type-http-headers]] +== HttpHeaders + +[source,ts] +--- +type HttpHeaders = Record +--- + +[[shared-type-i-b-distribution]] +== IBDistribution + +[source,ts] +--- +type IBDistribution = 'll' | 'spl' +--- + +[[shared-type-i-b-lambda]] +== IBLambda + +[source,ts] +--- +type IBLambda = 'df' | 'ttf' +--- + +[[shared-type-id]] +== Id + +[source,ts] +--- +type Id = string +--- + +[[shared-type-ids]] +== Ids + +[source,ts] +--- +type Ids = Id | Id[] +--- + +[[shared-type-index-alias]] +== IndexAlias + +[source,ts] +--- +type IndexAlias = string +--- + +[[shared-type-index-name]] +== IndexName + +[source,ts] +--- +type IndexName = string +--- + +[[shared-type-index-pattern]] +== IndexPattern + +[source,ts] +--- +type IndexPattern = string +--- + +[[shared-type-index-patterns]] +== IndexPatterns + +[source,ts] +--- +type IndexPatterns = IndexPattern[] +--- + +[[shared-type-indexing-stats]] +== IndexingStats + +[source,ts] +--- +interface IndexingStats { + index_current: long + delete_current: long + delete_time?: Duration + delete_time_in_millis: DurationValue + delete_total: long + is_throttled: boolean + noop_update_total: long + throttle_time?: Duration + throttle_time_in_millis: DurationValue + index_time?: Duration + index_time_in_millis: DurationValue + index_total: long + index_failed: long + types?: Record + write_load?: double +} +--- + +[[shared-type-indices]] +== Indices + +[source,ts] +--- +type Indices = IndexName | IndexName[] +--- + +[[shared-type-indices-options]] +== IndicesOptions + +[source,ts] +--- +interface IndicesOptions { + /** @property 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`. */ + allow_no_indices?: boolean + /** @property expand_wildcards 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. Supports comma-separated values, such as `open,hidden`. */ + expand_wildcards?: ExpandWildcards + /** @property ignore_unavailable If true, missing or closed indices are not included in the response. */ + ignore_unavailable?: boolean + /** @property ignore_throttled If true, concrete, expanded or aliased indices are ignored when frozen. */ + ignore_throttled?: boolean +} +--- + +[[shared-type-indices-response-base]] +== IndicesResponseBase + +[source,ts] +--- +interface IndicesResponseBase extends AcknowledgedResponseBase { + _shards?: ShardStatistics +} +--- + +[[shared-type-inline-get]] +== InlineGet + +[source,ts] +--- +interface InlineGetKeys { + fields?: Record + found: boolean + _seq_no?: SequenceNumber + _primary_term?: long + _routing?: Routing + _source?: TDocument +} +export type InlineGet = InlineGetKeys + & { [property: string]: any } +--- + +[[shared-type-ip]] +== Ip + +[source,ts] +--- +type Ip = string +--- + +[[shared-type-knn-query]] +== KnnQuery + +[source,ts] +--- +interface KnnQuery extends QueryDslQueryBase { + /** @property field The name of the vector field to search against */ + field: Field + /** @property query_vector The query vector */ + query_vector?: QueryVector + /** @property query_vector_builder The query vector builder. You must provide a query_vector_builder or query_vector, but not both. */ + query_vector_builder?: QueryVectorBuilder + /** @property num_candidates The number of nearest neighbor candidates to consider per shard */ + num_candidates?: integer + /** @property k The final number of nearest neighbors to return as top hits */ + k?: integer + /** @property filter Filters for the kNN search query */ + filter?: QueryDslQueryContainer | QueryDslQueryContainer[] + /** @property similarity The minimum similarity for a vector to be considered a match */ + similarity?: float +} +--- + +[[shared-type-knn-retriever]] +== KnnRetriever + +[source,ts] +--- +interface KnnRetriever extends RetrieverBase { + /** @property field The name of the vector field to search against. */ + field: string + /** @property query_vector Query vector. Must have the same number of dimensions as the vector field you are searching against. You must provide a query_vector_builder or query_vector, but not both. */ + query_vector?: QueryVector + /** @property query_vector_builder Defines a model to build a query vector. */ + query_vector_builder?: QueryVectorBuilder + /** @property k Number of nearest neighbors to return as top hits. */ + k: integer + /** @property num_candidates Number of nearest neighbor candidates to consider per shard. */ + num_candidates: integer + /** @property similarity The minimum similarity required for a document to be considered a match. */ + similarity?: float +} +--- + +[[shared-type-knn-search]] +== KnnSearch + +[source,ts] +--- +interface KnnSearch { + /** @property field The name of the vector field to search against */ + field: Field + /** @property query_vector The query vector */ + query_vector?: QueryVector + /** @property query_vector_builder The query vector builder. You must provide a query_vector_builder or query_vector, but not both. */ + query_vector_builder?: QueryVectorBuilder + /** @property k The final number of nearest neighbors to return as top hits */ + k?: integer + /** @property num_candidates The number of nearest neighbor candidates to consider per shard */ + num_candidates?: integer + /** @property boost Boost value to apply to kNN scores */ + boost?: float + /** @property filter Filters for the kNN search query */ + filter?: QueryDslQueryContainer | QueryDslQueryContainer[] + /** @property similarity The minimum similarity for a vector to be considered a match */ + similarity?: float + /** @property inner_hits If defined, each search hit will contain inner hits. */ + inner_hits?: SearchInnerHits +} +--- + +[[shared-type-lat-lon-geo-location]] +== LatLonGeoLocation + +[source,ts] +--- +interface LatLonGeoLocation { + /** @property lat Latitude */ + lat: double + /** @property lon Longitude */ + lon: double +} +--- + +[[shared-type-level]] +== Level + +[source,ts] +--- +type Level = 'cluster' | 'indices' | 'shards' +--- + +[[shared-type-lifecycle-operation-mode]] +== LifecycleOperationMode + +[source,ts] +--- +type LifecycleOperationMode = 'RUNNING' | 'STOPPING' | 'STOPPED' +--- + +[[shared-type-mapbox-vector-tiles]] +== MapboxVectorTiles + +[source,ts] +--- +type MapboxVectorTiles = ArrayBuffer +--- + +[[shared-type-merges-stats]] +== MergesStats + +[source,ts] +--- +interface MergesStats { + current: long + current_docs: long + current_size?: string + current_size_in_bytes: long + total: long + total_auto_throttle?: string + total_auto_throttle_in_bytes: long + total_docs: long + total_size?: string + total_size_in_bytes: long + total_stopped_time?: Duration + total_stopped_time_in_millis: DurationValue + total_throttled_time?: Duration + total_throttled_time_in_millis: DurationValue + total_time?: Duration + total_time_in_millis: DurationValue +} +--- + +[[shared-type-metadata]] +== Metadata + +[source,ts] +--- +type Metadata = Record +--- + +[[shared-type-metrics]] +== Metrics + +[source,ts] +--- +type Metrics = string | string[] +--- + +[[shared-type-minimum-should-match]] +== MinimumShouldMatch + +[source,ts] +--- +type MinimumShouldMatch = integer | string +--- + +[[shared-type-multi-term-query-rewrite]] +== MultiTermQueryRewrite + +[source,ts] +--- +type MultiTermQueryRewrite = string +--- + +[[shared-type-name]] +== Name + +[source,ts] +--- +type Name = string +--- + +[[shared-type-names]] +== Names + +[source,ts] +--- +type Names = Name | Name[] +--- + +[[shared-type-namespace]] +== Namespace + +[source,ts] +--- +type Namespace = string +--- + +[[shared-type-nested-sort-value]] +== NestedSortValue + +[source,ts] +--- +interface NestedSortValue { + filter?: QueryDslQueryContainer + max_children?: integer + nested?: NestedSortValue + path: Field +} +--- + +[[shared-type-node-attributes]] +== NodeAttributes + +[source,ts] +--- +interface NodeAttributes { + /** @property attributes Lists node attributes. */ + attributes: Record + /** @property ephemeral_id The ephemeral ID of the node. */ + ephemeral_id: Id + /** @property id The unique identifier of the node. */ + id?: NodeId + /** @property name The unique identifier of the node. */ + name: NodeName + /** @property transport_address The host and port where transport HTTP connections are accepted. */ + transport_address: TransportAddress +} +--- + +[[shared-type-node-id]] +== NodeId + +[source,ts] +--- +type NodeId = string +--- + +[[shared-type-node-ids]] +== NodeIds + +[source,ts] +--- +type NodeIds = NodeId | NodeId[] +--- + +[[shared-type-node-name]] +== NodeName + +[source,ts] +--- +type NodeName = string +--- + +[[shared-type-node-role]] +== NodeRole + +[source,ts] +--- +type NodeRole = 'master' | 'data' | 'data_cold' | 'data_content' | 'data_frozen' | 'data_hot' | 'data_warm' | 'client' | 'ingest' | 'ml' | 'voting_only' | 'transform' | 'remote_cluster_client' | 'coordinating_only' +--- + +[[shared-type-node-roles]] +== NodeRoles + +[source,ts] +--- +type NodeRoles = NodeRole[] +--- + +[[shared-type-node-shard]] +== NodeShard + +[source,ts] +--- +interface NodeShard { + state: IndicesStatsShardRoutingState + primary: boolean + node?: NodeName + shard: integer + index: IndexName + allocation_id?: Record + recovery_source?: Record + unassigned_info?: ClusterAllocationExplainUnassignedInformation + relocating_node?: NodeId | null + relocation_failure_info?: RelocationFailureInfo +} +--- + +[[shared-type-node-statistics]] +== NodeStatistics + +[source,ts] +--- +interface NodeStatistics { + failures?: ErrorCause[] + /** @property total Total number of nodes selected by the request. */ + total: integer + /** @property successful Number of nodes that responded successfully to the request. */ + successful: integer + /** @property failed Number of nodes that rejected the request or failed to respond. If this value is not 0, a reason for the rejection or failure is included in the response. */ + failed: integer +} +--- + +[[shared-type-normalization]] +== Normalization + +[source,ts] +--- +type Normalization = 'no' | 'h1' | 'h2' | 'h3' | 'z' +--- + +[[shared-type-op-type]] +== OpType + +[source,ts] +--- +type OpType = 'index' | 'create' +--- + +[[shared-type-password]] +== Password + +[source,ts] +--- +type Password = string +--- + +[[shared-type-percentage]] +== Percentage + +[source,ts] +--- +type Percentage = string | float +--- + +[[shared-type-pipeline-name]] +== PipelineName + +[source,ts] +--- +type PipelineName = string +--- + +[[shared-type-plugin-stats]] +== PluginStats + +[source,ts] +--- +interface PluginStats { + classname: string + description: string + elasticsearch_version: VersionString + extended_plugins: string[] + has_native_controller: boolean + java_version: VersionString + name: Name + version: VersionString + licensed: boolean +} +--- + +[[shared-type-property-name]] +== PropertyName + +[source,ts] +--- +type PropertyName = string +--- + +[[shared-type-query-cache-stats]] +== QueryCacheStats + +[source,ts] +--- +interface QueryCacheStats { + /** @property cache_count Total number of entries added to the query cache across all shards assigned to selected nodes. This number includes current and evicted entries. */ + cache_count: long + /** @property cache_size Total number of entries currently in the query cache across all shards assigned to selected nodes. */ + cache_size: long + /** @property evictions Total number of query cache evictions across all shards assigned to selected nodes. */ + evictions: long + /** @property hit_count Total count of query cache hits across all shards assigned to selected nodes. */ + hit_count: long + /** @property memory_size Total amount of memory used for the query cache across all shards assigned to selected nodes. */ + memory_size?: ByteSize + /** @property memory_size_in_bytes Total amount, in bytes, of memory used for the query cache across all shards assigned to selected nodes. */ + memory_size_in_bytes: long + /** @property miss_count Total count of query cache misses across all shards assigned to selected nodes. */ + miss_count: long + /** @property total_count Total count of hits and misses in the query cache across all shards assigned to selected nodes. */ + total_count: long +} +--- + +[[shared-type-query-vector]] +== QueryVector + +[source,ts] +--- +type QueryVector = float[] +--- + +[[shared-type-query-vector-builder]] +== QueryVectorBuilder + +[source,ts] +--- +interface QueryVectorBuilder { + text_embedding?: TextEmbedding +} +--- + +[[shared-type-r-r-f-retriever]] +== RRFRetriever + +[source,ts] +--- +interface RRFRetriever extends RetrieverBase { + /** @property retrievers A list of child retrievers to specify which sets of returned top documents will have the RRF formula applied to them. */ + retrievers: RetrieverContainer[] + /** @property rank_constant This value determines how much influence documents in individual result sets per query have over the final ranked result set. */ + rank_constant?: integer + /** @property rank_window_size This value determines the size of the individual result sets per query. */ + rank_window_size?: integer +} +--- + +[[shared-type-rank-base]] +== RankBase + +[source,ts] +--- +interface RankBase { +} +--- + +[[shared-type-rank-container]] +== RankContainer + +[source,ts] +--- +interface RankContainer { + /** @property rrf The reciprocal rank fusion parameters */ + rrf?: RrfRank +} +--- + +[[shared-type-recovery-stats]] +== RecoveryStats + +[source,ts] +--- +interface RecoveryStats { + current_as_source: long + current_as_target: long + throttle_time?: Duration + throttle_time_in_millis: DurationValue +} +--- + +[[shared-type-refresh]] +== Refresh + +[source,ts] +--- +type Refresh = boolean | 'true' | 'false' | 'wait_for' +--- + +[[shared-type-refresh-stats]] +== RefreshStats + +[source,ts] +--- +interface RefreshStats { + external_total: long + external_total_time_in_millis: DurationValue + listeners: long + total: long + total_time?: Duration + total_time_in_millis: DurationValue +} +--- + +[[shared-type-relation-name]] +== RelationName + +[source,ts] +--- +type RelationName = string +--- + +[[shared-type-relocation-failure-info]] +== RelocationFailureInfo + +[source,ts] +--- +interface RelocationFailureInfo { + failed_attempts: integer +} +--- + +[[shared-type-request-base]] +== RequestBase + +[source,ts] +--- +interface RequestBase extends SpecUtilsCommonQueryParameters { +} +--- + +[[shared-type-request-cache-stats]] +== RequestCacheStats + +[source,ts] +--- +interface RequestCacheStats { + evictions: long + hit_count: long + memory_size?: string + memory_size_in_bytes: long + miss_count: long +} +--- + +[[shared-type-result]] +== Result + +[source,ts] +--- +type Result = 'created' | 'updated' | 'deleted' | 'not_found' | 'noop' +--- + +[[shared-type-retries]] +== Retries + +[source,ts] +--- +interface Retries { + bulk: long + search: long +} +--- + +[[shared-type-retriever-base]] +== RetrieverBase + +[source,ts] +--- +interface RetrieverBase { + /** @property filter Query to filter the documents that can match. */ + filter?: QueryDslQueryContainer | QueryDslQueryContainer[] + /** @property min_score Minimum _score for matching documents. Documents with a lower _score are not included in the top documents. */ + min_score?: float +} +--- + +[[shared-type-retriever-container]] +== RetrieverContainer + +[source,ts] +--- +interface RetrieverContainer { + /** @property standard A retriever that replaces the functionality of a traditional query. */ + standard?: StandardRetriever + /** @property knn A retriever that replaces the functionality of a knn search. */ + knn?: KnnRetriever + /** @property rrf A retriever that produces top documents from reciprocal rank fusion (RRF). */ + rrf?: RRFRetriever + /** @property text_similarity_reranker A retriever that reranks the top documents based on a reranking model using the InferenceAPI */ + text_similarity_reranker?: TextSimilarityReranker +} +--- + +[[shared-type-routing]] +== Routing + +[source,ts] +--- +type Routing = string +--- + +[[shared-type-rrf-rank]] +== RrfRank + +[source,ts] +--- +interface RrfRank { + /** @property rank_constant How much influence documents in individual result sets per query have over the final ranked result set */ + rank_constant?: long + /** @property rank_window_size Size of the individual result sets per query */ + rank_window_size?: long +} +--- + +[[shared-type-scalar-value]] +== ScalarValue + +[source,ts] +--- +type ScalarValue = long | double | string | boolean | null +--- + +[[shared-type-score-sort]] +== ScoreSort + +[source,ts] +--- +interface ScoreSort { + order?: SortOrder +} +--- + +[[shared-type-script]] +== Script + +[source,ts] +--- +interface Script { + /** @property source The script source. */ + source?: string + /** @property id The `id` for a stored script. */ + id?: Id + /** @property params Specifies any named parameters that are passed into the script as variables. Use parameters instead of hard-coded values to decrease compile time. */ + params?: Record + /** @property lang Specifies the language the script is written in. */ + lang?: ScriptLanguage + options?: Record +} +--- + +[[shared-type-script-field]] +== ScriptField + +[source,ts] +--- +interface ScriptField { + script: Script | string + ignore_failure?: boolean +} +--- + +[[shared-type-script-language]] +== ScriptLanguage + +[source,ts] +--- +type ScriptLanguage = 'painless' | 'expression' | 'mustache' | 'java' | string +--- + +[[shared-type-script-sort]] +== ScriptSort + +[source,ts] +--- +interface ScriptSort { + order?: SortOrder + script: Script | string + type?: ScriptSortType + mode?: SortMode + nested?: NestedSortValue +} +--- + +[[shared-type-script-sort-type]] +== ScriptSortType + +[source,ts] +--- +type ScriptSortType = 'string' | 'number' | 'version' +--- + +[[shared-type-script-transform]] +== ScriptTransform + +[source,ts] +--- +interface ScriptTransform { + lang?: string + params?: Record + source?: string + id?: string +} +--- + +[[shared-type-scroll-id]] +== ScrollId + +[source,ts] +--- +type ScrollId = string +--- + +[[shared-type-scroll-ids]] +== ScrollIds + +[source,ts] +--- +type ScrollIds = ScrollId | ScrollId[] +--- + +[[shared-type-search-stats]] +== SearchStats + +[source,ts] +--- +interface SearchStats { + fetch_current: long + fetch_time?: Duration + fetch_time_in_millis: DurationValue + fetch_total: long + open_contexts?: long + query_current: long + query_time?: Duration + query_time_in_millis: DurationValue + query_total: long + scroll_current: long + scroll_time?: Duration + scroll_time_in_millis: DurationValue + scroll_total: long + suggest_current: long + suggest_time?: Duration + suggest_time_in_millis: DurationValue + suggest_total: long + groups?: Record +} +--- + +[[shared-type-search-transform]] +== SearchTransform + +[source,ts] +--- +interface SearchTransform { + request: WatcherSearchInputRequestDefinition + timeout: Duration +} +--- + +[[shared-type-search-type]] +== SearchType + +[source,ts] +--- +type SearchType = 'query_then_fetch' | 'dfs_query_then_fetch' +--- + +[[shared-type-segments-stats]] +== SegmentsStats + +[source,ts] +--- +interface SegmentsStats { + /** @property count Total number of segments across all shards assigned to selected nodes. */ + count: integer + /** @property doc_values_memory Total amount of memory used for doc values across all shards assigned to selected nodes. */ + doc_values_memory?: ByteSize + /** @property doc_values_memory_in_bytes Total amount, in bytes, of memory used for doc values across all shards assigned to selected nodes. */ + doc_values_memory_in_bytes: long + /** @property file_sizes This object is not populated by the cluster stats API. To get information on segment files, use the node stats API. */ + file_sizes: Record + /** @property fixed_bit_set Total amount of memory used by fixed bit sets across all shards assigned to selected nodes. Fixed bit sets are used for nested object field types and type filters for join fields. */ + fixed_bit_set?: ByteSize + /** @property fixed_bit_set_memory_in_bytes Total amount of memory, in bytes, used by fixed bit sets across all shards assigned to selected nodes. */ + fixed_bit_set_memory_in_bytes: long + /** @property index_writer_memory Total amount of memory used by all index writers across all shards assigned to selected nodes. */ + index_writer_memory?: ByteSize + index_writer_max_memory_in_bytes?: long + /** @property index_writer_memory_in_bytes Total amount, in bytes, of memory used by all index writers across all shards assigned to selected nodes. */ + index_writer_memory_in_bytes: long + /** @property max_unsafe_auto_id_timestamp Unix timestamp, in milliseconds, of the most recently retried indexing request. */ + max_unsafe_auto_id_timestamp: long + /** @property memory Total amount of memory used for segments across all shards assigned to selected nodes. */ + memory?: ByteSize + /** @property memory_in_bytes Total amount, in bytes, of memory used for segments across all shards assigned to selected nodes. */ + memory_in_bytes: long + /** @property norms_memory Total amount of memory used for normalization factors across all shards assigned to selected nodes. */ + norms_memory?: ByteSize + /** @property norms_memory_in_bytes Total amount, in bytes, of memory used for normalization factors across all shards assigned to selected nodes. */ + norms_memory_in_bytes: long + /** @property points_memory Total amount of memory used for points across all shards assigned to selected nodes. */ + points_memory?: ByteSize + /** @property points_memory_in_bytes Total amount, in bytes, of memory used for points across all shards assigned to selected nodes. */ + points_memory_in_bytes: long + stored_memory?: ByteSize + /** @property stored_fields_memory_in_bytes Total amount, in bytes, of memory used for stored fields across all shards assigned to selected nodes. */ + stored_fields_memory_in_bytes: long + /** @property terms_memory_in_bytes Total amount, in bytes, of memory used for terms across all shards assigned to selected nodes. */ + terms_memory_in_bytes: long + /** @property terms_memory Total amount of memory used for terms across all shards assigned to selected nodes. */ + terms_memory?: ByteSize + /** @property term_vectory_memory Total amount of memory used for term vectors across all shards assigned to selected nodes. */ + term_vectory_memory?: ByteSize + /** @property term_vectors_memory_in_bytes Total amount, in bytes, of memory used for term vectors across all shards assigned to selected nodes. */ + term_vectors_memory_in_bytes: long + /** @property version_map_memory Total amount of memory used by all version maps across all shards assigned to selected nodes. */ + version_map_memory?: ByteSize + /** @property version_map_memory_in_bytes Total amount, in bytes, of memory used by all version maps across all shards assigned to selected nodes. */ + version_map_memory_in_bytes: long +} +--- + +[[shared-type-sequence-number]] +== SequenceNumber + +[source,ts] +--- +type SequenceNumber = long +--- + +[[shared-type-service]] +== Service + +[source,ts] +--- +type Service = string +--- + +[[shared-type-shard-failure]] +== ShardFailure + +[source,ts] +--- +interface ShardFailure { + index?: IndexName + node?: string + reason: ErrorCause + shard: integer + status?: string +} +--- + +[[shared-type-shard-statistics]] +== ShardStatistics + +[source,ts] +--- +interface ShardStatistics { + failed: uint + /** @property successful Indicates how many shards have successfully run the search. */ + successful: uint + /** @property total Indicates how many shards the search will run on overall. */ + total: uint + failures?: ShardFailure[] + skipped?: uint +} +--- + +[[shared-type-shards-operation-response-base]] +== ShardsOperationResponseBase + +[source,ts] +--- +interface ShardsOperationResponseBase { + _shards?: ShardStatistics +} +--- + +[[shared-type-sliced-scroll]] +== SlicedScroll + +[source,ts] +--- +interface SlicedScroll { + field?: Field + id: Id + max: integer +} +--- + +[[shared-type-slices]] +== Slices + +[source,ts] +--- +type Slices = integer | SlicesCalculation +--- + +[[shared-type-slices-calculation]] +== SlicesCalculation + +[source,ts] +--- +type SlicesCalculation = 'auto' +--- + +[[shared-type-sort]] +== Sort + +[source,ts] +--- +type Sort = SortCombinations | SortCombinations[] +--- + +[[shared-type-sort-combinations]] +== SortCombinations + +[source,ts] +--- +type SortCombinations = Field | SortOptions +--- + +[[shared-type-sort-mode]] +== SortMode + +[source,ts] +--- +type SortMode = 'min' | 'max' | 'sum' | 'avg' | 'median' +--- + +[[shared-type-sort-options]] +== SortOptions + +[source,ts] +--- +interface SortOptionsKeys { + _score?: ScoreSort + _doc?: ScoreSort + _geo_distance?: GeoDistanceSort + _script?: ScriptSort +} +export type SortOptions = SortOptionsKeys + & { [property: string]: FieldSort | SortOrder | ScoreSort | GeoDistanceSort | ScriptSort } +--- + +[[shared-type-sort-order]] +== SortOrder + +[source,ts] +--- +type SortOrder = 'asc' | 'desc' +--- + +[[shared-type-sort-results]] +== SortResults + +[source,ts] +--- +type SortResults = FieldValue[] +--- + +[[shared-type-standard-retriever]] +== StandardRetriever + +[source,ts] +--- +interface StandardRetriever extends RetrieverBase { + /** @property query Defines a query to retrieve a set of top documents. */ + query?: QueryDslQueryContainer + /** @property search_after Defines a search after object parameter used for pagination. */ + search_after?: SortResults + /** @property terminate_after Maximum number of documents to collect for each shard. */ + terminate_after?: integer + /** @property sort A sort object that that specifies the order of matching documents. */ + sort?: Sort + /** @property collapse Collapses the top documents by a specified key into a single top document per key. */ + collapse?: SearchFieldCollapse +} +--- + +[[shared-type-store-stats]] +== StoreStats + +[source,ts] +--- +interface StoreStats { + /** @property size Total size of all shards assigned to selected nodes. */ + size?: ByteSize + /** @property size_in_bytes Total size, in bytes, of all shards assigned to selected nodes. */ + size_in_bytes: long + /** @property reserved A prediction of how much larger the shard stores will eventually grow due to ongoing peer recoveries, restoring snapshots, and similar activities. */ + reserved?: ByteSize + /** @property reserved_in_bytes A prediction, in bytes, of how much larger the shard stores will eventually grow due to ongoing peer recoveries, restoring snapshots, and similar activities. */ + reserved_in_bytes: long + /** @property total_data_set_size Total data set size of all shards assigned to selected nodes. This includes the size of shards not stored fully on the nodes, such as the cache for partially mounted indices. */ + total_data_set_size?: ByteSize + /** @property total_data_set_size_in_bytes Total data set size, in bytes, of all shards assigned to selected nodes. This includes the size of shards not stored fully on the nodes, such as the cache for partially mounted indices. */ + total_data_set_size_in_bytes?: long +} +--- + +[[shared-type-stored-script]] +== StoredScript + +[source,ts] +--- +interface StoredScript { + /** @property lang Specifies the language the script is written in. */ + lang: ScriptLanguage + options?: Record + /** @property source The script source. */ + source: string +} +--- + +[[shared-type-suggest-mode]] +== SuggestMode + +[source,ts] +--- +type SuggestMode = 'missing' | 'popular' | 'always' +--- + +[[shared-type-suggestion-name]] +== SuggestionName + +[source,ts] +--- +type SuggestionName = string +--- + +[[shared-type-task-failure]] +== TaskFailure + +[source,ts] +--- +interface TaskFailure { + task_id: long + node_id: NodeId + status: string + reason: ErrorCause +} +--- + +[[shared-type-task-id]] +== TaskId + +[source,ts] +--- +type TaskId = string | integer +--- + +[[shared-type-text-embedding]] +== TextEmbedding + +[source,ts] +--- +interface TextEmbedding { + model_id: string + model_text: string +} +--- + +[[shared-type-text-similarity-reranker]] +== TextSimilarityReranker + +[source,ts] +--- +interface TextSimilarityReranker extends RetrieverBase { + /** @property retriever The nested retriever which will produce the first-level results, that will later be used for reranking. */ + retriever: RetrieverContainer + /** @property rank_window_size This value determines how many documents we will consider from the nested retriever. */ + rank_window_size?: integer + /** @property inference_id Unique identifier of the inference endpoint created using the inference API. */ + inference_id?: string + /** @property inference_text The text snippet used as the basis for similarity comparison */ + inference_text?: string + /** @property field The document field to be used for text similarity comparisons. This field should contain the text that will be evaluated against the inference_text */ + field?: string +} +--- + +[[shared-type-thread-type]] +== ThreadType + +[source,ts] +--- +type ThreadType = 'cpu' | 'wait' | 'block' | 'gpu' | 'mem' +--- + +[[shared-type-time-of-day]] +== TimeOfDay + +[source,ts] +--- +type TimeOfDay = string +--- + +[[shared-type-time-unit]] +== TimeUnit + +[source,ts] +--- +type TimeUnit = 'nanos' | 'micros' | 'ms' | 's' | 'm' | 'h' | 'd' +--- + +[[shared-type-time-zone]] +== TimeZone + +[source,ts] +--- +type TimeZone = string +--- + +[[shared-type-top-left-bottom-right-geo-bounds]] +== TopLeftBottomRightGeoBounds + +[source,ts] +--- +interface TopLeftBottomRightGeoBounds { + top_left: GeoLocation + bottom_right: GeoLocation +} +--- + +[[shared-type-top-right-bottom-left-geo-bounds]] +== TopRightBottomLeftGeoBounds + +[source,ts] +--- +interface TopRightBottomLeftGeoBounds { + top_right: GeoLocation + bottom_left: GeoLocation +} +--- + +[[shared-type-transform-container]] +== TransformContainer + +[source,ts] +--- +interface TransformContainer { + chain?: TransformContainer[] + script?: ScriptTransform + search?: SearchTransform +} +--- + +[[shared-type-translog-stats]] +== TranslogStats + +[source,ts] +--- +interface TranslogStats { + earliest_last_modified_age: long + operations: long + size?: string + size_in_bytes: long + uncommitted_operations: integer + uncommitted_size?: string + uncommitted_size_in_bytes: long +} +--- + +[[shared-type-transport-address]] +== TransportAddress + +[source,ts] +--- +type TransportAddress = string +--- + +[[shared-type-unit-float-millis]] +== UnitFloatMillis + +[source,ts] +--- +type UnitFloatMillis = double +--- + +[[shared-type-unit-millis]] +== UnitMillis + +[source,ts] +--- +type UnitMillis = long +--- + +[[shared-type-unit-nanos]] +== UnitNanos + +[source,ts] +--- +type UnitNanos = long +--- + +[[shared-type-unit-seconds]] +== UnitSeconds + +[source,ts] +--- +type UnitSeconds = long +--- + +[[shared-type-username]] +== Username + +[source,ts] +--- +type Username = string +--- + +[[shared-type-uuid]] +== Uuid + +[source,ts] +--- +type Uuid = string +--- + +[[shared-type-version-number]] +== VersionNumber + +[source,ts] +--- +type VersionNumber = long +--- + +[[shared-type-version-string]] +== VersionString + +[source,ts] +--- +type VersionString = string +--- + +[[shared-type-version-type]] +== VersionType + +[source,ts] +--- +type VersionType = 'internal' | 'external' | 'external_gte' | 'force' +--- + +[[shared-type-wait-for-active-shard-options]] +== WaitForActiveShardOptions + +[source,ts] +--- +type WaitForActiveShardOptions = 'all' | 'index-setting' +--- + +[[shared-type-wait-for-active-shards]] +== WaitForActiveShards + +[source,ts] +--- +type WaitForActiveShards = integer | WaitForActiveShardOptions +--- + +[[shared-type-wait-for-events]] +== WaitForEvents + +[source,ts] +--- +type WaitForEvents = 'immediate' | 'urgent' | 'high' | 'normal' | 'low' | 'languid' +--- + +[[shared-type-warmer-stats]] +== WarmerStats + +[source,ts] +--- +interface WarmerStats { + current: long + total: long + total_time?: Duration + total_time_in_millis: DurationValue +} +--- + +[[shared-type-wkt-geo-bounds]] +== WktGeoBounds + +[source,ts] +--- +interface WktGeoBounds { + wkt: string +} +--- + +[[shared-type-write-response-base]] +== WriteResponseBase + +[source,ts] +--- +interface WriteResponseBase { + _id: Id + _index: IndexName + _primary_term?: long + result: Result + _seq_no?: SequenceNumber + _shards: ShardStatistics + _version: VersionNumber + forced_refresh?: boolean +} +--- + +[[shared-type-byte]] +== byte + +[source,ts] +--- +type byte = number +--- + +[[shared-type-double]] +== double + +[source,ts] +--- +type double = number +--- + +[[shared-type-float]] +== float + +[source,ts] +--- +type float = number +--- + +[[shared-type-integer]] +== integer + +[source,ts] +--- +type integer = number +--- + +[[shared-type-long]] +== long + +[source,ts] +--- +type long = number +--- + +[[shared-type-short]] +== short + +[source,ts] +--- +type short = number +--- + +[[shared-type-uint]] +== uint + +[source,ts] +--- +type uint = number +--- + +[[shared-type-ulong]] +== ulong + +[source,ts] +--- +type ulong = number +--- + +[[shared-type-spec-utils-base-node]] +== SpecUtilsBaseNode + +[source,ts] +--- +interface SpecUtilsBaseNode { + attributes: Record + host: Host + ip: Ip + name: Name + roles?: NodeRoles + transport_address: TransportAddress +} +--- + +[[shared-type-spec-utils-null-value]] +== SpecUtilsNullValue + +[source,ts] +--- +type SpecUtilsNullValue = null +--- + +[[shared-type-spec-utils-pipe-separated-flags]] +== SpecUtilsPipeSeparatedFlags + +[source,ts] +--- +type SpecUtilsPipeSeparatedFlags = T | string +--- + +[[shared-type-spec-utils-stringified]] +== SpecUtilsStringified + +[source,ts] +--- +type SpecUtilsStringified = T | string +--- + +[[shared-type-spec-utils-void]] +== SpecUtilsVoid + +[source,ts] +--- + +--- + +[[shared-type-spec-utils-with-null-value]] +== SpecUtilsWithNullValue + +[source,ts] +--- +type SpecUtilsWithNullValue = T | SpecUtilsNullValue +--- + +[[shared-type-spec-utils-additional-properties]] +== SpecUtilsAdditionalProperties + +[source,ts] +--- +interface SpecUtilsAdditionalProperties { +} +--- + +[[shared-type-spec-utils-additional-property]] +== SpecUtilsAdditionalProperty + +[source,ts] +--- +interface SpecUtilsAdditionalProperty { +} +--- + +[[shared-type-spec-utils-common-query-parameters]] +== SpecUtilsCommonQueryParameters + +[source,ts] +--- +interface SpecUtilsCommonQueryParameters { + /** @property error_trace When set to `true` Elasticsearch will include the full stack trace of errors when they occur. */ + error_trace?: boolean + /** @property filter_path Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch. */ + filter_path?: string | string[] + /** @property human When set to `true` will return statistics in a format suitable for humans. For example `"exists_time": "1h"` for humans and `"eixsts_time_in_millis": 3600000` for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines. */ + human?: boolean + /** @property pretty If set to `true` the returned JSON will be "pretty-formatted". Only use this option for debugging only. */ + pretty?: boolean +} +--- + +[[shared-type-spec-utils-common-cat-query-parameters]] +== SpecUtilsCommonCatQueryParameters + +[source,ts] +--- +interface SpecUtilsCommonCatQueryParameters { + /** @property format Specifies the format to return the columnar data in, can be set to `text`, `json`, `cbor`, `yaml`, or `smile`. */ + format?: string + /** @property h List of columns to appear in the response. Supports simple wildcards. */ + h?: Names + /** @property help When set to `true` will output available columns. This option can't be combined with any other query string option. */ + help?: boolean + /** @property local If `true`, the request computes the list of selected nodes from the local cluster state. If `false` the list of selected nodes are computed from the cluster state of the master node. In both cases the coordinating node will send requests for further information to each selected node. */ + local?: boolean + /** @property master_timeout Period to wait for a connection to the master node. */ + master_timeout?: Duration + /** @property s List of columns that determine how the table should be sorted. Sorting defaults to ascending and can be changed by setting `:asc` or `:desc` as a suffix to the column name. */ + s?: Names + /** @property v When set to `true` will enable verbose output. */ + v?: boolean +} +--- + +[[shared-type-spec-utils-overload-of]] +== SpecUtilsOverloadOf + +[source,ts] +--- +interface SpecUtilsOverloadOf { +} +--- + diff --git a/docs/reference-shutdown-delete_node.asciidoc b/docs/reference-shutdown-delete_node.asciidoc new file mode 100644 index 000000000..790b9c173 --- /dev/null +++ b/docs/reference-shutdown-delete_node.asciidoc @@ -0,0 +1,62 @@ +[[reference-shutdown-delete_node]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.shutdown.deleteNode + +Removes a node from the shutdown list. Designed for indirect use by ECE/ESS and ECK. Direct use is not supported. + +https://www.elastic.co/guide/en/elasticsearch/reference/current[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ShutdownDeleteNodeRequest, options?): Promise +---- + +[discrete] +===== `ShutdownDeleteNodeRequest` + +[source,ts] +---- +interface ShutdownDeleteNodeRequest extends <> { + node_id: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `ShutdownDeleteNodeResponse` + +[source,ts] +---- +type ShutdownDeleteNodeResponse = <> +---- + diff --git a/docs/reference-shutdown-get_node.asciidoc b/docs/reference-shutdown-get_node.asciidoc new file mode 100644 index 000000000..9ca3e3712 --- /dev/null +++ b/docs/reference-shutdown-get_node.asciidoc @@ -0,0 +1,64 @@ +[[reference-shutdown-get_node]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.shutdown.getNode + +Retrieve status of a node or nodes that are currently marked as shutting down. Designed for indirect use by ECE/ESS and ECK. Direct use is not supported. + +https://www.elastic.co/guide/en/elasticsearch/reference/current[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ShutdownGetNodeRequest, options?): Promise +---- + +[discrete] +===== `ShutdownGetNodeRequest` + +[source,ts] +---- +interface ShutdownGetNodeRequest extends <> { + node_id?: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `ShutdownGetNodeResponse` + +[source,ts] +---- +interface ShutdownGetNodeResponse { + nodes: ShutdownGetNodeNodeShutdownStatus[] +} +---- + diff --git a/docs/reference-shutdown-put_node.asciidoc b/docs/reference-shutdown-put_node.asciidoc new file mode 100644 index 000000000..34acceb29 --- /dev/null +++ b/docs/reference-shutdown-put_node.asciidoc @@ -0,0 +1,66 @@ +[[reference-shutdown-put_node]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.shutdown.putNode + +Adds a node to be shut down. Designed for indirect use by ECE/ESS and ECK. Direct use is not supported. + +https://www.elastic.co/guide/en/elasticsearch/reference/current[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(ShutdownPutNodeRequest, options?): Promise +---- + +[discrete] +===== `ShutdownPutNodeRequest` + +[source,ts] +---- +interface ShutdownPutNodeRequest extends <> { + node_id: <> + master_timeout?: <> + timeout?: <> + type: ShutdownType + reason: string + allocation_delay?: string + target_node_name?: string +} +---- + +[discrete] +===== `ShutdownPutNodeResponse` + +[source,ts] +---- +type ShutdownPutNodeResponse = <> +---- + diff --git a/docs/reference-simulate-ingest.asciidoc b/docs/reference-simulate-ingest.asciidoc new file mode 100644 index 000000000..fbb13cc58 --- /dev/null +++ b/docs/reference-simulate-ingest.asciidoc @@ -0,0 +1,59 @@ +[[reference-simulate-ingest]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.simulate.ingest + +Simulates running ingest with example documents. + +{ref}/simulate-ingest-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SimulateIngestRequest, options?): Promise +---- + +[discrete] +===== `SimulateIngestRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SimulateIngestResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-slm-delete_lifecycle.asciidoc b/docs/reference-slm-delete_lifecycle.asciidoc new file mode 100644 index 000000000..c0b7a2a47 --- /dev/null +++ b/docs/reference-slm-delete_lifecycle.asciidoc @@ -0,0 +1,60 @@ +[[reference-slm-delete_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.deleteLifecycle + +Deletes an existing snapshot lifecycle policy. + +{ref}/slm-api-delete-policy.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmDeleteLifecycleRequest, options?): Promise +---- + +[discrete] +===== `SlmDeleteLifecycleRequest` + +[source,ts] +---- +interface SlmDeleteLifecycleRequest extends <> { + policy_id: <> +} +---- + +[discrete] +===== `SlmDeleteLifecycleResponse` + +[source,ts] +---- +type SlmDeleteLifecycleResponse = <> +---- + diff --git a/docs/reference-slm-execute_lifecycle.asciidoc b/docs/reference-slm-execute_lifecycle.asciidoc new file mode 100644 index 000000000..2bf0fe486 --- /dev/null +++ b/docs/reference-slm-execute_lifecycle.asciidoc @@ -0,0 +1,62 @@ +[[reference-slm-execute_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.executeLifecycle + +Immediately creates a snapshot according to the lifecycle policy, without waiting for the scheduled time. + +{ref}/slm-api-execute-lifecycle.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmExecuteLifecycleRequest, options?): Promise +---- + +[discrete] +===== `SlmExecuteLifecycleRequest` + +[source,ts] +---- +interface SlmExecuteLifecycleRequest extends <> { + policy_id: <> +} +---- + +[discrete] +===== `SlmExecuteLifecycleResponse` + +[source,ts] +---- +interface SlmExecuteLifecycleResponse { + snapshot_name: <> +} +---- + diff --git a/docs/reference-slm-execute_retention.asciidoc b/docs/reference-slm-execute_retention.asciidoc new file mode 100644 index 000000000..c8d31d36b --- /dev/null +++ b/docs/reference-slm-execute_retention.asciidoc @@ -0,0 +1,59 @@ +[[reference-slm-execute_retention]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.executeRetention + +Deletes any snapshots that are expired according to the policy's retention rules. + +{ref}/slm-api-execute-retention.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmExecuteRetentionRequest, options?): Promise +---- + +[discrete] +===== `SlmExecuteRetentionRequest` + +[source,ts] +---- +interface SlmExecuteRetentionRequest extends <> { +} +---- + +[discrete] +===== `SlmExecuteRetentionResponse` + +[source,ts] +---- +type SlmExecuteRetentionResponse = <> +---- + diff --git a/docs/reference-slm-get_lifecycle.asciidoc b/docs/reference-slm-get_lifecycle.asciidoc new file mode 100644 index 000000000..3032258e9 --- /dev/null +++ b/docs/reference-slm-get_lifecycle.asciidoc @@ -0,0 +1,60 @@ +[[reference-slm-get_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.getLifecycle + +Retrieves one or more snapshot lifecycle policy definitions and information about the latest snapshot attempts. + +{ref}/slm-api-get-policy.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmGetLifecycleRequest, options?): Promise +---- + +[discrete] +===== `SlmGetLifecycleRequest` + +[source,ts] +---- +interface SlmGetLifecycleRequest extends <> { + policy_id?: <> +} +---- + +[discrete] +===== `SlmGetLifecycleResponse` + +[source,ts] +---- +type SlmGetLifecycleResponse = Record<<>, SlmSnapshotLifecycle> +---- + diff --git a/docs/reference-slm-get_stats.asciidoc b/docs/reference-slm-get_stats.asciidoc new file mode 100644 index 000000000..1d1222418 --- /dev/null +++ b/docs/reference-slm-get_stats.asciidoc @@ -0,0 +1,70 @@ +[[reference-slm-get_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.getStats + +Returns global and policy-level statistics about actions taken by snapshot lifecycle management. + +{ref}/slm-api-get-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmGetStatsRequest, options?): Promise +---- + +[discrete] +===== `SlmGetStatsRequest` + +[source,ts] +---- +interface SlmGetStatsRequest extends <> { +} +---- + +[discrete] +===== `SlmGetStatsResponse` + +[source,ts] +---- +interface SlmGetStatsResponse { + retention_deletion_time: <> + retention_deletion_time_millis: <><<>> + retention_failed: <> + retention_runs: <> + retention_timed_out: <> + total_snapshots_deleted: <> + total_snapshot_deletion_failures: <> + total_snapshots_failed: <> + total_snapshots_taken: <> + policy_stats: string[] +} +---- + diff --git a/docs/reference-slm-get_status.asciidoc b/docs/reference-slm-get_status.asciidoc new file mode 100644 index 000000000..cffe46710 --- /dev/null +++ b/docs/reference-slm-get_status.asciidoc @@ -0,0 +1,61 @@ +[[reference-slm-get_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.getStatus + +Retrieves the status of snapshot lifecycle management (SLM). + +{ref}/slm-api-get-status.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmGetStatusRequest, options?): Promise +---- + +[discrete] +===== `SlmGetStatusRequest` + +[source,ts] +---- +interface SlmGetStatusRequest extends <> { +} +---- + +[discrete] +===== `SlmGetStatusResponse` + +[source,ts] +---- +interface SlmGetStatusResponse { + operation_mode: <> +} +---- + diff --git a/docs/reference-slm-put_lifecycle.asciidoc b/docs/reference-slm-put_lifecycle.asciidoc new file mode 100644 index 000000000..56dd37317 --- /dev/null +++ b/docs/reference-slm-put_lifecycle.asciidoc @@ -0,0 +1,67 @@ +[[reference-slm-put_lifecycle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.putLifecycle + +Creates or updates a snapshot lifecycle policy. + +{ref}/slm-api-put-policy.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmPutLifecycleRequest, options?): Promise +---- + +[discrete] +===== `SlmPutLifecycleRequest` + +[source,ts] +---- +interface SlmPutLifecycleRequest extends <> { + policy_id: <> + master_timeout?: <> + timeout?: <> + config?: SlmConfiguration + name?: <> + repository?: string + retention?: SlmRetention + schedule?: WatcherCronExpression +} +---- + +[discrete] +===== `SlmPutLifecycleResponse` + +[source,ts] +---- +type SlmPutLifecycleResponse = <> +---- + diff --git a/docs/reference-slm-start.asciidoc b/docs/reference-slm-start.asciidoc new file mode 100644 index 000000000..6a0c84747 --- /dev/null +++ b/docs/reference-slm-start.asciidoc @@ -0,0 +1,59 @@ +[[reference-slm-start]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.start + +Turns on snapshot lifecycle management (SLM). + +{ref}/slm-api-start.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmStartRequest, options?): Promise +---- + +[discrete] +===== `SlmStartRequest` + +[source,ts] +---- +interface SlmStartRequest extends <> { +} +---- + +[discrete] +===== `SlmStartResponse` + +[source,ts] +---- +type SlmStartResponse = <> +---- + diff --git a/docs/reference-slm-stop.asciidoc b/docs/reference-slm-stop.asciidoc new file mode 100644 index 000000000..615a6a2a5 --- /dev/null +++ b/docs/reference-slm-stop.asciidoc @@ -0,0 +1,59 @@ +[[reference-slm-stop]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.slm.stop + +Turns off snapshot lifecycle management (SLM). + +{ref}/slm-api-stop.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SlmStopRequest, options?): Promise +---- + +[discrete] +===== `SlmStopRequest` + +[source,ts] +---- +interface SlmStopRequest extends <> { +} +---- + +[discrete] +===== `SlmStopResponse` + +[source,ts] +---- +type SlmStopResponse = <> +---- + diff --git a/docs/reference-snapshot-cleanup_repository.asciidoc b/docs/reference-snapshot-cleanup_repository.asciidoc new file mode 100644 index 000000000..0dd6cb101 --- /dev/null +++ b/docs/reference-snapshot-cleanup_repository.asciidoc @@ -0,0 +1,64 @@ +[[reference-snapshot-cleanup_repository]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.cleanupRepository + +Triggers the review of a snapshot repository’s contents and deletes any stale data not referenced by existing snapshots. + +{ref}/clean-up-snapshot-repo-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotCleanupRepositoryRequest, options?): Promise +---- + +[discrete] +===== `SnapshotCleanupRepositoryRequest` + +[source,ts] +---- +interface SnapshotCleanupRepositoryRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `SnapshotCleanupRepositoryResponse` + +[source,ts] +---- +interface SnapshotCleanupRepositoryResponse { + results: SnapshotCleanupRepositoryCleanupRepositoryResults +} +---- + diff --git a/docs/reference-snapshot-clone.asciidoc b/docs/reference-snapshot-clone.asciidoc new file mode 100644 index 000000000..6afcd7d05 --- /dev/null +++ b/docs/reference-snapshot-clone.asciidoc @@ -0,0 +1,65 @@ +[[reference-snapshot-clone]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.clone + +Clones indices from one snapshot into another snapshot in the same repository. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotCloneRequest, options?): Promise +---- + +[discrete] +===== `SnapshotCloneRequest` + +[source,ts] +---- +interface SnapshotCloneRequest extends <> { + repository: <> + snapshot: <> + target_snapshot: <> + master_timeout?: <> + timeout?: <> + indices: string +} +---- + +[discrete] +===== `SnapshotCloneResponse` + +[source,ts] +---- +type SnapshotCloneResponse = <> +---- + diff --git a/docs/reference-snapshot-create.asciidoc b/docs/reference-snapshot-create.asciidoc new file mode 100644 index 000000000..9609ad216 --- /dev/null +++ b/docs/reference-snapshot-create.asciidoc @@ -0,0 +1,72 @@ +[[reference-snapshot-create]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.create + +Creates a snapshot in a repository. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotCreateRequest, options?): Promise +---- + +[discrete] +===== `SnapshotCreateRequest` + +[source,ts] +---- +interface SnapshotCreateRequest extends <> { + repository: <> + snapshot: <> + master_timeout?: <> + wait_for_completion?: boolean + ignore_unavailable?: boolean + include_global_state?: boolean + indices?: <> + feature_states?: string[] + metadata?: <> + partial?: boolean +} +---- + +[discrete] +===== `SnapshotCreateResponse` + +[source,ts] +---- +interface SnapshotCreateResponse { + accepted?: boolean + snapshot?: SnapshotSnapshotInfo +} +---- + diff --git a/docs/reference-snapshot-create_repository.asciidoc b/docs/reference-snapshot-create_repository.asciidoc new file mode 100644 index 000000000..07874ace1 --- /dev/null +++ b/docs/reference-snapshot-create_repository.asciidoc @@ -0,0 +1,64 @@ +[[reference-snapshot-create_repository]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.createRepository + +Creates a repository. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotCreateRepositoryRequest, options?): Promise +---- + +[discrete] +===== `SnapshotCreateRepositoryRequest` + +[source,ts] +---- +interface SnapshotCreateRepositoryRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> + verify?: boolean + repository?: SnapshotRepository +} +---- + +[discrete] +===== `SnapshotCreateRepositoryResponse` + +[source,ts] +---- +type SnapshotCreateRepositoryResponse = <> +---- + diff --git a/docs/reference-snapshot-delete.asciidoc b/docs/reference-snapshot-delete.asciidoc new file mode 100644 index 000000000..e7b8c5f89 --- /dev/null +++ b/docs/reference-snapshot-delete.asciidoc @@ -0,0 +1,62 @@ +[[reference-snapshot-delete]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.delete + +Deletes one or more snapshots. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotDeleteRequest, options?): Promise +---- + +[discrete] +===== `SnapshotDeleteRequest` + +[source,ts] +---- +interface SnapshotDeleteRequest extends <> { + repository: <> + snapshot: <> + master_timeout?: <> +} +---- + +[discrete] +===== `SnapshotDeleteResponse` + +[source,ts] +---- +type SnapshotDeleteResponse = <> +---- + diff --git a/docs/reference-snapshot-delete_repository.asciidoc b/docs/reference-snapshot-delete_repository.asciidoc new file mode 100644 index 000000000..0b984d967 --- /dev/null +++ b/docs/reference-snapshot-delete_repository.asciidoc @@ -0,0 +1,62 @@ +[[reference-snapshot-delete_repository]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.deleteRepository + +Deletes a repository. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotDeleteRepositoryRequest, options?): Promise +---- + +[discrete] +===== `SnapshotDeleteRepositoryRequest` + +[source,ts] +---- +interface SnapshotDeleteRepositoryRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `SnapshotDeleteRepositoryResponse` + +[source,ts] +---- +type SnapshotDeleteRepositoryResponse = <> +---- + diff --git a/docs/reference-snapshot-get.asciidoc b/docs/reference-snapshot-get.asciidoc new file mode 100644 index 000000000..54c9ad8c7 --- /dev/null +++ b/docs/reference-snapshot-get.asciidoc @@ -0,0 +1,79 @@ +[[reference-snapshot-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.get + +Returns information about a snapshot. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotGetRequest, options?): Promise +---- + +[discrete] +===== `SnapshotGetRequest` + +[source,ts] +---- +interface SnapshotGetRequest extends <> { + repository: <> + snapshot: <> + ignore_unavailable?: boolean + master_timeout?: <> + verbose?: boolean + index_details?: boolean + index_names?: boolean + include_repository?: boolean + sort?: SnapshotSnapshotSort + size?: <> + order?: <> + after?: string + offset?: <> + from_sort_value?: string + slm_policy_filter?: <> +} +---- + +[discrete] +===== `SnapshotGetResponse` + +[source,ts] +---- +interface SnapshotGetResponse { + responses?: SnapshotGetSnapshotResponseItem[] + snapshots?: SnapshotSnapshotInfo[] + total: <> + remaining: <> +} +---- + diff --git a/docs/reference-snapshot-get_repository.asciidoc b/docs/reference-snapshot-get_repository.asciidoc new file mode 100644 index 000000000..0b5c6a54b --- /dev/null +++ b/docs/reference-snapshot-get_repository.asciidoc @@ -0,0 +1,62 @@ +[[reference-snapshot-get_repository]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.getRepository + +Returns information about a repository. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotGetRepositoryRequest, options?): Promise +---- + +[discrete] +===== `SnapshotGetRepositoryRequest` + +[source,ts] +---- +interface SnapshotGetRepositoryRequest extends <> { + name?: <> + local?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `SnapshotGetRepositoryResponse` + +[source,ts] +---- +type SnapshotGetRepositoryResponse = Record +---- + diff --git a/docs/reference-snapshot-repository_analyze.asciidoc b/docs/reference-snapshot-repository_analyze.asciidoc new file mode 100644 index 000000000..7d5f006cf --- /dev/null +++ b/docs/reference-snapshot-repository_analyze.asciidoc @@ -0,0 +1,59 @@ +[[reference-snapshot-repository_analyze]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.repositoryAnalyze + +Analyzes a repository for correctness and performance + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotRepositoryAnalyzeRequest, options?): Promise +---- + +[discrete] +===== `SnapshotRepositoryAnalyzeRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `SnapshotRepositoryAnalyzeResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-snapshot-restore.asciidoc b/docs/reference-snapshot-restore.asciidoc new file mode 100644 index 000000000..ba0f12ade --- /dev/null +++ b/docs/reference-snapshot-restore.asciidoc @@ -0,0 +1,76 @@ +[[reference-snapshot-restore]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.restore + +Restores a snapshot. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotRestoreRequest, options?): Promise +---- + +[discrete] +===== `SnapshotRestoreRequest` + +[source,ts] +---- +interface SnapshotRestoreRequest extends <> { + repository: <> + snapshot: <> + master_timeout?: <> + wait_for_completion?: boolean + feature_states?: string[] + ignore_index_settings?: string[] + ignore_unavailable?: boolean + include_aliases?: boolean + include_global_state?: boolean + index_settings?: IndicesIndexSettings + indices?: <> + partial?: boolean + rename_pattern?: string + rename_replacement?: string +} +---- + +[discrete] +===== `SnapshotRestoreResponse` + +[source,ts] +---- +interface SnapshotRestoreResponse { + accepted?: boolean + snapshot?: SnapshotRestoreSnapshotRestore +} +---- + diff --git a/docs/reference-snapshot-status.asciidoc b/docs/reference-snapshot-status.asciidoc new file mode 100644 index 000000000..20dc786f7 --- /dev/null +++ b/docs/reference-snapshot-status.asciidoc @@ -0,0 +1,65 @@ +[[reference-snapshot-status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.status + +Returns information about the status of a snapshot. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotStatusRequest, options?): Promise +---- + +[discrete] +===== `SnapshotStatusRequest` + +[source,ts] +---- +interface SnapshotStatusRequest extends <> { + repository?: <> + snapshot?: <> + ignore_unavailable?: boolean + master_timeout?: <> +} +---- + +[discrete] +===== `SnapshotStatusResponse` + +[source,ts] +---- +interface SnapshotStatusResponse { + snapshots: SnapshotStatus[] +} +---- + diff --git a/docs/reference-snapshot-verify_repository.asciidoc b/docs/reference-snapshot-verify_repository.asciidoc new file mode 100644 index 000000000..ae608f3e8 --- /dev/null +++ b/docs/reference-snapshot-verify_repository.asciidoc @@ -0,0 +1,64 @@ +[[reference-snapshot-verify_repository]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.snapshot.verifyRepository + +Verifies a repository. + +{ref}/modules-snapshots.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SnapshotVerifyRepositoryRequest, options?): Promise +---- + +[discrete] +===== `SnapshotVerifyRepositoryRequest` + +[source,ts] +---- +interface SnapshotVerifyRepositoryRequest extends <> { + name: <> + master_timeout?: <> + timeout?: <> +} +---- + +[discrete] +===== `SnapshotVerifyRepositoryResponse` + +[source,ts] +---- +interface SnapshotVerifyRepositoryResponse { + nodes: Record +} +---- + diff --git a/docs/reference-sql-clear_cursor.asciidoc b/docs/reference-sql-clear_cursor.asciidoc new file mode 100644 index 000000000..8cc8ea9f8 --- /dev/null +++ b/docs/reference-sql-clear_cursor.asciidoc @@ -0,0 +1,62 @@ +[[reference-sql-clear_cursor]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.sql.clearCursor + +Clears the SQL cursor + +{ref}/clear-sql-cursor-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SqlClearCursorRequest, options?): Promise +---- + +[discrete] +===== `SqlClearCursorRequest` + +[source,ts] +---- +interface SqlClearCursorRequest extends <> { + cursor: string +} +---- + +[discrete] +===== `SqlClearCursorResponse` + +[source,ts] +---- +interface SqlClearCursorResponse { + succeeded: boolean +} +---- + diff --git a/docs/reference-sql-delete_async.asciidoc b/docs/reference-sql-delete_async.asciidoc new file mode 100644 index 000000000..2363a28c2 --- /dev/null +++ b/docs/reference-sql-delete_async.asciidoc @@ -0,0 +1,60 @@ +[[reference-sql-delete_async]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.sql.deleteAsync + +Deletes an async SQL search or a stored synchronous SQL search. If the search is still running, the API cancels it. + +{ref}/delete-async-sql-search-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SqlDeleteAsyncRequest, options?): Promise +---- + +[discrete] +===== `SqlDeleteAsyncRequest` + +[source,ts] +---- +interface SqlDeleteAsyncRequest extends <> { + id: <> +} +---- + +[discrete] +===== `SqlDeleteAsyncResponse` + +[source,ts] +---- +type SqlDeleteAsyncResponse = <> +---- + diff --git a/docs/reference-sql-get_async.asciidoc b/docs/reference-sql-get_async.asciidoc new file mode 100644 index 000000000..55d5ad533 --- /dev/null +++ b/docs/reference-sql-get_async.asciidoc @@ -0,0 +1,71 @@ +[[reference-sql-get_async]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.sql.getAsync + +Returns the current status and available results for an async SQL search or stored synchronous SQL search + +{ref}/get-async-sql-search-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SqlGetAsyncRequest, options?): Promise +---- + +[discrete] +===== `SqlGetAsyncRequest` + +[source,ts] +---- +interface SqlGetAsyncRequest extends <> { + id: <> + delimiter?: string + format?: string + keep_alive?: <> + wait_for_completion_timeout?: <> +} +---- + +[discrete] +===== `SqlGetAsyncResponse` + +[source,ts] +---- +interface SqlGetAsyncResponse { + id: <> + is_running: boolean + is_partial: boolean + columns?: SqlColumn[] + cursor?: string + rows: SqlRow[] +} +---- + diff --git a/docs/reference-sql-get_async_status.asciidoc b/docs/reference-sql-get_async_status.asciidoc new file mode 100644 index 000000000..addfed27d --- /dev/null +++ b/docs/reference-sql-get_async_status.asciidoc @@ -0,0 +1,67 @@ +[[reference-sql-get_async_status]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.sql.getAsyncStatus + +Returns the current status of an async SQL search or a stored synchronous SQL search + +{ref}/get-async-sql-search-status-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SqlGetAsyncStatusRequest, options?): Promise +---- + +[discrete] +===== `SqlGetAsyncStatusRequest` + +[source,ts] +---- +interface SqlGetAsyncStatusRequest extends <> { + id: <> +} +---- + +[discrete] +===== `SqlGetAsyncStatusResponse` + +[source,ts] +---- +interface SqlGetAsyncStatusResponse { + id: string + is_running: boolean + is_partial: boolean + start_time_in_millis: <><<>> + expiration_time_in_millis: <><<>> + completion_status?: <> +} +---- + diff --git a/docs/reference-sql-query.asciidoc b/docs/reference-sql-query.asciidoc new file mode 100644 index 000000000..5e3e6925d --- /dev/null +++ b/docs/reference-sql-query.asciidoc @@ -0,0 +1,83 @@ +[[reference-sql-query]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.sql.query + +Executes a SQL request + +{ref}/sql-search-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SqlQueryRequest, options?): Promise +---- + +[discrete] +===== `SqlQueryRequest` + +[source,ts] +---- +interface SqlQueryRequest extends <> { + format?: SqlQuerySqlFormat + catalog?: string + columnar?: boolean + cursor?: string + fetch_size?: <> + filter?: QueryDslQueryContainer + query?: string + request_timeout?: <> + page_timeout?: <> + time_zone?: <> + field_multi_value_leniency?: boolean + runtime_mappings?: MappingRuntimeFields + wait_for_completion_timeout?: <> + params?: Record + keep_alive?: <> + keep_on_completion?: boolean + index_using_frozen?: boolean +} +---- + +[discrete] +===== `SqlQueryResponse` + +[source,ts] +---- +interface SqlQueryResponse { + id?: <> + is_running?: boolean + is_partial?: boolean + columns?: SqlColumn[] + cursor?: string + rows: SqlRow[] +} +---- + diff --git a/docs/reference-sql-translate.asciidoc b/docs/reference-sql-translate.asciidoc new file mode 100644 index 000000000..57f0d153a --- /dev/null +++ b/docs/reference-sql-translate.asciidoc @@ -0,0 +1,70 @@ +[[reference-sql-translate]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.sql.translate + +Translates SQL into Elasticsearch queries + +{ref}/sql-translate-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SqlTranslateRequest, options?): Promise +---- + +[discrete] +===== `SqlTranslateRequest` + +[source,ts] +---- +interface SqlTranslateRequest extends <> { + fetch_size?: <> + filter?: QueryDslQueryContainer + query: string + time_zone?: <> +} +---- + +[discrete] +===== `SqlTranslateResponse` + +[source,ts] +---- +interface SqlTranslateResponse { + aggregations?: Record + size?: <> + _source?: SearchSourceConfig + fields?: (QueryDslFieldAndFormat | <>)[] + query?: QueryDslQueryContainer + sort?: <> +} +---- + diff --git a/docs/reference-ssl-certificates.asciidoc b/docs/reference-ssl-certificates.asciidoc new file mode 100644 index 000000000..472f160ff --- /dev/null +++ b/docs/reference-ssl-certificates.asciidoc @@ -0,0 +1,59 @@ +[[reference-ssl-certificates]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.ssl.certificates + +Get SSL certificates. Get information about the X.509 certificates that are used to encrypt communications in the cluster. The API returns a list that includes certificates from all TLS contexts including: - Settings for transport and HTTP interfaces - TLS settings that are used within authentication realms - TLS settings for remote monitoring exporters The list includes certificates that are used for configuring trust, such as those configured in the `xpack.security.transport.ssl.truststore` and `xpack.security.transport.ssl.certificate_authorities` settings. It also includes certificates that are used for configuring server identity, such as `xpack.security.http.ssl.keystore` and `xpack.security.http.ssl.certificate settings`. The list does not include certificates that are sourced from the default SSL context of the Java Runtime Environment (JRE), even if those certificates are in use within Elasticsearch. NOTE: When a PKCS#11 token is configured as the truststore of the JRE, the API returns all the certificates that are included in the PKCS#11 token irrespective of whether these are used in the Elasticsearch TLS configuration. If Elasticsearch is configured to use a keystore or truststore, the API output includes all certificates in that store, even though some of the certificates might not be in active use within the cluster. + +{ref}/security-api-ssl.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SslCertificatesRequest, options?): Promise +---- + +[discrete] +===== `SslCertificatesRequest` + +[source,ts] +---- +interface SslCertificatesRequest extends <> { +} +---- + +[discrete] +===== `SslCertificatesResponse` + +[source,ts] +---- +type SslCertificatesResponse = SslCertificatesCertificateInformation[] +---- + diff --git a/docs/reference-synonyms-delete_synonym.asciidoc b/docs/reference-synonyms-delete_synonym.asciidoc new file mode 100644 index 000000000..116c2f2c7 --- /dev/null +++ b/docs/reference-synonyms-delete_synonym.asciidoc @@ -0,0 +1,60 @@ +[[reference-synonyms-delete_synonym]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.synonyms.deleteSynonym + +Deletes a synonym set + +{ref}/delete-synonyms-set.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SynonymsDeleteSynonymRequest, options?): Promise +---- + +[discrete] +===== `SynonymsDeleteSynonymRequest` + +[source,ts] +---- +interface SynonymsDeleteSynonymRequest extends <> { + id: <> +} +---- + +[discrete] +===== `SynonymsDeleteSynonymResponse` + +[source,ts] +---- +type SynonymsDeleteSynonymResponse = <> +---- + diff --git a/docs/reference-synonyms-delete_synonym_rule.asciidoc b/docs/reference-synonyms-delete_synonym_rule.asciidoc new file mode 100644 index 000000000..461ba4a1f --- /dev/null +++ b/docs/reference-synonyms-delete_synonym_rule.asciidoc @@ -0,0 +1,61 @@ +[[reference-synonyms-delete_synonym_rule]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.synonyms.deleteSynonymRule + +Deletes a synonym rule in a synonym set + +{ref}/delete-synonym-rule.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SynonymsDeleteSynonymRuleRequest, options?): Promise +---- + +[discrete] +===== `SynonymsDeleteSynonymRuleRequest` + +[source,ts] +---- +interface SynonymsDeleteSynonymRuleRequest extends <> { + set_id: <> + rule_id: <> +} +---- + +[discrete] +===== `SynonymsDeleteSynonymRuleResponse` + +[source,ts] +---- +type SynonymsDeleteSynonymRuleResponse = SynonymsSynonymsUpdateResult +---- + diff --git a/docs/reference-synonyms-get_synonym.asciidoc b/docs/reference-synonyms-get_synonym.asciidoc new file mode 100644 index 000000000..93a8c957e --- /dev/null +++ b/docs/reference-synonyms-get_synonym.asciidoc @@ -0,0 +1,65 @@ +[[reference-synonyms-get_synonym]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.synonyms.getSynonym + +Retrieves a synonym set + +{ref}/get-synonyms-set.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SynonymsGetSynonymRequest, options?): Promise +---- + +[discrete] +===== `SynonymsGetSynonymRequest` + +[source,ts] +---- +interface SynonymsGetSynonymRequest extends <> { + id: <> + from?: <> + size?: <> +} +---- + +[discrete] +===== `SynonymsGetSynonymResponse` + +[source,ts] +---- +interface SynonymsGetSynonymResponse { + count: <> + synonyms_set: SynonymsSynonymRuleRead[] +} +---- + diff --git a/docs/reference-synonyms-get_synonym_rule.asciidoc b/docs/reference-synonyms-get_synonym_rule.asciidoc new file mode 100644 index 000000000..3ac127f01 --- /dev/null +++ b/docs/reference-synonyms-get_synonym_rule.asciidoc @@ -0,0 +1,61 @@ +[[reference-synonyms-get_synonym_rule]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.synonyms.getSynonymRule + +Retrieves a synonym rule from a synonym set + +{ref}/get-synonym-rule.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SynonymsGetSynonymRuleRequest, options?): Promise +---- + +[discrete] +===== `SynonymsGetSynonymRuleRequest` + +[source,ts] +---- +interface SynonymsGetSynonymRuleRequest extends <> { + set_id: <> + rule_id: <> +} +---- + +[discrete] +===== `SynonymsGetSynonymRuleResponse` + +[source,ts] +---- +type SynonymsGetSynonymRuleResponse = SynonymsSynonymRuleRead +---- + diff --git a/docs/reference-synonyms-get_synonyms_sets.asciidoc b/docs/reference-synonyms-get_synonyms_sets.asciidoc new file mode 100644 index 000000000..6b97c2ac6 --- /dev/null +++ b/docs/reference-synonyms-get_synonyms_sets.asciidoc @@ -0,0 +1,64 @@ +[[reference-synonyms-get_synonyms_sets]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.synonyms.getSynonymsSets + +Retrieves a summary of all defined synonym sets + +{ref}/list-synonyms-sets.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SynonymsGetSynonymsSetsRequest, options?): Promise +---- + +[discrete] +===== `SynonymsGetSynonymsSetsRequest` + +[source,ts] +---- +interface SynonymsGetSynonymsSetsRequest extends <> { + from?: <> + size?: <> +} +---- + +[discrete] +===== `SynonymsGetSynonymsSetsResponse` + +[source,ts] +---- +interface SynonymsGetSynonymsSetsResponse { + count: <> + results: SynonymsGetSynonymsSetsSynonymsSetItem[] +} +---- + diff --git a/docs/reference-synonyms-put_synonym.asciidoc b/docs/reference-synonyms-put_synonym.asciidoc new file mode 100644 index 000000000..ccfd2ed7e --- /dev/null +++ b/docs/reference-synonyms-put_synonym.asciidoc @@ -0,0 +1,64 @@ +[[reference-synonyms-put_synonym]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.synonyms.putSynonym + +Creates or updates a synonym set. + +{ref}/put-synonyms-set.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SynonymsPutSynonymRequest, options?): Promise +---- + +[discrete] +===== `SynonymsPutSynonymRequest` + +[source,ts] +---- +interface SynonymsPutSynonymRequest extends <> { + id: <> + synonyms_set: SynonymsSynonymRule | SynonymsSynonymRule[] +} +---- + +[discrete] +===== `SynonymsPutSynonymResponse` + +[source,ts] +---- +interface SynonymsPutSynonymResponse { + result: <> + reload_analyzers_details: IndicesReloadSearchAnalyzersReloadResult +} +---- + diff --git a/docs/reference-synonyms-put_synonym_rule.asciidoc b/docs/reference-synonyms-put_synonym_rule.asciidoc new file mode 100644 index 000000000..599aba881 --- /dev/null +++ b/docs/reference-synonyms-put_synonym_rule.asciidoc @@ -0,0 +1,62 @@ +[[reference-synonyms-put_synonym_rule]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.synonyms.putSynonymRule + +Creates or updates a synonym rule in a synonym set + +{ref}/put-synonym-rule.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(SynonymsPutSynonymRuleRequest, options?): Promise +---- + +[discrete] +===== `SynonymsPutSynonymRuleRequest` + +[source,ts] +---- +interface SynonymsPutSynonymRuleRequest extends <> { + set_id: <> + rule_id: <> + synonyms: SynonymsSynonymString +} +---- + +[discrete] +===== `SynonymsPutSynonymRuleResponse` + +[source,ts] +---- +type SynonymsPutSynonymRuleResponse = SynonymsSynonymsUpdateResult +---- + diff --git a/docs/reference-tasks-cancel.asciidoc b/docs/reference-tasks-cancel.asciidoc new file mode 100644 index 000000000..8aecd48bb --- /dev/null +++ b/docs/reference-tasks-cancel.asciidoc @@ -0,0 +1,64 @@ +[[reference-tasks-cancel]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.tasks.cancel + +Cancels a task, if it can be cancelled through an API. + +{ref}/tasks.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TasksCancelRequest, options?): Promise +---- + +[discrete] +===== `TasksCancelRequest` + +[source,ts] +---- +interface TasksCancelRequest extends <> { + task_id?: <> + actions?: string | string[] + nodes?: string[] + parent_task_id?: string + wait_for_completion?: boolean +} +---- + +[discrete] +===== `TasksCancelResponse` + +[source,ts] +---- +type TasksCancelResponse = TasksTaskListResponseBase +---- + diff --git a/docs/reference-tasks-get.asciidoc b/docs/reference-tasks-get.asciidoc new file mode 100644 index 000000000..1f2d0cec6 --- /dev/null +++ b/docs/reference-tasks-get.asciidoc @@ -0,0 +1,67 @@ +[[reference-tasks-get]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.tasks.get + +Get task information. Returns information about the tasks currently executing in the cluster. + +{ref}/tasks.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TasksGetRequest, options?): Promise +---- + +[discrete] +===== `TasksGetRequest` + +[source,ts] +---- +interface TasksGetRequest extends <> { + task_id: <> + timeout?: <> + wait_for_completion?: boolean +} +---- + +[discrete] +===== `TasksGetResponse` + +[source,ts] +---- +interface TasksGetResponse { + completed: boolean + task: TasksTaskInfo + response?: any + error?: <> +} +---- + diff --git a/docs/reference-tasks-list.asciidoc b/docs/reference-tasks-list.asciidoc new file mode 100644 index 000000000..f77940b84 --- /dev/null +++ b/docs/reference-tasks-list.asciidoc @@ -0,0 +1,67 @@ +[[reference-tasks-list]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.tasks.list + +The task management API returns information about tasks currently executing on one or more nodes in the cluster. + +{ref}/tasks.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TasksListRequest, options?): Promise +---- + +[discrete] +===== `TasksListRequest` + +[source,ts] +---- +interface TasksListRequest extends <> { + actions?: string | string[] + detailed?: boolean + group_by?: TasksGroupBy + nodes?: <> + parent_task_id?: <> + master_timeout?: <> + timeout?: <> + wait_for_completion?: boolean +} +---- + +[discrete] +===== `TasksListResponse` + +[source,ts] +---- +type TasksListResponse = TasksTaskListResponseBase +---- + diff --git a/docs/reference-terms_enum.asciidoc b/docs/reference-terms_enum.asciidoc new file mode 100644 index 000000000..ceacd72c3 --- /dev/null +++ b/docs/reference-terms_enum.asciidoc @@ -0,0 +1,71 @@ +[[reference-terms_enum]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.termsEnum + +Get terms in an index. Discover terms that match a partial string in an index. This "terms enum" API is designed for low-latency look-ups used in auto-complete scenarios. If the `complete` property in the response is false, the returned terms set may be incomplete and should be treated as approximate. This can occur due to a few reasons, such as a request timeout or a node error. NOTE: The terms enum API may return terms from deleted documents. Deleted documents are initially only marked as deleted. It is not until their segments are merged that documents are actually deleted. Until that happens, the terms enum API will return terms from these documents. + +{ref}/search-terms-enum.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TermsEnumRequest, options?): Promise +---- + +[discrete] +===== `TermsEnumRequest` + +[source,ts] +---- +interface TermsEnumRequest extends <> { + index: <> + field: <> + size?: <> + timeout?: <> + case_insensitive?: boolean + index_filter?: QueryDslQueryContainer + string?: string + search_after?: string +} +---- + +[discrete] +===== `TermsEnumResponse` + +[source,ts] +---- +interface TermsEnumResponse { + _shards: <> + terms: string[] + complete: boolean +} +---- + diff --git a/docs/reference-termvectors.asciidoc b/docs/reference-termvectors.asciidoc new file mode 100644 index 000000000..e9e8ab9aa --- /dev/null +++ b/docs/reference-termvectors.asciidoc @@ -0,0 +1,82 @@ +[[reference-termvectors]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.termvectors + +Get term vector information. Get information and statistics about terms in the fields of a particular document. + +{ref}/docs-termvectors.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TermvectorsRequest, options?): Promise +---- + +[discrete] +===== `TermvectorsRequest` + +[source,ts] +---- +interface TermvectorsRequest extends <> { + index: <> + id?: <> + fields?: <> + field_statistics?: boolean + offsets?: boolean + payloads?: boolean + positions?: boolean + preference?: string + realtime?: boolean + routing?: <> + term_statistics?: boolean + version?: <> + version_type?: <> + doc?: TDocument + filter?: TermvectorsFilter + per_field_analyzer?: Record<<>, string> +} +---- + +[discrete] +===== `TermvectorsResponse` + +[source,ts] +---- +interface TermvectorsResponse { + found: boolean + _id?: <> + _index: <> + term_vectors?: Record<<>, TermvectorsTermVector> + took: <> + _version: <> +} +---- + diff --git a/docs/reference-text_structure-find_field_structure.asciidoc b/docs/reference-text_structure-find_field_structure.asciidoc new file mode 100644 index 000000000..f8ccbefd8 --- /dev/null +++ b/docs/reference-text_structure-find_field_structure.asciidoc @@ -0,0 +1,59 @@ +[[reference-text_structure-find_field_structure]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.textStructure.findFieldStructure + +Finds the structure of a text field in an index. + +{ref}/find-field-structure.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TextStructureFindFieldStructureRequest, options?): Promise +---- + +[discrete] +===== `TextStructureFindFieldStructureRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `TextStructureFindFieldStructureResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-text_structure-find_message_structure.asciidoc b/docs/reference-text_structure-find_message_structure.asciidoc new file mode 100644 index 000000000..da7e1047e --- /dev/null +++ b/docs/reference-text_structure-find_message_structure.asciidoc @@ -0,0 +1,59 @@ +[[reference-text_structure-find_message_structure]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.textStructure.findMessageStructure + +Finds the structure of a list of messages. The messages must contain data that is suitable to be ingested into Elasticsearch. + +{ref}/find-message-structure.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TextStructureFindMessageStructureRequest, options?): Promise +---- + +[discrete] +===== `TextStructureFindMessageStructureRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `TextStructureFindMessageStructureResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-text_structure-find_structure.asciidoc b/docs/reference-text_structure-find_structure.asciidoc new file mode 100644 index 000000000..c0c42ab2c --- /dev/null +++ b/docs/reference-text_structure-find_structure.asciidoc @@ -0,0 +1,98 @@ +[[reference-text_structure-find_structure]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.textStructure.findStructure + +Finds the structure of a text file. The text file must contain data that is suitable to be ingested into Elasticsearch. + +{ref}/find-structure.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TextStructureFindStructureRequest, options?): Promise +---- + +[discrete] +===== `TextStructureFindStructureRequest` + +[source,ts] +---- +interface TextStructureFindStructureRequest { + charset?: string + column_names?: string + delimiter?: string + ecs_compatibility?: string + explain?: boolean + format?: string + grok_pattern?: <> + has_header_row?: boolean + line_merge_size_limit?: <> + lines_to_sample?: <> + quote?: string + should_trim_fields?: boolean + timeout?: <> + timestamp_field?: <> + timestamp_format?: string + text_files?: TJsonDocument[] +} +---- + +[discrete] +===== `TextStructureFindStructureResponse` + +[source,ts] +---- +interface TextStructureFindStructureResponse { + charset: string + has_header_row?: boolean + has_<>_order_marker: boolean + format: string + field_stats: Record<<>, TextStructureFindStructureFieldStat> + sample_start: string + num_messages_analyzed: <> + mappings: MappingTypeMapping + quote?: string + delimiter?: string + need_client_timezone: boolean + num_lines_analyzed: <> + column_names?: string[] + explanation?: string[] + grok_pattern?: <> + multiline_start_pattern?: string + exclude_lines_pattern?: string + java_timestamp_formats?: string[] + joda_timestamp_formats?: string[] + timestamp_field?: <> + should_trim_fields?: boolean + ingest_pipeline: IngestPipelineConfig +} +---- + diff --git a/docs/reference-text_structure-test_grok_pattern.asciidoc b/docs/reference-text_structure-test_grok_pattern.asciidoc new file mode 100644 index 000000000..36557bfac --- /dev/null +++ b/docs/reference-text_structure-test_grok_pattern.asciidoc @@ -0,0 +1,64 @@ +[[reference-text_structure-test_grok_pattern]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.textStructure.testGrokPattern + +Tests a Grok pattern on some text. + +{ref}/test-grok-pattern.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TextStructureTestGrokPatternRequest, options?): Promise +---- + +[discrete] +===== `TextStructureTestGrokPatternRequest` + +[source,ts] +---- +interface TextStructureTestGrokPatternRequest extends <> { + ecs_compatibility?: string + grok_pattern: <> + text: string[] +} +---- + +[discrete] +===== `TextStructureTestGrokPatternResponse` + +[source,ts] +---- +interface TextStructureTestGrokPatternResponse { + matches: TextStructureTestGrokPatternMatchedText[] +} +---- + diff --git a/docs/reference-transform-delete_transform.asciidoc b/docs/reference-transform-delete_transform.asciidoc new file mode 100644 index 000000000..ef2e836c9 --- /dev/null +++ b/docs/reference-transform-delete_transform.asciidoc @@ -0,0 +1,63 @@ +[[reference-transform-delete_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.deleteTransform + +Delete a transform. Deletes a transform. + +{ref}/delete-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformDeleteTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformDeleteTransformRequest` + +[source,ts] +---- +interface TransformDeleteTransformRequest extends <> { + transform_id: <> + force?: boolean + delete_dest_index?: boolean + timeout?: <> +} +---- + +[discrete] +===== `TransformDeleteTransformResponse` + +[source,ts] +---- +type TransformDeleteTransformResponse = <> +---- + diff --git a/docs/reference-transform-get_node_stats.asciidoc b/docs/reference-transform-get_node_stats.asciidoc new file mode 100644 index 000000000..1eda67927 --- /dev/null +++ b/docs/reference-transform-get_node_stats.asciidoc @@ -0,0 +1,57 @@ +[[reference-transform-get_node_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.getNodeStats + +Retrieves transform usage information for transform nodes. + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformGetNodeStatsRequest, options?): Promise +---- + +[discrete] +===== `TransformGetNodeStatsRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `TransformGetNodeStatsResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-transform-get_transform.asciidoc b/docs/reference-transform-get_transform.asciidoc new file mode 100644 index 000000000..cd4e5a3e9 --- /dev/null +++ b/docs/reference-transform-get_transform.asciidoc @@ -0,0 +1,67 @@ +[[reference-transform-get_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.getTransform + +Get transforms. Retrieves configuration information for transforms. + +{ref}/get-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformGetTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformGetTransformRequest` + +[source,ts] +---- +interface TransformGetTransformRequest extends <> { + transform_id?: <> + allow_no_match?: boolean + from?: <> + size?: <> + exclude_generated?: boolean +} +---- + +[discrete] +===== `TransformGetTransformResponse` + +[source,ts] +---- +interface TransformGetTransformResponse { + count: <> + transforms: TransformGetTransformTransformSummary[] +} +---- + diff --git a/docs/reference-transform-get_transform_stats.asciidoc b/docs/reference-transform-get_transform_stats.asciidoc new file mode 100644 index 000000000..c85f6dd01 --- /dev/null +++ b/docs/reference-transform-get_transform_stats.asciidoc @@ -0,0 +1,67 @@ +[[reference-transform-get_transform_stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.getTransformStats + +Get transform stats. Retrieves usage information for transforms. + +{ref}/get-transform-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformGetTransformStatsRequest, options?): Promise +---- + +[discrete] +===== `TransformGetTransformStatsRequest` + +[source,ts] +---- +interface TransformGetTransformStatsRequest extends <> { + transform_id: <> + allow_no_match?: boolean + from?: <> + size?: <> + timeout?: <> +} +---- + +[discrete] +===== `TransformGetTransformStatsResponse` + +[source,ts] +---- +interface TransformGetTransformStatsResponse { + count: <> + transforms: TransformGetTransformStatsTransformStats[] +} +---- + diff --git a/docs/reference-transform-preview_transform.asciidoc b/docs/reference-transform-preview_transform.asciidoc new file mode 100644 index 000000000..e0600a399 --- /dev/null +++ b/docs/reference-transform-preview_transform.asciidoc @@ -0,0 +1,73 @@ +[[reference-transform-preview_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.previewTransform + +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. + +{ref}/preview-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformPreviewTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformPreviewTransformRequest` + +[source,ts] +---- +interface TransformPreviewTransformRequest extends <> { + transform_id?: <> + timeout?: <> + dest?: TransformDestination + description?: string + frequency?: <> + pivot?: TransformPivot + source?: TransformSource + settings?: TransformSettings + sync?: TransformSyncContainer + retention_policy?: TransformRetentionPolicyContainer + latest?: TransformLatest +} +---- + +[discrete] +===== `TransformPreviewTransformResponse` + +[source,ts] +---- +interface TransformPreviewTransformResponse { + generated_dest_index: IndicesIndexState + preview: TTransform[] +} +---- + diff --git a/docs/reference-transform-put_transform.asciidoc b/docs/reference-transform-put_transform.asciidoc new file mode 100644 index 000000000..640a21a4b --- /dev/null +++ b/docs/reference-transform-put_transform.asciidoc @@ -0,0 +1,72 @@ +[[reference-transform-put_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.putTransform + +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. + +{ref}/put-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformPutTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformPutTransformRequest` + +[source,ts] +---- +interface TransformPutTransformRequest extends <> { + transform_id: <> + defer_validation?: boolean + timeout?: <> + dest: TransformDestination + description?: string + frequency?: <> + latest?: TransformLatest + _meta?: <> + pivot?: TransformPivot + retention_policy?: TransformRetentionPolicyContainer + settings?: TransformSettings + source: TransformSource + sync?: TransformSyncContainer +} +---- + +[discrete] +===== `TransformPutTransformResponse` + +[source,ts] +---- +type TransformPutTransformResponse = <> +---- + diff --git a/docs/reference-transform-reset_transform.asciidoc b/docs/reference-transform-reset_transform.asciidoc new file mode 100644 index 000000000..77ee8eb4a --- /dev/null +++ b/docs/reference-transform-reset_transform.asciidoc @@ -0,0 +1,61 @@ +[[reference-transform-reset_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.resetTransform + +Reset a transform. Resets 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. + +{ref}/reset-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformResetTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformResetTransformRequest` + +[source,ts] +---- +interface TransformResetTransformRequest extends <> { + transform_id: <> + force?: boolean +} +---- + +[discrete] +===== `TransformResetTransformResponse` + +[source,ts] +---- +type TransformResetTransformResponse = <> +---- + diff --git a/docs/reference-transform-schedule_now_transform.asciidoc b/docs/reference-transform-schedule_now_transform.asciidoc new file mode 100644 index 000000000..281e19c9d --- /dev/null +++ b/docs/reference-transform-schedule_now_transform.asciidoc @@ -0,0 +1,61 @@ +[[reference-transform-schedule_now_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.scheduleNowTransform + +Schedule a transform to start now. Instantly runs a transform to process data. If you _schedule_now a transform, it will process the new data instantly, without waiting for the configured frequency interval. After _schedule_now API is called, the transform will be processed again at now + frequency unless _schedule_now API is called again in the meantime. + +{ref}/schedule-now-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformScheduleNowTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformScheduleNowTransformRequest` + +[source,ts] +---- +interface TransformScheduleNowTransformRequest extends <> { + transform_id: <> + timeout?: <> +} +---- + +[discrete] +===== `TransformScheduleNowTransformResponse` + +[source,ts] +---- +type TransformScheduleNowTransformResponse = <> +---- + diff --git a/docs/reference-transform-start_transform.asciidoc b/docs/reference-transform-start_transform.asciidoc new file mode 100644 index 000000000..4325fba33 --- /dev/null +++ b/docs/reference-transform-start_transform.asciidoc @@ -0,0 +1,62 @@ +[[reference-transform-start_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.startTransform + +Start a transform. Starts 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. + +{ref}/start-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformStartTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformStartTransformRequest` + +[source,ts] +---- +interface TransformStartTransformRequest extends <> { + transform_id: <> + timeout?: <> + from?: string +} +---- + +[discrete] +===== `TransformStartTransformResponse` + +[source,ts] +---- +type TransformStartTransformResponse = <> +---- + diff --git a/docs/reference-transform-stop_transform.asciidoc b/docs/reference-transform-stop_transform.asciidoc new file mode 100644 index 000000000..e96b21b3b --- /dev/null +++ b/docs/reference-transform-stop_transform.asciidoc @@ -0,0 +1,65 @@ +[[reference-transform-stop_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.stopTransform + +Stop transforms. Stops one or more transforms. + +{ref}/stop-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformStopTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformStopTransformRequest` + +[source,ts] +---- +interface TransformStopTransformRequest extends <> { + transform_id: <> + allow_no_match?: boolean + force?: boolean + timeout?: <> + wait_for_checkpoint?: boolean + wait_for_completion?: boolean +} +---- + +[discrete] +===== `TransformStopTransformResponse` + +[source,ts] +---- +type TransformStopTransformResponse = <> +---- + diff --git a/docs/reference-transform-update_transform.asciidoc b/docs/reference-transform-update_transform.asciidoc new file mode 100644 index 000000000..44947d1e4 --- /dev/null +++ b/docs/reference-transform-update_transform.asciidoc @@ -0,0 +1,85 @@ +[[reference-transform-update_transform]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.updateTransform + +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. + +{ref}/update-transform.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformUpdateTransformRequest, options?): Promise +---- + +[discrete] +===== `TransformUpdateTransformRequest` + +[source,ts] +---- +interface TransformUpdateTransformRequest extends <> { + transform_id: <> + defer_validation?: boolean + timeout?: <> + dest?: TransformDestination + description?: string + frequency?: <> + _meta?: <> + source?: TransformSource + settings?: TransformSettings + sync?: TransformSyncContainer + retention_policy?: TransformRetentionPolicyContainer | null +} +---- + +[discrete] +===== `TransformUpdateTransformResponse` + +[source,ts] +---- +interface TransformUpdateTransformResponse { + authorization?: MlTransformAuthorization + create_time: <> + description: string + dest: ReindexDestination + frequency?: <> + id: <> + latest?: TransformLatest + pivot?: TransformPivot + retention_policy?: TransformRetentionPolicyContainer + settings: TransformSettings + source: ReindexSource + sync?: TransformSyncContainer + version: <> + _meta?: <> +} +---- + diff --git a/docs/reference-transform-upgrade_transforms.asciidoc b/docs/reference-transform-upgrade_transforms.asciidoc new file mode 100644 index 000000000..08adf941d --- /dev/null +++ b/docs/reference-transform-upgrade_transforms.asciidoc @@ -0,0 +1,65 @@ +[[reference-transform-upgrade_transforms]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.transform.upgradeTransforms + +Upgrades all transforms. 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. + +{ref}/upgrade-transforms.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(TransformUpgradeTransformsRequest, options?): Promise +---- + +[discrete] +===== `TransformUpgradeTransformsRequest` + +[source,ts] +---- +interface TransformUpgradeTransformsRequest extends <> { + dry_run?: boolean + timeout?: <> +} +---- + +[discrete] +===== `TransformUpgradeTransformsResponse` + +[source,ts] +---- +interface TransformUpgradeTransformsResponse { + needs_update: <> + no_action: <> + updated: <> +} +---- + diff --git a/docs/reference-update.asciidoc b/docs/reference-update.asciidoc new file mode 100644 index 000000000..f78860896 --- /dev/null +++ b/docs/reference-update.asciidoc @@ -0,0 +1,79 @@ +[[reference-update]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.update + +Update a document. Updates a document by running a script or passing a partial document. + +{ref}/docs-update.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(UpdateRequest, options?): Promise +---- + +[discrete] +===== `UpdateRequest` + +[source,ts] +---- +interface UpdateRequest extends <> { + id: <> + index: <> + if_primary_term?: <> + if_seq_no?: <> + lang?: string + refresh?: <> + require_alias?: boolean + retry_on_conflict?: <> + routing?: <> + timeout?: <> + wait_for_active_shards?: <> + _source_excludes?: <> + _source_includes?: <> + detect_noop?: boolean + doc?: TPartialDocument + doc_as_upsert?: boolean + script?: <> | string + scripted_upsert?: boolean + _source?: SearchSourceConfig + upsert?: TDocument +} +---- + +[discrete] +===== `UpdateResponse` + +[source,ts] +---- +type UpdateResponse = UpdateUpdateWriteResponseBase +---- + diff --git a/docs/reference-update_by_query.asciidoc b/docs/reference-update_by_query.asciidoc new file mode 100644 index 000000000..498387651 --- /dev/null +++ b/docs/reference-update_by_query.asciidoc @@ -0,0 +1,111 @@ +[[reference-update_by_query]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.updateByQuery + +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. + +{ref}/docs-update-by-query.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(UpdateByQueryRequest, options?): Promise +---- + +[discrete] +===== `UpdateByQueryRequest` + +[source,ts] +---- +interface UpdateByQueryRequest extends <> { + index: <> + allow_no_indices?: boolean + analyzer?: string + analyze_wildcard?: boolean + default_operator?: QueryDslOperator + df?: string + expand_wildcards?: <> + from?: <> + ignore_unavailable?: boolean + lenient?: boolean + pipeline?: string + preference?: string + q?: string + refresh?: boolean + request_cache?: boolean + requests_per_second?: <> + routing?: <> + scroll?: <> + scroll_size?: <> + search_timeout?: <> + search_type?: <> + slices?: <> + sort?: string[] + stats?: string[] + terminate_after?: <> + timeout?: <> + version?: boolean + version_type?: boolean + wait_for_active_shards?: <> + wait_for_completion?: boolean + max_docs?: <> + query?: QueryDslQueryContainer + script?: <> | string + slice?: <> + conflicts?: <> +} +---- + +[discrete] +===== `UpdateByQueryResponse` + +[source,ts] +---- +interface UpdateByQueryResponse { + batches?: <> + failures?: <>[] + noops?: <> + deleted?: <> + requests_per_second?: <> + retries?: <> + task?: <> + timed_out?: boolean + took?: <><<>> + total?: <> + updated?: <> + version_conflicts?: <> + throttled?: <> + throttled_millis?: <><<>> + throttled_until?: <> + throttled_until_millis?: <><<>> +} +---- + diff --git a/docs/reference-update_by_query_rethrottle.asciidoc b/docs/reference-update_by_query_rethrottle.asciidoc new file mode 100644 index 000000000..57da9c7af --- /dev/null +++ b/docs/reference-update_by_query_rethrottle.asciidoc @@ -0,0 +1,63 @@ +[[reference-update_by_query_rethrottle]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.updateByQueryRethrottle + +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. + +{ref}/docs-update-by-query.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(UpdateByQueryRethrottleRequest, options?): Promise +---- + +[discrete] +===== `UpdateByQueryRethrottleRequest` + +[source,ts] +---- +interface UpdateByQueryRethrottleRequest extends <> { + task_id: <> + requests_per_second?: <> +} +---- + +[discrete] +===== `UpdateByQueryRethrottleResponse` + +[source,ts] +---- +interface UpdateByQueryRethrottleResponse { + nodes: Record +} +---- + diff --git a/docs/reference-watcher-ack_watch.asciidoc b/docs/reference-watcher-ack_watch.asciidoc new file mode 100644 index 000000000..421ee5418 --- /dev/null +++ b/docs/reference-watcher-ack_watch.asciidoc @@ -0,0 +1,63 @@ +[[reference-watcher-ack_watch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.ackWatch + +Acknowledges a watch, manually throttling the execution of the watch's actions. + +{ref}/watcher-api-ack-watch.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherAckWatchRequest, options?): Promise +---- + +[discrete] +===== `WatcherAckWatchRequest` + +[source,ts] +---- +interface WatcherAckWatchRequest extends <> { + watch_id: <> + action_id?: <> +} +---- + +[discrete] +===== `WatcherAckWatchResponse` + +[source,ts] +---- +interface WatcherAckWatchResponse { + status: WatcherWatchStatus +} +---- + diff --git a/docs/reference-watcher-activate_watch.asciidoc b/docs/reference-watcher-activate_watch.asciidoc new file mode 100644 index 000000000..077bf3c4f --- /dev/null +++ b/docs/reference-watcher-activate_watch.asciidoc @@ -0,0 +1,62 @@ +[[reference-watcher-activate_watch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.activateWatch + +Activates a currently inactive watch. + +{ref}/watcher-api-activate-watch.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherActivateWatchRequest, options?): Promise +---- + +[discrete] +===== `WatcherActivateWatchRequest` + +[source,ts] +---- +interface WatcherActivateWatchRequest extends <> { + watch_id: <> +} +---- + +[discrete] +===== `WatcherActivateWatchResponse` + +[source,ts] +---- +interface WatcherActivateWatchResponse { + status: WatcherActivationStatus +} +---- + diff --git a/docs/reference-watcher-deactivate_watch.asciidoc b/docs/reference-watcher-deactivate_watch.asciidoc new file mode 100644 index 000000000..3ba6b9cbe --- /dev/null +++ b/docs/reference-watcher-deactivate_watch.asciidoc @@ -0,0 +1,62 @@ +[[reference-watcher-deactivate_watch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.deactivateWatch + +Deactivates a currently active watch. + +{ref}/watcher-api-deactivate-watch.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherDeactivateWatchRequest, options?): Promise +---- + +[discrete] +===== `WatcherDeactivateWatchRequest` + +[source,ts] +---- +interface WatcherDeactivateWatchRequest extends <> { + watch_id: <> +} +---- + +[discrete] +===== `WatcherDeactivateWatchResponse` + +[source,ts] +---- +interface WatcherDeactivateWatchResponse { + status: WatcherActivationStatus +} +---- + diff --git a/docs/reference-watcher-delete_watch.asciidoc b/docs/reference-watcher-delete_watch.asciidoc new file mode 100644 index 000000000..debba3358 --- /dev/null +++ b/docs/reference-watcher-delete_watch.asciidoc @@ -0,0 +1,64 @@ +[[reference-watcher-delete_watch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.deleteWatch + +Removes a watch from Watcher. + +{ref}/watcher-api-delete-watch.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherDeleteWatchRequest, options?): Promise +---- + +[discrete] +===== `WatcherDeleteWatchRequest` + +[source,ts] +---- +interface WatcherDeleteWatchRequest extends <> { + id: <> +} +---- + +[discrete] +===== `WatcherDeleteWatchResponse` + +[source,ts] +---- +interface WatcherDeleteWatchResponse { + found: boolean + _id: <> + _version: <> +} +---- + diff --git a/docs/reference-watcher-execute_watch.asciidoc b/docs/reference-watcher-execute_watch.asciidoc new file mode 100644 index 000000000..877a43baa --- /dev/null +++ b/docs/reference-watcher-execute_watch.asciidoc @@ -0,0 +1,71 @@ +[[reference-watcher-execute_watch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.executeWatch + +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 execute the watch without executing 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 execution. + +{ref}/watcher-api-execute-watch.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherExecuteWatchRequest, options?): Promise +---- + +[discrete] +===== `WatcherExecuteWatchRequest` + +[source,ts] +---- +interface WatcherExecuteWatchRequest extends <> { + id?: <> + debug?: boolean + action_modes?: Record + alternative_input?: Record + ignore_condition?: boolean + record_execution?: boolean + simulated_actions?: WatcherSimulatedActions + trigger_data?: WatcherScheduleTriggerEvent + watch?: WatcherWatch +} +---- + +[discrete] +===== `WatcherExecuteWatchResponse` + +[source,ts] +---- +interface WatcherExecuteWatchResponse { + _id: <> + watch_record: WatcherExecuteWatchWatchRecord +} +---- + diff --git a/docs/reference-watcher-get_settings.asciidoc b/docs/reference-watcher-get_settings.asciidoc new file mode 100644 index 000000000..212247439 --- /dev/null +++ b/docs/reference-watcher-get_settings.asciidoc @@ -0,0 +1,59 @@ +[[reference-watcher-get_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.getSettings + +Retrieve settings for the watcher system index + +{ref}/watcher-api-get-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherGetSettingsRequest, options?): Promise +---- + +[discrete] +===== `WatcherGetSettingsRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `WatcherGetSettingsResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-watcher-get_watch.asciidoc b/docs/reference-watcher-get_watch.asciidoc new file mode 100644 index 000000000..ca6ef6c0e --- /dev/null +++ b/docs/reference-watcher-get_watch.asciidoc @@ -0,0 +1,68 @@ +[[reference-watcher-get_watch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.getWatch + +Retrieves a watch by its ID. + +{ref}/watcher-api-get-watch.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherGetWatchRequest, options?): Promise +---- + +[discrete] +===== `WatcherGetWatchRequest` + +[source,ts] +---- +interface WatcherGetWatchRequest extends <> { + id: <> +} +---- + +[discrete] +===== `WatcherGetWatchResponse` + +[source,ts] +---- +interface WatcherGetWatchResponse { + found: boolean + _id: <> + status?: WatcherWatchStatus + watch?: WatcherWatch + _primary_term?: <> + _seq_no?: <> + _version?: <> +} +---- + diff --git a/docs/reference-watcher-put_watch.asciidoc b/docs/reference-watcher-put_watch.asciidoc new file mode 100644 index 000000000..13b2ccb87 --- /dev/null +++ b/docs/reference-watcher-put_watch.asciidoc @@ -0,0 +1,77 @@ +[[reference-watcher-put_watch]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.putWatch + +Creates a new watch, or updates an existing one. + +{ref}/watcher-api-put-watch.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherPutWatchRequest, options?): Promise +---- + +[discrete] +===== `WatcherPutWatchRequest` + +[source,ts] +---- +interface WatcherPutWatchRequest extends <> { + id: <> + active?: boolean + if_primary_term?: <> + if_seq_no?: <> + version?: <> + actions?: Record + condition?: WatcherConditionContainer + input?: WatcherInputContainer + metadata?: <> + throttle_period?: string + transform?: <> + trigger?: WatcherTriggerContainer +} +---- + +[discrete] +===== `WatcherPutWatchResponse` + +[source,ts] +---- +interface WatcherPutWatchResponse { + created: boolean + _id: <> + _primary_term: <> + _seq_no: <> + _version: <> +} +---- + diff --git a/docs/reference-watcher-query_watches.asciidoc b/docs/reference-watcher-query_watches.asciidoc new file mode 100644 index 000000000..ca4920921 --- /dev/null +++ b/docs/reference-watcher-query_watches.asciidoc @@ -0,0 +1,67 @@ +[[reference-watcher-query_watches]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.queryWatches + +Retrieves stored watches. + +{ref}/watcher-api-query-watches.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherQueryWatchesRequest, options?): Promise +---- + +[discrete] +===== `WatcherQueryWatchesRequest` + +[source,ts] +---- +interface WatcherQueryWatchesRequest extends <> { + from?: <> + size?: <> + query?: QueryDslQueryContainer + sort?: <> + search_after?: <> +} +---- + +[discrete] +===== `WatcherQueryWatchesResponse` + +[source,ts] +---- +interface WatcherQueryWatchesResponse { + count: <> + watches: WatcherQueryWatch[] +} +---- + diff --git a/docs/reference-watcher-start.asciidoc b/docs/reference-watcher-start.asciidoc new file mode 100644 index 000000000..c20edc7e6 --- /dev/null +++ b/docs/reference-watcher-start.asciidoc @@ -0,0 +1,59 @@ +[[reference-watcher-start]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.start + +Starts Watcher if it is not already running. + +{ref}/watcher-api-start.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherStartRequest, options?): Promise +---- + +[discrete] +===== `WatcherStartRequest` + +[source,ts] +---- +interface WatcherStartRequest extends <> { +} +---- + +[discrete] +===== `WatcherStartResponse` + +[source,ts] +---- +type WatcherStartResponse = <> +---- + diff --git a/docs/reference-watcher-stats.asciidoc b/docs/reference-watcher-stats.asciidoc new file mode 100644 index 000000000..48543906b --- /dev/null +++ b/docs/reference-watcher-stats.asciidoc @@ -0,0 +1,66 @@ +[[reference-watcher-stats]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.stats + +Retrieves the current Watcher metrics. + +{ref}/watcher-api-stats.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherStatsRequest, options?): Promise +---- + +[discrete] +===== `WatcherStatsRequest` + +[source,ts] +---- +interface WatcherStatsRequest extends <> { + metric?: WatcherStatsWatcherMetric | WatcherStatsWatcherMetric[] + emit_stacktraces?: boolean +} +---- + +[discrete] +===== `WatcherStatsResponse` + +[source,ts] +---- +interface WatcherStatsResponse { + _nodes: <> + cluster_name: <> + manually_stopped: boolean + stats: WatcherStatsWatcherNodeStats[] +} +---- + diff --git a/docs/reference-watcher-stop.asciidoc b/docs/reference-watcher-stop.asciidoc new file mode 100644 index 000000000..0ee7b0aba --- /dev/null +++ b/docs/reference-watcher-stop.asciidoc @@ -0,0 +1,59 @@ +[[reference-watcher-stop]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.stop + +Stops Watcher if it is running. + +{ref}/watcher-api-stop.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherStopRequest, options?): Promise +---- + +[discrete] +===== `WatcherStopRequest` + +[source,ts] +---- +interface WatcherStopRequest extends <> { +} +---- + +[discrete] +===== `WatcherStopResponse` + +[source,ts] +---- +type WatcherStopResponse = <> +---- + diff --git a/docs/reference-watcher-update_settings.asciidoc b/docs/reference-watcher-update_settings.asciidoc new file mode 100644 index 000000000..9c3cc18df --- /dev/null +++ b/docs/reference-watcher-update_settings.asciidoc @@ -0,0 +1,59 @@ +[[reference-watcher-update_settings]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.watcher.updateSettings + +Update settings for the watcher system index + +{ref}/watcher-api-update-settings.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(WatcherUpdateSettingsRequest, options?): Promise +---- + +[discrete] +===== `WatcherUpdateSettingsRequest` + +[source,ts] +---- +{ +} +---- + +[discrete] +===== `WatcherUpdateSettingsResponse` + +[source,ts] +---- +n/a +---- + diff --git a/docs/reference-xpack-info.asciidoc b/docs/reference-xpack-info.asciidoc new file mode 100644 index 000000000..9fb5bb316 --- /dev/null +++ b/docs/reference-xpack-info.asciidoc @@ -0,0 +1,67 @@ +[[reference-xpack-info]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.xpack.info + +Provides general information about the installed X-Pack features. + +{ref}/info-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(XpackInfoRequest, options?): Promise +---- + +[discrete] +===== `XpackInfoRequest` + +[source,ts] +---- +interface XpackInfoRequest extends <> { + categories?: XpackInfoXPackCategory[] + accept_enterprise?: boolean + human?: boolean +} +---- + +[discrete] +===== `XpackInfoResponse` + +[source,ts] +---- +interface XpackInfoResponse { + build: XpackInfoBuildInformation + features: XpackInfoFeatures + license: XpackInfoMinimalLicenseInformation + tagline: string +} +---- + diff --git a/docs/reference-xpack-usage.asciidoc b/docs/reference-xpack-usage.asciidoc new file mode 100644 index 000000000..04b83dc10 --- /dev/null +++ b/docs/reference-xpack-usage.asciidoc @@ -0,0 +1,90 @@ +[[reference-xpack-usage]] + +//////// +=========================================================================================================================== +|| || +|| || +|| || +|| ██████╗ ███████╗ █████╗ ██████╗ ███╗ ███╗███████╗ || +|| ██╔══██╗██╔════╝██╔══██╗██╔══██╗████╗ ████║██╔════╝ || +|| ██████╔╝█████╗ ███████║██║ ██║██╔████╔██║█████╗ || +|| ██╔══██╗██╔══╝ ██╔══██║██║ ██║██║╚██╔╝██║██╔══╝ || +|| ██║ ██║███████╗██║ ██║██████╔╝██║ ╚═╝ ██║███████╗ || +|| ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚══════╝ || +|| || +|| || +|| This file is autogenerated, DO NOT send pull requests that changes this file directly. || +|| You should update the script that does the generation, which can be found in: || +|| https://github.com/elastic/elastic-client-generator-js || +|| || +|| You can run the script with the following command: || +|| npm run elasticsearch -- --version || +|| || +|| || +|| || +=========================================================================================================================== +//////// + +[discrete] +=== client.xpack.usage + +This API provides information about which features are currently enabled and available under the current license and some usage statistics. + +{ref}/usage-api.html[{es} documentation] + +[discrete] +==== Function signature + +[source,ts] +---- +(XpackUsageRequest, options?): Promise +---- + +[discrete] +===== `XpackUsageRequest` + +[source,ts] +---- +interface XpackUsageRequest extends <> { + master_timeout?: <> +} +---- + +[discrete] +===== `XpackUsageResponse` + +[source,ts] +---- +interface XpackUsageResponse { + aggregate_metric: XpackUsageBase + analytics: XpackUsageAnalytics + archive: XpackUsageArchive + watcher: XpackUsageWatcher + ccr: XpackUsageCcr + data_frame?: XpackUsageBase + data_science?: XpackUsageBase + data_streams?: XpackUsageDataStreams + data_tiers: XpackUsageDataTiers + enrich?: XpackUsageBase + eql: XpackUsageEql + flattened?: XpackUsageFlattened + frozen_indices: XpackUsageFrozenIndices + graph: XpackUsageBase + health_api?: XpackUsageHealthStatistics + ilm: XpackUsageIlm + logstash: XpackUsageBase + ml: XpackUsageMachineLearning + monitoring: XpackUsageMonitoring + rollup: XpackUsageBase + runtime_fields?: XpackUsageRuntimeFieldTypes + spatial: XpackUsageBase + searchable_snapshots: XpackUsageSearchableSnapshots + security: XpackUsageSecurity + slm: XpackUsageSlm + sql: XpackUsageSql + transform: XpackUsageBase + vectors?: XpackUsageVector + voting_only: XpackUsageBase +} +---- + diff --git a/docs/reference.asciidoc b/docs/reference.asciidoc index 403af082d..f7c374225 100644 --- a/docs/reference.asciidoc +++ b/docs/reference.asciidoc @@ -26,11945 +26,1000 @@ == API Reference [discrete] -=== bulk -Bulk index or delete documents. -Performs multiple indexing or delete operations in a single API call. -This reduces overhead and can greatly increase indexing speed. - -{ref}/docs-bulk.html[Endpoint documentation] -[source,ts] ----- -client.bulk({ ... }) ----- +=== client.asyncSearch.delete [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string)*: Name of the data stream, index, or index alias to perform bulk actions on. -** *`operations` (Optional, { index, create, update, delete } | { detect_noop, doc, doc_as_upsert, script, scripted_upsert, _source, upsert } | object[])* -** *`pipeline` (Optional, string)*: ID of the pipeline to use to preprocess incoming documents. -If the index has a default ingest pipeline specified, then setting the value to `_none` disables the default ingest pipeline for this request. -If a final pipeline is configured it will always run, regardless of the value of this parameter. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true`, Elasticsearch refreshes 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` do nothing with refreshes. -Valid values: `true`, `false`, `wait_for`. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`_source` (Optional, boolean | string | string[])*: `true` or `false` to return the `_source` field or not, or a list of fields to return. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude from the response. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -** *`timeout` (Optional, string | -1 | 0)*: Period each action waits for the following operations: automatic index creation, dynamic mapping updates, waiting for active shards. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). -** *`require_alias` (Optional, boolean)*: If `true`, the request’s actions must target an index alias. - +=== client.asyncSearch.get [discrete] -=== clear_scroll -Clear a scrolling search. - -Clear the search context and results for a scrolling search. - -{ref}/clear-scroll-api.html[Endpoint documentation] -[source,ts] ----- -client.clearScroll({ ... }) ----- +=== client.asyncSearch.status [discrete] -==== Arguments - -* *Request (object):* -** *`scroll_id` (Optional, string | string[])*: List of scroll IDs to clear. -To clear all scroll IDs, use `_all`. - +=== client.asyncSearch.submit [discrete] -=== close_point_in_time -Close a point in time. - -A point in time must be opened explicitly before being used in search requests. -The `keep_alive` parameter tells Elasticsearch how long it should persist. -A point in time is automatically closed when the `keep_alive` period has elapsed. -However, keeping points in time has a cost; close them as soon as they are no longer required for search requests. - -{ref}/point-in-time-api.html[Endpoint documentation] -[source,ts] ----- -client.closePointInTime({ id }) ----- +=== client.autoscaling.deleteAutoscalingPolicy [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: The ID of the point-in-time. - +=== client.autoscaling.getAutoscalingCapacity [discrete] -=== count -Returns number of documents matching a query. - -{ref}/search-count.html[Endpoint documentation] -[source,ts] ----- -client.count({ ... }) ----- +=== client.autoscaling.getAutoscalingPolicy [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases to search. -Supports wildcards (`*`). -To search all data streams and indices, omit this parameter or use `*` or `_all`. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Defines the search definition using the Query DSL. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`analyzer` (Optional, string)*: Analyzer to use for the query string. -This parameter can only be used when the `q` query string parameter is specified. -** *`analyze_wildcard` (Optional, boolean)*: If `true`, wildcard and prefix queries are analyzed. -This parameter can only be used when the `q` query string parameter is specified. -** *`default_operator` (Optional, Enum("and" | "or"))*: The default operator for query string query: `AND` or `OR`. -This parameter can only be used when the `q` query string parameter is specified. -** *`df` (Optional, string)*: Field to use as default where no field prefix is given in the query string. -This parameter can only be used when the `q` query string parameter is specified. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -** *`ignore_throttled` (Optional, boolean)*: If `true`, concrete, expanded or aliased indices are ignored when frozen. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`lenient` (Optional, boolean)*: If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored. -** *`min_score` (Optional, number)*: Sets the minimum `_score` value that documents must have to be included in the result. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`terminate_after` (Optional, number)*: 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. -** *`q` (Optional, string)*: Query in the Lucene query string syntax. - +=== client.autoscaling.putAutoscalingPolicy [discrete] -=== create -Index a document. -Adds a JSON document to the specified data stream or index and makes it searchable. -If the target is an index and the document already exists, the request updates the document and increments its version. - -{ref}/docs-index_.html[Endpoint documentation] -[source,ts] ----- -client.create({ id, index }) ----- +=== client.bulk [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Unique identifier for the document. -** *`index` (string)*: Name of the data stream or index to target. -If the target doesn’t exist and matches the name or wildcard (`*`) pattern of an index template with a `data_stream` definition, this request creates the data stream. -If the target doesn’t exist and doesn’t match a data stream template, this request creates the index. -** *`document` (Optional, object)*: A document. -** *`pipeline` (Optional, string)*: ID of the pipeline to use to preprocess incoming documents. -If the index has a default ingest pipeline specified, then setting the value to `_none` disables the default ingest pipeline for this request. -If a final pipeline is configured it will always run, regardless of the value of this parameter. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true`, Elasticsearch refreshes 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` do nothing with refreshes. -Valid values: `true`, `false`, `wait_for`. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`timeout` (Optional, string | -1 | 0)*: Period the request waits for the following operations: automatic index creation, dynamic mapping updates, waiting for active shards. -** *`version` (Optional, number)*: Explicit version number for concurrency control. -The specified version must match the current version of the document for the request to succeed. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type: `external`, `external_gte`. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - +=== client.cat.aliases [discrete] -=== delete -Delete a document. -Removes a JSON document from the specified index. - -{ref}/docs-delete.html[Endpoint documentation] -[source,ts] ----- -client.delete({ id, index }) ----- +=== client.cat.allocation [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Unique identifier for the document. -** *`index` (string)*: Name of the target index. -** *`if_primary_term` (Optional, number)*: Only perform the operation if the document has this primary term. -** *`if_seq_no` (Optional, number)*: Only perform the operation if the document has this sequence number. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true`, Elasticsearch refreshes 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` do nothing with refreshes. -Valid values: `true`, `false`, `wait_for`. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for active shards. -** *`version` (Optional, number)*: Explicit version number for concurrency control. -The specified version must match the current version of the document for the request to succeed. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type: `external`, `external_gte`. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - +=== client.cat.componentTemplates [discrete] -=== delete_by_query -Delete documents. -Deletes documents that match the specified query. - -{ref}/docs-delete-by-query.html[Endpoint documentation] -[source,ts] ----- -client.deleteByQuery({ index }) ----- +=== client.cat.count [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams, indices, and aliases to search. -Supports wildcards (`*`). -To search all data streams or indices, omit this parameter or use `*` or `_all`. -** *`max_docs` (Optional, number)*: The maximum number of documents to delete. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Specifies the documents to delete using the Query DSL. -** *`slice` (Optional, { field, id, max })*: Slice the request manually using the provided slice ID and total number of slices. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`analyzer` (Optional, string)*: Analyzer to use for the query string. -** *`analyze_wildcard` (Optional, boolean)*: If `true`, wildcard and prefix queries are analyzed. -** *`conflicts` (Optional, Enum("abort" | "proceed"))*: What to do if delete by query hits version conflicts: `abort` or `proceed`. -** *`default_operator` (Optional, Enum("and" | "or"))*: The default operator for query string query: `AND` or `OR`. -** *`df` (Optional, string)*: Field to use as default where no field prefix is given in the query string. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`from` (Optional, number)*: Starting offset (default: 0) -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`lenient` (Optional, boolean)*: If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`refresh` (Optional, boolean)*: If `true`, Elasticsearch refreshes all shards involved in the delete by query after the request completes. -** *`request_cache` (Optional, boolean)*: If `true`, the request cache is used for this request. -Defaults to the index-level setting. -** *`requests_per_second` (Optional, float)*: The throttle for this request in sub-requests per second. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`q` (Optional, string)*: Query in the Lucene query string syntax. -** *`scroll` (Optional, string | -1 | 0)*: Period to retain the search context for scrolling. -** *`scroll_size` (Optional, number)*: Size of the scroll request that powers the operation. -** *`search_timeout` (Optional, string | -1 | 0)*: Explicit timeout for each search request. -Defaults to no timeout. -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: The type of the search operation. -Available options: `query_then_fetch`, `dfs_query_then_fetch`. -** *`slices` (Optional, number | Enum("auto"))*: The number of slices this task should be divided into. -** *`sort` (Optional, string[])*: A list of : pairs. -** *`stats` (Optional, string[])*: Specific `tag` of the request for logging and statistical purposes. -** *`terminate_after` (Optional, number)*: 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. -** *`timeout` (Optional, string | -1 | 0)*: Period each deletion request waits for active shards. -** *`version` (Optional, boolean)*: If `true`, returns the document version as part of a hit. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). -** *`wait_for_completion` (Optional, boolean)*: If `true`, the request blocks until the operation is complete. - +=== client.cat.fielddata [discrete] -=== delete_by_query_rethrottle -Throttle a delete by query operation. - -Change the number of requests per second for a particular delete 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. - -{ref}/docs-delete-by-query.html[Endpoint documentation] -[source,ts] ----- -client.deleteByQueryRethrottle({ task_id }) ----- +=== client.cat.health [discrete] -==== Arguments - -* *Request (object):* -** *`task_id` (string | number)*: The ID for the task. -** *`requests_per_second` (Optional, float)*: The throttle for this request in sub-requests per second. - +=== client.cat.help [discrete] -=== delete_script -Delete a script or search template. -Deletes a stored script or search template. - -{ref}/modules-scripting.html[Endpoint documentation] -[source,ts] ----- -client.deleteScript({ id }) ----- +=== client.cat.indices [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the stored script or search template. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.cat.master [discrete] -=== exists -Check a document. -Checks if a specified document exists. - -{ref}/docs-get.html[Endpoint documentation] -[source,ts] ----- -client.exists({ id, index }) ----- +=== client.cat.mlDataFrameAnalytics [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier of the document. -** *`index` (string)*: List of data streams, indices, and aliases. -Supports wildcards (`*`). -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`realtime` (Optional, boolean)*: If `true`, the request is real-time as opposed to near-real-time. -** *`refresh` (Optional, boolean)*: If `true`, Elasticsearch refreshes all shards involved in the delete by query after the request completes. -** *`routing` (Optional, string)*: Target the specified primary shard. -** *`_source` (Optional, boolean | string | string[])*: `true` or `false` to return the `_source` field or not, or a list of fields to return. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude in the response. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -** *`stored_fields` (Optional, string | string[])*: List of stored fields to return as part of a hit. -If no fields are specified, no stored fields are included in the response. -If this field is specified, the `_source` parameter defaults to false. -** *`version` (Optional, number)*: Explicit version number for concurrency control. -The specified version must match the current version of the document for the request to succeed. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type: `external`, `external_gte`. - +=== client.cat.mlDatafeeds [discrete] -=== exists_source -Check for a document source. -Checks if a document's `_source` is stored. - -{ref}/docs-get.html[Endpoint documentation] -[source,ts] ----- -client.existsSource({ id, index }) ----- +=== client.cat.mlJobs [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier of the document. -** *`index` (string)*: List of data streams, indices, and aliases. -Supports wildcards (`*`). -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`realtime` (Optional, boolean)*: If true, the request is real-time as opposed to near-real-time. -** *`refresh` (Optional, boolean)*: If `true`, Elasticsearch refreshes all shards involved in the delete by query after the request completes. -** *`routing` (Optional, string)*: Target the specified primary shard. -** *`_source` (Optional, boolean | string | string[])*: `true` or `false` to return the `_source` field or not, or a list of fields to return. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude in the response. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -** *`version` (Optional, number)*: Explicit version number for concurrency control. -The specified version must match the current version of the document for the request to succeed. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type: `external`, `external_gte`. - +=== client.cat.mlTrainedModels [discrete] -=== explain -Explain a document match result. -Returns information about why a specific document matches, or doesn’t match, a query. - -{ref}/search-explain.html[Endpoint documentation] -[source,ts] ----- -client.explain({ id, index }) ----- +=== client.cat.nodeattrs [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Defines the document ID. -** *`index` (string)*: Index names used to limit the request. -Only a single index name can be provided to this parameter. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Defines the search definition using the Query DSL. -** *`analyzer` (Optional, string)*: Analyzer to use for the query string. -This parameter can only be used when the `q` query string parameter is specified. -** *`analyze_wildcard` (Optional, boolean)*: If `true`, wildcard and prefix queries are analyzed. -** *`default_operator` (Optional, Enum("and" | "or"))*: The default operator for query string query: `AND` or `OR`. -** *`df` (Optional, string)*: Field to use as default where no field prefix is given in the query string. -** *`lenient` (Optional, boolean)*: If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`_source` (Optional, boolean | string | string[])*: True or false to return the `_source` field or not, or a list of fields to return. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude from the response. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -** *`stored_fields` (Optional, string | string[])*: A list of stored fields to return in the response. -** *`q` (Optional, string)*: Query in the Lucene query string syntax. - +=== client.cat.nodes [discrete] -=== field_caps -Get the field capabilities. - -Get information about the capabilities of fields among multiple indices. - -For data streams, the API returns field capabilities among the stream’s backing indices. -It returns runtime fields like any other field. -For example, a runtime field with a type of keyword is returned the same as any other field that belongs to the `keyword` family. - -{ref}/search-field-caps.html[Endpoint documentation] -[source,ts] ----- -client.fieldCaps({ ... }) ----- +=== client.cat.pendingTasks [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. Supports wildcards (*). To target all data streams and indices, omit this parameter or use * or _all. -** *`fields` (Optional, string | string[])*: List of fields to retrieve capabilities for. Wildcard (`*`) expressions are supported. -** *`index_filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Allows to filter indices if the provided query rewrites to match_none on every shard. -** *`runtime_mappings` (Optional, Record)*: Defines ad-hoc runtime fields in the request similar to the way it is done in search requests. -These fields exist only as part of the query and take precedence over fields defined with the same name in the index mappings. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. Supports a list of values, such as `open,hidden`. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, missing or closed indices are not included in the response. -** *`include_unmapped` (Optional, boolean)*: If true, unmapped fields are included in the response. -** *`filters` (Optional, string)*: An optional set of filters: can include +metadata,-metadata,-nested,-multifield,-parent -** *`types` (Optional, string[])*: Only return results for fields that have one of the types in the list -** *`include_empty_fields` (Optional, boolean)*: If false, empty fields are not included in the response. - +=== client.cat.plugins [discrete] -=== get -Get a document by its ID. -Retrieves the document with the specified ID from an index. - -{ref}/docs-get.html[Endpoint documentation] -[source,ts] ----- -client.get({ id, index }) ----- +=== client.cat.recovery [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Unique identifier of the document. -** *`index` (string)*: Name of the index that contains the document. -** *`force_synthetic_source` (Optional, boolean)*: Should this request force synthetic _source? -Use this to test if the mapping supports synthetic _source and to get a sense of the worst case performance. -Fetches with this enabled will be slower the enabling synthetic source natively in the index. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. Random by default. -** *`realtime` (Optional, boolean)*: If `true`, the request is real-time as opposed to near-real-time. -** *`refresh` (Optional, boolean)*: If true, Elasticsearch refreshes the affected shards to make this operation visible to search. If false, do nothing with refreshes. -** *`routing` (Optional, string)*: Target the specified primary shard. -** *`_source` (Optional, boolean | string | string[])*: True or false to return the _source field or not, or a list of fields to return. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude in the response. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -** *`stored_fields` (Optional, string | string[])*: List of stored fields to return as part of a hit. -If no fields are specified, no stored fields are included in the response. -If this field is specified, the `_source` parameter defaults to false. -** *`version` (Optional, number)*: Explicit version number for concurrency control. The specified version must match the current version of the document for the request to succeed. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type: internal, external, external_gte. - +=== client.cat.repositories [discrete] -=== get_script -Get a script or search template. -Retrieves a stored script or search template. - -{ref}/modules-scripting.html[Endpoint documentation] -[source,ts] ----- -client.getScript({ id }) ----- +=== client.cat.segments [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the stored script or search template. -** *`master_timeout` (Optional, string | -1 | 0)*: Specify timeout for connection to master - +=== client.cat.shards [discrete] -=== get_script_context -Get script contexts. - -Get a list of supported script contexts and their methods. - -{painless}/painless-contexts.html[Endpoint documentation] -[source,ts] ----- -client.getScriptContext() ----- - +=== client.cat.snapshots [discrete] -=== get_script_languages -Get script languages. - -Get a list of available script types, languages, and contexts. - -{ref}/modules-scripting.html[Endpoint documentation] -[source,ts] ----- -client.getScriptLanguages() ----- - +=== client.cat.tasks [discrete] -=== get_source -Get a document's source. -Returns the source of a document. - -{ref}/docs-get.html[Endpoint documentation] -[source,ts] ----- -client.getSource({ id, index }) ----- +=== client.cat.templates [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Unique identifier of the document. -** *`index` (string)*: Name of the index that contains the document. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. Random by default. -** *`realtime` (Optional, boolean)*: Boolean) If true, the request is real-time as opposed to near-real-time. -** *`refresh` (Optional, boolean)*: If true, Elasticsearch refreshes the affected shards to make this operation visible to search. If false, do nothing with refreshes. -** *`routing` (Optional, string)*: Target the specified primary shard. -** *`_source` (Optional, boolean | string | string[])*: True or false to return the _source field or not, or a list of fields to return. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude in the response. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -** *`stored_fields` (Optional, string | string[])* -** *`version` (Optional, number)*: Explicit version number for concurrency control. The specified version must match the current version of the document for the request to succeed. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type: internal, external, external_gte. - +=== client.cat.threadPool [discrete] -=== health_report -Returns the health of the cluster. - -{ref}/health-api.html[Endpoint documentation] -[source,ts] ----- -client.healthReport({ ... }) ----- +=== client.cat.transforms [discrete] -==== Arguments - -* *Request (object):* -** *`feature` (Optional, string | string[])*: A feature of the cluster, as returned by the top-level health report API. -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout. -** *`verbose` (Optional, boolean)*: Opt-in for more information about the health of the system. -** *`size` (Optional, number)*: Limit the number of affected resources the health report API returns. - +=== client.ccr.deleteAutoFollowPattern [discrete] -=== index -Index a document. -Adds a JSON document to the specified data stream or index and makes it searchable. -If the target is an index and the document already exists, the request updates the document and increments its version. - -{ref}/docs-index_.html[Endpoint documentation] -[source,ts] ----- -client.index({ index }) ----- +=== client.ccr.follow [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Name of the data stream or index to target. -** *`id` (Optional, string)*: Unique identifier for the document. -** *`document` (Optional, object)*: A document. -** *`if_primary_term` (Optional, number)*: Only perform the operation if the document has this primary term. -** *`if_seq_no` (Optional, number)*: Only perform the operation if the document has this sequence number. -** *`op_type` (Optional, Enum("index" | "create"))*: Set to create to only index the document if it does not already exist (put if absent). -If a document with the specified `_id` already exists, the indexing operation will fail. -Same as using the `/_create` endpoint. -Valid values: `index`, `create`. -If document id is specified, it defaults to `index`. -Otherwise, it defaults to `create`. -** *`pipeline` (Optional, string)*: ID of the pipeline to use to preprocess incoming documents. -If the index has a default ingest pipeline specified, then setting the value to `_none` disables the default ingest pipeline for this request. -If a final pipeline is configured it will always run, regardless of the value of this parameter. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true`, Elasticsearch refreshes 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` do nothing with refreshes. -Valid values: `true`, `false`, `wait_for`. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`timeout` (Optional, string | -1 | 0)*: Period the request waits for the following operations: automatic index creation, dynamic mapping updates, waiting for active shards. -** *`version` (Optional, number)*: Explicit version number for concurrency control. -The specified version must match the current version of the document for the request to succeed. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type: `external`, `external_gte`. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). -** *`require_alias` (Optional, boolean)*: If `true`, the destination must be an index alias. - +=== client.ccr.followInfo [discrete] -=== info -Get cluster info. -Returns basic information about the cluster. - -{ref}/index.html[Endpoint documentation] -[source,ts] ----- -client.info() ----- - +=== client.ccr.followStats [discrete] -=== knn_search -Run a knn search. - -NOTE: The kNN search API has been replaced by the `knn` option in the search API. - -Perform a k-nearest neighbor (kNN) search on a dense_vector field and return the matching documents. -Given a query vector, the API finds the k closest vectors and returns those documents as search hits. - -Elasticsearch uses the HNSW algorithm to support efficient kNN search. -Like most kNN algorithms, HNSW is an approximate method that sacrifices result accuracy for improved search speed. -This means the results returned are not always the true k closest neighbors. - -The kNN search API supports restricting the search using a filter. -The search will return the top k documents that also match the filter query. - -{ref}/search-search.html[Endpoint documentation] -[source,ts] ----- -client.knnSearch({ index, knn }) ----- +=== client.ccr.forgetFollower [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: A list of index names to search; -use `_all` or to perform the operation on all indices -** *`knn` ({ field, query_vector, k, num_candidates })*: kNN query to execute -** *`_source` (Optional, boolean | { excludes, includes })*: Indicates which source fields are returned for matching documents. These -fields are returned in the hits._source property of the search response. -** *`docvalue_fields` (Optional, { field, format, include_unmapped }[])*: The request returns doc values for field names matching these patterns -in the hits.fields property of the response. Accepts wildcard (*) patterns. -** *`stored_fields` (Optional, string | string[])*: List of stored fields to return as part of a hit. If no fields are specified, -no stored fields are included in the response. If this field is specified, the _source -parameter defaults to false. You can pass _source: true to return both source fields -and stored fields in the search response. -** *`fields` (Optional, string | string[])*: The request returns values for field names matching these patterns -in the hits.fields property of the response. Accepts wildcard (*) patterns. -** *`filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type } | { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type }[])*: Query to filter the documents that can match. The kNN search will return the top -`k` documents that also match this filter. The value can be a single query or a -list of queries. If `filter` isn't provided, all documents are allowed to match. -** *`routing` (Optional, string)*: A list of specific routing values - +=== client.ccr.getAutoFollowPattern [discrete] -=== mget -Get multiple documents. - -Get multiple JSON documents by ID from one or more indices. -If you specify an index in the request URI, you only need to specify the document IDs in the request body. -To ensure fast responses, this multi get (mget) API responds with partial results if one or more shards fail. - -{ref}/docs-multi-get.html[Endpoint documentation] -[source,ts] ----- -client.mget({ ... }) ----- +=== client.ccr.pauseAutoFollowPattern [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string)*: Name of the index to retrieve documents from when `ids` are specified, or when a document in the `docs` array does not specify an index. -** *`docs` (Optional, { _id, _index, routing, _source, stored_fields, version, version_type }[])*: The documents you want to retrieve. Required if no index is specified in the request URI. -** *`ids` (Optional, string | string[])*: The IDs of the documents you want to retrieve. Allowed when the index is specified in the request URI. -** *`force_synthetic_source` (Optional, boolean)*: Should this request force synthetic _source? -Use this to test if the mapping supports synthetic _source and to get a sense of the worst case performance. -Fetches with this enabled will be slower the enabling synthetic source natively in the index. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. Random by default. -** *`realtime` (Optional, boolean)*: If `true`, the request is real-time as opposed to near-real-time. -** *`refresh` (Optional, boolean)*: If `true`, the request refreshes relevant shards before retrieving documents. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`_source` (Optional, boolean | string | string[])*: True or false to return the `_source` field or not, or a list of fields to return. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude from the response. -You can also use this parameter to exclude fields from the subset specified in `_source_includes` query parameter. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -If this parameter is specified, only these source fields are returned. You can exclude fields from this subset using the `_source_excludes` query parameter. -If the `_source` parameter is `false`, this parameter is ignored. -** *`stored_fields` (Optional, string | string[])*: If `true`, retrieves the document fields stored in the index rather than the document `_source`. - +=== client.ccr.pauseFollow [discrete] -=== msearch -Run multiple searches. - -The format of the request is similar to the bulk API format and makes use of the newline delimited JSON (NDJSON) format. -The structure is as follows: - -``` -header\n -body\n -header\n -body\n -``` - -This structure is specifically optimized to reduce parsing if a specific search ends up redirected to another node. - -IMPORTANT: The final line of data must end with a newline character `\n`. -Each newline character may be preceded by a carriage return `\r`. -When sending requests to this endpoint the `Content-Type` header should be set to `application/x-ndjson`. - -{ref}/search-multi-search.html[Endpoint documentation] -[source,ts] ----- -client.msearch({ ... }) ----- +=== client.ccr.putAutoFollowPattern [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and index aliases to search. -** *`searches` (Optional, { allow_no_indices, expand_wildcards, ignore_unavailable, index, preference, request_cache, routing, search_type, ccs_minimize_roundtrips, allow_partial_search_results, ignore_throttled } | { aggregations, collapse, query, explain, ext, stored_fields, docvalue_fields, knn, from, highlight, indices_boost, min_score, post_filter, profile, rescore, script_fields, search_after, size, sort, _source, fields, terminate_after, stats, timeout, track_scores, track_total_hits, version, runtime_mappings, seq_no_primary_term, pit, suggest }[])* -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`ccs_minimize_roundtrips` (Optional, boolean)*: If true, network roundtrips between the coordinating node and remote clusters are minimized for cross-cluster search requests. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of index that wildcard expressions can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. -** *`ignore_throttled` (Optional, boolean)*: If true, concrete, expanded or aliased indices are ignored when frozen. -** *`ignore_unavailable` (Optional, boolean)*: If true, missing or closed indices are not included in the response. -** *`include_named_queries_score` (Optional, boolean)*: Indicates whether hit.matched_queries should be rendered as a map that includes -the name of the matched query associated with its score (true) -or as an array containing the name of the matched queries (false) -This functionality reruns each named query on every hit in a search response. -Typically, this adds a small overhead to a request. -However, using computationally expensive named queries on a large number of hits may add significant overhead. -** *`max_concurrent_searches` (Optional, number)*: Maximum number of concurrent searches the multi search API can execute. -** *`max_concurrent_shard_requests` (Optional, number)*: Maximum number of concurrent shard requests that each sub-search request executes per node. -** *`pre_filter_shard_size` (Optional, number)*: Defines a threshold that enforces a pre-filter roundtrip to prefilter search shards based on query rewriting if the number of shards the search request expands to exceeds the threshold. This filter roundtrip can limit the number of shards significantly if for instance a shard can not match any documents based on its rewrite method i.e., if date filters are mandatory to match but the shard bounds and the query are disjoint. -** *`rest_total_hits_as_int` (Optional, boolean)*: If true, hits.total are returned as an integer in the response. Defaults to false, which returns an object. -** *`routing` (Optional, string)*: Custom routing value used to route search operations to a specific shard. -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: Indicates whether global term and document frequencies should be used when scoring returned documents. -** *`typed_keys` (Optional, boolean)*: Specifies whether aggregation and suggester names should be prefixed by their respective types in the response. - +=== client.ccr.resumeAutoFollowPattern [discrete] -=== msearch_template -Run multiple templated searches. - -{ref}/search-multi-search.html[Endpoint documentation] -[source,ts] ----- -client.msearchTemplate({ ... }) ----- +=== client.ccr.resumeFollow [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases to search. -Supports wildcards (`*`). -To search all data streams and indices, omit this parameter or use `*`. -** *`search_templates` (Optional, { allow_no_indices, expand_wildcards, ignore_unavailable, index, preference, request_cache, routing, search_type, ccs_minimize_roundtrips, allow_partial_search_results, ignore_throttled } | { aggregations, collapse, query, explain, ext, stored_fields, docvalue_fields, knn, from, highlight, indices_boost, min_score, post_filter, profile, rescore, script_fields, search_after, size, sort, _source, fields, terminate_after, stats, timeout, track_scores, track_total_hits, version, runtime_mappings, seq_no_primary_term, pit, suggest }[])* -** *`ccs_minimize_roundtrips` (Optional, boolean)*: If `true`, network round-trips are minimized for cross-cluster search requests. -** *`max_concurrent_searches` (Optional, number)*: Maximum number of concurrent searches the API can run. -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: The type of the search operation. -Available options: `query_then_fetch`, `dfs_query_then_fetch`. -** *`rest_total_hits_as_int` (Optional, boolean)*: If `true`, the response returns `hits.total` as an integer. -If `false`, it returns `hits.total` as an object. -** *`typed_keys` (Optional, boolean)*: If `true`, the response prefixes aggregation and suggester names with their respective types. - +=== client.ccr.stats [discrete] -=== mtermvectors -Get multiple term vectors. - -You can specify existing documents by index and ID or provide artificial documents in the body of the request. -You can specify the index in the request body or request URI. -The response contains a `docs` array with all the fetched termvectors. -Each element has the structure provided by the termvectors API. - -{ref}/docs-multi-termvectors.html[Endpoint documentation] -[source,ts] ----- -client.mtermvectors({ ... }) ----- +=== client.ccr.unfollow [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string)*: Name of the index that contains the documents. -** *`docs` (Optional, { _id, _index, routing, _source, stored_fields, version, version_type }[])*: Array of existing or artificial documents. -** *`ids` (Optional, string[])*: Simplified syntax to specify documents by their ID if they're in the same index. -** *`fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in the statistics. -Used as the default list unless a specific field list is provided in the `completion_fields` or `fielddata_fields` parameters. -** *`field_statistics` (Optional, boolean)*: If `true`, the response includes the document count, sum of document frequencies, and sum of total term frequencies. -** *`offsets` (Optional, boolean)*: If `true`, the response includes term offsets. -** *`payloads` (Optional, boolean)*: If `true`, the response includes term payloads. -** *`positions` (Optional, boolean)*: If `true`, the response includes term positions. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`realtime` (Optional, boolean)*: If true, the request is real-time as opposed to near-real-time. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`term_statistics` (Optional, boolean)*: If true, the response includes term frequency and document frequency. -** *`version` (Optional, number)*: If `true`, returns the document version as part of a hit. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type. - +=== client.clearScroll [discrete] -=== open_point_in_time -Open a point in time. - -A search request by default runs against the most recent visible data of the target indices, -which is called point in time. Elasticsearch pit (point in time) is a lightweight view into the -state of the data as it existed when initiated. In some cases, it’s preferred to perform multiple -search requests using the same point in time. For example, if refreshes happen between -`search_after` requests, then the results of those requests might not be consistent as changes happening -between searches are only visible to the more recent point in time. - -A point in time must be opened explicitly before being used in search requests. -The `keep_alive` parameter tells Elasticsearch how long it should persist. - -{ref}/point-in-time-api.html[Endpoint documentation] -[source,ts] ----- -client.openPointInTime({ index, keep_alive }) ----- +=== client.closePointInTime [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: A list of index names to open point in time; use `_all` or empty string to perform the operation on all indices -** *`keep_alive` (string | -1 | 0)*: Extends the time to live of the corresponding point in time. -** *`index_filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Allows to filter indices if the provided query rewrites to `match_none` on every shard. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. Valid values are: `all`, `open`, `closed`, `hidden`, `none`. - +=== client.cluster.allocationExplain [discrete] -=== ping -Ping the cluster. -Returns whether the cluster is running. - -{ref}/index.html[Endpoint documentation] -[source,ts] ----- -client.ping() ----- - +=== client.cluster.deleteComponentTemplate [discrete] -=== put_script -Create or update a script or search template. -Creates or updates a stored script or search template. - -{ref}/modules-scripting.html[Endpoint documentation] -[source,ts] ----- -client.putScript({ id, script }) ----- +=== client.cluster.deleteVotingConfigExclusions [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the stored script or search template. -Must be unique within the cluster. -** *`script` ({ lang, options, source })*: Contains the script or search template, its parameters, and its language. -** *`context` (Optional, string)*: Context in which the script or search template should run. -To prevent errors, the API immediately compiles the script or template in this context. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.cluster.existsComponentTemplate [discrete] -=== rank_eval -Evaluate ranked search results. - -Evaluate the quality of ranked search results over a set of typical search queries. - -{ref}/search-rank-eval.html[Endpoint documentation] -[source,ts] ----- -client.rankEval({ requests }) ----- +=== client.cluster.getComponentTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`requests` ({ id, request, ratings, template_id, params }[])*: A set of typical search requests, together with their provided ratings. -** *`index` (Optional, string | string[])*: List of data streams, indices, and index aliases used to limit the request. Wildcard (`*`) expressions are supported. -To target all data streams and indices in a cluster, omit this parameter or use `_all` or `*`. -** *`metric` (Optional, { precision, recall, mean_reciprocal_rank, dcg, expected_reciprocal_rank })*: Definition of the evaluation metric to calculate. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, missing or closed indices are not included in the response. -** *`search_type` (Optional, string)*: Search operation type - +=== client.cluster.getSettings [discrete] -=== reindex -Reindex documents. -Copies documents from a source to a destination. The source can be any existing index, alias, or data stream. The destination must differ from the source. For example, you cannot reindex a data stream into itself. - -{ref}/docs-reindex.html[Endpoint documentation] -[source,ts] ----- -client.reindex({ dest, source }) ----- +=== client.cluster.health [discrete] -==== Arguments - -* *Request (object):* -** *`dest` ({ index, op_type, pipeline, routing, version_type })*: The destination you are copying to. -** *`source` ({ index, query, remote, size, slice, sort, _source, runtime_mappings })*: The source you are copying from. -** *`conflicts` (Optional, Enum("abort" | "proceed"))*: Set to proceed to continue reindexing even if there are conflicts. -** *`max_docs` (Optional, number)*: The maximum number of documents to reindex. -** *`script` (Optional, { source, id, params, lang, options })*: The script to run to update the document source or metadata when reindexing. -** *`size` (Optional, number)* -** *`refresh` (Optional, boolean)*: If `true`, the request refreshes affected shards to make this operation visible to search. -** *`requests_per_second` (Optional, float)*: The throttle for this request in sub-requests per second. -Defaults to no throttle. -** *`scroll` (Optional, string | -1 | 0)*: Specifies how long a consistent view of the index should be maintained for scrolled search. -** *`slices` (Optional, number | Enum("auto"))*: The number of slices this task should be divided into. -Defaults to 1 slice, meaning the task isn’t sliced into subtasks. -** *`timeout` (Optional, string | -1 | 0)*: Period each indexing waits for automatic index creation, dynamic mapping updates, and waiting for active shards. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). -** *`wait_for_completion` (Optional, boolean)*: If `true`, the request blocks until the operation is complete. -** *`require_alias` (Optional, boolean)*: If `true`, the destination must be an index alias. - +=== client.cluster.info [discrete] -=== reindex_rethrottle -Throttle a reindex operation. - -Change the number of requests per second for a particular reindex operation. - -{ref}/docs-reindex.html[Endpoint documentation] -[source,ts] ----- -client.reindexRethrottle({ task_id }) ----- +=== client.cluster.pendingTasks [discrete] -==== Arguments - -* *Request (object):* -** *`task_id` (string)*: Identifier for the task. -** *`requests_per_second` (Optional, float)*: The throttle for this request in sub-requests per second. - +=== client.cluster.postVotingConfigExclusions [discrete] -=== render_search_template -Render a search template. - -Render a search template as a search request body. - -{ref}/render-search-template-api.html[Endpoint documentation] -[source,ts] ----- -client.renderSearchTemplate({ ... }) ----- +=== client.cluster.putComponentTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: ID of the search template to render. -If no `source` is specified, this or the `id` request body parameter is required. -** *`file` (Optional, string)* -** *`params` (Optional, Record)*: Key-value pairs used to replace Mustache variables in the template. -The key is the variable name. -The value is the variable value. -** *`source` (Optional, string)*: An inline search template. -Supports the same parameters as the search API's request body. -These parameters also support Mustache variables. -If no `id` or `` is specified, this parameter is required. - +=== client.cluster.putSettings [discrete] -=== scripts_painless_execute -Run a script. -Runs a script and returns a result. - -{painless}/painless-execute-api.html[Endpoint documentation] -[source,ts] ----- -client.scriptsPainlessExecute({ ... }) ----- +=== client.cluster.remoteInfo [discrete] -==== Arguments - -* *Request (object):* -** *`context` (Optional, string)*: The context that the script should run in. -** *`context_setup` (Optional, { document, index, query })*: Additional parameters for the `context`. -** *`script` (Optional, { source, id, params, lang, options })*: The Painless script to execute. - +=== client.cluster.reroute [discrete] -=== scroll -Run a scrolling search. - -IMPORTANT: The scroll API is no longer recommend for deep pagination. If you need to preserve the index state while paging through more than 10,000 hits, use the `search_after` parameter with a point in time (PIT). - -The scroll API gets large sets of results from a single scrolling search request. -To get the necessary scroll ID, submit a search API request that includes an argument for the `scroll` query parameter. -The `scroll` parameter indicates how long Elasticsearch should retain the search context for the request. -The search response returns a scroll ID in the `_scroll_id` response body parameter. -You can then use the scroll ID with the scroll API to retrieve the next batch of results for the request. -If the Elasticsearch security features are enabled, the access to the results of a specific scroll ID is restricted to the user or API key that submitted the search. - -You can also use the scroll API to specify a new scroll parameter that extends or shortens the retention period for the search context. - -IMPORTANT: Results from a scrolling search reflect the state of the index at the time of the initial search request. Subsequent indexing or document changes only affect later search and scroll requests. - -{ref}/search-request-body.html[Endpoint documentation] -[source,ts] ----- -client.scroll({ scroll_id }) ----- +=== client.cluster.state [discrete] -==== Arguments - -* *Request (object):* -** *`scroll_id` (string)*: Scroll ID of the search. -** *`scroll` (Optional, string | -1 | 0)*: Period to retain the search context for scrolling. -** *`rest_total_hits_as_int` (Optional, boolean)*: If true, the API response’s hit.total property is returned as an integer. If false, the API response’s hit.total property is returned as an object. - +=== client.cluster.stats [discrete] -=== search -Run a search. - -Get search hits that match the query defined in the request. -You can provide search queries using the `q` query string parameter or the request body. -If both are specified, only the query parameter is used. - -{ref}/search-search.html[Endpoint documentation] -[source,ts] ----- -client.search({ ... }) ----- +=== client.connector.checkIn [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases to search. -Supports wildcards (`*`). -To search all data streams and indices, omit this parameter or use `*` or `_all`. -** *`aggregations` (Optional, Record)*: Defines the aggregations that are run as part of the search request. -** *`collapse` (Optional, { field, inner_hits, max_concurrent_group_searches, collapse })*: Collapses search results the values of the specified field. -** *`explain` (Optional, boolean)*: If true, returns detailed information about score computation as part of a hit. -** *`ext` (Optional, Record)*: Configuration of search extensions defined by Elasticsearch plugins. -** *`from` (Optional, number)*: Starting document offset. -Needs to be non-negative. -By default, you cannot page through more than 10,000 hits using the `from` and `size` parameters. -To page through more hits, use the `search_after` parameter. -** *`highlight` (Optional, { encoder, fields })*: Specifies the highlighter to use for retrieving highlighted snippets from one or more fields in your search results. -** *`track_total_hits` (Optional, boolean | number)*: Number of hits matching the query to count accurately. -If `true`, the exact number of hits is returned at the cost of some performance. -If `false`, the response does not include the total number of hits matching the query. -** *`indices_boost` (Optional, Record[])*: Boosts the _score of documents from specified indices. -** *`docvalue_fields` (Optional, { field, format, include_unmapped }[])*: Array of wildcard (`*`) patterns. -The request returns doc values for field names matching these patterns in the `hits.fields` property of the response. -** *`knn` (Optional, { field, query_vector, query_vector_builder, k, num_candidates, boost, filter, similarity, inner_hits } | { field, query_vector, query_vector_builder, k, num_candidates, boost, filter, similarity, inner_hits }[])*: Defines the approximate kNN search to run. -** *`rank` (Optional, { rrf })*: Defines the Reciprocal Rank Fusion (RRF) to use. -** *`min_score` (Optional, number)*: Minimum `_score` for matching documents. -Documents with a lower `_score` are not included in the search results. -** *`post_filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Use the `post_filter` parameter to filter search results. -The search hits are filtered after the aggregations are calculated. -A post filter has no impact on the aggregation results. -** *`profile` (Optional, boolean)*: Set to `true` to return detailed timing information about the execution of individual components in a search request. -NOTE: This is a debugging tool and adds significant overhead to search execution. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Defines the search definition using the Query DSL. -** *`rescore` (Optional, { window_size, query, learning_to_rank } | { window_size, query, learning_to_rank }[])*: Can be used to improve precision by reordering just the top (for example 100 - 500) documents returned by the `query` and `post_filter` phases. -** *`retriever` (Optional, { standard, knn, rrf, text_similarity_reranker, rule })*: A retriever is a specification to describe top documents returned from a search. A retriever replaces other elements of the search API that also return top documents such as query and knn. -** *`script_fields` (Optional, Record)*: Retrieve a script evaluation (based on different fields) for each hit. -** *`search_after` (Optional, number | number | string | boolean | null | User-defined value[])*: Used to retrieve the next page of hits using a set of sort values from the previous page. -** *`size` (Optional, number)*: The number of hits to return. -By default, you cannot page through more than 10,000 hits using the `from` and `size` parameters. -To page through more hits, use the `search_after` parameter. -** *`slice` (Optional, { field, id, max })*: Can be used to split a scrolled search into multiple slices that can be consumed independently. -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])*: A list of : pairs. -** *`_source` (Optional, boolean | { excludes, includes })*: Indicates which source fields are returned for matching documents. -These fields are returned in the hits._source property of the search response. -** *`fields` (Optional, { field, format, include_unmapped }[])*: Array of wildcard (`*`) patterns. -The request returns values for field names matching these patterns in the `hits.fields` property of the response. -** *`suggest` (Optional, { text })*: Defines a suggester that provides similar looking terms based on a provided text. -** *`terminate_after` (Optional, number)*: 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. -If set to `0` (default), the query does not terminate early. -** *`timeout` (Optional, string)*: Specifies the period of time to wait for a response from each shard. -If no response is received before the timeout expires, the request fails and returns an error. -Defaults to no timeout. -** *`track_scores` (Optional, boolean)*: If true, calculate and return document scores, even if the scores are not used for sorting. -** *`version` (Optional, boolean)*: If true, returns document version as part of a hit. -** *`seq_no_primary_term` (Optional, boolean)*: If `true`, returns sequence number and primary term of the last modification of each hit. -** *`stored_fields` (Optional, string | string[])*: List of stored fields to return as part of a hit. -If no fields are specified, no stored fields are included in the response. -If this field is specified, the `_source` parameter defaults to `false`. -You can pass `_source: true` to return both source fields and stored fields in the search response. -** *`pit` (Optional, { id, keep_alive })*: Limits the search to a point in time (PIT). -If you provide a PIT, you cannot specify an `` in the request path. -** *`runtime_mappings` (Optional, Record)*: Defines one or more runtime fields in the search request. -These fields take precedence over mapped fields with the same name. -** *`stats` (Optional, string[])*: Stats groups to associate with the search. -Each group maintains a statistics aggregation for its associated searches. -You can retrieve these stats using the indices stats API. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`allow_partial_search_results` (Optional, boolean)*: If true, returns partial results if there are shard request timeouts or shard failures. If false, returns an error with no partial results. -** *`analyzer` (Optional, string)*: Analyzer to use for the query string. -This parameter can only be used when the q query string parameter is specified. -** *`analyze_wildcard` (Optional, boolean)*: If true, wildcard and prefix queries are analyzed. -This parameter can only be used when the q query string parameter is specified. -** *`batched_reduce_size` (Optional, number)*: The number of shard results that should be reduced at once on the coordinating node. -This value should be used as a protection mechanism to reduce the memory overhead per search request if the potential number of shards in the request can be large. -** *`ccs_minimize_roundtrips` (Optional, boolean)*: If true, network round-trips between the coordinating node and the remote clusters are minimized when executing cross-cluster search (CCS) requests. -** *`default_operator` (Optional, Enum("and" | "or"))*: The default operator for query string query: AND or OR. -This parameter can only be used when the `q` query string parameter is specified. -** *`df` (Optional, string)*: Field to use as default where no field prefix is given in the query string. -This parameter can only be used when the q query string parameter is specified. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -** *`ignore_throttled` (Optional, boolean)*: If `true`, concrete, expanded or aliased indices will be ignored when frozen. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`include_named_queries_score` (Optional, boolean)*: Indicates whether hit.matched_queries should be rendered as a map that includes -the name of the matched query associated with its score (true) -or as an array containing the name of the matched queries (false) -This functionality reruns each named query on every hit in a search response. -Typically, this adds a small overhead to a request. -However, using computationally expensive named queries on a large number of hits may add significant overhead. -** *`lenient` (Optional, boolean)*: If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored. -This parameter can only be used when the `q` query string parameter is specified. -** *`max_concurrent_shard_requests` (Optional, number)*: Defines the number of concurrent shard requests per node this search executes concurrently. -This value should be used to limit the impact of the search on the cluster in order to limit the number of concurrent shard requests. -** *`preference` (Optional, string)*: Nodes and shards used for the search. -By default, Elasticsearch selects from eligible nodes and shards using adaptive replica selection, accounting for allocation awareness. Valid values are: -`_only_local` to run the search only on shards on the local node; -`_local` to, if possible, run the search on shards on the local node, or if not, select shards using the default method; -`_only_nodes:,` to run the search on only the specified nodes IDs, where, if suitable shards exist on more than one selected node, use shards on those nodes using the default method, or if none of the specified nodes are available, select shards from any available node using the default method; -`_prefer_nodes:,` to if possible, run the search on the specified nodes IDs, or if not, select shards using the default method; -`_shards:,` to run the search only on the specified shards; -`` (any string that does not start with `_`) to route searches with the same `` to the same shards in the same order. -** *`pre_filter_shard_size` (Optional, number)*: Defines a threshold that enforces a pre-filter roundtrip to prefilter search shards based on query rewriting if the number of shards the search request expands to exceeds the threshold. -This filter roundtrip can limit the number of shards significantly if for instance a shard can not match any documents based on its rewrite method (if date filters are mandatory to match but the shard bounds and the query are disjoint). -When unspecified, the pre-filter phase is executed if any of these conditions is met: -the request targets more than 128 shards; -the request targets one or more read-only index; -the primary sort of the query targets an indexed field. -** *`request_cache` (Optional, boolean)*: If `true`, the caching of search results is enabled for requests where `size` is `0`. -Defaults to index level settings. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`scroll` (Optional, string | -1 | 0)*: Period to retain the search context for scrolling. See Scroll search results. -By default, this value cannot exceed `1d` (24 hours). -You can change this limit using the `search.max_keep_alive` cluster-level setting. -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: How distributed term frequencies are calculated for relevance scoring. -** *`suggest_field` (Optional, string)*: Specifies which field to use for suggestions. -** *`suggest_mode` (Optional, Enum("missing" | "popular" | "always"))*: Specifies the suggest mode. -This parameter can only be used when the `suggest_field` and `suggest_text` query string parameters are specified. -** *`suggest_size` (Optional, number)*: Number of suggestions to return. -This parameter can only be used when the `suggest_field` and `suggest_text` query string parameters are specified. -** *`suggest_text` (Optional, string)*: The source text for which the suggestions should be returned. -This parameter can only be used when the `suggest_field` and `suggest_text` query string parameters are specified. -** *`typed_keys` (Optional, boolean)*: If `true`, aggregation and suggester names are be prefixed by their respective types in the response. -** *`rest_total_hits_as_int` (Optional, boolean)*: Indicates whether `hits.total` should be rendered as an integer or an object in the rest search response. -** *`_source_excludes` (Optional, string | string[])*: A list of source fields to exclude from the response. -You can also use this parameter to exclude fields from the subset specified in `_source_includes` query parameter. -If the `_source` parameter is `false`, this parameter is ignored. -** *`_source_includes` (Optional, string | string[])*: A list of source fields to include in the response. -If this parameter is specified, only these source fields are returned. -You can exclude fields from this subset using the `_source_excludes` query parameter. -If the `_source` parameter is `false`, this parameter is ignored. -** *`q` (Optional, string)*: Query in the Lucene query string syntax using query parameter search. -Query parameter searches do not support the full Elasticsearch Query DSL but are handy for testing. -** *`force_synthetic_source` (Optional, boolean)*: Should this request force synthetic _source? -Use this to test if the mapping supports synthetic _source and to get a sense of the worst case performance. -Fetches with this enabled will be slower the enabling synthetic source natively in the index. - +=== client.connector.delete [discrete] -=== search_mvt -Search a vector tile. - -Search a vector tile for geospatial values. - -{ref}/search-vector-tile-api.html[Endpoint documentation] -[source,ts] ----- -client.searchMvt({ index, field, zoom, x, y }) ----- +=== client.connector.get [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams, indices, or aliases to search -** *`field` (string)*: Field containing geospatial data to return -** *`zoom` (number)*: Zoom level for the vector tile to search -** *`x` (number)*: X coordinate for the vector tile to search -** *`y` (number)*: Y coordinate for the vector tile to search -** *`aggs` (Optional, Record)*: Sub-aggregations for the geotile_grid. - -Supports the following aggregation types: -- avg -- cardinality -- max -- min -- sum -** *`buffer` (Optional, number)*: Size, in pixels, of a clipping buffer outside the tile. This allows renderers -to avoid outline artifacts from geometries that extend past the extent of the tile. -** *`exact_bounds` (Optional, boolean)*: If false, the meta layer’s feature is the bounding box of the tile. -If true, the meta layer’s feature is a bounding box resulting from a -geo_bounds aggregation. The aggregation runs on values that intersect -the // tile with wrap_longitude set to false. The resulting -bounding box may be larger than the vector tile. -** *`extent` (Optional, number)*: Size, in pixels, of a side of the tile. Vector tiles are square with equal sides. -** *`fields` (Optional, string | string[])*: Fields to return in the `hits` layer. Supports wildcards (`*`). -This parameter does not support fields with array values. Fields with array -values may return inconsistent results. -** *`grid_agg` (Optional, Enum("geotile" | "geohex"))*: Aggregation used to create a grid for the `field`. -** *`grid_precision` (Optional, number)*: Additional zoom levels available through the aggs layer. For example, if is 7 -and grid_precision is 8, you can zoom in up to level 15. Accepts 0-8. If 0, results -don’t include the aggs layer. -** *`grid_type` (Optional, Enum("grid" | "point" | "centroid"))*: Determines the geometry type for features in the aggs layer. In the aggs layer, -each feature represents a geotile_grid cell. If 'grid' each feature is a Polygon -of the cells bounding box. If 'point' each feature is a Point that is the centroid -of the cell. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Query DSL used to filter documents for the search. -** *`runtime_mappings` (Optional, Record)*: Defines one or more runtime fields in the search request. These fields take -precedence over mapped fields with the same name. -** *`size` (Optional, number)*: Maximum number of features to return in the hits layer. Accepts 0-10000. -If 0, results don’t include the hits layer. -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])*: Sorts features in the hits layer. By default, the API calculates a bounding -box for each feature. It sorts features based on this box’s diagonal length, -from longest to shortest. -** *`track_total_hits` (Optional, boolean | number)*: Number of hits matching the query to count accurately. If `true`, the exact number -of hits is returned at the cost of some performance. If `false`, the response does -not include the total number of hits matching the query. -** *`with_labels` (Optional, boolean)*: If `true`, the hits and aggs layers will contain additional point features representing -suggested label positions for the original features. - +=== client.connector.list [discrete] -=== search_shards -Get the search shards. - -Get the indices and shards that a search request would be run against. -This information can be useful for working out issues or planning optimizations with routing and shard preferences. -When filtered aliases are used, the filter is returned as part of the indices section. - -{ref}/search-shards.html[Endpoint documentation] -[source,ts] ----- -client.searchShards({ ... }) ----- +=== client.connector.post [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: Returns the indices and shards that a search request would be executed against. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. - +=== client.connector.put [discrete] -=== search_template -Run a search with a search template. - -{ref}/search-template.html[Endpoint documentation] -[source,ts] ----- -client.searchTemplate({ ... }) ----- +=== client.connector.syncJobCancel [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, -and aliases to search. Supports wildcards (*). -** *`explain` (Optional, boolean)*: If `true`, returns detailed information about score calculation as part of each hit. -** *`id` (Optional, string)*: ID of the search template to use. If no source is specified, -this parameter is required. -** *`params` (Optional, Record)*: Key-value pairs used to replace Mustache variables in the template. -The key is the variable name. -The value is the variable value. -** *`profile` (Optional, boolean)*: If `true`, the query execution is profiled. -** *`source` (Optional, string)*: An inline search template. Supports the same parameters as the search API's -request body. Also supports Mustache variables. If no id is specified, this -parameter is required. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`ccs_minimize_roundtrips` (Optional, boolean)*: If `true`, network round-trips are minimized for cross-cluster search requests. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_throttled` (Optional, boolean)*: If `true`, specified concrete, expanded, or aliased indices are not included in the response when throttled. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`scroll` (Optional, string | -1 | 0)*: Specifies how long a consistent view of the index -should be maintained for scrolled search. -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: The type of the search operation. -** *`rest_total_hits_as_int` (Optional, boolean)*: If true, hits.total are rendered as an integer in the response. -** *`typed_keys` (Optional, boolean)*: If `true`, the response prefixes aggregation and suggester names with their respective types. - +=== client.connector.syncJobCheckIn [discrete] -=== terms_enum -Get terms in an index. - -Discover terms that match a partial string in an index. -This "terms enum" API is designed for low-latency look-ups used in auto-complete scenarios. - -If the `complete` property in the response is false, the returned terms set may be incomplete and should be treated as approximate. -This can occur due to a few reasons, such as a request timeout or a node error. - -NOTE: The terms enum API may return terms from deleted documents. Deleted documents are initially only marked as deleted. It is not until their segments are merged that documents are actually deleted. Until that happens, the terms enum API will return terms from these documents. - -{ref}/search-terms-enum.html[Endpoint documentation] -[source,ts] ----- -client.termsEnum({ index, field }) ----- +=== client.connector.syncJobClaim [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: List of data streams, indices, and index aliases to search. Wildcard (*) expressions are supported. -** *`field` (string)*: The string to match at the start of indexed terms. If not provided, all terms in the field are considered. -** *`size` (Optional, number)*: How many matching terms to return. -** *`timeout` (Optional, string | -1 | 0)*: The maximum length of time to spend collecting results. Defaults to "1s" (one second). If the timeout is exceeded the complete flag set to false in the response and the results may be partial or empty. -** *`case_insensitive` (Optional, boolean)*: When true the provided search string is matched against index terms without case sensitivity. -** *`index_filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Allows to filter an index shard if the provided query rewrites to match_none. -** *`string` (Optional, string)*: The string after which terms in the index should be returned. Allows for a form of pagination if the last result from one request is passed as the search_after parameter for a subsequent request. -** *`search_after` (Optional, string)* - +=== client.connector.syncJobDelete [discrete] -=== termvectors -Get term vector information. - -Get information and statistics about terms in the fields of a particular document. - -{ref}/docs-termvectors.html[Endpoint documentation] -[source,ts] ----- -client.termvectors({ index }) ----- +=== client.connector.syncJobError [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Name of the index that contains the document. -** *`id` (Optional, string)*: Unique identifier of the document. -** *`doc` (Optional, object)*: An artificial document (a document not present in the index) for which you want to retrieve term vectors. -** *`filter` (Optional, { max_doc_freq, max_num_terms, max_term_freq, max_word_length, min_doc_freq, min_term_freq, min_word_length })*: Filter terms based on their tf-idf scores. -** *`per_field_analyzer` (Optional, Record)*: Overrides the default per-field analyzer. -** *`fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in the statistics. -Used as the default list unless a specific field list is provided in the `completion_fields` or `fielddata_fields` parameters. -** *`field_statistics` (Optional, boolean)*: If `true`, the response includes the document count, sum of document frequencies, and sum of total term frequencies. -** *`offsets` (Optional, boolean)*: If `true`, the response includes term offsets. -** *`payloads` (Optional, boolean)*: If `true`, the response includes term payloads. -** *`positions` (Optional, boolean)*: If `true`, the response includes term positions. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`realtime` (Optional, boolean)*: If true, the request is real-time as opposed to near-real-time. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`term_statistics` (Optional, boolean)*: If `true`, the response includes term frequency and document frequency. -** *`version` (Optional, number)*: If `true`, returns the document version as part of a hit. -** *`version_type` (Optional, Enum("internal" | "external" | "external_gte" | "force"))*: Specific version type. - +=== client.connector.syncJobGet [discrete] -=== update -Update a document. -Updates a document by running a script or passing a partial document. - -{ref}/docs-update.html[Endpoint documentation] -[source,ts] ----- -client.update({ id, index }) ----- +=== client.connector.syncJobList [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Document ID -** *`index` (string)*: The name of the index -** *`detect_noop` (Optional, boolean)*: Set to false to disable setting 'result' in the response -to 'noop' if no change to the document occurred. -** *`doc` (Optional, object)*: A partial update to an existing document. -** *`doc_as_upsert` (Optional, boolean)*: Set to true to use the contents of 'doc' as the value of 'upsert' -** *`script` (Optional, { source, id, params, lang, options })*: Script to execute to update the document. -** *`scripted_upsert` (Optional, boolean)*: Set to true to execute the script whether or not the document exists. -** *`_source` (Optional, boolean | { excludes, includes })*: Set to false to disable source retrieval. You can also specify a comma-separated -list of the fields you want to retrieve. -** *`upsert` (Optional, object)*: If the document does not already exist, the contents of 'upsert' are inserted as a -new document. If the document exists, the 'script' is executed. -** *`if_primary_term` (Optional, number)*: Only perform the operation if the document has this primary term. -** *`if_seq_no` (Optional, number)*: Only perform the operation if the document has this sequence number. -** *`lang` (Optional, string)*: The script language. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If 'true', Elasticsearch refreshes 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' do nothing with refreshes. -** *`require_alias` (Optional, boolean)*: If true, the destination must be an index alias. -** *`retry_on_conflict` (Optional, number)*: Specify how many times should the operation be retried when a conflict occurs. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for dynamic mapping updates and active shards. -This guarantees Elasticsearch waits for at least the timeout before failing. -The actual wait time could be longer, particularly when multiple waits occur. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: The number of shard copies that must be active before proceeding with the operations. -Set to 'all' or any positive integer up to the total number of shards in the index -(number_of_replicas+1). Defaults to 1 meaning the primary shard. -** *`_source_excludes` (Optional, string | string[])*: Specify the source fields you want to exclude. -** *`_source_includes` (Optional, string | string[])*: Specify the source fields you want to retrieve. - +=== client.connector.syncJobPost [discrete] -=== update_by_query -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. - -{ref}/docs-update-by-query.html[Endpoint documentation] -[source,ts] ----- -client.updateByQuery({ index }) ----- +=== client.connector.syncJobUpdateStats [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams, indices, and aliases to search. -Supports wildcards (`*`). -To search all data streams or indices, omit this parameter or use `*` or `_all`. -** *`max_docs` (Optional, number)*: The maximum number of documents to update. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Specifies the documents to update using the Query DSL. -** *`script` (Optional, { source, id, params, lang, options })*: The script to run to update the document source or metadata when updating. -** *`slice` (Optional, { field, id, max })*: Slice the request manually using the provided slice ID and total number of slices. -** *`conflicts` (Optional, Enum("abort" | "proceed"))*: What to do if update by query hits version conflicts: `abort` or `proceed`. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`analyzer` (Optional, string)*: Analyzer to use for the query string. -** *`analyze_wildcard` (Optional, boolean)*: If `true`, wildcard and prefix queries are analyzed. -** *`default_operator` (Optional, Enum("and" | "or"))*: The default operator for query string query: `AND` or `OR`. -** *`df` (Optional, string)*: Field to use as default where no field prefix is given in the query string. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`from` (Optional, number)*: Starting offset (default: 0) -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`lenient` (Optional, boolean)*: If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored. -** *`pipeline` (Optional, string)*: ID of the pipeline to use to preprocess incoming documents. -If the index has a default ingest pipeline specified, then setting the value to `_none` disables the default ingest pipeline for this request. -If a final pipeline is configured it will always run, regardless of the value of this parameter. -** *`preference` (Optional, string)*: Specifies the node or shard the operation should be performed on. -Random by default. -** *`q` (Optional, string)*: Query in the Lucene query string syntax. -** *`refresh` (Optional, boolean)*: If `true`, Elasticsearch refreshes affected shards to make the operation visible to search. -** *`request_cache` (Optional, boolean)*: If `true`, the request cache is used for this request. -** *`requests_per_second` (Optional, float)*: The throttle for this request in sub-requests per second. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`scroll` (Optional, string | -1 | 0)*: Period to retain the search context for scrolling. -** *`scroll_size` (Optional, number)*: Size of the scroll request that powers the operation. -** *`search_timeout` (Optional, string | -1 | 0)*: Explicit timeout for each search request. -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: The type of the search operation. Available options: `query_then_fetch`, `dfs_query_then_fetch`. -** *`slices` (Optional, number | Enum("auto"))*: The number of slices this task should be divided into. -** *`sort` (Optional, string[])*: A list of : pairs. -** *`stats` (Optional, string[])*: Specific `tag` of the request for logging and statistical purposes. -** *`terminate_after` (Optional, number)*: 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. -** *`timeout` (Optional, string | -1 | 0)*: Period each update request waits for the following operations: dynamic mapping updates, waiting for active shards. -** *`version` (Optional, boolean)*: If `true`, returns the document version as part of a hit. -** *`version_type` (Optional, boolean)*: Should the document increment the version number (internal) on hit or not (reindex) -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). -** *`wait_for_completion` (Optional, boolean)*: If `true`, the request blocks until the operation is complete. - +=== client.connector.updateActiveFiltering [discrete] -=== update_by_query_rethrottle -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. - -{ref}/docs-update-by-query.html[Endpoint documentation] -[source,ts] ----- -client.updateByQueryRethrottle({ task_id }) ----- +=== client.connector.updateApiKeyId [discrete] -==== Arguments - -* *Request (object):* -** *`task_id` (string)*: The ID for the task. -** *`requests_per_second` (Optional, float)*: The throttle for this request in sub-requests per second. - +=== client.connector.updateConfiguration [discrete] -=== async_search +=== client.connector.updateError [discrete] -==== delete -Delete an async search. - -If the asynchronous search is still running, it is cancelled. -Otherwise, the saved search results are deleted. -If the Elasticsearch security features are enabled, the deletion of a specific async search is restricted to: the authenticated user that submitted the original search request; users that have the `cancel_task` cluster privilege. - -{ref}/async-search.html[Endpoint documentation] -[source,ts] ----- -client.asyncSearch.delete({ id }) ----- - +=== client.connector.updateFeatures [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: A unique identifier for the async search. - +=== client.connector.updateFiltering [discrete] -==== get -Get async search results. - -Retrieve the results of a previously submitted asynchronous search request. -If the Elasticsearch security features are enabled, access to the results of a specific async search is restricted to the user or API key that submitted it. - -{ref}/async-search.html[Endpoint documentation] -[source,ts] ----- -client.asyncSearch.get({ id }) ----- - +=== client.connector.updateFilteringValidation [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: A unique identifier for the async search. -** *`keep_alive` (Optional, string | -1 | 0)*: Specifies how long the async search should be available in the cluster. -When not specified, the `keep_alive` set with the corresponding submit async request will be used. -Otherwise, it is possible to override the value and extend the validity of the request. -When this period expires, the search, if still running, is cancelled. -If the search is completed, its saved results are deleted. -** *`typed_keys` (Optional, boolean)*: Specify whether aggregation and suggester names should be prefixed by their respective types in the response -** *`wait_for_completion_timeout` (Optional, string | -1 | 0)*: Specifies to wait for the search to be completed up until the provided timeout. -Final results will be returned if available before the timeout expires, otherwise the currently available results will be returned once the timeout expires. -By default no timeout is set meaning that the currently available results will be returned without any additional wait. - +=== client.connector.updateIndexName [discrete] -==== status -Get the async search status. - -Get the status of a previously submitted async search request given its identifier, without retrieving search results. -If the Elasticsearch security features are enabled, use of this API is restricted to the `monitoring_user` role. - -{ref}/async-search.html[Endpoint documentation] -[source,ts] ----- -client.asyncSearch.status({ id }) ----- - +=== client.connector.updateName [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: A unique identifier for the async search. - +=== client.connector.updateNative [discrete] -==== submit -Run an async search. - -When the primary sort of the results is an indexed field, shards get sorted based on minimum and maximum value that they hold for that field. Partial results become available following the sort criteria that was requested. - -Warning: Asynchronous search does not support scroll or search requests that include only the suggest section. - -By default, Elasticsearch does not allow you to store an async search response larger than 10Mb and an attempt to do this results in an error. -The maximum allowed size for a stored async search response can be set by changing the `search.max_async_search_response_size` cluster level setting. - -{ref}/async-search.html[Endpoint documentation] -[source,ts] ----- -client.asyncSearch.submit({ ... }) ----- - +=== client.connector.updatePipeline [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: A list of index names to search; use `_all` or empty string to perform the operation on all indices -** *`aggregations` (Optional, Record)* -** *`collapse` (Optional, { field, inner_hits, max_concurrent_group_searches, collapse })* -** *`explain` (Optional, boolean)*: If true, returns detailed information about score computation as part of a hit. -** *`ext` (Optional, Record)*: Configuration of search extensions defined by Elasticsearch plugins. -** *`from` (Optional, number)*: Starting document offset. By default, you cannot page through more than 10,000 -hits using the from and size parameters. To page through more hits, use the -search_after parameter. -** *`highlight` (Optional, { encoder, fields })* -** *`track_total_hits` (Optional, boolean | number)*: Number of hits matching the query to count accurately. If true, the exact -number of hits is returned at the cost of some performance. If false, the -response does not include the total number of hits matching the query. -Defaults to 10,000 hits. -** *`indices_boost` (Optional, Record[])*: Boosts the _score of documents from specified indices. -** *`docvalue_fields` (Optional, { field, format, include_unmapped }[])*: Array of wildcard (*) patterns. The request returns doc values for field -names matching these patterns in the hits.fields property of the response. -** *`knn` (Optional, { field, query_vector, query_vector_builder, k, num_candidates, boost, filter, similarity, inner_hits } | { field, query_vector, query_vector_builder, k, num_candidates, boost, filter, similarity, inner_hits }[])*: Defines the approximate kNN search to run. -** *`min_score` (Optional, number)*: Minimum _score for matching documents. Documents with a lower _score are -not included in the search results. -** *`post_filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })* -** *`profile` (Optional, boolean)* -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Defines the search definition using the Query DSL. -** *`rescore` (Optional, { window_size, query, learning_to_rank } | { window_size, query, learning_to_rank }[])* -** *`script_fields` (Optional, Record)*: Retrieve a script evaluation (based on different fields) for each hit. -** *`search_after` (Optional, number | number | string | boolean | null | User-defined value[])* -** *`size` (Optional, number)*: The number of hits to return. By default, you cannot page through more -than 10,000 hits using the from and size parameters. To page through more -hits, use the search_after parameter. -** *`slice` (Optional, { field, id, max })* -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])* -** *`_source` (Optional, boolean | { excludes, includes })*: Indicates which source fields are returned for matching documents. These -fields are returned in the hits._source property of the search response. -** *`fields` (Optional, { field, format, include_unmapped }[])*: Array of wildcard (*) patterns. The request returns values for field names -matching these patterns in the hits.fields property of the response. -** *`suggest` (Optional, { text })* -** *`terminate_after` (Optional, number)*: 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. Defaults to 0, which does not terminate query execution early. -** *`timeout` (Optional, string)*: Specifies the period of time to wait for a response from each shard. If no response -is received before the timeout expires, the request fails and returns an error. -Defaults to no timeout. -** *`track_scores` (Optional, boolean)*: If true, calculate and return document scores, even if the scores are not used for sorting. -** *`version` (Optional, boolean)*: If true, returns document version as part of a hit. -** *`seq_no_primary_term` (Optional, boolean)*: If true, returns sequence number and primary term of the last modification -of each hit. See Optimistic concurrency control. -** *`stored_fields` (Optional, string | string[])*: List of stored fields to return as part of a hit. If no fields are specified, -no stored fields are included in the response. If this field is specified, the _source -parameter defaults to false. You can pass _source: true to return both source fields -and stored fields in the search response. -** *`pit` (Optional, { id, keep_alive })*: Limits the search to a point in time (PIT). If you provide a PIT, you -cannot specify an in the request path. -** *`runtime_mappings` (Optional, Record)*: Defines one or more runtime fields in the search request. These fields take -precedence over mapped fields with the same name. -** *`stats` (Optional, string[])*: Stats groups to associate with the search. Each group maintains a statistics -aggregation for its associated searches. You can retrieve these stats using -the indices stats API. -** *`wait_for_completion_timeout` (Optional, string | -1 | 0)*: Blocks and waits until the search is completed up to a certain timeout. -When the async search completes within the timeout, the response won’t include the ID as the results are not stored in the cluster. -** *`keep_on_completion` (Optional, boolean)*: If `true`, results are stored for later retrieval when the search completes within the `wait_for_completion_timeout`. -** *`keep_alive` (Optional, string | -1 | 0)*: Specifies how long the async search needs to be available. -Ongoing async searches and any saved search results are deleted after this period. -** *`allow_no_indices` (Optional, boolean)*: Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified) -** *`allow_partial_search_results` (Optional, boolean)*: Indicate if an error should be returned if there is a partial search failure or timeout -** *`analyzer` (Optional, string)*: The analyzer to use for the query string -** *`analyze_wildcard` (Optional, boolean)*: Specify whether wildcard and prefix queries should be analyzed (default: false) -** *`batched_reduce_size` (Optional, number)*: Affects how often partial results become available, which happens whenever shard results are reduced. -A partial reduction is performed every time the coordinating node has received a certain number of new shard responses (5 by default). -** *`ccs_minimize_roundtrips` (Optional, boolean)*: The default value is the only supported value. -** *`default_operator` (Optional, Enum("and" | "or"))*: The default operator for query string query (AND or OR) -** *`df` (Optional, string)*: The field to use as default where no field prefix is given in the query string -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`ignore_throttled` (Optional, boolean)*: Whether specified concrete, expanded or aliased indices should be ignored when throttled -** *`ignore_unavailable` (Optional, boolean)*: Whether specified concrete indices should be ignored when unavailable (missing or closed) -** *`lenient` (Optional, boolean)*: Specify whether format-based query failures (such as providing text to a numeric field) should be ignored -** *`max_concurrent_shard_requests` (Optional, number)*: The number of concurrent shard requests per node this search executes concurrently. This value should be used to limit the impact of the search on the cluster in order to limit the number of concurrent shard requests -** *`preference` (Optional, string)*: Specify the node or shard the operation should be performed on (default: random) -** *`pre_filter_shard_size` (Optional, number)*: The default value cannot be changed, which enforces the execution of a pre-filter roundtrip to retrieve statistics from each shard so that the ones that surely don’t hold any document matching the query get skipped. -** *`request_cache` (Optional, boolean)*: Specify if request cache should be used for this request or not, defaults to true -** *`routing` (Optional, string)*: A list of specific routing values -** *`scroll` (Optional, string | -1 | 0)* -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: Search operation type -** *`suggest_field` (Optional, string)*: Specifies which field to use for suggestions. -** *`suggest_mode` (Optional, Enum("missing" | "popular" | "always"))*: Specify suggest mode -** *`suggest_size` (Optional, number)*: How many suggestions to return in response -** *`suggest_text` (Optional, string)*: The source text for which the suggestions should be returned. -** *`typed_keys` (Optional, boolean)*: Specify whether aggregation and suggester names should be prefixed by their respective types in the response -** *`rest_total_hits_as_int` (Optional, boolean)* -** *`_source_excludes` (Optional, string | string[])*: A list of fields to exclude from the returned _source field -** *`_source_includes` (Optional, string | string[])*: A list of fields to extract and return from the _source field -** *`q` (Optional, string)*: Query in the Lucene query string syntax - +=== client.connector.updateScheduling [discrete] -=== autoscaling +=== client.connector.updateServiceType [discrete] -==== delete_autoscaling_policy -Delete an autoscaling policy. - -NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. - -{ref}/autoscaling-delete-autoscaling-policy.html[Endpoint documentation] -[source,ts] ----- -client.autoscaling.deleteAutoscalingPolicy({ name }) ----- - +=== client.connector.updateStatus [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: the name of the autoscaling policy - +=== client.count [discrete] -==== get_autoscaling_capacity -Get the autoscaling capacity. - -NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. - -This API gets the current autoscaling capacity based on the configured autoscaling policy. -It will return information to size the cluster appropriately to the current workload. - -The `required_capacity` is calculated as the maximum of the `required_capacity` result of all individual deciders that are enabled for the policy. - -The operator should verify that the `current_nodes` match the operator’s knowledge of the cluster to avoid making autoscaling decisions based on stale or incomplete information. - -The response contains decider-specific information you can use to diagnose how and why autoscaling determined a certain capacity was required. -This information is provided for diagnosis only. -Do not use this information to make autoscaling decisions. - -{ref}/autoscaling-get-autoscaling-capacity.html[Endpoint documentation] -[source,ts] ----- -client.autoscaling.getAutoscalingCapacity() ----- - - +=== client.create [discrete] -==== get_autoscaling_policy -Get an autoscaling policy. - -NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. - -{ref}/autoscaling-get-autoscaling-capacity.html[Endpoint documentation] -[source,ts] ----- -client.autoscaling.getAutoscalingPolicy({ name }) ----- - +=== client.danglingIndices.deleteDanglingIndex [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: the name of the autoscaling policy - +=== client.danglingIndices.importDanglingIndex [discrete] -==== put_autoscaling_policy -Create or update an autoscaling policy. - -NOTE: This feature is designed for indirect use by Elasticsearch Service, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported. - -{ref}/autoscaling-put-autoscaling-policy.html[Endpoint documentation] -[source,ts] ----- -client.autoscaling.putAutoscalingPolicy({ name }) ----- - +=== client.danglingIndices.listDanglingIndices [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: the name of the autoscaling policy -** *`policy` (Optional, { roles, deciders })* - +=== client.delete [discrete] -=== cat +=== client.deleteByQuery [discrete] -==== aliases -Get aliases. -Retrieves the cluster’s index aliases, including filter and routing information. -The API does not return data stream aliases. - -CAT APIs are only intended for human consumption using the command line or the Kibana console. They are not intended for use by applications. For application consumption, use the aliases API. - -{ref}/cat-alias.html[Endpoint documentation] -[source,ts] ----- -client.cat.aliases({ ... }) ----- - +=== client.deleteByQueryRethrottle [discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string | string[])*: A list of aliases to retrieve. Supports wildcards (`*`). To retrieve all aliases, omit this parameter or use `*` or `_all`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. - +=== client.deleteScript [discrete] -==== allocation -Provides a snapshot of the number of shards allocated to each data node and their disk space. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. - -{ref}/cat-allocation.html[Endpoint documentation] -[source,ts] ----- -client.cat.allocation({ ... }) ----- - +=== client.enrich.deletePolicy [discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: List of node identifiers or names used to limit the returned information. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.enrich.executePolicy [discrete] -==== component_templates -Get component templates. -Returns information about component templates in a cluster. -Component templates are building blocks for constructing index templates that specify index mappings, settings, and aliases. - -CAT APIs are only intended for human consumption using the command line or Kibana console. -They are not intended for use by applications. For application consumption, use the get component template API. - -{ref}/cat-component-templates.html[Endpoint documentation] -[source,ts] ----- -client.cat.componentTemplates({ ... }) ----- - +=== client.enrich.getPolicy [discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: The name of the component template. Accepts wildcard expressions. If omitted, all component templates are returned. -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.enrich.putPolicy [discrete] -==== count -Get a document count. -Provides quick access to a document count for a data stream, an index, or an entire cluster. -The document count only includes live documents, not deleted documents which have not yet been removed by the merge process. - -CAT APIs are only intended for human consumption using the command line or Kibana console. -They are not intended for use by applications. For application consumption, use the count API. - -{ref}/cat-count.html[Endpoint documentation] -[source,ts] ----- -client.cat.count({ ... }) ----- - +=== client.enrich.stats [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). To target all data streams and indices, omit this parameter or use `*` or `_all`. - +=== client.eql.delete [discrete] -==== fielddata -Returns the amount of heap memory currently used by the field data cache on every data node in the cluster. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. -They are not intended for use by applications. For application consumption, use the nodes stats API. - -{ref}/cat-fielddata.html[Endpoint documentation] -[source,ts] ----- -client.cat.fielddata({ ... }) ----- - +=== client.eql.get [discrete] -==== Arguments - -* *Request (object):* -** *`fields` (Optional, string | string[])*: List of fields used to limit returned information. -To retrieve all fields, omit this parameter. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. - +=== client.eql.getStatus [discrete] -==== health -Returns the health status of a cluster, similar to the cluster health API. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. -They are not intended for use by applications. For application consumption, use the cluster health API. -This API is often used to check malfunctioning clusters. -To help you track cluster health alongside log files and alerting systems, the API returns timestamps in two formats: -`HH:MM:SS`, which is human-readable but includes no date information; -`Unix epoch time`, which is machine-sortable and includes date information. -The latter format is useful for cluster recoveries that take multiple days. -You can use the cat health API to verify cluster health across multiple nodes. -You also can use the API to track the recovery of a large cluster over a longer period of time. - -{ref}/cat-health.html[Endpoint documentation] -[source,ts] ----- -client.cat.health({ ... }) ----- - +=== client.eql.search [discrete] -==== Arguments - -* *Request (object):* -** *`time` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: The unit used to display time values. -** *`ts` (Optional, boolean)*: If true, returns `HH:MM:SS` and Unix epoch timestamps. - +=== client.esql.asyncQuery [discrete] -==== help -Get CAT help. -Returns help for the CAT APIs. - -{ref}/cat.html[Endpoint documentation] -[source,ts] ----- -client.cat.help() ----- - - +=== client.esql.asyncQueryGet [discrete] -==== indices -Get index information. -Returns high-level information about indices in a cluster, including backing indices for data streams. - -Use this request to get the following information for each index in a cluster: -- shard count -- document count -- deleted document count -- primary store size -- total store size of all shards, including shard replicas - -These metrics are retrieved directly from Lucene, which Elasticsearch uses internally to power indexing and search. As a result, all document counts include hidden nested documents. -To get an accurate count of Elasticsearch documents, use the cat count or count APIs. - -CAT APIs are only intended for human consumption using the command line or Kibana console. -They are not intended for use by applications. For application consumption, use an index endpoint. - -{ref}/cat-indices.html[Endpoint documentation] -[source,ts] ----- -client.cat.indices({ ... }) ----- - +=== client.esql.query [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: The type of index that wildcard patterns can match. -** *`health` (Optional, Enum("green" | "yellow" | "red"))*: The health status used to limit returned indices. By default, the response includes indices of any health status. -** *`include_unloaded_segments` (Optional, boolean)*: If true, the response includes information from segments that are not loaded into memory. -** *`pri` (Optional, boolean)*: If true, the response only includes information from primary shards. -** *`time` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: The unit used to display time values. - +=== client.exists [discrete] -==== master -Returns information about the master node, including the ID, bound IP address, and name. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. - -{ref}/cat-master.html[Endpoint documentation] -[source,ts] ----- -client.cat.master({ ... }) ----- - +=== client.existsSource [discrete] -==== Arguments - -* *Request (object):* -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.explain [discrete] -==== ml_data_frame_analytics -Get data frame analytics jobs. -Returns configuration and usage information about data frame analytics jobs. - -CAT APIs are only intended for human consumption using the Kibana -console or command line. They are not intended for use by applications. For -application consumption, use the get data frame analytics jobs statistics API. - -{ref}/cat-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.cat.mlDataFrameAnalytics({ ... }) ----- - +=== client.features.getFeatures [discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: The ID of the data frame analytics to fetch -** *`allow_no_match` (Optional, boolean)*: Whether to ignore if a wildcard expression matches no configs. (This includes `_all` string or when no configs have been specified) -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit in which to display byte values -** *`h` (Optional, Enum("assignment_explanation" | "create_time" | "description" | "dest_index" | "failure_reason" | "id" | "model_memory_limit" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "progress" | "source_index" | "state" | "type" | "version") | Enum("assignment_explanation" | "create_time" | "description" | "dest_index" | "failure_reason" | "id" | "model_memory_limit" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "progress" | "source_index" | "state" | "type" | "version")[])*: List of column names to display. -** *`s` (Optional, Enum("assignment_explanation" | "create_time" | "description" | "dest_index" | "failure_reason" | "id" | "model_memory_limit" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "progress" | "source_index" | "state" | "type" | "version") | Enum("assignment_explanation" | "create_time" | "description" | "dest_index" | "failure_reason" | "id" | "model_memory_limit" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "progress" | "source_index" | "state" | "type" | "version")[])*: List of column names or column aliases used to sort the -response. -** *`time` (Optional, string | -1 | 0)*: Unit used to display time values. - +=== client.features.resetFeatures [discrete] -==== ml_datafeeds -Get datafeeds. -Returns configuration and usage information about datafeeds. -This API returns a maximum of 10,000 datafeeds. -If the Elasticsearch security features are enabled, you must have `monitor_ml`, `monitor`, `manage_ml`, or `manage` -cluster privileges to use this API. - -CAT APIs are only intended for human consumption using the Kibana -console or command line. They are not intended for use by applications. For -application consumption, use the get datafeed statistics API. - -{ref}/cat-datafeeds.html[Endpoint documentation] -[source,ts] ----- -client.cat.mlDatafeeds({ ... }) ----- - +=== client.fieldCaps [discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (Optional, string)*: A numerical character string that uniquely identifies the datafeed. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -* Contains wildcard expressions and there are no datafeeds that match. -* Contains the `_all` string or no identifiers and there are no matches. -* Contains wildcard expressions and there are only partial matches. - -If `true`, the API returns an empty datafeeds array when there are no matches and the subset of results when -there are partial matches. If `false`, the API returns a 404 status code when there are no matches or only -partial matches. -** *`h` (Optional, Enum("ae" | "bc" | "id" | "na" | "ne" | "ni" | "nn" | "sba" | "sc" | "seah" | "st" | "s") | Enum("ae" | "bc" | "id" | "na" | "ne" | "ni" | "nn" | "sba" | "sc" | "seah" | "st" | "s")[])*: List of column names to display. -** *`s` (Optional, Enum("ae" | "bc" | "id" | "na" | "ne" | "ni" | "nn" | "sba" | "sc" | "seah" | "st" | "s") | Enum("ae" | "bc" | "id" | "na" | "ne" | "ni" | "nn" | "sba" | "sc" | "seah" | "st" | "s")[])*: List of column names or column aliases used to sort the response. -** *`time` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: The unit used to display time values. - +=== client.fleet.globalCheckpoints [discrete] -==== ml_jobs -Get anomaly detection jobs. -Returns configuration and usage information for anomaly detection jobs. -This API returns a maximum of 10,000 jobs. -If the Elasticsearch security features are enabled, you must have `monitor_ml`, -`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. - -CAT APIs are only intended for human consumption using the Kibana -console or command line. They are not intended for use by applications. For -application consumption, use the get anomaly detection job statistics API. - -{ref}/cat-anomaly-detectors.html[Endpoint documentation] -[source,ts] ----- -client.cat.mlJobs({ ... }) ----- - +=== client.fleet.msearch [discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (Optional, string)*: Identifier for the anomaly detection job. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -* Contains wildcard expressions and there are no jobs that match. -* Contains the `_all` string or no identifiers and there are no matches. -* Contains wildcard expressions and there are only partial matches. - -If `true`, the API returns an empty jobs array when there are no matches and the subset of results when there -are partial matches. If `false`, the API returns a 404 status code when there are no matches or only partial -matches. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. -** *`h` (Optional, Enum("assignment_explanation" | "buckets.count" | "buckets.time.exp_avg" | "buckets.time.exp_avg_hour" | "buckets.time.max" | "buckets.time.min" | "buckets.time.total" | "data.buckets" | "data.earliest_record" | "data.empty_buckets" | "data.input_bytes" | "data.input_fields" | "data.input_records" | "data.invalid_dates" | "data.last" | "data.last_empty_bucket" | "data.last_sparse_bucket" | "data.latest_record" | "data.missing_fields" | "data.out_of_order_timestamps" | "data.processed_fields" | "data.processed_records" | "data.sparse_buckets" | "forecasts.memory.avg" | "forecasts.memory.max" | "forecasts.memory.min" | "forecasts.memory.total" | "forecasts.records.avg" | "forecasts.records.max" | "forecasts.records.min" | "forecasts.records.total" | "forecasts.time.avg" | "forecasts.time.max" | "forecasts.time.min" | "forecasts.time.total" | "forecasts.total" | "id" | "model.bucket_allocation_failures" | "model.by_fields" | "model.bytes" | "model.bytes_exceeded" | "model.categorization_status" | "model.categorized_doc_count" | "model.dead_category_count" | "model.failed_category_count" | "model.frequent_category_count" | "model.log_time" | "model.memory_limit" | "model.memory_status" | "model.over_fields" | "model.partition_fields" | "model.rare_category_count" | "model.timestamp" | "model.total_category_count" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "opened_time" | "state") | Enum("assignment_explanation" | "buckets.count" | "buckets.time.exp_avg" | "buckets.time.exp_avg_hour" | "buckets.time.max" | "buckets.time.min" | "buckets.time.total" | "data.buckets" | "data.earliest_record" | "data.empty_buckets" | "data.input_bytes" | "data.input_fields" | "data.input_records" | "data.invalid_dates" | "data.last" | "data.last_empty_bucket" | "data.last_sparse_bucket" | "data.latest_record" | "data.missing_fields" | "data.out_of_order_timestamps" | "data.processed_fields" | "data.processed_records" | "data.sparse_buckets" | "forecasts.memory.avg" | "forecasts.memory.max" | "forecasts.memory.min" | "forecasts.memory.total" | "forecasts.records.avg" | "forecasts.records.max" | "forecasts.records.min" | "forecasts.records.total" | "forecasts.time.avg" | "forecasts.time.max" | "forecasts.time.min" | "forecasts.time.total" | "forecasts.total" | "id" | "model.bucket_allocation_failures" | "model.by_fields" | "model.bytes" | "model.bytes_exceeded" | "model.categorization_status" | "model.categorized_doc_count" | "model.dead_category_count" | "model.failed_category_count" | "model.frequent_category_count" | "model.log_time" | "model.memory_limit" | "model.memory_status" | "model.over_fields" | "model.partition_fields" | "model.rare_category_count" | "model.timestamp" | "model.total_category_count" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "opened_time" | "state")[])*: List of column names to display. -** *`s` (Optional, Enum("assignment_explanation" | "buckets.count" | "buckets.time.exp_avg" | "buckets.time.exp_avg_hour" | "buckets.time.max" | "buckets.time.min" | "buckets.time.total" | "data.buckets" | "data.earliest_record" | "data.empty_buckets" | "data.input_bytes" | "data.input_fields" | "data.input_records" | "data.invalid_dates" | "data.last" | "data.last_empty_bucket" | "data.last_sparse_bucket" | "data.latest_record" | "data.missing_fields" | "data.out_of_order_timestamps" | "data.processed_fields" | "data.processed_records" | "data.sparse_buckets" | "forecasts.memory.avg" | "forecasts.memory.max" | "forecasts.memory.min" | "forecasts.memory.total" | "forecasts.records.avg" | "forecasts.records.max" | "forecasts.records.min" | "forecasts.records.total" | "forecasts.time.avg" | "forecasts.time.max" | "forecasts.time.min" | "forecasts.time.total" | "forecasts.total" | "id" | "model.bucket_allocation_failures" | "model.by_fields" | "model.bytes" | "model.bytes_exceeded" | "model.categorization_status" | "model.categorized_doc_count" | "model.dead_category_count" | "model.failed_category_count" | "model.frequent_category_count" | "model.log_time" | "model.memory_limit" | "model.memory_status" | "model.over_fields" | "model.partition_fields" | "model.rare_category_count" | "model.timestamp" | "model.total_category_count" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "opened_time" | "state") | Enum("assignment_explanation" | "buckets.count" | "buckets.time.exp_avg" | "buckets.time.exp_avg_hour" | "buckets.time.max" | "buckets.time.min" | "buckets.time.total" | "data.buckets" | "data.earliest_record" | "data.empty_buckets" | "data.input_bytes" | "data.input_fields" | "data.input_records" | "data.invalid_dates" | "data.last" | "data.last_empty_bucket" | "data.last_sparse_bucket" | "data.latest_record" | "data.missing_fields" | "data.out_of_order_timestamps" | "data.processed_fields" | "data.processed_records" | "data.sparse_buckets" | "forecasts.memory.avg" | "forecasts.memory.max" | "forecasts.memory.min" | "forecasts.memory.total" | "forecasts.records.avg" | "forecasts.records.max" | "forecasts.records.min" | "forecasts.records.total" | "forecasts.time.avg" | "forecasts.time.max" | "forecasts.time.min" | "forecasts.time.total" | "forecasts.total" | "id" | "model.bucket_allocation_failures" | "model.by_fields" | "model.bytes" | "model.bytes_exceeded" | "model.categorization_status" | "model.categorized_doc_count" | "model.dead_category_count" | "model.failed_category_count" | "model.frequent_category_count" | "model.log_time" | "model.memory_limit" | "model.memory_status" | "model.over_fields" | "model.partition_fields" | "model.rare_category_count" | "model.timestamp" | "model.total_category_count" | "node.address" | "node.ephemeral_id" | "node.id" | "node.name" | "opened_time" | "state")[])*: List of column names or column aliases used to sort the response. -** *`time` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: The unit used to display time values. - +=== client.fleet.search [discrete] -==== ml_trained_models -Get trained models. -Returns configuration and usage information about inference trained models. - -CAT APIs are only intended for human consumption using the Kibana -console or command line. They are not intended for use by applications. For -application consumption, use the get trained models statistics API. - -{ref}/cat-trained-model.html[Endpoint documentation] -[source,ts] ----- -client.cat.mlTrainedModels({ ... }) ----- - +=== client.get [discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (Optional, string)*: A unique identifier for the trained model. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: contains wildcard expressions and there are no models that match; contains the `_all` string or no identifiers and there are no matches; contains wildcard expressions and there are only partial matches. -If `true`, the API returns an empty array when there are no matches and the subset of results when there are partial matches. -If `false`, the API returns a 404 status code when there are no matches or only partial matches. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. -** *`h` (Optional, Enum("create_time" | "created_by" | "data_frame_analytics_id" | "description" | "heap_size" | "id" | "ingest.count" | "ingest.current" | "ingest.failed" | "ingest.pipelines" | "ingest.time" | "license" | "operations" | "version") | Enum("create_time" | "created_by" | "data_frame_analytics_id" | "description" | "heap_size" | "id" | "ingest.count" | "ingest.current" | "ingest.failed" | "ingest.pipelines" | "ingest.time" | "license" | "operations" | "version")[])*: A list of column names to display. -** *`s` (Optional, Enum("create_time" | "created_by" | "data_frame_analytics_id" | "description" | "heap_size" | "id" | "ingest.count" | "ingest.current" | "ingest.failed" | "ingest.pipelines" | "ingest.time" | "license" | "operations" | "version") | Enum("create_time" | "created_by" | "data_frame_analytics_id" | "description" | "heap_size" | "id" | "ingest.count" | "ingest.current" | "ingest.failed" | "ingest.pipelines" | "ingest.time" | "license" | "operations" | "version")[])*: A list of column names or aliases used to sort the response. -** *`from` (Optional, number)*: Skips the specified number of transforms. -** *`size` (Optional, number)*: The maximum number of transforms to display. - +=== client.getScript [discrete] -==== nodeattrs -Returns information about custom node attributes. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. - -{ref}/cat-nodeattrs.html[Endpoint documentation] -[source,ts] ----- -client.cat.nodeattrs({ ... }) ----- - +=== client.getScriptContext [discrete] -==== Arguments - -* *Request (object):* -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.getScriptLanguages [discrete] -==== nodes -Returns information about the nodes in a cluster. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. - -{ref}/cat-nodes.html[Endpoint documentation] -[source,ts] ----- -client.cat.nodes({ ... }) ----- - +=== client.getSource [discrete] -==== Arguments - -* *Request (object):* -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. -** *`full_id` (Optional, boolean | string)*: If `true`, return the full node ID. If `false`, return the shortened node ID. -** *`include_unloaded_segments` (Optional, boolean)*: If true, the response includes information from segments that are not loaded into memory. - +=== client.graph.explore [discrete] -==== pending_tasks -Returns cluster-level changes that have not yet been executed. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the pending cluster tasks API. - -{ref}/cat-pending-tasks.html[Endpoint documentation] -[source,ts] ----- -client.cat.pendingTasks({ ... }) ----- - +=== client.healthReport [discrete] -==== Arguments - -* *Request (object):* -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.ilm.deleteLifecycle [discrete] -==== plugins -Returns a list of plugins running on each node of a cluster. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. - -{ref}/cat-plugins.html[Endpoint documentation] -[source,ts] ----- -client.cat.plugins({ ... }) ----- - +=== client.ilm.explainLifecycle [discrete] -==== Arguments - -* *Request (object):* -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.ilm.getLifecycle [discrete] -==== recovery -Returns information about ongoing and completed shard recoveries. -Shard recovery is the process of initializing a shard copy, such as restoring a primary shard from a snapshot or syncing a replica shard from a primary shard. When a shard recovery completes, the recovered shard is available for search and indexing. -For data streams, the API returns information about the stream’s backing indices. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the index recovery API. - -{ref}/cat-recovery.html[Endpoint documentation] -[source,ts] ----- -client.cat.recovery({ ... }) ----- - +=== client.ilm.getStatus [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: A list of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`active_only` (Optional, boolean)*: If `true`, the response only includes ongoing shard recoveries. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. -** *`detailed` (Optional, boolean)*: If `true`, the response includes detailed information about shard recoveries. - +=== client.ilm.migrateToDataTiers [discrete] -==== repositories -Returns the snapshot repositories for a cluster. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the get snapshot repository API. - -{ref}/cat-repositories.html[Endpoint documentation] -[source,ts] ----- -client.cat.repositories() ----- - - +=== client.ilm.moveToStep [discrete] -==== segments -Returns low-level information about the Lucene segments in index shards. -For data streams, the API returns information about the backing indices. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the index segments API. - -{ref}/cat-segments.html[Endpoint documentation] -[source,ts] ----- -client.cat.segments({ ... }) ----- - +=== client.ilm.putLifecycle [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: A list of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.ilm.removePolicy [discrete] -==== shards -Returns information about the shards in a cluster. -For data streams, the API returns information about the backing indices. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. - -{ref}/cat-shards.html[Endpoint documentation] -[source,ts] ----- -client.cat.shards({ ... }) ----- - +=== client.ilm.retry [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: A list of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`bytes` (Optional, Enum("b" | "kb" | "mb" | "gb" | "tb" | "pb"))*: The unit used to display byte values. - +=== client.ilm.start [discrete] -==== snapshots -Returns information about the snapshots stored in one or more repositories. -A snapshot is a backup of an index or running Elasticsearch cluster. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the get snapshot API. - -{ref}/cat-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.cat.snapshots({ ... }) ----- - +=== client.ilm.stop [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (Optional, string | string[])*: A list of snapshot repositories used to limit the request. -Accepts wildcard expressions. -`_all` returns all repositories. -If any repository fails during the request, Elasticsearch returns an error. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, the response does not include information from unavailable snapshots. - +=== client.index [discrete] -==== tasks -Returns information about tasks currently executing in the cluster. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the task management API. - -{ref}/tasks.html[Endpoint documentation] -[source,ts] ----- -client.cat.tasks({ ... }) ----- - +=== client.indices.addBlock [discrete] -==== Arguments - -* *Request (object):* -** *`actions` (Optional, string[])*: The task action names, which are used to limit the response. -** *`detailed` (Optional, boolean)*: If `true`, the response includes detailed information about shard recoveries. -** *`node_id` (Optional, string[])*: Unique node identifiers, which are used to limit the response. -** *`parent_task_id` (Optional, string)*: The parent task identifier, which is used to limit the response. - +=== client.indices.analyze [discrete] -==== templates -Returns information about index templates in a cluster. -You can use index templates to apply index settings and field mappings to new indices at creation. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the get index template API. - -{ref}/cat-templates.html[Endpoint documentation] -[source,ts] ----- -client.cat.templates({ ... }) ----- - +=== client.indices.clearCache [discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: The name of the template to return. -Accepts wildcard expressions. If omitted, all templates are returned. -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.indices.clone [discrete] -==== thread_pool -Returns thread pool statistics for each node in a cluster. -Returned information includes all built-in thread pools and custom thread pools. -IMPORTANT: cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the nodes info API. - -{ref}/cat-thread-pool.html[Endpoint documentation] -[source,ts] ----- -client.cat.threadPool({ ... }) ----- - +=== client.indices.close [discrete] -==== Arguments - -* *Request (object):* -** *`thread_pool_patterns` (Optional, string | string[])*: A list of thread pool names used to limit the request. -Accepts wildcard expressions. -** *`time` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: The unit used to display time values. -** *`local` (Optional, boolean)*: If `true`, the request computes the list of selected nodes from the -local cluster state. If `false` the list of selected nodes are computed -from the cluster state of the master node. In both cases the coordinating -node will send requests for further information to each selected node. - +=== client.indices.create [discrete] -==== transforms -Get transforms. -Returns configuration and usage information about transforms. - -CAT APIs are only intended for human consumption using the Kibana -console or command line. They are not intended for use by applications. For -application consumption, use the get transform statistics API. - -{ref}/cat-transforms.html[Endpoint documentation] -[source,ts] ----- -client.cat.transforms({ ... }) ----- - +=== client.indices.createDataStream [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (Optional, string)*: A transform identifier or a wildcard expression. -If you do not specify one of these options, the API returns information for all transforms. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: contains wildcard expressions and there are no transforms that match; contains the `_all` string or no identifiers and there are no matches; contains wildcard expressions and there are only partial matches. -If `true`, it returns an empty transforms array when there are no matches and the subset of results when there are partial matches. -If `false`, the request returns a 404 status code when there are no matches or only partial matches. -** *`from` (Optional, number)*: Skips the specified number of transforms. -** *`h` (Optional, Enum("changes_last_detection_time" | "checkpoint" | "checkpoint_duration_time_exp_avg" | "checkpoint_progress" | "create_time" | "delete_time" | "description" | "dest_index" | "documents_deleted" | "documents_indexed" | "docs_per_second" | "documents_processed" | "frequency" | "id" | "index_failure" | "index_time" | "index_total" | "indexed_documents_exp_avg" | "last_search_time" | "max_page_search_size" | "pages_processed" | "pipeline" | "processed_documents_exp_avg" | "processing_time" | "reason" | "search_failure" | "search_time" | "search_total" | "source_index" | "state" | "transform_type" | "trigger_count" | "version") | Enum("changes_last_detection_time" | "checkpoint" | "checkpoint_duration_time_exp_avg" | "checkpoint_progress" | "create_time" | "delete_time" | "description" | "dest_index" | "documents_deleted" | "documents_indexed" | "docs_per_second" | "documents_processed" | "frequency" | "id" | "index_failure" | "index_time" | "index_total" | "indexed_documents_exp_avg" | "last_search_time" | "max_page_search_size" | "pages_processed" | "pipeline" | "processed_documents_exp_avg" | "processing_time" | "reason" | "search_failure" | "search_time" | "search_total" | "source_index" | "state" | "transform_type" | "trigger_count" | "version")[])*: List of column names to display. -** *`s` (Optional, Enum("changes_last_detection_time" | "checkpoint" | "checkpoint_duration_time_exp_avg" | "checkpoint_progress" | "create_time" | "delete_time" | "description" | "dest_index" | "documents_deleted" | "documents_indexed" | "docs_per_second" | "documents_processed" | "frequency" | "id" | "index_failure" | "index_time" | "index_total" | "indexed_documents_exp_avg" | "last_search_time" | "max_page_search_size" | "pages_processed" | "pipeline" | "processed_documents_exp_avg" | "processing_time" | "reason" | "search_failure" | "search_time" | "search_total" | "source_index" | "state" | "transform_type" | "trigger_count" | "version") | Enum("changes_last_detection_time" | "checkpoint" | "checkpoint_duration_time_exp_avg" | "checkpoint_progress" | "create_time" | "delete_time" | "description" | "dest_index" | "documents_deleted" | "documents_indexed" | "docs_per_second" | "documents_processed" | "frequency" | "id" | "index_failure" | "index_time" | "index_total" | "indexed_documents_exp_avg" | "last_search_time" | "max_page_search_size" | "pages_processed" | "pipeline" | "processed_documents_exp_avg" | "processing_time" | "reason" | "search_failure" | "search_time" | "search_total" | "source_index" | "state" | "transform_type" | "trigger_count" | "version")[])*: List of column names or column aliases used to sort the response. -** *`time` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: The unit used to display time values. -** *`size` (Optional, number)*: The maximum number of transforms to obtain. - +=== client.indices.dataStreamsStats [discrete] -=== ccr +=== client.indices.delete [discrete] -==== delete_auto_follow_pattern -Deletes auto-follow patterns. - -{ref}/ccr-delete-auto-follow-pattern.html[Endpoint documentation] -[source,ts] ----- -client.ccr.deleteAutoFollowPattern({ name }) ----- - +=== client.indices.deleteAlias [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the auto follow pattern. - +=== client.indices.deleteDataLifecycle [discrete] -==== follow -Creates a new follower index configured to follow the referenced leader index. - -{ref}/ccr-put-follow.html[Endpoint documentation] -[source,ts] ----- -client.ccr.follow({ index, leader_index, remote_cluster }) ----- - +=== client.indices.deleteDataStream [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: The name of the follower index. -** *`leader_index` (string)*: The name of the index in the leader cluster to follow. -** *`remote_cluster` (string)*: The remote cluster containing the leader index. -** *`data_stream_name` (Optional, string)*: If the leader index is part of a data stream, the name to which the local data stream for the followed index should be renamed. -** *`max_outstanding_read_requests` (Optional, number)*: The maximum number of outstanding reads requests from the remote cluster. -** *`max_outstanding_write_requests` (Optional, number)*: The maximum number of outstanding write requests on the follower. -** *`max_read_request_operation_count` (Optional, number)*: The maximum number of operations to pull per read from the remote cluster. -** *`max_read_request_size` (Optional, number | string)*: The maximum size in bytes of per read of a batch of operations pulled from the remote cluster. -** *`max_retry_delay` (Optional, string | -1 | 0)*: The maximum time to wait before retrying an operation that failed exceptionally. An exponential backoff strategy is employed when -retrying. -** *`max_write_buffer_count` (Optional, number)*: The maximum number of operations that can be queued for writing. When this limit is reached, reads from the remote cluster will be -deferred until the number of queued operations goes below the limit. -** *`max_write_buffer_size` (Optional, number | string)*: The maximum total bytes of operations that can be queued for writing. When this limit is reached, reads from the remote cluster will -be deferred until the total bytes of queued operations goes below the limit. -** *`max_write_request_operation_count` (Optional, number)*: The maximum number of operations per bulk write request executed on the follower. -** *`max_write_request_size` (Optional, number | string)*: The maximum total bytes of operations per bulk write request executed on the follower. -** *`read_poll_timeout` (Optional, string | -1 | 0)*: The maximum time to wait for new operations on the remote cluster when the follower index is synchronized with the leader index. -When the timeout has elapsed, the poll for operations will return to the follower so that it can update some statistics. -Then the follower will immediately attempt to read from the leader again. -** *`settings` (Optional, { index, mode, routing_path, soft_deletes, sort, number_of_shards, number_of_replicas, number_of_routing_shards, check_on_startup, codec, routing_partition_size, load_fixed_bitset_filters_eagerly, hidden, auto_expand_replicas, merge, search, refresh_interval, max_result_window, max_inner_result_window, max_rescore_window, max_docvalue_fields_search, max_script_fields, max_ngram_diff, max_shingle_diff, blocks, max_refresh_listeners, analyze, highlight, max_terms_count, max_regex_length, routing, gc_deletes, default_pipeline, final_pipeline, lifecycle, provided_name, creation_date, creation_date_string, uuid, version, verified_before_close, format, max_slices_per_scroll, translog, query_string, priority, top_metrics_max_size, analysis, settings, time_series, queries, similarity, mapping, indexing.slowlog, indexing_pressure, store })*: Settings to override from the leader index. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: Specifies the number of shards to wait on being active before responding. This defaults to waiting on none of the shards to be -active. -A shard must be restored from the leader index before being active. Restoring a follower shard requires transferring all the -remote Lucene segment files to the follower index. - +=== client.indices.deleteIndexTemplate [discrete] -==== follow_info -Retrieves information about all follower indices, including parameters and status for each follower index - -{ref}/ccr-get-follow-info.html[Endpoint documentation] -[source,ts] ----- -client.ccr.followInfo({ index }) ----- - +=== client.indices.deleteTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: A list of index patterns; use `_all` to perform the operation on all indices - +=== client.indices.diskUsage [discrete] -==== follow_stats -Retrieves follower stats. return shard-level stats about the following tasks associated with each shard for the specified indices. - -{ref}/ccr-get-follow-stats.html[Endpoint documentation] -[source,ts] ----- -client.ccr.followStats({ index }) ----- - +=== client.indices.downsample [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: A list of index patterns; use `_all` to perform the operation on all indices - +=== client.indices.exists [discrete] -==== forget_follower -Removes the follower retention leases from the leader. - -{ref}/ccr-post-forget-follower.html[Endpoint documentation] -[source,ts] ----- -client.ccr.forgetFollower({ index }) ----- - +=== client.indices.existsAlias [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: the name of the leader index for which specified follower retention leases should be removed -** *`follower_cluster` (Optional, string)* -** *`follower_index` (Optional, string)* -** *`follower_index_uuid` (Optional, string)* -** *`leader_remote_cluster` (Optional, string)* - +=== client.indices.existsIndexTemplate [discrete] -==== get_auto_follow_pattern -Gets configured auto-follow patterns. Returns the specified auto-follow pattern collection. - -{ref}/ccr-get-auto-follow-pattern.html[Endpoint documentation] -[source,ts] ----- -client.ccr.getAutoFollowPattern({ ... }) ----- - +=== client.indices.existsTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: Specifies the auto-follow pattern collection that you want to retrieve. If you do not specify a name, the API returns information for all collections. - +=== client.indices.explainDataLifecycle [discrete] -==== pause_auto_follow_pattern -Pauses an auto-follow pattern - -{ref}/ccr-pause-auto-follow-pattern.html[Endpoint documentation] -[source,ts] ----- -client.ccr.pauseAutoFollowPattern({ name }) ----- - +=== client.indices.fieldUsageStats [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the auto follow pattern that should pause discovering new indices to follow. - +=== client.indices.flush [discrete] -==== pause_follow -Pauses a follower index. The follower index will not fetch any additional operations from the leader index. - -{ref}/ccr-post-pause-follow.html[Endpoint documentation] -[source,ts] ----- -client.ccr.pauseFollow({ index }) ----- - +=== client.indices.forcemerge [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: The name of the follower index that should pause following its leader index. - +=== client.indices.get [discrete] -==== put_auto_follow_pattern -Creates a new named collection of auto-follow patterns against a specified remote cluster. Newly created indices on the remote cluster matching any of the specified patterns will be automatically configured as follower indices. - -{ref}/ccr-put-auto-follow-pattern.html[Endpoint documentation] -[source,ts] ----- -client.ccr.putAutoFollowPattern({ name, remote_cluster }) ----- - +=== client.indices.getAlias [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the collection of auto-follow patterns. -** *`remote_cluster` (string)*: The remote cluster containing the leader indices to match against. -** *`follow_index_pattern` (Optional, string)*: The name of follower index. The template {{leader_index}} can be used to derive the name of the follower index from the name of the leader index. When following a data stream, use {{leader_index}}; CCR does not support changes to the names of a follower data stream’s backing indices. -** *`leader_index_patterns` (Optional, string[])*: An array of simple index patterns to match against indices in the remote cluster specified by the remote_cluster field. -** *`leader_index_exclusion_patterns` (Optional, string[])*: An array of simple index patterns that can be used to exclude indices from being auto-followed. Indices in the remote cluster whose names are matching one or more leader_index_patterns and one or more leader_index_exclusion_patterns won’t be followed. -** *`max_outstanding_read_requests` (Optional, number)*: The maximum number of outstanding reads requests from the remote cluster. -** *`settings` (Optional, Record)*: Settings to override from the leader index. Note that certain settings can not be overrode (e.g., index.number_of_shards). -** *`max_outstanding_write_requests` (Optional, number)*: The maximum number of outstanding reads requests from the remote cluster. -** *`read_poll_timeout` (Optional, string | -1 | 0)*: The maximum time to wait for new operations on the remote cluster when the follower index is synchronized with the leader index. When the timeout has elapsed, the poll for operations will return to the follower so that it can update some statistics. Then the follower will immediately attempt to read from the leader again. -** *`max_read_request_operation_count` (Optional, number)*: The maximum number of operations to pull per read from the remote cluster. -** *`max_read_request_size` (Optional, number | string)*: The maximum size in bytes of per read of a batch of operations pulled from the remote cluster. -** *`max_retry_delay` (Optional, string | -1 | 0)*: The maximum time to wait before retrying an operation that failed exceptionally. An exponential backoff strategy is employed when retrying. -** *`max_write_buffer_count` (Optional, number)*: The maximum number of operations that can be queued for writing. When this limit is reached, reads from the remote cluster will be deferred until the number of queued operations goes below the limit. -** *`max_write_buffer_size` (Optional, number | string)*: The maximum total bytes of operations that can be queued for writing. When this limit is reached, reads from the remote cluster will be deferred until the total bytes of queued operations goes below the limit. -** *`max_write_request_operation_count` (Optional, number)*: The maximum number of operations per bulk write request executed on the follower. -** *`max_write_request_size` (Optional, number | string)*: The maximum total bytes of operations per bulk write request executed on the follower. - +=== client.indices.getDataLifecycle [discrete] -==== resume_auto_follow_pattern -Resumes an auto-follow pattern that has been paused - -{ref}/ccr-resume-auto-follow-pattern.html[Endpoint documentation] -[source,ts] ----- -client.ccr.resumeAutoFollowPattern({ name }) ----- - +=== client.indices.getDataStream [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the auto follow pattern to resume discovering new indices to follow. - +=== client.indices.getFieldMapping [discrete] -==== resume_follow -Resumes a follower index that has been paused - -{ref}/ccr-post-resume-follow.html[Endpoint documentation] -[source,ts] ----- -client.ccr.resumeFollow({ index }) ----- - +=== client.indices.getIndexTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: The name of the follow index to resume following. -** *`max_outstanding_read_requests` (Optional, number)* -** *`max_outstanding_write_requests` (Optional, number)* -** *`max_read_request_operation_count` (Optional, number)* -** *`max_read_request_size` (Optional, string)* -** *`max_retry_delay` (Optional, string | -1 | 0)* -** *`max_write_buffer_count` (Optional, number)* -** *`max_write_buffer_size` (Optional, string)* -** *`max_write_request_operation_count` (Optional, number)* -** *`max_write_request_size` (Optional, string)* -** *`read_poll_timeout` (Optional, string | -1 | 0)* - +=== client.indices.getMapping [discrete] -==== stats -Gets all stats related to cross-cluster replication. - -{ref}/ccr-get-stats.html[Endpoint documentation] -[source,ts] ----- -client.ccr.stats() ----- - - +=== client.indices.getSettings [discrete] -==== unfollow -Stops the following task associated with a follower index and removes index metadata and settings associated with cross-cluster replication. - -{ref}/ccr-post-unfollow.html[Endpoint documentation] -[source,ts] ----- -client.ccr.unfollow({ index }) ----- - +=== client.indices.getTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: The name of the follower index that should be turned into a regular index. - +=== client.indices.migrateToDataStream [discrete] -=== cluster +=== client.indices.modifyDataStream [discrete] -==== allocation_explain -Provides explanations for shard allocations in the cluster. - -{ref}/cluster-allocation-explain.html[Endpoint documentation] -[source,ts] ----- -client.cluster.allocationExplain({ ... }) ----- - +=== client.indices.open [discrete] -==== Arguments - -* *Request (object):* -** *`current_node` (Optional, string)*: Specifies the node ID or the name of the node to only explain a shard that is currently located on the specified node. -** *`index` (Optional, string)*: Specifies the name of the index that you would like an explanation for. -** *`primary` (Optional, boolean)*: If true, returns explanation for the primary shard for the given shard ID. -** *`shard` (Optional, number)*: Specifies the ID of the shard that you would like an explanation for. -** *`include_disk_info` (Optional, boolean)*: If true, returns information about disk usage and shard sizes. -** *`include_yes_decisions` (Optional, boolean)*: If true, returns YES decisions in explanation. - +=== client.indices.promoteDataStream [discrete] -==== delete_component_template -Delete component templates. -Deletes component templates. -Component templates are building blocks for constructing index templates that specify index mappings, settings, and aliases. - -{ref}/indices-component-template.html[Endpoint documentation] -[source,ts] ----- -client.cluster.deleteComponentTemplate({ name }) ----- - +=== client.indices.putAlias [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: List or wildcard expression of component template names used to limit the request. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.indices.putDataLifecycle [discrete] -==== delete_voting_config_exclusions -Clears cluster voting config exclusions. - -{ref}/voting-config-exclusions.html[Endpoint documentation] -[source,ts] ----- -client.cluster.deleteVotingConfigExclusions({ ... }) ----- - +=== client.indices.putIndexTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`wait_for_removal` (Optional, boolean)*: Specifies whether to wait for all excluded nodes to be removed from the -cluster before clearing the voting configuration exclusions list. -Defaults to true, meaning that all excluded nodes must be removed from -the cluster before this API takes any action. If set to false then the -voting configuration exclusions list is cleared even if some excluded -nodes are still in the cluster. - +=== client.indices.putMapping [discrete] -==== exists_component_template -Check component templates. -Returns information about whether a particular component template exists. - -{ref}/indices-component-template.html[Endpoint documentation] -[source,ts] ----- -client.cluster.existsComponentTemplate({ name }) ----- - +=== client.indices.putSettings [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: List of component template names used to limit the request. -Wildcard (*) expressions are supported. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is -received before the timeout expires, the request fails and returns an -error. -** *`local` (Optional, boolean)*: If true, the request retrieves information from the local node only. -Defaults to false, which means information is retrieved from the master node. - +=== client.indices.putTemplate [discrete] -==== get_component_template -Get component templates. -Retrieves information about component templates. - -{ref}/indices-component-template.html[Endpoint documentation] -[source,ts] ----- -client.cluster.getComponentTemplate({ ... }) ----- - +=== client.indices.recovery [discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: List of component template names used to limit the request. -Wildcard (`*`) expressions are supported. -** *`flat_settings` (Optional, boolean)*: If `true`, returns settings in flat format. -** *`include_defaults` (Optional, boolean)*: Return all default configurations for the component template (default: false) -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. -If `false`, information is retrieved from the master node. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.indices.refresh [discrete] -==== get_settings -Returns cluster-wide settings. -By default, it returns only settings that have been explicitly defined. - -{ref}/cluster-get-settings.html[Endpoint documentation] -[source,ts] ----- -client.cluster.getSettings({ ... }) ----- - +=== client.indices.reloadSearchAnalyzers [discrete] -==== Arguments - -* *Request (object):* -** *`flat_settings` (Optional, boolean)*: If `true`, returns settings in flat format. -** *`include_defaults` (Optional, boolean)*: If `true`, returns default cluster settings from the local node. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.indices.resolveCluster [discrete] -==== health -The cluster health API returns a simple status on the health of the cluster. You can also use the API to get the health status of only specified data streams and indices. For data streams, the API retrieves the health status of the stream’s backing indices. -The cluster health status is: green, yellow or red. On the shard level, a red status indicates that the specific shard is not allocated in the cluster, yellow means that the primary shard is allocated but replicas are not, and green means that all shards are allocated. The index level status is controlled by the worst shard status. The cluster status is controlled by the worst index status. - -{ref}/cluster-health.html[Endpoint documentation] -[source,ts] ----- -client.cluster.health({ ... }) ----- - +=== client.indices.resolveIndex [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and index aliases used to limit the request. Wildcard expressions (`*`) are supported. To target all data streams and indices in a cluster, omit this parameter or use _all or `*`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`level` (Optional, Enum("cluster" | "indices" | "shards"))*: Can be one of cluster, indices or shards. Controls the details level of the health information returned. -** *`local` (Optional, boolean)*: If true, the request retrieves information from the local node only. Defaults to false, which means information is retrieved from the master node. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: A number controlling to how many active shards to wait for, all to wait for all shards in the cluster to be active, or 0 to not wait. -** *`wait_for_events` (Optional, Enum("immediate" | "urgent" | "high" | "normal" | "low" | "languid"))*: Can be one of immediate, urgent, high, normal, low, languid. Wait until all currently queued events with the given priority are processed. -** *`wait_for_nodes` (Optional, string | number)*: The request waits until the specified number N of nodes is available. It also accepts >=N, <=N, >N and yellow > red. By default, will not wait for any status. - +=== client.indices.rollover [discrete] -==== info -Get cluster info. -Returns basic information about the cluster. - -{ref}/cluster-info.html[Endpoint documentation] -[source,ts] ----- -client.cluster.info({ target }) ----- - +=== client.indices.segments [discrete] -==== Arguments - -* *Request (object):* -** *`target` (Enum("_all" | "http" | "ingest" | "thread_pool" | "script") | Enum("_all" | "http" | "ingest" | "thread_pool" | "script")[])*: Limits the information returned to the specific target. Supports a list, such as http,ingest. - +=== client.indices.shardStores [discrete] -==== pending_tasks -Returns cluster-level changes (such as create index, update mapping, allocate or fail shard) that have not yet been executed. -NOTE: This API returns a list of any pending updates to the cluster state. -These are distinct from the tasks reported by the Task Management API which include periodic tasks and tasks initiated by the user, such as node stats, search queries, or create index requests. -However, if a user-initiated task such as a create index command causes a cluster state update, the activity of this task might be reported by both task api and pending cluster tasks API. - -{ref}/cluster-pending.html[Endpoint documentation] -[source,ts] ----- -client.cluster.pendingTasks({ ... }) ----- - +=== client.indices.shrink [discrete] -==== Arguments - -* *Request (object):* -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. -If `false`, information is retrieved from the master node. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.indices.simulateIndexTemplate [discrete] -==== post_voting_config_exclusions -Updates the cluster voting config exclusions by node ids or node names. - -{ref}/voting-config-exclusions.html[Endpoint documentation] -[source,ts] ----- -client.cluster.postVotingConfigExclusions({ ... }) ----- - +=== client.indices.simulateTemplate [discrete] -==== Arguments - -* *Request (object):* -** *`node_names` (Optional, string | string[])*: A list of the names of the nodes to exclude from the -voting configuration. If specified, you may not also specify node_ids. -** *`node_ids` (Optional, string | string[])*: A list of the persistent ids of the nodes to exclude -from the voting configuration. If specified, you may not also specify node_names. -** *`timeout` (Optional, string | -1 | 0)*: When adding a voting configuration exclusion, the API waits for the -specified nodes to be excluded from the voting configuration before -returning. If the timeout expires before the appropriate condition -is satisfied, the request fails and returns an error. - +=== client.indices.split [discrete] -==== put_component_template -Create or update a component template. -Creates or updates a component template. -Component templates are building blocks for constructing index templates that specify index mappings, settings, and aliases. - -An index template can be composed of multiple component templates. -To use a component template, specify it in an index template’s `composed_of` list. -Component templates are only applied to new data streams and indices as part of a matching index template. - -Settings and mappings specified directly in the index template or the create index request override any settings or mappings specified in a component template. - -Component templates are only used during index creation. -For data streams, this includes data stream creation and the creation of a stream’s backing indices. -Changes to component templates do not affect existing indices, including a stream’s backing indices. - -You can use C-style `/* *\/` block comments in component templates. -You can include comments anywhere in the request body except before the opening curly bracket. - -{ref}/indices-component-template.html[Endpoint documentation] -[source,ts] ----- -client.cluster.putComponentTemplate({ name, template }) ----- - +=== client.indices.stats [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Name of the component template to create. -Elasticsearch includes the following built-in component templates: `logs-mappings`; `logs-settings`; `metrics-mappings`; `metrics-settings`;`synthetics-mapping`; `synthetics-settings`. -Elastic Agent uses these templates to configure backing indices for its data streams. -If you use Elastic Agent and want to overwrite one of these templates, set the `version` for your replacement template higher than the current version. -If you don’t use Elastic Agent and want to disable all built-in component and index templates, set `stack.templates.enabled` to `false` using the cluster update settings API. -** *`template` ({ aliases, mappings, settings, defaults, data_stream, lifecycle })*: The template to be applied which includes mappings, settings, or aliases configuration. -** *`version` (Optional, number)*: Version number used to manage component templates externally. -This number isn't automatically generated or incremented by Elasticsearch. -To unset a version, replace the template without specifying a version. -** *`_meta` (Optional, Record)*: Optional user metadata about the component template. -May have any contents. This map is not automatically generated by Elasticsearch. -This information is stored in the cluster state, so keeping it short is preferable. -To unset `_meta`, replace the template without specifying this information. -** *`deprecated` (Optional, boolean)*: Marks this index template as deprecated. When creating or updating a non-deprecated index template -that uses deprecated components, Elasticsearch will emit a deprecation warning. -** *`create` (Optional, boolean)*: If `true`, this request cannot replace or update existing component templates. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.indices.unfreeze [discrete] -==== put_settings -Updates the cluster settings. - -{ref}/cluster-update-settings.html[Endpoint documentation] -[source,ts] ----- -client.cluster.putSettings({ ... }) ----- - +=== client.indices.updateAliases [discrete] -==== Arguments - -* *Request (object):* -** *`persistent` (Optional, Record)* -** *`transient` (Optional, Record)* -** *`flat_settings` (Optional, boolean)*: Return settings in flat format (default: false) -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout - +=== client.indices.validateQuery [discrete] -==== remote_info -The cluster remote info API allows you to retrieve all of the configured -remote cluster information. It returns connection and endpoint information -keyed by the configured remote cluster alias. - -{ref}/cluster-remote-info.html[Endpoint documentation] -[source,ts] ----- -client.cluster.remoteInfo() ----- - - +=== client.inference.delete [discrete] -==== reroute -Allows to manually change the allocation of individual shards in the cluster. - -{ref}/cluster-reroute.html[Endpoint documentation] -[source,ts] ----- -client.cluster.reroute({ ... }) ----- - +=== client.inference.get [discrete] -==== Arguments - -* *Request (object):* -** *`commands` (Optional, { cancel, move, allocate_replica, allocate_stale_primary, allocate_empty_primary }[])*: Defines the commands to perform. -** *`dry_run` (Optional, boolean)*: If true, then the request simulates the operation only and returns the resulting state. -** *`explain` (Optional, boolean)*: If true, then the response contains an explanation of why the commands can or cannot be executed. -** *`metric` (Optional, string | string[])*: Limits the information returned to the specified metrics. -** *`retry_failed` (Optional, boolean)*: If true, then retries allocation of shards that are blocked due to too many subsequent allocation failures. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.inference.inference [discrete] -==== state -Returns a comprehensive information about the state of the cluster. - -{ref}/cluster-state.html[Endpoint documentation] -[source,ts] ----- -client.cluster.state({ ... }) ----- - +=== client.inference.put [discrete] -==== Arguments - -* *Request (object):* -** *`metric` (Optional, string | string[])*: Limit the information returned to the specified metrics -** *`index` (Optional, string | string[])*: A list of index names; use `_all` or empty string to perform the operation on all indices -** *`allow_no_indices` (Optional, boolean)*: Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified) -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`flat_settings` (Optional, boolean)*: Return settings in flat format (default: false) -** *`ignore_unavailable` (Optional, boolean)*: Whether specified concrete indices should be ignored when unavailable (missing or closed) -** *`local` (Optional, boolean)*: Return local information, do not retrieve the state from master node (default: false) -** *`master_timeout` (Optional, string | -1 | 0)*: Specify timeout for connection to master -** *`wait_for_metadata_version` (Optional, number)*: Wait for the metadata version to be equal or greater than the specified metadata version -** *`wait_for_timeout` (Optional, string | -1 | 0)*: The maximum time to wait for wait_for_metadata_version before timing out - +=== client.inference.streamInference [discrete] -==== stats -Returns cluster statistics. -It returns basic index metrics (shard numbers, store size, memory usage) and information about the current nodes that form the cluster (number, roles, os, jvm versions, memory usage, cpu and installed plugins). - -{ref}/cluster-stats.html[Endpoint documentation] -[source,ts] ----- -client.cluster.stats({ ... }) ----- - +=== client.info [discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: List of node filters used to limit returned information. Defaults to all nodes in the cluster. -** *`include_remotes` (Optional, boolean)*: Include remote cluster data into the response -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for each node to respond. -If a node does not respond before its timeout expires, the response does not include its stats. -However, timed out nodes are included in the response’s `_nodes.failed` property. Defaults to no timeout. - +=== client.ingest.deleteGeoipDatabase [discrete] -=== connector +=== client.ingest.deletePipeline [discrete] -==== check_in -Check in a connector. - -Update the `last_seen` field in the connector and set it to the current timestamp. - -{ref}/check-in-connector-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.checkIn({ connector_id }) ----- - +=== client.ingest.geoIpStats [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be checked in - +=== client.ingest.getGeoipDatabase [discrete] -==== delete -Delete a connector. - -Removes a connector and associated sync jobs. -This is a destructive action that is not recoverable. -NOTE: This action doesn’t delete any API keys, ingest pipelines, or data indices associated with the connector. -These need to be removed manually. - -{ref}/delete-connector-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.delete({ connector_id }) ----- - +=== client.ingest.getPipeline [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be deleted -** *`delete_sync_jobs` (Optional, boolean)*: A flag indicating if associated sync jobs should be also removed. Defaults to false. - +=== client.ingest.processorGrok [discrete] -==== get -Get a connector. - -Get the details about a connector. - -{ref}/get-connector-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.get({ connector_id }) ----- - +=== client.ingest.putGeoipDatabase [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector - +=== client.ingest.putPipeline [discrete] -==== list -Get all connectors. - -Get information about all connectors. - -{ref}/list-connector-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.list({ ... }) ----- - +=== client.ingest.simulate [discrete] -==== Arguments - -* *Request (object):* -** *`from` (Optional, number)*: Starting offset (default: 0) -** *`size` (Optional, number)*: Specifies a max number of results to get -** *`index_name` (Optional, string | string[])*: A list of connector index names to fetch connector documents for -** *`connector_name` (Optional, string | string[])*: A list of connector names to fetch connector documents for -** *`service_type` (Optional, string | string[])*: A list of connector service types to fetch connector documents for -** *`query` (Optional, string)*: A wildcard query string that filters connectors with matching name, description or index name - +=== client.knnSearch [discrete] -==== post -Create a connector. - -Connectors are Elasticsearch integrations that bring content from third-party data sources, which can be deployed on Elastic Cloud or hosted on your own infrastructure. -Elastic managed connectors (Native connectors) are a managed service on Elastic Cloud. -Self-managed connectors (Connector clients) are self-managed on your infrastructure. - -{ref}/create-connector-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.post({ ... }) ----- - +=== client.license.delete [discrete] -==== Arguments - -* *Request (object):* -** *`description` (Optional, string)* -** *`index_name` (Optional, string)* -** *`is_native` (Optional, boolean)* -** *`language` (Optional, string)* -** *`name` (Optional, string)* -** *`service_type` (Optional, string)* - +=== client.license.get [discrete] -==== put -Create or update a connector. - -{ref}/create-connector-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.put({ ... }) ----- - +=== client.license.getBasicStatus [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (Optional, string)*: The unique identifier of the connector to be created or updated. ID is auto-generated if not provided. -** *`description` (Optional, string)* -** *`index_name` (Optional, string)* -** *`is_native` (Optional, boolean)* -** *`language` (Optional, string)* -** *`name` (Optional, string)* -** *`service_type` (Optional, string)* - +=== client.license.getTrialStatus [discrete] -==== sync_job_cancel -Cancel a connector sync job. - -Cancel a connector sync job, which sets the status to cancelling and updates `cancellation_requested_at` to the current time. -The connector service is then responsible for setting the status of connector sync jobs to cancelled. - -{ref}/cancel-connector-sync-job-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobCancel({ connector_sync_job_id }) ----- - +=== client.license.post [discrete] -==== Arguments - -* *Request (object):* -** *`connector_sync_job_id` (string)*: The unique identifier of the connector sync job - +=== client.license.postStartBasic [discrete] -==== sync_job_check_in -Checks in a connector sync job (refreshes 'last_seen'). - -{ref}/check-in-connector-sync-job-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobCheckIn() ----- - - +=== client.license.postStartTrial [discrete] -==== sync_job_claim -Claims a connector sync job. -[source,ts] ----- -client.connector.syncJobClaim() ----- - - +=== client.logstash.deletePipeline [discrete] -==== sync_job_delete -Delete a connector sync job. - -Remove a connector sync job and its associated data. -This is a destructive action that is not recoverable. - -{ref}/delete-connector-sync-job-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobDelete({ connector_sync_job_id }) ----- - +=== client.logstash.getPipeline [discrete] -==== Arguments - -* *Request (object):* -** *`connector_sync_job_id` (string)*: The unique identifier of the connector sync job to be deleted - +=== client.logstash.putPipeline [discrete] -==== sync_job_error -Sets an error for a connector sync job. - -{ref}/set-connector-sync-job-error-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobError() ----- - - +=== client.mget [discrete] -==== sync_job_get -Get a connector sync job. - -{ref}/get-connector-sync-job-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobGet({ connector_sync_job_id }) ----- - +=== client.migration.deprecations [discrete] -==== Arguments - -* *Request (object):* -** *`connector_sync_job_id` (string)*: The unique identifier of the connector sync job - +=== client.migration.getFeatureUpgradeStatus [discrete] -==== sync_job_list -Get all connector sync jobs. - -Get information about all stored connector sync jobs listed by their creation date in ascending order. - -{ref}/list-connector-sync-jobs-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobList({ ... }) ----- - +=== client.migration.postFeatureUpgrade [discrete] -==== Arguments - -* *Request (object):* -** *`from` (Optional, number)*: Starting offset (default: 0) -** *`size` (Optional, number)*: Specifies a max number of results to get -** *`status` (Optional, Enum("canceling" | "canceled" | "completed" | "error" | "in_progress" | "pending" | "suspended"))*: A sync job status to fetch connector sync jobs for -** *`connector_id` (Optional, string)*: A connector id to fetch connector sync jobs for -** *`job_type` (Optional, Enum("full" | "incremental" | "access_control") | Enum("full" | "incremental" | "access_control")[])*: A list of job types to fetch the sync jobs for - +=== client.ml.clearTrainedModelDeploymentCache [discrete] -==== sync_job_post -Create a connector sync job. - -Create a connector sync job document in the internal index and initialize its counters and timestamps with default values. - -{ref}/create-connector-sync-job-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobPost({ id }) ----- - +=== client.ml.closeJob [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: The id of the associated connector -** *`job_type` (Optional, Enum("full" | "incremental" | "access_control"))* -** *`trigger_method` (Optional, Enum("on_demand" | "scheduled"))* - +=== client.ml.deleteCalendar [discrete] -==== sync_job_update_stats -Updates the stats fields in the connector sync job document. - -{ref}/set-connector-sync-job-stats-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.syncJobUpdateStats() ----- - - +=== client.ml.deleteCalendarEvent [discrete] -==== update_active_filtering -Activate the connector draft filter. - -Activates the valid draft filtering for a connector. - -{ref}/update-connector-filtering-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateActiveFiltering({ connector_id }) ----- - +=== client.ml.deleteCalendarJob [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated - +=== client.ml.deleteDataFrameAnalytics [discrete] -==== update_api_key_id -Update the connector API key ID. - -Update the `api_key_id` and `api_key_secret_id` fields of a connector. -You can specify the ID of the API key used for authorization and the ID of the connector secret where the API key is stored. -The connector secret ID is required only for Elastic managed (native) connectors. -Self-managed connectors (connector clients) do not use this field. - -{ref}/update-connector-api-key-id-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateApiKeyId({ connector_id }) ----- - +=== client.ml.deleteDatafeed [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`api_key_id` (Optional, string)* -** *`api_key_secret_id` (Optional, string)* - +=== client.ml.deleteExpiredData [discrete] -==== update_configuration -Update the connector configuration. - -Update the configuration field in the connector document. - -{ref}/update-connector-configuration-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateConfiguration({ connector_id }) ----- - +=== client.ml.deleteFilter [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`configuration` (Optional, Record)* -** *`values` (Optional, Record)* - +=== client.ml.deleteForecast [discrete] -==== update_error -Update the connector error field. - -Set the error field for the connector. -If the error provided in the request body is non-null, the connector’s status is updated to error. -Otherwise, if the error is reset to null, the connector status is updated to connected. - -{ref}/update-connector-error-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateError({ connector_id, error }) ----- - +=== client.ml.deleteJob [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`error` (T | null)* - +=== client.ml.deleteModelSnapshot [discrete] -==== update_features -Updates the connector features in the connector document. - -{ref}/update-connector-features-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateFeatures() ----- - - +=== client.ml.deleteTrainedModel [discrete] -==== update_filtering -Update the connector filtering. - -Update the draft filtering configuration of a connector and marks the draft validation state as edited. -The filtering draft is activated once validated by the running Elastic connector service. -The filtering property is used to configure sync rules (both basic and advanced) for a connector. - -{ref}/update-connector-filtering-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateFiltering({ connector_id }) ----- - +=== client.ml.deleteTrainedModelAlias [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`filtering` (Optional, { active, domain, draft }[])* -** *`rules` (Optional, { created_at, field, id, order, policy, rule, updated_at, value }[])* -** *`advanced_snippet` (Optional, { created_at, updated_at, value })* - +=== client.ml.estimateModelMemory [discrete] -==== update_filtering_validation -Update the connector draft filtering validation. - -Update the draft filtering validation info for a connector. -[source,ts] ----- -client.connector.updateFilteringValidation({ connector_id, validation }) ----- - +=== client.ml.evaluateDataFrame [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`validation` ({ errors, state })* - +=== client.ml.explainDataFrameAnalytics [discrete] -==== update_index_name -Update the connector index name. - -Update the `index_name` field of a connector, specifying the index where the data ingested by the connector is stored. - -{ref}/update-connector-index-name-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateIndexName({ connector_id, index_name }) ----- - +=== client.ml.flushJob [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`index_name` (T | null)* - +=== client.ml.forecast [discrete] -==== update_name -Update the connector name and description. - -{ref}/update-connector-name-description-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateName({ connector_id }) ----- - +=== client.ml.getBuckets [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`name` (Optional, string)* -** *`description` (Optional, string)* - +=== client.ml.getCalendarEvents [discrete] -==== update_native -Update the connector is_native flag. -[source,ts] ----- -client.connector.updateNative({ connector_id, is_native }) ----- - +=== client.ml.getCalendars [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`is_native` (boolean)* - +=== client.ml.getCategories [discrete] -==== update_pipeline -Update the connector pipeline. - -When you create a new connector, the configuration of an ingest pipeline is populated with default settings. - -{ref}/update-connector-pipeline-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updatePipeline({ connector_id, pipeline }) ----- - +=== client.ml.getDataFrameAnalytics [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`pipeline` ({ extract_binary_content, name, reduce_whitespace, run_ml_inference })* - +=== client.ml.getDataFrameAnalyticsStats [discrete] -==== update_scheduling -Update the connector scheduling. - -{ref}/update-connector-scheduling-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateScheduling({ connector_id, scheduling }) ----- - +=== client.ml.getDatafeedStats [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`scheduling` ({ access_control, full, incremental })* - +=== client.ml.getDatafeeds [discrete] -==== update_service_type -Update the connector service type. - -{ref}/update-connector-service-type-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateServiceType({ connector_id, service_type }) ----- - +=== client.ml.getFilters [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`service_type` (string)* - +=== client.ml.getInfluencers [discrete] -==== update_status -Update the connector status. - -{ref}/update-connector-status-api.html[Endpoint documentation] -[source,ts] ----- -client.connector.updateStatus({ connector_id, status }) ----- - +=== client.ml.getJobStats [discrete] -==== Arguments - -* *Request (object):* -** *`connector_id` (string)*: The unique identifier of the connector to be updated -** *`status` (Enum("created" | "needs_configuration" | "configured" | "connected" | "error"))* - +=== client.ml.getJobs [discrete] -=== dangling_indices +=== client.ml.getMemoryStats [discrete] -==== delete_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. - -{ref}/modules-gateway-dangling-indices.html[Endpoint documentation] -[source,ts] ----- -client.danglingIndices.deleteDanglingIndex({ index_uuid, accept_data_loss }) ----- - +=== client.ml.getModelSnapshotUpgradeStats [discrete] -==== Arguments - -* *Request (object):* -** *`index_uuid` (string)*: The UUID of the index to delete. Use the get dangling indices API to find the UUID. -** *`accept_data_loss` (boolean)*: This parameter must be set to true to acknowledge that it will no longer be possible to recove data from the dangling index. -** *`master_timeout` (Optional, string | -1 | 0)*: Specify timeout for connection to master -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout - +=== client.ml.getModelSnapshots [discrete] -==== import_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. - -{ref}/modules-gateway-dangling-indices.html[Endpoint documentation] -[source,ts] ----- -client.danglingIndices.importDanglingIndex({ index_uuid, accept_data_loss }) ----- - +=== client.ml.getOverallBuckets [discrete] -==== Arguments - -* *Request (object):* -** *`index_uuid` (string)*: The UUID of the index to import. Use the get dangling indices API to locate the UUID. -** *`accept_data_loss` (boolean)*: 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. -** *`master_timeout` (Optional, string | -1 | 0)*: Specify timeout for connection to master -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout - +=== client.ml.getRecords [discrete] -==== list_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. - -{ref}/modules-gateway-dangling-indices.html[Endpoint documentation] -[source,ts] ----- -client.danglingIndices.listDanglingIndices() ----- - - +=== client.ml.getTrainedModels [discrete] -=== enrich +=== client.ml.getTrainedModelsStats [discrete] -==== delete_policy -Delete an enrich policy. -Deletes an existing enrich policy and its enrich index. - -{ref}/delete-enrich-policy-api.html[Endpoint documentation] -[source,ts] ----- -client.enrich.deletePolicy({ name }) ----- - +=== client.ml.inferTrainedModel [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Enrich policy to delete. - +=== client.ml.info [discrete] -==== execute_policy -Creates the enrich index for an existing enrich policy. - -{ref}/execute-enrich-policy-api.html[Endpoint documentation] -[source,ts] ----- -client.enrich.executePolicy({ name }) ----- - +=== client.ml.openJob [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Enrich policy to execute. -** *`wait_for_completion` (Optional, boolean)*: If `true`, the request blocks other enrich policy execution requests until complete. - +=== client.ml.postCalendarEvents [discrete] -==== get_policy -Get an enrich policy. -Returns information about an enrich policy. - -{ref}/get-enrich-policy-api.html[Endpoint documentation] -[source,ts] ----- -client.enrich.getPolicy({ ... }) ----- - +=== client.ml.postData [discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string | string[])*: List of enrich policy names used to limit the request. -To return information for all enrich policies, omit this parameter. - +=== client.ml.previewDataFrameAnalytics [discrete] -==== put_policy -Create an enrich policy. -Creates an enrich policy. - -{ref}/put-enrich-policy-api.html[Endpoint documentation] -[source,ts] ----- -client.enrich.putPolicy({ name }) ----- - +=== client.ml.previewDatafeed [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Name of the enrich policy to create or update. -** *`geo_match` (Optional, { enrich_fields, indices, match_field, query, name, elasticsearch_version })*: Matches enrich data to incoming documents based on a `geo_shape` query. -** *`match` (Optional, { enrich_fields, indices, match_field, query, name, elasticsearch_version })*: Matches enrich data to incoming documents based on a `term` query. -** *`range` (Optional, { enrich_fields, indices, match_field, query, name, elasticsearch_version })*: Matches a number, date, or IP address in incoming documents to a range in the enrich index based on a `term` query. - +=== client.ml.putCalendar [discrete] -==== stats -Get enrich stats. -Returns enrich coordinator statistics and information about enrich policies that are currently executing. - -{ref}/enrich-stats-api.html[Endpoint documentation] -[source,ts] ----- -client.enrich.stats() ----- - - +=== client.ml.putCalendarJob [discrete] -=== eql +=== client.ml.putDataFrameAnalytics [discrete] -==== delete -Deletes an async EQL search or a stored synchronous EQL search. -The API also deletes results for the search. - -{ref}/eql-search-api.html[Endpoint documentation] -[source,ts] ----- -client.eql.delete({ id }) ----- - +=== client.ml.putDatafeed [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the search to delete. -A search ID is provided in the EQL search API's response for an async search. -A search ID is also provided if the request’s `keep_on_completion` parameter is `true`. - +=== client.ml.putFilter [discrete] -==== get -Returns the current status and available results for an async EQL search or a stored synchronous EQL search. - -{ref}/get-async-eql-search-api.html[Endpoint documentation] -[source,ts] ----- -client.eql.get({ id }) ----- - +=== client.ml.putJob [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the search. -** *`keep_alive` (Optional, string | -1 | 0)*: Period for which the search and its results are stored on the cluster. -Defaults to the keep_alive value set by the search’s EQL search API request. -** *`wait_for_completion_timeout` (Optional, string | -1 | 0)*: Timeout duration to wait for the request to finish. -Defaults to no timeout, meaning the request waits for complete search results. - +=== client.ml.putTrainedModel [discrete] -==== get_status -Returns the current status for an async EQL search or a stored synchronous EQL search without returning results. - -{ref}/get-async-eql-status-api.html[Endpoint documentation] -[source,ts] ----- -client.eql.getStatus({ id }) ----- - +=== client.ml.putTrainedModelAlias [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the search. - +=== client.ml.putTrainedModelDefinitionPart [discrete] -==== search -Returns results matching a query expressed in Event Query Language (EQL) - -{ref}/eql-search-api.html[Endpoint documentation] -[source,ts] ----- -client.eql.search({ index, query }) ----- - +=== client.ml.putTrainedModelVocabulary [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: The name of the index to scope the operation -** *`query` (string)*: EQL query you wish to run. -** *`case_sensitive` (Optional, boolean)* -** *`event_category_field` (Optional, string)*: Field containing the event classification, such as process, file, or network. -** *`tiebreaker_field` (Optional, string)*: Field used to sort hits with the same timestamp in ascending order -** *`timestamp_field` (Optional, string)*: Field containing event timestamp. Default "@timestamp" -** *`fetch_size` (Optional, number)*: Maximum number of events to search at a time for sequence queries. -** *`filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type } | { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type }[])*: Query, written in Query DSL, used to filter the events on which the EQL query runs. -** *`keep_alive` (Optional, string | -1 | 0)* -** *`keep_on_completion` (Optional, boolean)* -** *`wait_for_completion_timeout` (Optional, string | -1 | 0)* -** *`size` (Optional, number)*: For basic queries, the maximum number of matching events to return. Defaults to 10 -** *`fields` (Optional, { field, format, include_unmapped } | { field, format, include_unmapped }[])*: Array of wildcard (*) patterns. The response returns values for field names matching these patterns in the fields property of each hit. -** *`result_position` (Optional, Enum("tail" | "head"))* -** *`runtime_mappings` (Optional, Record)* -** *`max_samples_per_key` (Optional, number)*: By default, the response of a sample query contains up to `10` samples, with one sample per unique set of join keys. Use the `size` -parameter to get a smaller or larger set of samples. To retrieve more than one sample per set of join keys, use the -`max_samples_per_key` parameter. Pipes are not supported for sample queries. -** *`allow_no_indices` (Optional, boolean)* -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])* -** *`ignore_unavailable` (Optional, boolean)*: If true, missing or closed indices are not included in the response. - +=== client.ml.resetJob [discrete] -=== esql +=== client.ml.revertModelSnapshot [discrete] -==== async_query -Executes an ESQL request asynchronously - -{ref}/esql-async-query-api.html[Endpoint documentation] -[source,ts] ----- -client.esql.asyncQuery() ----- - - +=== client.ml.setUpgradeMode [discrete] -==== async_query_get -Retrieves the results of a previously submitted async query request given its ID. - -{ref}/esql-async-query-get-api.html[Endpoint documentation] -[source,ts] ----- -client.esql.asyncQueryGet() ----- - - +=== client.ml.startDataFrameAnalytics [discrete] -==== query -Executes an ES|QL request - -{ref}/esql-rest.html[Endpoint documentation] -[source,ts] ----- -client.esql.query({ query }) ----- - +=== client.ml.startDatafeed [discrete] -==== Arguments - -* *Request (object):* -** *`query` (string)*: The ES|QL query API accepts an ES|QL query string in the query parameter, runs it, and returns the results. -** *`columnar` (Optional, boolean)*: By default, ES|QL returns results as rows. For example, FROM returns each individual document as one row. For the JSON, YAML, CBOR and smile formats, ES|QL can return the results in a columnar fashion where one row represents all the values of a certain column in the results. -** *`filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Specify a Query DSL query in the filter parameter to filter the set of documents that an ES|QL query runs on. -** *`locale` (Optional, string)* -** *`params` (Optional, number | number | string | boolean | null | User-defined value[])*: To avoid any attempts of hacking or code injection, extract the values in a separate list of parameters. Use question mark placeholders (?) in the query string for each of the parameters. -** *`profile` (Optional, boolean)*: If provided and `true` the response will include an extra `profile` object -with information on how the query was executed. This information is for human debugging -and its format can change at any time but it can give some insight into the performance -of each part of the query. -** *`tables` (Optional, Record>)*: Tables to use with the LOOKUP operation. The top level key is the table -name and the next level key is the column name. -** *`format` (Optional, Enum("csv" | "json" | "tsv" | "txt" | "yaml" | "cbor" | "smile" | "arrow"))*: A short version of the Accept header, e.g. json, yaml. -** *`delimiter` (Optional, string)*: The character to use between values within a CSV row. Only valid for the CSV format. -** *`drop_null_columns` (Optional, boolean)*: Should columns that are entirely `null` be removed from the `columns` and `values` portion of the results? -Defaults to `false`. If `true` then the response will include an extra section under the name `all_columns` which has the name of all columns. - +=== client.ml.startTrainedModelDeployment [discrete] -=== features +=== client.ml.stopDataFrameAnalytics [discrete] -==== get_features -Gets a list of features which can be included in snapshots using the feature_states field when creating a snapshot - -{ref}/get-features-api.html[Endpoint documentation] -[source,ts] ----- -client.features.getFeatures() ----- - - +=== client.ml.stopDatafeed [discrete] -==== reset_features -Resets the internal state of features, usually by deleting system indices - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.features.resetFeatures() ----- - - +=== client.ml.stopTrainedModelDeployment [discrete] -=== fleet +=== client.ml.updateDataFrameAnalytics [discrete] -==== global_checkpoints -Returns the current global checkpoints for an index. This API is design for internal use by the fleet server project. - -{ref}/get-global-checkpoints.html[Endpoint documentation] -[source,ts] ----- -client.fleet.globalCheckpoints({ index }) ----- - +=== client.ml.updateDatafeed [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string)*: A single index or index alias that resolves to a single index. -** *`wait_for_advance` (Optional, boolean)*: A boolean value which controls whether to wait (until the timeout) for the global checkpoints -to advance past the provided `checkpoints`. -** *`wait_for_index` (Optional, boolean)*: A boolean value which controls whether to wait (until the timeout) for the target index to exist -and all primary shards be active. Can only be true when `wait_for_advance` is true. -** *`checkpoints` (Optional, number[])*: A comma separated list of previous global checkpoints. When used in combination with `wait_for_advance`, -the API will only return once the global checkpoints advances past the checkpoints. Providing an empty list -will cause Elasticsearch to immediately return the current global checkpoints. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a global checkpoints to advance past `checkpoints`. - +=== client.ml.updateFilter [discrete] -==== msearch -Executes several [fleet searches](https://www.elastic.co/guide/en/elasticsearch/reference/current/fleet-search.html) with a single API request. -The API follows the same structure as the [multi search](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-multi-search.html) API. However, similar to the fleet search API, it -supports the wait_for_checkpoints parameter. -[source,ts] ----- -client.fleet.msearch({ ... }) ----- - +=== client.ml.updateJob [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string)*: A single target to search. If the target is an index alias, it must resolve to a single index. -** *`searches` (Optional, { allow_no_indices, expand_wildcards, ignore_unavailable, index, preference, request_cache, routing, search_type, ccs_minimize_roundtrips, allow_partial_search_results, ignore_throttled } | { aggregations, collapse, query, explain, ext, stored_fields, docvalue_fields, knn, from, highlight, indices_boost, min_score, post_filter, profile, rescore, script_fields, search_after, size, sort, _source, fields, terminate_after, stats, timeout, track_scores, track_total_hits, version, runtime_mappings, seq_no_primary_term, pit, suggest }[])* -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`ccs_minimize_roundtrips` (Optional, boolean)*: If true, network roundtrips between the coordinating node and remote clusters are minimized for cross-cluster search requests. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of index that wildcard expressions can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. -** *`ignore_throttled` (Optional, boolean)*: If true, concrete, expanded or aliased indices are ignored when frozen. -** *`ignore_unavailable` (Optional, boolean)*: If true, missing or closed indices are not included in the response. -** *`max_concurrent_searches` (Optional, number)*: Maximum number of concurrent searches the multi search API can execute. -** *`max_concurrent_shard_requests` (Optional, number)*: Maximum number of concurrent shard requests that each sub-search request executes per node. -** *`pre_filter_shard_size` (Optional, number)*: Defines a threshold that enforces a pre-filter roundtrip to prefilter search shards based on query rewriting if the number of shards the search request expands to exceeds the threshold. This filter roundtrip can limit the number of shards significantly if for instance a shard can not match any documents based on its rewrite method i.e., if date filters are mandatory to match but the shard bounds and the query are disjoint. -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))*: Indicates whether global term and document frequencies should be used when scoring returned documents. -** *`rest_total_hits_as_int` (Optional, boolean)*: If true, hits.total are returned as an integer in the response. Defaults to false, which returns an object. -** *`typed_keys` (Optional, boolean)*: Specifies whether aggregation and suggester names should be prefixed by their respective types in the response. -** *`wait_for_checkpoints` (Optional, number[])*: A comma separated list of checkpoints. When configured, the search API will only be executed on a shard -after the relevant checkpoint has become visible for search. Defaults to an empty list which will cause -Elasticsearch to immediately execute the search. -** *`allow_partial_search_results` (Optional, boolean)*: If true, returns partial results if there are shard request timeouts or [shard failures](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-replication.html#shard-failures). If false, returns -an error with no partial results. Defaults to the configured cluster setting `search.default_allow_partial_results` -which is true by default. - +=== client.ml.updateModelSnapshot [discrete] -==== search -The purpose of the fleet search api is to provide a search api where the search will only be executed -after provided checkpoint has been processed and is visible for searches inside of Elasticsearch. -[source,ts] ----- -client.fleet.search({ index }) ----- - +=== client.ml.updateTrainedModelDeployment [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string)*: A single target to search. If the target is an index alias, it must resolve to a single index. -** *`aggregations` (Optional, Record)* -** *`collapse` (Optional, { field, inner_hits, max_concurrent_group_searches, collapse })* -** *`explain` (Optional, boolean)*: If true, returns detailed information about score computation as part of a hit. -** *`ext` (Optional, Record)*: Configuration of search extensions defined by Elasticsearch plugins. -** *`from` (Optional, number)*: Starting document offset. By default, you cannot page through more than 10,000 -hits using the from and size parameters. To page through more hits, use the -search_after parameter. -** *`highlight` (Optional, { encoder, fields })* -** *`track_total_hits` (Optional, boolean | number)*: Number of hits matching the query to count accurately. If true, the exact -number of hits is returned at the cost of some performance. If false, the -response does not include the total number of hits matching the query. -Defaults to 10,000 hits. -** *`indices_boost` (Optional, Record[])*: Boosts the _score of documents from specified indices. -** *`docvalue_fields` (Optional, { field, format, include_unmapped }[])*: Array of wildcard (*) patterns. The request returns doc values for field -names matching these patterns in the hits.fields property of the response. -** *`min_score` (Optional, number)*: Minimum _score for matching documents. Documents with a lower _score are -not included in the search results. -** *`post_filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })* -** *`profile` (Optional, boolean)* -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Defines the search definition using the Query DSL. -** *`rescore` (Optional, { window_size, query, learning_to_rank } | { window_size, query, learning_to_rank }[])* -** *`script_fields` (Optional, Record)*: Retrieve a script evaluation (based on different fields) for each hit. -** *`search_after` (Optional, number | number | string | boolean | null | User-defined value[])* -** *`size` (Optional, number)*: The number of hits to return. By default, you cannot page through more -than 10,000 hits using the from and size parameters. To page through more -hits, use the search_after parameter. -** *`slice` (Optional, { field, id, max })* -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])* -** *`_source` (Optional, boolean | { excludes, includes })*: Indicates which source fields are returned for matching documents. These -fields are returned in the hits._source property of the search response. -** *`fields` (Optional, { field, format, include_unmapped }[])*: Array of wildcard (*) patterns. The request returns values for field names -matching these patterns in the hits.fields property of the response. -** *`suggest` (Optional, { text })* -** *`terminate_after` (Optional, number)*: 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. Defaults to 0, which does not terminate query execution early. -** *`timeout` (Optional, string)*: Specifies the period of time to wait for a response from each shard. If no response -is received before the timeout expires, the request fails and returns an error. -Defaults to no timeout. -** *`track_scores` (Optional, boolean)*: If true, calculate and return document scores, even if the scores are not used for sorting. -** *`version` (Optional, boolean)*: If true, returns document version as part of a hit. -** *`seq_no_primary_term` (Optional, boolean)*: If true, returns sequence number and primary term of the last modification -of each hit. See Optimistic concurrency control. -** *`stored_fields` (Optional, string | string[])*: List of stored fields to return as part of a hit. If no fields are specified, -no stored fields are included in the response. If this field is specified, the _source -parameter defaults to false. You can pass _source: true to return both source fields -and stored fields in the search response. -** *`pit` (Optional, { id, keep_alive })*: Limits the search to a point in time (PIT). If you provide a PIT, you -cannot specify an in the request path. -** *`runtime_mappings` (Optional, Record)*: Defines one or more runtime fields in the search request. These fields take -precedence over mapped fields with the same name. -** *`stats` (Optional, string[])*: Stats groups to associate with the search. Each group maintains a statistics -aggregation for its associated searches. You can retrieve these stats using -the indices stats API. -** *`allow_no_indices` (Optional, boolean)* -** *`analyzer` (Optional, string)* -** *`analyze_wildcard` (Optional, boolean)* -** *`batched_reduce_size` (Optional, number)* -** *`ccs_minimize_roundtrips` (Optional, boolean)* -** *`default_operator` (Optional, Enum("and" | "or"))* -** *`df` (Optional, string)* -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])* -** *`ignore_throttled` (Optional, boolean)* -** *`ignore_unavailable` (Optional, boolean)* -** *`lenient` (Optional, boolean)* -** *`max_concurrent_shard_requests` (Optional, number)* -** *`preference` (Optional, string)* -** *`pre_filter_shard_size` (Optional, number)* -** *`request_cache` (Optional, boolean)* -** *`routing` (Optional, string)* -** *`scroll` (Optional, string | -1 | 0)* -** *`search_type` (Optional, Enum("query_then_fetch" | "dfs_query_then_fetch"))* -** *`suggest_field` (Optional, string)*: Specifies which field to use for suggestions. -** *`suggest_mode` (Optional, Enum("missing" | "popular" | "always"))* -** *`suggest_size` (Optional, number)* -** *`suggest_text` (Optional, string)*: The source text for which the suggestions should be returned. -** *`typed_keys` (Optional, boolean)* -** *`rest_total_hits_as_int` (Optional, boolean)* -** *`_source_excludes` (Optional, string | string[])* -** *`_source_includes` (Optional, string | string[])* -** *`q` (Optional, string)* -** *`wait_for_checkpoints` (Optional, number[])*: A comma separated list of checkpoints. When configured, the search API will only be executed on a shard -after the relevant checkpoint has become visible for search. Defaults to an empty list which will cause -Elasticsearch to immediately execute the search. -** *`allow_partial_search_results` (Optional, boolean)*: If true, returns partial results if there are shard request timeouts or [shard failures](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-replication.html#shard-failures). If false, returns -an error with no partial results. Defaults to the configured cluster setting `search.default_allow_partial_results` -which is true by default. - +=== client.ml.upgradeJobSnapshot [discrete] -=== graph +=== client.monitoring.bulk [discrete] -==== explore -Extracts and summarizes information about the documents and terms in an Elasticsearch data stream or index. - -{ref}/graph-explore-api.html[Endpoint documentation] -[source,ts] ----- -client.graph.explore({ index }) ----- - +=== client.msearch [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: Name of the index. -** *`connections` (Optional, { connections, query, vertices })*: Specifies or more fields from which you want to extract terms that are associated with the specified vertices. -** *`controls` (Optional, { sample_diversity, sample_size, timeout, use_significance })*: Direct the Graph API how to build the graph. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: A seed query that identifies the documents of interest. Can be any valid Elasticsearch query. -** *`vertices` (Optional, { exclude, field, include, min_doc_count, shard_min_doc_count, size }[])*: Specifies one or more fields that contain the terms you want to include in the graph as vertices. -** *`routing` (Optional, string)*: Custom value used to route operations to a specific shard. -** *`timeout` (Optional, string | -1 | 0)*: Specifies the period of time to wait for a response from each shard. -If no response is received before the timeout expires, the request fails and returns an error. -Defaults to no timeout. - +=== client.msearchTemplate [discrete] -=== ilm +=== client.mtermvectors [discrete] -==== delete_lifecycle -Deletes the specified lifecycle policy definition. You cannot delete policies that are currently in use. If the policy is being used to manage any indices, the request fails and returns an error. - -{ref}/ilm-delete-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.ilm.deleteLifecycle({ policy }) ----- - +=== client.nodes.clearRepositoriesMeteringArchive [discrete] -==== Arguments - -* *Request (object):* -** *`policy` (string)*: Identifier for the policy. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.nodes.getRepositoriesMeteringInfo [discrete] -==== explain_lifecycle -Retrieves information about the index’s current lifecycle state, such as the currently executing phase, action, and step. Shows when the index entered each one, the definition of the running phase, and information about any failures. - -{ref}/ilm-explain-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.ilm.explainLifecycle({ index }) ----- - +=== client.nodes.hotThreads [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: List of data streams, indices, and aliases to target. Supports wildcards (`*`). -To target all data streams and indices, use `*` or `_all`. -** *`only_errors` (Optional, boolean)*: Filters the returned indices to only indices that are managed by ILM and are in an error state, either due to an encountering an error while executing the policy, or attempting to use a policy that does not exist. -** *`only_managed` (Optional, boolean)*: Filters the returned indices to only indices that are managed by ILM. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.nodes.info [discrete] -==== get_lifecycle -Retrieves a lifecycle policy. - -{ref}/ilm-get-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.ilm.getLifecycle({ ... }) ----- - +=== client.nodes.reloadSecureSettings [discrete] -==== Arguments - -* *Request (object):* -** *`policy` (Optional, string)*: Identifier for the policy. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.nodes.stats [discrete] -==== get_status -Retrieves the current index lifecycle management (ILM) status. - -{ref}/ilm-get-status.html[Endpoint documentation] -[source,ts] ----- -client.ilm.getStatus() ----- - - +=== client.nodes.usage [discrete] -==== migrate_to_data_tiers -Switches the indices, ILM policies, and legacy, composable and component templates from using custom node attributes and -attribute-based allocation filters to using data tiers, and optionally deletes one legacy index template.+ -Using node roles enables ILM to automatically move the indices between data tiers. - -{ref}/ilm-migrate-to-data-tiers.html[Endpoint documentation] -[source,ts] ----- -client.ilm.migrateToDataTiers({ ... }) ----- - +=== client.openPointInTime [discrete] -==== Arguments - -* *Request (object):* -** *`legacy_template_to_delete` (Optional, string)* -** *`node_attribute` (Optional, string)* -** *`dry_run` (Optional, boolean)*: If true, simulates the migration from node attributes based allocation filters to data tiers, but does not perform the migration. -This provides a way to retrieve the indices and ILM policies that need to be migrated. - +=== client.ping [discrete] -==== move_to_step -Manually moves an index into the specified step and executes that step. - -{ref}/ilm-move-to-step.html[Endpoint documentation] -[source,ts] ----- -client.ilm.moveToStep({ index, current_step, next_step }) ----- - +=== client.putScript [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: The name of the index whose lifecycle step is to change -** *`current_step` ({ action, name, phase })* -** *`next_step` ({ action, name, phase })* - +=== client.queryRules.deleteRule [discrete] -==== put_lifecycle -Creates a lifecycle policy. If the specified policy exists, the policy is replaced and the policy version is incremented. - -{ref}/ilm-put-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.ilm.putLifecycle({ policy }) ----- - +=== client.queryRules.deleteRuleset [discrete] -==== Arguments - -* *Request (object):* -** *`policy` (string)*: Identifier for the policy. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.queryRules.getRule [discrete] -==== remove_policy -Removes the assigned lifecycle policy and stops managing the specified index - -{ref}/ilm-remove-policy.html[Endpoint documentation] -[source,ts] ----- -client.ilm.removePolicy({ index }) ----- - +=== client.queryRules.getRuleset [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: The name of the index to remove policy on - +=== client.queryRules.listRulesets [discrete] -==== retry -Retries executing the policy for an index that is in the ERROR step. - -{ref}/ilm-retry-policy.html[Endpoint documentation] -[source,ts] ----- -client.ilm.retry({ index }) ----- - +=== client.queryRules.putRule [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: The name of the indices (comma-separated) whose failed lifecycle step is to be retry - +=== client.queryRules.putRuleset [discrete] -==== start -Start the index lifecycle management (ILM) plugin. - -{ref}/ilm-start.html[Endpoint documentation] -[source,ts] ----- -client.ilm.start({ ... }) ----- - +=== client.queryRules.test [discrete] -==== Arguments - -* *Request (object):* -** *`master_timeout` (Optional, string | -1 | 0)* -** *`timeout` (Optional, string | -1 | 0)* - +=== client.rankEval [discrete] -==== stop -Halts all lifecycle management operations and stops the index lifecycle management (ILM) plugin - -{ref}/ilm-stop.html[Endpoint documentation] -[source,ts] ----- -client.ilm.stop({ ... }) ----- - +=== client.reindex [discrete] -==== Arguments - -* *Request (object):* -** *`master_timeout` (Optional, string | -1 | 0)* -** *`timeout` (Optional, string | -1 | 0)* - +=== client.reindexRethrottle [discrete] -=== indices +=== client.renderSearchTemplate [discrete] -==== add_block -Add an index block. -Limits the operations allowed on an index by blocking specific operation types. - -{ref}/index-modules-blocks.html[Endpoint documentation] -[source,ts] ----- -client.indices.addBlock({ index, block }) ----- - +=== client.rollup.deleteJob [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: A comma separated list of indices to add a block to -** *`block` (Enum("metadata" | "read" | "read_only" | "write"))*: The block to add (one of read, write, read_only or metadata) -** *`allow_no_indices` (Optional, boolean)*: Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified) -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`ignore_unavailable` (Optional, boolean)*: Whether specified concrete indices should be ignored when unavailable (missing or closed) -** *`master_timeout` (Optional, string | -1 | 0)*: Specify timeout for connection to master -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout - +=== client.rollup.getJobs [discrete] -==== analyze -Get tokens from text analysis. -The analyze API performs [analysis](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis.html) on a text string and returns the resulting tokens. - -{ref}/indices-analyze.html[Endpoint documentation] -[source,ts] ----- -client.indices.analyze({ ... }) ----- - +=== client.rollup.getRollupCaps [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string)*: Index used to derive the analyzer. -If specified, the `analyzer` or field parameter overrides this value. -If no index is specified or the index does not have a default analyzer, the analyze API uses the standard analyzer. -** *`analyzer` (Optional, string)*: The name of the analyzer that should be applied to the provided `text`. -This could be a built-in analyzer, or an analyzer that’s been configured in the index. -** *`attributes` (Optional, string[])*: Array of token attributes used to filter the output of the `explain` parameter. -** *`char_filter` (Optional, string | { type, escaped_tags } | { type, mappings, mappings_path } | { type, flags, pattern, replacement } | { type, mode, name } | { type, normalize_kana, normalize_kanji }[])*: Array of character filters used to preprocess characters before the tokenizer. -** *`explain` (Optional, boolean)*: If `true`, the response includes token attributes and additional details. -** *`field` (Optional, string)*: Field used to derive the analyzer. -To use this parameter, you must specify an index. -If specified, the `analyzer` parameter overrides this value. -** *`filter` (Optional, string | { type, preserve_original } | { type, common_words, common_words_path, ignore_case, query_mode } | { type, filter, script } | { type, delimiter, encoding } | { type, max_gram, min_gram, side, preserve_original } | { type, articles, articles_path, articles_case } | { type, max_output_size, separator } | { type, dedup, dictionary, locale, longest_only } | { type } | { type, mode, types } | { type, keep_words, keep_words_case, keep_words_path } | { type, ignore_case, keywords, keywords_path, keywords_pattern } | { type } | { type, max, min } | { type, consume_all_tokens, max_token_count } | { type, language } | { type, filters, preserve_original } | { type, max_gram, min_gram, preserve_original } | { type, stoptags } | { type, patterns, preserve_original } | { type, all, flags, pattern, replacement } | { type } | { type, script } | { type } | { type } | { type, filler_token, max_shingle_size, min_shingle_size, output_unigrams, output_unigrams_if_no_shingles, token_separator } | { type, language } | { type, rules, rules_path } | { type, language } | { type, ignore_case, remove_trailing, stopwords, stopwords_path } | { type, expand, format, lenient, synonyms, synonyms_path, synonyms_set, tokenizer, updateable } | { type, expand, format, lenient, synonyms, synonyms_path, synonyms_set, tokenizer, updateable } | { type } | { type, length } | { type, only_on_same_position } | { type } | { type, adjust_offsets, catenate_all, catenate_numbers, catenate_words, generate_number_parts, generate_word_parts, ignore_keywords, preserve_original, protected_words, protected_words_path, split_on_case_change, split_on_numerics, stem_english_possessive, type_table, type_table_path } | { type, catenate_all, catenate_numbers, catenate_words, generate_number_parts, generate_word_parts, preserve_original, protected_words, protected_words_path, split_on_case_change, split_on_numerics, stem_english_possessive, type_table, type_table_path } | { type, minimum_length } | { type, use_romaji } | { type, stoptags } | { type, alternate, case_first, case_level, country, decomposition, hiragana_quaternary_mode, language, numeric, rules, strength, variable_top, variant } | { type, unicode_set_filter } | { type, name } | { type, dir, id } | { type, encoder, languageset, max_code_len, name_type, replace, rule_type } | { type }[])*: Array of token filters used to apply after the tokenizer. -** *`normalizer` (Optional, string)*: Normalizer to use to convert text into a single token. -** *`text` (Optional, string | string[])*: Text to analyze. -If an array of strings is provided, it is analyzed as a multi-value field. -** *`tokenizer` (Optional, string | { type, tokenize_on_chars, max_token_length } | { type, max_token_length } | { type, custom_token_chars, max_gram, min_gram, token_chars } | { type, buffer_size } | { type } | { type } | { type, custom_token_chars, max_gram, min_gram, token_chars } | { type, buffer_size, delimiter, replacement, reverse, skip } | { type, flags, group, pattern } | { type, pattern } | { type, pattern } | { type, max_token_length } | { type } | { type, max_token_length } | { type, max_token_length } | { type, rule_files } | { type, discard_punctuation, mode, nbest_cost, nbest_examples, user_dictionary, user_dictionary_rules, discard_compound_token } | { type, decompound_mode, discard_punctuation, user_dictionary, user_dictionary_rules })*: Tokenizer to use to convert text into tokens. - +=== client.rollup.getRollupIndexCaps [discrete] -==== clear_cache -Clears the caches of one or more indices. -For data streams, the API clears the caches of the stream’s backing indices. - -{ref}/indices-clearcache.html[Endpoint documentation] -[source,ts] ----- -client.indices.clearCache({ ... }) ----- - +=== client.rollup.putJob [discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`fielddata` (Optional, boolean)*: If `true`, clears the fields cache. -Use the `fields` parameter to clear the cache of specific fields only. -** *`fields` (Optional, string | string[])*: List of field names used to limit the `fielddata` parameter. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`query` (Optional, boolean)*: If `true`, clears the query cache. -** *`request` (Optional, boolean)*: If `true`, clears the request cache. - +=== client.rollup.rollupSearch [discrete] -==== clone -Clones an existing index. - -{ref}/indices-clone-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.clone({ index, target }) ----- - +=== client.rollup.startJob [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Name of the source index to clone. -** *`target` (string)*: Name of the target index to create. -** *`aliases` (Optional, Record)*: Aliases for the resulting index. -** *`settings` (Optional, Record)*: Configuration options for the target index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - +=== client.rollup.stopJob [discrete] -==== close -Closes an index. - -{ref}/indices-close.html[Endpoint documentation] -[source,ts] ----- -client.indices.close({ index }) ----- - +=== client.scriptsPainlessExecute [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List or wildcard expression of index names used to limit the request. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - +=== client.scroll [discrete] -==== create -Create an index. -Creates a new index. - -{ref}/indices-create-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.create({ index }) ----- - +=== client.search [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Name of the index you wish to create. -** *`aliases` (Optional, Record)*: Aliases for the index. -** *`mappings` (Optional, { all_field, date_detection, dynamic, dynamic_date_formats, dynamic_templates, _field_names, index_field, _meta, numeric_detection, properties, _routing, _size, _source, runtime, enabled, subobjects, _data_stream_timestamp })*: Mapping for fields in the index. If specified, this mapping can include: -- Field names -- Field data types -- Mapping parameters -** *`settings` (Optional, { index, mode, routing_path, soft_deletes, sort, number_of_shards, number_of_replicas, number_of_routing_shards, check_on_startup, codec, routing_partition_size, load_fixed_bitset_filters_eagerly, hidden, auto_expand_replicas, merge, search, refresh_interval, max_result_window, max_inner_result_window, max_rescore_window, max_docvalue_fields_search, max_script_fields, max_ngram_diff, max_shingle_diff, blocks, max_refresh_listeners, analyze, highlight, max_terms_count, max_regex_length, routing, gc_deletes, default_pipeline, final_pipeline, lifecycle, provided_name, creation_date, creation_date_string, uuid, version, verified_before_close, format, max_slices_per_scroll, translog, query_string, priority, top_metrics_max_size, analysis, settings, time_series, queries, similarity, mapping, indexing.slowlog, indexing_pressure, store })*: Configuration options for the index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - +=== client.searchApplication.delete [discrete] -==== create_data_stream -Create a data stream. -Creates a data stream. -You must have a matching index template with data stream enabled. - -{ref}/data-streams.html[Endpoint documentation] -[source,ts] ----- -client.indices.createDataStream({ name }) ----- - +=== client.searchApplication.deleteBehavioralAnalytics [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Name of the data stream, which must meet the following criteria: -Lowercase only; -Cannot include `\`, `/`, `*`, `?`, `"`, `<`, `>`, `|`, `,`, `#`, `:`, or a space character; -Cannot start with `-`, `_`, `+`, or `.ds-`; -Cannot be `.` or `..`; -Cannot be longer than 255 bytes. Multi-byte characters count towards this limit faster. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.searchApplication.get [discrete] -==== data_streams_stats -Get data stream stats. -Retrieves statistics for one or more data streams. - -{ref}/data-streams.html[Endpoint documentation] -[source,ts] ----- -client.indices.dataStreamsStats({ ... }) ----- - +=== client.searchApplication.getBehavioralAnalytics [discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: List of data streams used to limit the request. -Wildcard expressions (`*`) are supported. -To target all data streams in a cluster, omit this parameter or use `*`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of data stream that wildcard patterns can match. -Supports a list of values, such as `open,hidden`. - +=== client.searchApplication.list [discrete] -==== delete -Delete indices. -Deletes one or more indices. - -{ref}/indices-delete-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.delete({ index }) ----- - +=== client.searchApplication.postBehavioralAnalyticsEvent [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of indices to delete. -You cannot specify index aliases. -By default, this parameter does not support wildcards (`*`) or `_all`. -To use wildcards or `_all`, set the `action.destructive_requires_name` cluster setting to `false`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.searchApplication.put [discrete] -==== delete_alias -Delete an alias. -Removes a data stream or index from an alias. - -{ref}/indices-aliases.html[Endpoint documentation] -[source,ts] ----- -client.indices.deleteAlias({ index, name }) ----- - +=== client.searchApplication.putBehavioralAnalytics [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams or indices used to limit the request. -Supports wildcards (`*`). -** *`name` (string | string[])*: List of aliases to remove. -Supports wildcards (`*`). To remove all aliases, use `*` or `_all`. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.searchApplication.renderQuery [discrete] -==== delete_data_lifecycle -Delete data stream lifecycles. -Removes the data stream lifecycle from a data stream, rendering it not managed by the data stream lifecycle. - -{ref}/data-streams-delete-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.indices.deleteDataLifecycle({ name }) ----- - +=== client.searchApplication.search [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: A list of data streams of which the data stream lifecycle will be deleted; use `*` to get all data streams -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether wildcard expressions should get expanded to open or closed indices (default: open) -** *`master_timeout` (Optional, string | -1 | 0)*: Specify timeout for connection to master -** *`timeout` (Optional, string | -1 | 0)*: Explicit timestamp for the document - +=== client.searchMvt [discrete] -==== delete_data_stream -Delete data streams. -Deletes one or more data streams and their backing indices. - -{ref}/data-streams.html[Endpoint documentation] -[source,ts] ----- -client.indices.deleteDataStream({ name }) ----- - +=== client.searchShards [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: List of data streams to delete. Wildcard (`*`) expressions are supported. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of data stream that wildcard patterns can match. Supports a list of values,such as `open,hidden`. - +=== client.searchTemplate [discrete] -==== delete_index_template -Delete an index template. -The provided may contain multiple template names separated by a comma. If multiple template -names are specified then there is no wildcard support and the provided names should match completely with -existing templates. - -{ref}/indices-delete-template.html[Endpoint documentation] -[source,ts] ----- -client.indices.deleteIndexTemplate({ name }) ----- - +=== client.searchableSnapshots.cacheStats [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: List of index template names used to limit the request. Wildcard (*) expressions are supported. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.searchableSnapshots.clearCache [discrete] -==== delete_template -Deletes a legacy index template. - -{ref}/indices-delete-template-v1.html[Endpoint documentation] -[source,ts] ----- -client.indices.deleteTemplate({ name }) ----- - +=== client.searchableSnapshots.mount [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the legacy index template to delete. -Wildcard (`*`) expressions are supported. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - +=== client.searchableSnapshots.stats [discrete] -==== disk_usage -Analyzes the disk usage of each field of an index or data stream. - -{ref}/indices-disk-usage.html[Endpoint documentation] -[source,ts] ----- -client.indices.diskUsage({ index }) ----- - +=== client.security.activateUserProfile [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams, indices, and aliases used to limit the request. -It’s recommended to execute this API with a single index (or the latest backing index of a data stream) as the API consumes resources significantly. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -** *`flush` (Optional, boolean)*: If `true`, the API performs a flush before analysis. -If `false`, the response may not include uncommitted data. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, missing or closed indices are not included in the response. -** *`run_expensive_tasks` (Optional, boolean)*: Analyzing field disk usage is resource-intensive. -To use the API, this parameter must be set to `true`. - +=== client.security.authenticate [discrete] -==== downsample -Aggregates a time series (TSDS) index and stores pre-computed statistical summaries (`min`, `max`, `sum`, `value_count` and `avg`) for each metric field grouped by a configured time interval. - -{ref}/indices-downsample-data-stream.html[Endpoint documentation] -[source,ts] ----- -client.indices.downsample({ index, target_index }) ----- - +=== client.security.bulkDeleteRole [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Name of the time series index to downsample. -** *`target_index` (string)*: Name of the index to create. -** *`config` (Optional, { fixed_interval })* - +=== client.security.bulkPutRole [discrete] -==== exists -Check indices. -Checks if one or more indices, index aliases, or data streams exist. - -{ref}/indices-exists.html[Endpoint documentation] -[source,ts] ----- -client.indices.exists({ index }) ----- - +=== client.security.bulkUpdateApiKeys [discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams, indices, and aliases. Supports wildcards (`*`). -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`flat_settings` (Optional, boolean)*: If `true`, returns settings in flat format. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`include_defaults` (Optional, boolean)*: If `true`, return all default settings in the response. -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. - +=== client.security.changePassword [discrete] -==== exists_alias -Check aliases. -Checks if one or more data stream or index aliases exist. - -{ref}/indices-aliases.html[Endpoint documentation] -[source,ts] ----- -client.indices.existsAlias({ name }) ----- - +=== client.security.clearApiKeyCache [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: List of aliases to check. Supports wildcards (`*`). -** *`index` (Optional, string | string[])*: List of data streams or indices used to limit the request. Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, requests that include a missing data stream or index in the target indices or data streams return an error. - +=== client.security.clearCachedPrivileges [discrete] -==== exists_index_template -Returns information about whether a particular index template exists. - -{ref}/index-templates.html[Endpoint documentation] -[source,ts] ----- -client.indices.existsIndexTemplate({ name }) ----- - +=== client.security.clearCachedRealms [discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: List of index template names used to limit the request. Wildcard (*) expressions are supported. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.security.clearCachedRoles [discrete] -==== exists_template -Check existence of index templates. -Returns information about whether a particular index template exists. - -{ref}/indices-template-exists-v1.html[Endpoint documentation] -[source,ts] ----- -client.indices.existsTemplate({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: The comma separated names of the index templates -** *`flat_settings` (Optional, boolean)*: Return settings in flat format (default: false) -** *`local` (Optional, boolean)*: Return local information, do not retrieve the state from master node (default: false) -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node - -[discrete] -==== explain_data_lifecycle -Get the status for a data stream lifecycle. -Retrieves information about an index or data stream’s current data stream lifecycle status, such as time since index creation, time since rollover, the lifecycle configuration managing the index, or any errors encountered during lifecycle execution. - -{ref}/data-streams-explain-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.indices.explainDataLifecycle({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: The name of the index to explain -** *`include_defaults` (Optional, boolean)*: indicates if the API should return the default values the system uses for the index's lifecycle -** *`master_timeout` (Optional, string | -1 | 0)*: Specify timeout for connection to master - -[discrete] -==== field_usage_stats -Returns field usage information for each shard and field of an index. - -{ref}/field-usage-stats.html[Endpoint documentation] -[source,ts] ----- -client.indices.fieldUsageStats({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List or wildcard expression of index names used to limit the request. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, missing or closed indices are not included in the response. -** *`fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in the statistics. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - -[discrete] -==== flush -Flushes one or more data streams or indices. - -{ref}/indices-flush.html[Endpoint documentation] -[source,ts] ----- -client.indices.flush({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases to flush. -Supports wildcards (`*`). -To flush all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`force` (Optional, boolean)*: If `true`, the request forces a flush even if there are no changes to commit to the index. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`wait_if_ongoing` (Optional, boolean)*: If `true`, the flush operation blocks until execution when another flush operation is running. -If `false`, Elasticsearch returns an error if you request a flush when another flush operation is running. - -[discrete] -==== forcemerge -Performs the force merge operation on one or more indices. - -{ref}/indices-forcemerge.html[Endpoint documentation] -[source,ts] ----- -client.indices.forcemerge({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: A list of index names; use `_all` or empty string to perform the operation on all indices -** *`allow_no_indices` (Optional, boolean)*: Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified) -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`flush` (Optional, boolean)*: Specify whether the index should be flushed after performing the operation (default: true) -** *`ignore_unavailable` (Optional, boolean)*: Whether specified concrete indices should be ignored when unavailable (missing or closed) -** *`max_num_segments` (Optional, number)*: The number of segments the index should be merged into (default: dynamic) -** *`only_expunge_deletes` (Optional, boolean)*: Specify whether the operation should only expunge deleted documents -** *`wait_for_completion` (Optional, boolean)*: Should the request wait until the force merge is completed. - -[discrete] -==== get -Get index information. -Returns information about one or more indices. For data streams, the API returns information about the -stream’s backing indices. - -{ref}/indices-get-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.get({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams, indices, and index aliases used to limit the request. -Wildcard expressions (*) are supported. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of index that wildcard expressions can match. If the request can target data streams, this argument -determines whether wildcard expressions match hidden data streams. Supports a list of values, -such as open,hidden. -** *`flat_settings` (Optional, boolean)*: If true, returns settings in flat format. -** *`ignore_unavailable` (Optional, boolean)*: If false, requests that target a missing index return an error. -** *`include_defaults` (Optional, boolean)*: If true, return all default settings in the response. -** *`local` (Optional, boolean)*: If true, the request retrieves information from the local node only. Defaults to false, which means information is retrieved from the master node. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`features` (Optional, { name, description } | { name, description }[])*: Return only information on specified index features - -[discrete] -==== get_alias -Get aliases. -Retrieves information for one or more data stream or index aliases. - -{ref}/indices-aliases.html[Endpoint documentation] -[source,ts] ----- -client.indices.getAlias({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string | string[])*: List of aliases to retrieve. -Supports wildcards (`*`). -To retrieve all aliases, omit this parameter or use `*` or `_all`. -** *`index` (Optional, string | string[])*: List of data streams or indices used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. - -[discrete] -==== get_data_lifecycle -Get data stream lifecycles. -Retrieves the data stream lifecycle configuration of one or more data streams. - -{ref}/data-streams-get-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.indices.getDataLifecycle({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: List of data streams to limit the request. -Supports wildcards (`*`). -To target all data streams, omit this parameter or use `*` or `_all`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of data stream that wildcard patterns can match. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`include_defaults` (Optional, boolean)*: If `true`, return all default settings in the response. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== get_data_stream -Get data streams. -Retrieves information about one or more data streams. - -{ref}/data-streams.html[Endpoint documentation] -[source,ts] ----- -client.indices.getDataStream({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string | string[])*: List of data stream names used to limit the request. -Wildcard (`*`) expressions are supported. If omitted, all data streams are returned. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of data stream that wildcard patterns can match. -Supports a list of values, such as `open,hidden`. -** *`include_defaults` (Optional, boolean)*: If true, returns all relevant default configurations for the index template. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`verbose` (Optional, boolean)*: Whether the maximum timestamp for each data stream should be calculated and returned. - -[discrete] -==== get_field_mapping -Get mapping definitions. -Retrieves mapping definitions for one or more fields. -For data streams, the API retrieves field mappings for the stream’s backing indices. - -{ref}/indices-get-field-mapping.html[Endpoint documentation] -[source,ts] ----- -client.indices.getFieldMapping({ fields }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`fields` (string | string[])*: List or wildcard expression of fields used to limit returned information. -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`include_defaults` (Optional, boolean)*: If `true`, return all default settings in the response. -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. - -[discrete] -==== get_index_template -Get index templates. -Returns information about one or more index templates. - -{ref}/indices-get-template.html[Endpoint documentation] -[source,ts] ----- -client.indices.getIndexTemplate({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: List of index template names used to limit the request. Wildcard (*) expressions are supported. -** *`local` (Optional, boolean)*: If true, the request retrieves information from the local node only. Defaults to false, which means information is retrieved from the master node. -** *`flat_settings` (Optional, boolean)*: If true, returns settings in flat format. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`include_defaults` (Optional, boolean)*: If true, returns all relevant default configurations for the index template. - -[discrete] -==== get_mapping -Get mapping definitions. -Retrieves mapping definitions for one or more indices. -For data streams, the API retrieves mappings for the stream’s backing indices. - -{ref}/indices-get-mapping.html[Endpoint documentation] -[source,ts] ----- -client.indices.getMapping({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== get_settings -Get index settings. -Returns setting information for one or more indices. For data streams, -returns setting information for the stream’s backing indices. - -{ref}/indices-get-settings.html[Endpoint documentation] -[source,ts] ----- -client.indices.getSettings({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit -the request. Supports wildcards (`*`). To target all data streams and -indices, omit this parameter or use `*` or `_all`. -** *`name` (Optional, string | string[])*: List or wildcard expression of settings to retrieve. -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -** *`flat_settings` (Optional, boolean)*: If `true`, returns settings in flat format. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`include_defaults` (Optional, boolean)*: If `true`, return all default settings in the response. -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. If -`false`, information is retrieved from the master node. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is -received before the timeout expires, the request fails and returns an -error. - -[discrete] -==== get_template -Get index templates. -Retrieves information about one or more index templates. - -{ref}/indices-get-template-v1.html[Endpoint documentation] -[source,ts] ----- -client.indices.getTemplate({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string | string[])*: List of index template names used to limit the request. -Wildcard (`*`) expressions are supported. -To return all index templates, omit this parameter or use a value of `_all` or `*`. -** *`flat_settings` (Optional, boolean)*: If `true`, returns settings in flat format. -** *`local` (Optional, boolean)*: If `true`, the request retrieves information from the local node only. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== migrate_to_data_stream -Convert an index alias to a data stream. -Converts an index alias to a data stream. -You must have a matching index template that is data stream enabled. -The alias must meet the following criteria: -The alias must have a write index; -All indices for the alias must have a `@timestamp` field mapping of a `date` or `date_nanos` field type; -The alias must not have any filters; -The alias must not use custom routing. -If successful, the request removes the alias and creates a data stream with the same name. -The indices for the alias become hidden backing indices for the stream. -The write index for the alias becomes the write index for the stream. - -{ref}/data-streams.html[Endpoint documentation] -[source,ts] ----- -client.indices.migrateToDataStream({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Name of the index alias to convert to a data stream. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== modify_data_stream -Update data streams. -Performs one or more data stream modification actions in a single atomic operation. - -{ref}/data-streams.html[Endpoint documentation] -[source,ts] ----- -client.indices.modifyDataStream({ actions }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`actions` ({ add_backing_index, remove_backing_index }[])*: Actions to perform. - -[discrete] -==== open -Opens a closed index. -For data streams, the API opens any closed backing indices. - -{ref}/indices-open-close.html[Endpoint documentation] -[source,ts] ----- -client.indices.open({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -By default, you must explicitly name the indices you using to limit the request. -To limit a request using `_all`, `*`, or other wildcard expressions, change the `action.destructive_requires_name` setting to false. -You can update this setting in the `elasticsearch.yml` file or using the cluster update settings API. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - -[discrete] -==== promote_data_stream -Promotes a data stream from a replicated data stream managed by CCR to a regular data stream - -{ref}/data-streams.html[Endpoint documentation] -[source,ts] ----- -client.indices.promoteDataStream({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the data stream -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== put_alias -Create or update an alias. -Adds a data stream or index to an alias. - -{ref}/indices-aliases.html[Endpoint documentation] -[source,ts] ----- -client.indices.putAlias({ index, name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: List of data streams or indices to add. -Supports wildcards (`*`). -Wildcard patterns that match both data streams and indices return an error. -** *`name` (string)*: Alias to update. -If the alias doesn’t exist, the request creates it. -Index alias names support date math. -** *`filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Query used to limit documents the alias can access. -** *`index_routing` (Optional, string)*: 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. -** *`is_write_index` (Optional, boolean)*: 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. -Data stream aliases don’t automatically set a write data stream, even if the alias points to one data stream. -** *`routing` (Optional, string)*: Value used to route indexing and search operations to a specific shard. -Data stream aliases don’t support this parameter. -** *`search_routing` (Optional, 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. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== put_data_lifecycle -Update data stream lifecycles. -Update the data stream lifecycle of the specified data streams. - -{ref}/data-streams-put-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.indices.putDataLifecycle({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: List of data streams used to limit the request. -Supports wildcards (`*`). -To target all data streams use `*` or `_all`. -** *`lifecycle` (Optional, { data_retention, downsampling, enabled })* -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Type of data stream that wildcard patterns can match. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `hidden`, `open`, `closed`, `none`. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is -received before the timeout expires, the request fails and returns an -error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== put_index_template -Create or update an index template. -Index templates define settings, mappings, and aliases that can be applied automatically to new indices. - -{ref}/indices-put-template.html[Endpoint documentation] -[source,ts] ----- -client.indices.putIndexTemplate({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Index or template name -** *`index_patterns` (Optional, string | string[])*: Name of the index template to create. -** *`composed_of` (Optional, string[])*: An ordered list of component template names. -Component templates are merged in the order specified, meaning that the last component template specified has the highest precedence. -** *`template` (Optional, { aliases, mappings, settings, lifecycle })*: Template to be applied. -It may optionally include an `aliases`, `mappings`, or `settings` configuration. -** *`data_stream` (Optional, { hidden, allow_custom_routing })*: If this object is included, the template is used to create data streams and their backing indices. -Supports an empty object. -Data streams require a matching index template with a `data_stream` object. -** *`priority` (Optional, number)*: Priority to determine index template precedence when a new data stream or index is created. -The index template with the highest priority is chosen. -If no priority is specified the template is treated as though it is of priority 0 (lowest priority). -This number is not automatically generated by Elasticsearch. -** *`version` (Optional, number)*: Version number used to manage index templates externally. -This number is not automatically generated by Elasticsearch. -** *`_meta` (Optional, Record)*: Optional user metadata about the index template. -May have any contents. -This map is not automatically generated by Elasticsearch. -** *`allow_auto_create` (Optional, boolean)*: This setting overrides the value of the `action.auto_create_index` cluster setting. -If set to `true` in a template, then indices can be automatically created using that template even if auto-creation of indices is disabled via `actions.auto_create_index`. -If set to `false`, then indices or data streams matching the template must always be explicitly created, and may never be automatically created. -** *`ignore_missing_component_templates` (Optional, string[])*: The configuration option ignore_missing_component_templates can be used when an index template -references a component template that might not exist -** *`deprecated` (Optional, boolean)*: Marks this index template as deprecated. When creating or updating a non-deprecated index template -that uses deprecated components, Elasticsearch will emit a deprecation warning. -** *`create` (Optional, boolean)*: If `true`, this request cannot replace or update existing index templates. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`cause` (Optional, string)*: User defined reason for creating/updating the index template - -[discrete] -==== put_mapping -Update field mappings. -Adds new fields to an existing data stream or index. -You can also use this API to change the search settings of existing fields. -For data streams, these changes are applied to all backing indices by default. - -{ref}/indices-put-mapping.html[Endpoint documentation] -[source,ts] ----- -client.indices.putMapping({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: A list of index names the mapping should be added to (supports wildcards); use `_all` or omit to add the mapping on all indices. -** *`date_detection` (Optional, boolean)*: Controls whether dynamic date detection is enabled. -** *`dynamic` (Optional, Enum("strict" | "runtime" | true | false))*: Controls whether new fields are added dynamically. -** *`dynamic_date_formats` (Optional, string[])*: If date detection is enabled then new string fields are checked -against 'dynamic_date_formats' and if the value matches then -a new date field is added instead of string. -** *`dynamic_templates` (Optional, Record | Record[])*: Specify dynamic templates for the mapping. -** *`_field_names` (Optional, { enabled })*: Control whether field names are enabled for the index. -** *`_meta` (Optional, Record)*: A mapping type can have custom meta data associated with it. These are -not used at all by Elasticsearch, but can be used to store -application-specific metadata. -** *`numeric_detection` (Optional, boolean)*: Automatically map strings into numeric data types for all fields. -** *`properties` (Optional, Record)*: Mapping for a field. For new fields, this mapping can include: - -- Field name -- Field data type -- Mapping parameters -** *`_routing` (Optional, { required })*: Enable making a routing value required on indexed documents. -** *`_source` (Optional, { compress, compress_threshold, enabled, excludes, includes, mode })*: Control whether the _source field is enabled on the index. -** *`runtime` (Optional, Record)*: Mapping of runtime fields for the index. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`write_index_only` (Optional, boolean)*: If `true`, the mappings are applied only to the current write index for the target. - -[discrete] -==== put_settings -Update index settings. -Changes dynamic index settings in real time. For data streams, index setting -changes are applied to all backing indices by default. - -{ref}/indices-update-settings.html[Endpoint documentation] -[source,ts] ----- -client.indices.putSettings({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit -the request. Supports wildcards (`*`). To target all data streams and -indices, omit this parameter or use `*` or `_all`. -** *`settings` (Optional, { index, mode, routing_path, soft_deletes, sort, number_of_shards, number_of_replicas, number_of_routing_shards, check_on_startup, codec, routing_partition_size, load_fixed_bitset_filters_eagerly, hidden, auto_expand_replicas, merge, search, refresh_interval, max_result_window, max_inner_result_window, max_rescore_window, max_docvalue_fields_search, max_script_fields, max_ngram_diff, max_shingle_diff, blocks, max_refresh_listeners, analyze, highlight, max_terms_count, max_regex_length, routing, gc_deletes, default_pipeline, final_pipeline, lifecycle, provided_name, creation_date, creation_date_string, uuid, version, verified_before_close, format, max_slices_per_scroll, translog, query_string, priority, top_metrics_max_size, analysis, settings, time_series, queries, similarity, mapping, indexing.slowlog, indexing_pressure, store })* -** *`allow_no_indices` (Optional, boolean)*: 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`. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. Supports a list of values, such as -`open,hidden`. -** *`flat_settings` (Optional, boolean)*: If `true`, returns settings in flat format. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, returns settings in flat format. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is -received before the timeout expires, the request fails and returns an -error. -** *`preserve_existing` (Optional, boolean)*: If `true`, existing index settings remain unchanged. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the - timeout expires, the request fails and returns an error. - -[discrete] -==== put_template -Create or update an index template. -Index templates define settings, mappings, and aliases that can be applied automatically to new indices. - -{ref}/indices-templates-v1.html[Endpoint documentation] -[source,ts] ----- -client.indices.putTemplate({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the template -** *`aliases` (Optional, Record)*: Aliases for the index. -** *`index_patterns` (Optional, string | string[])*: Array of wildcard expressions used to match the names -of indices during creation. -** *`mappings` (Optional, { all_field, date_detection, dynamic, dynamic_date_formats, dynamic_templates, _field_names, index_field, _meta, numeric_detection, properties, _routing, _size, _source, runtime, enabled, subobjects, _data_stream_timestamp })*: Mapping for fields in the index. -** *`order` (Optional, number)*: Order in which Elasticsearch applies this template if index -matches multiple templates. - -Templates with lower 'order' values are merged first. Templates with higher -'order' values are merged later, overriding templates with lower values. -** *`settings` (Optional, { index, mode, routing_path, soft_deletes, sort, number_of_shards, number_of_replicas, number_of_routing_shards, check_on_startup, codec, routing_partition_size, load_fixed_bitset_filters_eagerly, hidden, auto_expand_replicas, merge, search, refresh_interval, max_result_window, max_inner_result_window, max_rescore_window, max_docvalue_fields_search, max_script_fields, max_ngram_diff, max_shingle_diff, blocks, max_refresh_listeners, analyze, highlight, max_terms_count, max_regex_length, routing, gc_deletes, default_pipeline, final_pipeline, lifecycle, provided_name, creation_date, creation_date_string, uuid, version, verified_before_close, format, max_slices_per_scroll, translog, query_string, priority, top_metrics_max_size, analysis, settings, time_series, queries, similarity, mapping, indexing.slowlog, indexing_pressure, store })*: Configuration options for the index. -** *`version` (Optional, number)*: Version number used to manage index templates externally. This number -is not automatically generated by Elasticsearch. -** *`create` (Optional, boolean)*: If true, this request cannot replace or update existing index templates. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is -received before the timeout expires, the request fails and returns an error. -** *`cause` (Optional, string)* - -[discrete] -==== recovery -Returns information about ongoing and completed shard recoveries for one or more indices. -For data streams, the API returns information for the stream’s backing indices. - -{ref}/indices-recovery.html[Endpoint documentation] -[source,ts] ----- -client.indices.recovery({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`active_only` (Optional, boolean)*: If `true`, the response only includes ongoing shard recoveries. -** *`detailed` (Optional, boolean)*: If `true`, the response includes detailed information about shard recoveries. - -[discrete] -==== refresh -Refresh an index. -A refresh makes recent operations performed on one or more indices available for search. -For data streams, the API runs the refresh operation on the stream’s backing indices. - -{ref}/indices-refresh.html[Endpoint documentation] -[source,ts] ----- -client.indices.refresh({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. - -[discrete] -==== reload_search_analyzers -Reloads an index's search analyzers and their resources. - -{ref}/indices-reload-analyzers.html[Endpoint documentation] -[source,ts] ----- -client.indices.reloadSearchAnalyzers({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: A list of index names to reload analyzers for -** *`allow_no_indices` (Optional, boolean)*: Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified) -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`ignore_unavailable` (Optional, boolean)*: Whether specified concrete indices should be ignored when unavailable (missing or closed) - -[discrete] -==== resolve_cluster -Resolves the specified index expressions to return information about each cluster, including -the local cluster, if included. -Multiple patterns and remote clusters are supported. - -{ref}/indices-resolve-cluster-api.html[Endpoint documentation] -[source,ts] ----- -client.indices.resolveCluster({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: Comma-separated name(s) or index pattern(s) of the indices, aliases, and data streams to resolve. -Resources on remote clusters can be specified using the ``:`` syntax. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_throttled` (Optional, boolean)*: If true, concrete, expanded or aliased indices are ignored when frozen. Defaults to false. -** *`ignore_unavailable` (Optional, boolean)*: If false, the request returns an error if it targets a missing or closed index. Defaults to false. - -[discrete] -==== resolve_index -Resolves the specified name(s) and/or index patterns for indices, aliases, and data streams. -Multiple patterns and remote clusters are supported. - -{ref}/indices-resolve-index-api.html[Endpoint documentation] -[source,ts] ----- -client.indices.resolveIndex({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: Comma-separated name(s) or index pattern(s) of the indices, aliases, and data streams to resolve. -Resources on remote clusters can be specified using the ``:`` syntax. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`allow_no_indices` (Optional, boolean)*: 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`. - -[discrete] -==== rollover -Roll over to a new index. -Creates a new index for a data stream or index alias. - -{ref}/indices-rollover-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.rollover({ alias }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`alias` (string)*: Name of the data stream or index alias to roll over. -** *`new_index` (Optional, string)*: Name of the index to create. -Supports date math. -Data streams do not support this parameter. -** *`aliases` (Optional, Record)*: Aliases for the target index. -Data streams do not support this parameter. -** *`conditions` (Optional, { min_age, max_age, max_age_millis, min_docs, max_docs, max_size, max_size_bytes, min_size, min_size_bytes, max_primary_shard_size, max_primary_shard_size_bytes, min_primary_shard_size, min_primary_shard_size_bytes, max_primary_shard_docs, min_primary_shard_docs })*: Conditions for the rollover. -If specified, Elasticsearch only performs the rollover if the current index satisfies these conditions. -If this parameter is not specified, Elasticsearch performs the rollover unconditionally. -If conditions are specified, at least one of them must be a `max_*` condition. -The index will rollover if any `max_*` condition is satisfied and all `min_*` conditions are satisfied. -** *`mappings` (Optional, { all_field, date_detection, dynamic, dynamic_date_formats, dynamic_templates, _field_names, index_field, _meta, numeric_detection, properties, _routing, _size, _source, runtime, enabled, subobjects, _data_stream_timestamp })*: Mapping for fields in the index. -If specified, this mapping can include field names, field data types, and mapping paramaters. -** *`settings` (Optional, Record)*: Configuration options for the index. -Data streams do not support this parameter. -** *`dry_run` (Optional, boolean)*: If `true`, checks whether the current index satisfies the specified conditions but does not perform a rollover. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - -[discrete] -==== segments -Returns low-level information about the Lucene segments in index shards. -For data streams, the API returns information about the stream’s backing indices. - -{ref}/indices-segments.html[Endpoint documentation] -[source,ts] ----- -client.indices.segments({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -Supports wildcards (`*`). -To target all data streams and indices, omit this parameter or use `*` or `_all`. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. - -[discrete] -==== shard_stores -Retrieves store information about replica shards in one or more indices. -For data streams, the API retrieves store information for the stream’s backing indices. - -{ref}/indices-shards-stores.html[Endpoint documentation] -[source,ts] ----- -client.indices.shardStores({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases used to limit the request. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -** *`ignore_unavailable` (Optional, boolean)*: If true, missing or closed indices are not included in the response. -** *`status` (Optional, Enum("green" | "yellow" | "red" | "all") | Enum("green" | "yellow" | "red" | "all")[])*: List of shard health statuses used to limit the request. - -[discrete] -==== shrink -Shrinks an existing index into a new index with fewer primary shards. - -{ref}/indices-shrink-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.shrink({ index, target }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Name of the source index to shrink. -** *`target` (string)*: Name of the target index to create. -** *`aliases` (Optional, Record)*: The key is the alias name. -Index alias names support date math. -** *`settings` (Optional, Record)*: Configuration options for the target index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - -[discrete] -==== simulate_index_template -Simulate an index. -Returns the index configuration that would be applied to the specified index from an existing index template. - -{ref}/indices-simulate-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.simulateIndexTemplate({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Name of the index to simulate -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`include_defaults` (Optional, boolean)*: If true, returns all relevant default configurations for the index template. - -[discrete] -==== simulate_template -Simulate an index template. -Returns the index configuration that would be applied by a particular index template. - -{ref}/indices-simulate-template.html[Endpoint documentation] -[source,ts] ----- -client.indices.simulateTemplate({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: Name of the index template to simulate. To test a template configuration before you add it to the cluster, omit -this parameter and specify the template configuration in the request body. -** *`allow_auto_create` (Optional, boolean)*: This setting overrides the value of the `action.auto_create_index` cluster setting. -If set to `true` in a template, then indices can be automatically created using that template even if auto-creation of indices is disabled via `actions.auto_create_index`. -If set to `false`, then indices or data streams matching the template must always be explicitly created, and may never be automatically created. -** *`index_patterns` (Optional, string | string[])*: Array of wildcard (`*`) expressions used to match the names of data streams and indices during creation. -** *`composed_of` (Optional, string[])*: An ordered list of component template names. -Component templates are merged in the order specified, meaning that the last component template specified has the highest precedence. -** *`template` (Optional, { aliases, mappings, settings, lifecycle })*: Template to be applied. -It may optionally include an `aliases`, `mappings`, or `settings` configuration. -** *`data_stream` (Optional, { hidden, allow_custom_routing })*: If this object is included, the template is used to create data streams and their backing indices. -Supports an empty object. -Data streams require a matching index template with a `data_stream` object. -** *`priority` (Optional, number)*: Priority to determine index template precedence when a new data stream or index is created. -The index template with the highest priority is chosen. -If no priority is specified the template is treated as though it is of priority 0 (lowest priority). -This number is not automatically generated by Elasticsearch. -** *`version` (Optional, number)*: Version number used to manage index templates externally. -This number is not automatically generated by Elasticsearch. -** *`_meta` (Optional, Record)*: Optional user metadata about the index template. -May have any contents. -This map is not automatically generated by Elasticsearch. -** *`ignore_missing_component_templates` (Optional, string[])*: The configuration option ignore_missing_component_templates can be used when an index template -references a component template that might not exist -** *`deprecated` (Optional, boolean)*: Marks this index template as deprecated. When creating or updating a non-deprecated index template -that uses deprecated components, Elasticsearch will emit a deprecation warning. -** *`create` (Optional, boolean)*: If true, the template passed in the body is only used if no existing templates match the same index patterns. If false, the simulation uses the template with the highest priority. Note that the template is not permanently added or updated in either case; it is only used for the simulation. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`include_defaults` (Optional, boolean)*: If true, returns all relevant default configurations for the index template. - -[discrete] -==== split -Splits an existing index into a new index with more primary shards. - -{ref}/indices-split-index.html[Endpoint documentation] -[source,ts] ----- -client.indices.split({ index, target }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Name of the source index to split. -** *`target` (string)*: Name of the target index to create. -** *`aliases` (Optional, Record)*: Aliases for the resulting index. -** *`settings` (Optional, Record)*: Configuration options for the target index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, number | Enum("all" | "index-setting"))*: 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`). - -[discrete] -==== stats -Returns statistics for one or more indices. -For data streams, the API retrieves statistics for the stream’s backing indices. - -{ref}/indices-stats.html[Endpoint documentation] -[source,ts] ----- -client.indices.stats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`metric` (Optional, string | string[])*: Limit the information returned the specific metrics. -** *`index` (Optional, string | string[])*: A list of index names; use `_all` or empty string to perform the operation on all indices -** *`completion_fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in fielddata and suggest statistics. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. Supports a list of values, -such as `open,hidden`. -** *`fielddata_fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in fielddata statistics. -** *`fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in the statistics. -** *`forbid_closed_indices` (Optional, boolean)*: If true, statistics are not collected from closed indices. -** *`groups` (Optional, string | string[])*: List of search groups to include in the search statistics. -** *`include_segment_file_sizes` (Optional, boolean)*: If true, the call reports the aggregated disk usage of each one of the Lucene index files (only applies if segment stats are requested). -** *`include_unloaded_segments` (Optional, boolean)*: If true, the response includes information from segments that are not loaded into memory. -** *`level` (Optional, Enum("cluster" | "indices" | "shards"))*: Indicates whether statistics are aggregated at the cluster, index, or shard level. - -[discrete] -==== unfreeze -Unfreezes an index. - -{ref}/unfreeze-index-api.html[Endpoint documentation] -[source,ts] ----- -client.indices.unfreeze({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string)*: Identifier for the index. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_active_shards` (Optional, string)*: 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`). - -[discrete] -==== update_aliases -Create or update an alias. -Adds a data stream or index to an alias. - -{ref}/indices-aliases.html[Endpoint documentation] -[source,ts] ----- -client.indices.updateAliases({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`actions` (Optional, { add_backing_index, remove_backing_index }[])*: Actions to perform. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== validate_query -Validate a query. -Validates a query without running it. - -{ref}/search-validate.html[Endpoint documentation] -[source,ts] ----- -client.indices.validateQuery({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: List of data streams, indices, and aliases to search. -Supports wildcards (`*`). -To search all data streams or indices, omit this parameter or use `*` or `_all`. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Query in the Lucene query string syntax. -** *`allow_no_indices` (Optional, boolean)*: 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. -** *`all_shards` (Optional, boolean)*: If `true`, the validation is executed on all shards instead of one random shard per index. -** *`analyzer` (Optional, string)*: Analyzer to use for the query string. -This parameter can only be used when the `q` query string parameter is specified. -** *`analyze_wildcard` (Optional, boolean)*: If `true`, wildcard and prefix queries are analyzed. -** *`default_operator` (Optional, Enum("and" | "or"))*: The default operator for query string query: `AND` or `OR`. -** *`df` (Optional, string)*: Field to use as default where no field prefix is given in the query string. -This parameter can only be used when the `q` query string parameter is specified. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. -Supports a list of values, such as `open,hidden`. -Valid values are: `all`, `open`, `closed`, `hidden`, `none`. -** *`explain` (Optional, boolean)*: If `true`, the response returns detailed information if an error has occurred. -** *`ignore_unavailable` (Optional, boolean)*: If `false`, the request returns an error if it targets a missing or closed index. -** *`lenient` (Optional, boolean)*: If `true`, format-based query failures (such as providing text to a numeric field) in the query string will be ignored. -** *`rewrite` (Optional, boolean)*: If `true`, returns a more detailed explanation showing the actual Lucene query that will be executed. -** *`q` (Optional, string)*: Query in the Lucene query string syntax. - -[discrete] -=== inference -[discrete] -==== delete -Delete an inference endpoint - -{ref}/delete-inference-api.html[Endpoint documentation] -[source,ts] ----- -client.inference.delete({ inference_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`inference_id` (string)*: The inference Id -** *`task_type` (Optional, Enum("sparse_embedding" | "text_embedding" | "rerank" | "completion"))*: The task type -** *`dry_run` (Optional, boolean)*: When true, the endpoint is not deleted, and a list of ingest processors which reference this endpoint is returned -** *`force` (Optional, boolean)*: When true, the inference endpoint is forcefully deleted even if it is still being used by ingest processors or semantic text fields - -[discrete] -==== get -Get an inference endpoint - -{ref}/get-inference-api.html[Endpoint documentation] -[source,ts] ----- -client.inference.get({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`task_type` (Optional, Enum("sparse_embedding" | "text_embedding" | "rerank" | "completion"))*: The task type -** *`inference_id` (Optional, string)*: The inference Id - -[discrete] -==== inference -Perform inference on the service - -{ref}/post-inference-api.html[Endpoint documentation] -[source,ts] ----- -client.inference.inference({ inference_id, input }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`inference_id` (string)*: The inference Id -** *`input` (string | string[])*: Inference input. -Either a string or an array of strings. -** *`task_type` (Optional, Enum("sparse_embedding" | "text_embedding" | "rerank" | "completion"))*: The task type -** *`query` (Optional, string)*: Query input, required for rerank task. -Not required for other tasks. -** *`task_settings` (Optional, User-defined value)*: Optional task settings -** *`timeout` (Optional, string | -1 | 0)*: Specifies the amount of time to wait for the inference request to complete. - -[discrete] -==== put -Create an inference endpoint - -{ref}/put-inference-api.html[Endpoint documentation] -[source,ts] ----- -client.inference.put({ inference_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`inference_id` (string)*: The inference Id -** *`task_type` (Optional, Enum("sparse_embedding" | "text_embedding" | "rerank" | "completion"))*: The task type -** *`inference_config` (Optional, { service, service_settings, task_settings })* - -[discrete] -==== stream_inference -Perform streaming inference -[source,ts] ----- -client.inference.streamInference() ----- - - -[discrete] -=== ingest -[discrete] -==== delete_geoip_database -Deletes a geoip database configuration. - -{ref}/delete-geoip-database-api.html[Endpoint documentation] -[source,ts] ----- -client.ingest.deleteGeoipDatabase({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string | string[])*: A list of geoip database configurations to delete -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== delete_pipeline -Deletes one or more existing ingest pipeline. - -{ref}/delete-pipeline-api.html[Endpoint documentation] -[source,ts] ----- -client.ingest.deletePipeline({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Pipeline ID or wildcard expression of pipeline IDs used to limit the request. -To delete all ingest pipelines in a cluster, use a value of `*`. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== geo_ip_stats -Gets download statistics for GeoIP2 databases used with the geoip processor. - -{ref}/geoip-processor.html[Endpoint documentation] -[source,ts] ----- -client.ingest.geoIpStats() ----- - - -[discrete] -==== get_geoip_database -Returns information about one or more geoip database configurations. - -{ref}/get-geoip-database-api.html[Endpoint documentation] -[source,ts] ----- -client.ingest.getGeoipDatabase({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string | string[])*: List of database configuration IDs to retrieve. -Wildcard (`*`) expressions are supported. -To get all database configurations, omit this parameter or use `*`. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== get_pipeline -Returns information about one or more ingest pipelines. -This API returns a local reference of the pipeline. - -{ref}/get-pipeline-api.html[Endpoint documentation] -[source,ts] ----- -client.ingest.getPipeline({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: List of pipeline IDs to retrieve. -Wildcard (`*`) expressions are supported. -To get all ingest pipelines, omit this parameter or use `*`. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`summary` (Optional, boolean)*: Return pipelines without their definitions (default: false) - -[discrete] -==== processor_grok -Extracts structured fields out of a single text field within a document. -You choose which field to extract matched fields from, as well as the grok pattern you expect will match. -A grok pattern is like a regular expression that supports aliased expressions that can be reused. - -{ref}/grok-processor.html[Endpoint documentation] -[source,ts] ----- -client.ingest.processorGrok() ----- - - -[discrete] -==== put_geoip_database -Returns information about one or more geoip database configurations. - -{ref}/put-geoip-database-api.html[Endpoint documentation] -[source,ts] ----- -client.ingest.putGeoipDatabase({ id, name, maxmind }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: ID of the database configuration to create or update. -** *`name` (string)*: The provider-assigned name of the IP geolocation database to download. -** *`maxmind` ({ account_id })*: The configuration necessary to identify which IP geolocation provider to use to download the database, as well as any provider-specific configuration necessary for such downloading. -At present, the only supported provider is maxmind, and the maxmind provider requires that an account_id (string) is configured. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== put_pipeline -Creates or updates an ingest pipeline. -Changes made using this API take effect immediately. - -{ref}/ingest.html[Endpoint documentation] -[source,ts] ----- -client.ingest.putPipeline({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: ID of the ingest pipeline to create or update. -** *`_meta` (Optional, Record)*: Optional metadata about the ingest pipeline. May have any contents. This map is not automatically generated by Elasticsearch. -** *`description` (Optional, string)*: Description of the ingest pipeline. -** *`on_failure` (Optional, { append, attachment, bytes, circle, community_id, convert, csv, date, date_index_name, dissect, dot_expander, drop, enrich, fail, fingerprint, foreach, ip_location, geo_grid, geoip, grok, gsub, html_strip, inference, join, json, kv, lowercase, network_direction, pipeline, redact, registered_domain, remove, rename, reroute, script, set, set_security_user, sort, split, terminate, trim, uppercase, urldecode, uri_parts, user_agent }[])*: Processors to run immediately after a processor failure. Each processor supports a processor-level `on_failure` value. If a processor without an `on_failure` value fails, Elasticsearch uses this pipeline-level parameter as a fallback. The processors in this parameter run sequentially in the order specified. Elasticsearch will not attempt to run the pipeline's remaining processors. -** *`processors` (Optional, { append, attachment, bytes, circle, community_id, convert, csv, date, date_index_name, dissect, dot_expander, drop, enrich, fail, fingerprint, foreach, ip_location, geo_grid, geoip, grok, gsub, html_strip, inference, join, json, kv, lowercase, network_direction, pipeline, redact, registered_domain, remove, rename, reroute, script, set, set_security_user, sort, split, terminate, trim, uppercase, urldecode, uri_parts, user_agent }[])*: Processors used to perform transformations on documents before indexing. Processors run sequentially in the order specified. -** *`version` (Optional, number)*: Version number used by external systems to track ingest pipelines. This parameter is intended for external systems only. Elasticsearch does not use or validate pipeline version numbers. -** *`deprecated` (Optional, boolean)*: Marks this ingest pipeline as deprecated. -When a deprecated ingest pipeline is referenced as the default or final pipeline when creating or updating a non-deprecated index template, Elasticsearch will emit a deprecation warning. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. -** *`if_version` (Optional, number)*: Required version for optimistic concurrency control for pipeline updates - -[discrete] -==== simulate -Executes an ingest pipeline against a set of provided documents. - -{ref}/simulate-pipeline-api.html[Endpoint documentation] -[source,ts] ----- -client.ingest.simulate({ docs }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`docs` ({ _id, _index, _source }[])*: Sample documents to test in the pipeline. -** *`id` (Optional, string)*: Pipeline to test. -If you don’t specify a `pipeline` in the request body, this parameter is required. -** *`pipeline` (Optional, { description, on_failure, processors, version, deprecated, _meta })*: Pipeline to test. -If you don’t specify the `pipeline` request path parameter, this parameter is required. -If you specify both this and the request path parameter, the API only uses the request path parameter. -** *`verbose` (Optional, boolean)*: If `true`, the response includes output data for each processor in the executed pipeline. - -[discrete] -=== license -[discrete] -==== delete -Deletes licensing information for the cluster - -{ref}/delete-license.html[Endpoint documentation] -[source,ts] ----- -client.license.delete() ----- - - -[discrete] -==== get -Get license information. -Returns information about your Elastic license, including its type, its status, when it was issued, and when it expires. -For more information about the different types of licenses, refer to [Elastic Stack subscriptions](https://www.elastic.co/subscriptions). - -{ref}/get-license.html[Endpoint documentation] -[source,ts] ----- -client.license.get({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`accept_enterprise` (Optional, boolean)*: If `true`, this parameter returns enterprise for Enterprise license types. If `false`, this parameter returns platinum for both platinum and enterprise license types. This behavior is maintained for backwards compatibility. -This parameter is deprecated and will always be set to true in 8.x. -** *`local` (Optional, boolean)*: Specifies whether to retrieve local information. The default value is `false`, which means the information is retrieved from the master node. - -[discrete] -==== get_basic_status -Retrieves information about the status of the basic license. - -{ref}/get-basic-status.html[Endpoint documentation] -[source,ts] ----- -client.license.getBasicStatus() ----- - - -[discrete] -==== get_trial_status -Retrieves information about the status of the trial license. - -{ref}/get-trial-status.html[Endpoint documentation] -[source,ts] ----- -client.license.getTrialStatus() ----- - - -[discrete] -==== post -Updates the license for the cluster. - -{ref}/update-license.html[Endpoint documentation] -[source,ts] ----- -client.license.post({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`license` (Optional, { expiry_date_in_millis, issue_date_in_millis, start_date_in_millis, issued_to, issuer, max_nodes, max_resource_units, signature, type, uid })* -** *`licenses` (Optional, { expiry_date_in_millis, issue_date_in_millis, start_date_in_millis, issued_to, issuer, max_nodes, max_resource_units, signature, type, uid }[])*: A sequence of one or more JSON documents containing the license information. -** *`acknowledge` (Optional, boolean)*: Specifies whether you acknowledge the license changes. - -[discrete] -==== post_start_basic -The start basic API enables you to initiate an indefinite basic license, which gives access to all the basic features. If the basic license does not support all of the features that are available with your current license, however, you are notified in the response. You must then re-submit the API request with the acknowledge parameter set to true. -To check the status of your basic license, use the following API: [Get basic status](https://www.elastic.co/guide/en/elasticsearch/reference/current/get-basic-status.html). - -{ref}/start-basic.html[Endpoint documentation] -[source,ts] ----- -client.license.postStartBasic({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`acknowledge` (Optional, boolean)*: whether the user has acknowledged acknowledge messages (default: false) - -[discrete] -==== post_start_trial -The start trial API enables you to start a 30-day trial, which gives access to all subscription features. - -{ref}/start-trial.html[Endpoint documentation] -[source,ts] ----- -client.license.postStartTrial({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`acknowledge` (Optional, boolean)*: whether the user has acknowledged acknowledge messages (default: false) -** *`type_query_string` (Optional, string)* - -[discrete] -=== logstash -[discrete] -==== delete_pipeline -Deletes a pipeline used for Logstash Central Management. - -{ref}/logstash-api-delete-pipeline.html[Endpoint documentation] -[source,ts] ----- -client.logstash.deletePipeline({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the pipeline. - -[discrete] -==== get_pipeline -Retrieves pipelines used for Logstash Central Management. - -{ref}/logstash-api-get-pipeline.html[Endpoint documentation] -[source,ts] ----- -client.logstash.getPipeline({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string | string[])*: List of pipeline identifiers. - -[discrete] -==== put_pipeline -Creates or updates a pipeline used for Logstash Central Management. - -{ref}/logstash-api-put-pipeline.html[Endpoint documentation] -[source,ts] ----- -client.logstash.putPipeline({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the pipeline. -** *`pipeline` (Optional, { description, on_failure, processors, version, deprecated, _meta })* - -[discrete] -=== migration -[discrete] -==== deprecations -Retrieves information about different cluster, node, and index level settings that use deprecated features that will be removed or changed in the next major version. - -{ref}/migration-api-deprecation.html[Endpoint documentation] -[source,ts] ----- -client.migration.deprecations({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string)*: Comma-separate list of data streams or indices to check. Wildcard (*) expressions are supported. - -[discrete] -==== get_feature_upgrade_status -Find out whether system features need to be upgraded or not - -{ref}/migration-api-feature-upgrade.html[Endpoint documentation] -[source,ts] ----- -client.migration.getFeatureUpgradeStatus() ----- - - -[discrete] -==== post_feature_upgrade -Begin upgrades for system features - -{ref}/migration-api-feature-upgrade.html[Endpoint documentation] -[source,ts] ----- -client.migration.postFeatureUpgrade() ----- - - -[discrete] -=== ml -[discrete] -==== clear_trained_model_deployment_cache -Clear trained model deployment cache. -Cache will be cleared on all nodes where the trained model is assigned. -A trained model deployment may have an inference cache enabled. -As requests are handled by each allocated node, their responses may be cached on that individual node. -Calling this API clears the caches without restarting the deployment. - -{ref}/clear-trained-model-deployment-cache.html[Endpoint documentation] -[source,ts] ----- -client.ml.clearTrainedModelDeploymentCache({ model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. - -[discrete] -==== close_job -Close anomaly detection jobs. -A job can be opened and closed multiple times throughout its lifecycle. A closed job cannot receive data or perform analysis operations, but you can still explore and navigate results. -When you close a job, it runs housekeeping tasks such as pruning the model history, flushing buffers, calculating final results and persisting the model snapshots. Depending upon the size of the job, it could take several minutes to close and the equivalent time to re-open. After it is closed, the job has a minimal overhead on the cluster except for maintaining its meta data. Therefore it is a best practice to close jobs that are no longer required to process data. -If you close an anomaly detection job whose datafeed is running, the request first tries to stop the datafeed. This behavior is equivalent to calling stop datafeed API with the same timeout and force parameters as the close job request. -When a datafeed that has a specified end date stops, it automatically closes its associated job. - -{ref}/ml-close-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.closeJob({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. It can be a job identifier, a group name, or a wildcard expression. You can close multiple anomaly detection jobs in a single API request by using a group name, a list of jobs, or a wildcard expression. You can close all jobs by using `_all` or by specifying `*` as the job identifier. -** *`allow_no_match` (Optional, boolean)*: Refer to the description for the `allow_no_match` query parameter. -** *`force` (Optional, boolean)*: Refer to the descriptiion for the `force` query parameter. -** *`timeout` (Optional, string | -1 | 0)*: Refer to the description for the `timeout` query parameter. - -[discrete] -==== delete_calendar -Delete a calendar. -Removes all scheduled events from a calendar, then deletes it. - -{ref}/ml-delete-calendar.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteCalendar({ calendar_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (string)*: A string that uniquely identifies a calendar. - -[discrete] -==== delete_calendar_event -Delete events from a calendar. - -{ref}/ml-delete-calendar-event.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteCalendarEvent({ calendar_id, event_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (string)*: A string that uniquely identifies a calendar. -** *`event_id` (string)*: Identifier for the scheduled event. -You can obtain this identifier by using the get calendar events API. - -[discrete] -==== delete_calendar_job -Delete anomaly jobs from a calendar. - -{ref}/ml-delete-calendar-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteCalendarJob({ calendar_id, job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (string)*: A string that uniquely identifies a calendar. -** *`job_id` (string | string[])*: An identifier for the anomaly detection jobs. It can be a job identifier, a group name, or a -list of jobs or groups. - -[discrete] -==== delete_data_frame_analytics -Delete a data frame analytics job. - -{ref}/delete-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteDataFrameAnalytics({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the data frame analytics job. -** *`force` (Optional, boolean)*: If `true`, it deletes a job that is not stopped; this method is quicker than stopping and deleting the job. -** *`timeout` (Optional, string | -1 | 0)*: The time to wait for the job to be deleted. - -[discrete] -==== delete_datafeed -Delete a datafeed. - -{ref}/ml-delete-datafeed.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteDatafeed({ datafeed_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (string)*: A numerical character string that uniquely identifies the datafeed. This -identifier can contain lowercase alphanumeric characters (a-z and 0-9), -hyphens, and underscores. It must start and end with alphanumeric -characters. -** *`force` (Optional, boolean)*: Use to forcefully delete a started datafeed; this method is quicker than -stopping and deleting the datafeed. - -[discrete] -==== delete_expired_data -Delete expired ML data. -Deletes all job results, model snapshots and forecast data that have exceeded -their retention days period. Machine learning state documents that are not -associated with any job are also deleted. -You can limit the request to a single or set of anomaly detection jobs by -using a job identifier, a group name, a comma-separated list of jobs, or a -wildcard expression. You can delete expired data for all anomaly detection -jobs by using _all, by specifying * as the , or by omitting the -. - -{ref}/ml-delete-expired-data.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteExpiredData({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (Optional, string)*: Identifier for an anomaly detection job. It can be a job identifier, a -group name, or a wildcard expression. -** *`requests_per_second` (Optional, float)*: The desired requests per second for the deletion processes. The default -behavior is no throttling. -** *`timeout` (Optional, string | -1 | 0)*: How long can the underlying delete processes run until they are canceled. - -[discrete] -==== delete_filter -Delete a filter. -If an anomaly detection job references the filter, you cannot delete the -filter. You must update or delete the job before you can delete the filter. - -{ref}/ml-delete-filter.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteFilter({ filter_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`filter_id` (string)*: A string that uniquely identifies a filter. - -[discrete] -==== delete_forecast -Delete forecasts from a job. -By default, forecasts are retained for 14 days. You can specify a -different retention period with the `expires_in` parameter in the forecast -jobs API. The delete forecast API enables you to delete one or more -forecasts before they expire. - -{ref}/ml-delete-forecast.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteForecast({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`forecast_id` (Optional, string)*: A list of forecast identifiers. If you do not specify -this optional parameter or if you specify `_all` or `*` the API deletes -all forecasts from the job. -** *`allow_no_forecasts` (Optional, boolean)*: Specifies whether an error occurs when there are no forecasts. In -particular, if this parameter is set to `false` and there are no -forecasts associated with the job, attempts to delete all forecasts -return an error. -** *`timeout` (Optional, string | -1 | 0)*: Specifies the period of time to wait for the completion of the delete -operation. When this period of time elapses, the API fails and returns an -error. - -[discrete] -==== delete_job -Delete an anomaly detection job. -All job configuration, model state and results are deleted. -It is not currently possible to delete multiple jobs using wildcards or a -comma separated list. If you delete a job that has a datafeed, the request -first tries to delete the datafeed. This behavior is equivalent to calling -the delete datafeed API with the same timeout and force parameters as the -delete job request. - -{ref}/ml-delete-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteJob({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`force` (Optional, boolean)*: Use to forcefully delete an opened job; this method is quicker than -closing and deleting the job. -** *`delete_user_annotations` (Optional, boolean)*: Specifies whether annotations that have been added by the -user should be deleted along with any auto-generated annotations when the job is -reset. -** *`wait_for_completion` (Optional, boolean)*: Specifies whether the request should return immediately or wait until the -job deletion completes. - -[discrete] -==== delete_model_snapshot -Delete a model snapshot. -You cannot delete the active model snapshot. To delete that snapshot, first -revert to a different one. To identify the active model snapshot, refer to -the `model_snapshot_id` in the results from the get jobs API. - -{ref}/ml-delete-snapshot.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteModelSnapshot({ job_id, snapshot_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`snapshot_id` (string)*: Identifier for the model snapshot. - -[discrete] -==== delete_trained_model -Delete an unreferenced trained model. -The request deletes a trained inference model that is not referenced by an ingest pipeline. - -{ref}/delete-trained-models.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteTrainedModel({ model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. -** *`force` (Optional, boolean)*: Forcefully deletes a trained model that is referenced by ingest pipelines or has a started deployment. - -[discrete] -==== delete_trained_model_alias -Delete a trained model alias. -This API deletes an existing model alias that refers to a trained model. If -the model alias is missing or refers to a model other than the one identified -by the `model_id`, this API returns an error. - -{ref}/delete-trained-models-aliases.html[Endpoint documentation] -[source,ts] ----- -client.ml.deleteTrainedModelAlias({ model_alias, model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_alias` (string)*: The model alias to delete. -** *`model_id` (string)*: The trained model ID to which the model alias refers. - -[discrete] -==== estimate_model_memory -Estimate job model memory usage. -Makes an estimation of the memory usage for an anomaly detection job model. -It is based on analysis configuration details for the job and cardinality -estimates for the fields it references. - -{ref}/ml-apis.html[Endpoint documentation] -[source,ts] ----- -client.ml.estimateModelMemory({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`analysis_config` (Optional, { bucket_span, categorization_analyzer, categorization_field_name, categorization_filters, detectors, influencers, latency, model_prune_window, multivariate_by_fields, per_partition_categorization, summary_count_field_name })*: For a list of the properties that you can specify in the -`analysis_config` component of the body of this API. -** *`max_bucket_cardinality` (Optional, Record)*: Estimates of the highest cardinality in a single bucket that is observed -for influencer fields over the time period that the job analyzes data. -To produce a good answer, values must be provided for all influencer -fields. Providing values for fields that are not listed as `influencers` -has no effect on the estimation. -** *`overall_cardinality` (Optional, Record)*: Estimates of the cardinality that is observed for fields over the whole -time period that the job analyzes data. To produce a good answer, values -must be provided for fields referenced in the `by_field_name`, -`over_field_name` and `partition_field_name` of any detectors. Providing -values for other fields has no effect on the estimation. It can be -omitted from the request if no detectors have a `by_field_name`, -`over_field_name` or `partition_field_name`. - -[discrete] -==== evaluate_data_frame -Evaluate data frame analytics. -The API packages together commonly used evaluation metrics for various types -of machine learning features. This has been designed for use on indexes -created by data frame analytics. Evaluation requires both a ground truth -field and an analytics result field to be present. - -{ref}/evaluate-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.evaluateDataFrame({ evaluation, index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`evaluation` ({ classification, outlier_detection, regression })*: Defines the type of evaluation you want to perform. -** *`index` (string)*: Defines the `index` in which the evaluation will be performed. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: A query clause that retrieves a subset of data from the source index. - -[discrete] -==== explain_data_frame_analytics -Explain data frame analytics config. -This API provides explanations for a data frame analytics config that either -exists already or one that has not been created yet. The following -explanations are provided: -* which fields are included or not in the analysis and why, -* how much memory is estimated to be required. The estimate can be used when deciding the appropriate value for model_memory_limit setting later on. -If you have object fields or fields that are excluded via source filtering, they are not included in the explanation. - -{ref}/explain-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.explainDataFrameAnalytics({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: Identifier for the data frame analytics job. This identifier can contain -lowercase alphanumeric characters (a-z and 0-9), hyphens, and -underscores. It must start and end with alphanumeric characters. -** *`source` (Optional, { index, query, runtime_mappings, _source })*: The configuration of how to source the analysis data. It requires an -index. Optionally, query and _source may be specified. -** *`dest` (Optional, { index, results_field })*: The destination configuration, consisting of index and optionally -results_field (ml by default). -** *`analysis` (Optional, { classification, outlier_detection, regression })*: The analysis configuration, which contains the information necessary to -perform one of the following types of analysis: classification, outlier -detection, or regression. -** *`description` (Optional, string)*: A description of the job. -** *`model_memory_limit` (Optional, string)*: The approximate maximum amount of memory resources that are permitted for -analytical processing. If your `elasticsearch.yml` file contains an -`xpack.ml.max_model_memory_limit` setting, an error occurs when you try to -create data frame analytics jobs that have `model_memory_limit` values -greater than that setting. -** *`max_num_threads` (Optional, number)*: The maximum number of threads to be used by the analysis. Using more -threads may decrease the time necessary to complete the analysis at the -cost of using more CPU. Note that the process may use additional threads -for operational functionality other than the analysis itself. -** *`analyzed_fields` (Optional, { includes, excludes })*: Specify includes and/or excludes patterns to select which fields will be -included in the analysis. The patterns specified in excludes are applied -last, therefore excludes takes precedence. In other words, if the same -field is specified in both includes and excludes, then the field will not -be included in the analysis. -** *`allow_lazy_start` (Optional, boolean)*: Specifies whether this job can start when there is insufficient machine -learning node capacity for it to be immediately assigned to a node. - -[discrete] -==== flush_job -Force buffered data to be processed. -The flush jobs API is only applicable when sending data for analysis using -the post data API. Depending on the content of the buffer, then it might -additionally calculate new results. Both flush and close operations are -similar, however the flush is more efficient if you are expecting to send -more data for analysis. When flushing, the job remains open and is available -to continue analyzing data. A close operation additionally prunes and -persists the model state to disk and the job must be opened again before -analyzing further data. - -{ref}/ml-flush-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.flushJob({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`advance_time` (Optional, string | Unit)*: Refer to the description for the `advance_time` query parameter. -** *`calc_interim` (Optional, boolean)*: Refer to the description for the `calc_interim` query parameter. -** *`end` (Optional, string | Unit)*: Refer to the description for the `end` query parameter. -** *`skip_time` (Optional, string | Unit)*: Refer to the description for the `skip_time` query parameter. -** *`start` (Optional, string | Unit)*: Refer to the description for the `start` query parameter. - -[discrete] -==== forecast -Predict future behavior of a time series. - -Forecasts are not supported for jobs that perform population analysis; an -error occurs if you try to create a forecast for a job that has an -`over_field_name` in its configuration. Forcasts predict future behavior -based on historical data. - -{ref}/ml-forecast.html[Endpoint documentation] -[source,ts] ----- -client.ml.forecast({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. The job must be open when you -create a forecast; otherwise, an error occurs. -** *`duration` (Optional, string | -1 | 0)*: Refer to the description for the `duration` query parameter. -** *`expires_in` (Optional, string | -1 | 0)*: Refer to the description for the `expires_in` query parameter. -** *`max_model_memory` (Optional, string)*: Refer to the description for the `max_model_memory` query parameter. - -[discrete] -==== get_buckets -Get anomaly detection job results for buckets. -The API presents a chronological view of the records, grouped by bucket. - -{ref}/ml-get-bucket.html[Endpoint documentation] -[source,ts] ----- -client.ml.getBuckets({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`timestamp` (Optional, string | Unit)*: The timestamp of a single bucket result. If you do not specify this -parameter, the API returns information about all buckets. -** *`anomaly_score` (Optional, number)*: Refer to the description for the `anomaly_score` query parameter. -** *`desc` (Optional, boolean)*: Refer to the description for the `desc` query parameter. -** *`end` (Optional, string | Unit)*: Refer to the description for the `end` query parameter. -** *`exclude_interim` (Optional, boolean)*: Refer to the description for the `exclude_interim` query parameter. -** *`expand` (Optional, boolean)*: Refer to the description for the `expand` query parameter. -** *`page` (Optional, { from, size })* -** *`sort` (Optional, string)*: Refer to the desription for the `sort` query parameter. -** *`start` (Optional, string | Unit)*: Refer to the description for the `start` query parameter. -** *`from` (Optional, number)*: Skips the specified number of buckets. -** *`size` (Optional, number)*: Specifies the maximum number of buckets to obtain. - -[discrete] -==== get_calendar_events -Get info about events in calendars. - -{ref}/ml-get-calendar-event.html[Endpoint documentation] -[source,ts] ----- -client.ml.getCalendarEvents({ calendar_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (string)*: A string that uniquely identifies a calendar. You can get information for multiple calendars by using a list of ids or a wildcard expression. You can get information for all calendars by using `_all` or `*` or by omitting the calendar identifier. -** *`end` (Optional, string | Unit)*: Specifies to get events with timestamps earlier than this time. -** *`from` (Optional, number)*: Skips the specified number of events. -** *`job_id` (Optional, string)*: Specifies to get events for a specific anomaly detection job identifier or job group. It must be used with a calendar identifier of `_all` or `*`. -** *`size` (Optional, number)*: Specifies the maximum number of events to obtain. -** *`start` (Optional, string | Unit)*: Specifies to get events with timestamps after this time. - -[discrete] -==== get_calendars -Get calendar configuration info. - -{ref}/ml-get-calendar.html[Endpoint documentation] -[source,ts] ----- -client.ml.getCalendars({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (Optional, string)*: A string that uniquely identifies a calendar. You can get information for multiple calendars by using a list of ids or a wildcard expression. You can get information for all calendars by using `_all` or `*` or by omitting the calendar identifier. -** *`page` (Optional, { from, size })*: This object is supported only when you omit the calendar identifier. -** *`from` (Optional, number)*: Skips the specified number of calendars. This parameter is supported only when you omit the calendar identifier. -** *`size` (Optional, number)*: Specifies the maximum number of calendars to obtain. This parameter is supported only when you omit the calendar identifier. - -[discrete] -==== get_categories -Get anomaly detection job results for categories. - -{ref}/ml-get-category.html[Endpoint documentation] -[source,ts] ----- -client.ml.getCategories({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`category_id` (Optional, string)*: Identifier for the category, which is unique in the job. If you specify -neither the category ID nor the partition_field_value, the API returns -information about all categories. If you specify only the -partition_field_value, it returns information about all categories for -the specified partition. -** *`page` (Optional, { from, size })*: Configures pagination. -This parameter has the `from` and `size` properties. -** *`from` (Optional, number)*: Skips the specified number of categories. -** *`partition_field_value` (Optional, string)*: Only return categories for the specified partition. -** *`size` (Optional, number)*: Specifies the maximum number of categories to obtain. - -[discrete] -==== get_data_frame_analytics -Get data frame analytics job configuration info. -You can get information for multiple data frame analytics jobs in a single -API request by using a comma-separated list of data frame analytics jobs or a -wildcard expression. - -{ref}/get-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.getDataFrameAnalytics({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: Identifier for the data frame analytics job. If you do not specify this -option, the API returns information for the first hundred data frame -analytics jobs. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no data frame analytics -jobs that match. -2. Contains the `_all` string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -The default value returns an empty data_frame_analytics array when there -are no matches and the subset of results when there are partial matches. -If this parameter is `false`, the request returns a 404 status code when -there are no matches or only partial matches. -** *`from` (Optional, number)*: Skips the specified number of data frame analytics jobs. -** *`size` (Optional, number)*: Specifies the maximum number of data frame analytics jobs to obtain. -** *`exclude_generated` (Optional, boolean)*: Indicates if certain fields should be removed from the configuration on -retrieval. This allows the configuration to be in an acceptable format to -be retrieved and then added to another cluster. - -[discrete] -==== get_data_frame_analytics_stats -Get data frame analytics jobs usage info. - -{ref}/get-dfanalytics-stats.html[Endpoint documentation] -[source,ts] ----- -client.ml.getDataFrameAnalyticsStats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: Identifier for the data frame analytics job. If you do not specify this -option, the API returns information for the first hundred data frame -analytics jobs. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no data frame analytics -jobs that match. -2. Contains the `_all` string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -The default value returns an empty data_frame_analytics array when there -are no matches and the subset of results when there are partial matches. -If this parameter is `false`, the request returns a 404 status code when -there are no matches or only partial matches. -** *`from` (Optional, number)*: Skips the specified number of data frame analytics jobs. -** *`size` (Optional, number)*: Specifies the maximum number of data frame analytics jobs to obtain. -** *`verbose` (Optional, boolean)*: Defines whether the stats response should be verbose. - -[discrete] -==== get_datafeed_stats -Get datafeeds usage info. -You can get statistics for multiple datafeeds in a single API request by -using a comma-separated list of datafeeds or a wildcard expression. You can -get statistics for all datafeeds by using `_all`, by specifying `*` as the -``, or by omitting the ``. If the datafeed is stopped, the -only information you receive is the `datafeed_id` and the `state`. -This API returns a maximum of 10,000 datafeeds. - -{ref}/ml-get-datafeed-stats.html[Endpoint documentation] -[source,ts] ----- -client.ml.getDatafeedStats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (Optional, string | string[])*: Identifier for the datafeed. It can be a datafeed identifier or a -wildcard expression. If you do not specify one of these options, the API -returns information about all datafeeds. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no datafeeds that match. -2. Contains the `_all` string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -The default value is `true`, which returns an empty `datafeeds` array -when there are no matches and the subset of results when there are -partial matches. If this parameter is `false`, the request returns a -`404` status code when there are no matches or only partial matches. - -[discrete] -==== get_datafeeds -Get datafeeds configuration info. -You can get information for multiple datafeeds in a single API request by -using a comma-separated list of datafeeds or a wildcard expression. You can -get information for all datafeeds by using `_all`, by specifying `*` as the -``, or by omitting the ``. -This API returns a maximum of 10,000 datafeeds. - -{ref}/ml-get-datafeed.html[Endpoint documentation] -[source,ts] ----- -client.ml.getDatafeeds({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (Optional, string | string[])*: Identifier for the datafeed. It can be a datafeed identifier or a -wildcard expression. If you do not specify one of these options, the API -returns information about all datafeeds. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no datafeeds that match. -2. Contains the `_all` string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -The default value is `true`, which returns an empty `datafeeds` array -when there are no matches and the subset of results when there are -partial matches. If this parameter is `false`, the request returns a -`404` status code when there are no matches or only partial matches. -** *`exclude_generated` (Optional, boolean)*: Indicates if certain fields should be removed from the configuration on -retrieval. This allows the configuration to be in an acceptable format to -be retrieved and then added to another cluster. - -[discrete] -==== get_filters -Get filters. -You can get a single filter or all filters. - -{ref}/ml-get-filter.html[Endpoint documentation] -[source,ts] ----- -client.ml.getFilters({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`filter_id` (Optional, string | string[])*: A string that uniquely identifies a filter. -** *`from` (Optional, number)*: Skips the specified number of filters. -** *`size` (Optional, number)*: Specifies the maximum number of filters to obtain. - -[discrete] -==== get_influencers -Get anomaly detection job results for influencers. -Influencers are the entities that have contributed to, or are to blame for, -the anomalies. Influencer results are available only if an -`influencer_field_name` is specified in the job configuration. - -{ref}/ml-get-influencer.html[Endpoint documentation] -[source,ts] ----- -client.ml.getInfluencers({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`page` (Optional, { from, size })*: Configures pagination. -This parameter has the `from` and `size` properties. -** *`desc` (Optional, boolean)*: If true, the results are sorted in descending order. -** *`end` (Optional, string | Unit)*: Returns influencers with timestamps earlier than this time. -The default value means it is unset and results are not limited to -specific timestamps. -** *`exclude_interim` (Optional, boolean)*: If true, the output excludes interim results. By default, interim results -are included. -** *`influencer_score` (Optional, number)*: Returns influencers with anomaly scores greater than or equal to this -value. -** *`from` (Optional, number)*: Skips the specified number of influencers. -** *`size` (Optional, number)*: Specifies the maximum number of influencers to obtain. -** *`sort` (Optional, string)*: Specifies the sort field for the requested influencers. By default, the -influencers are sorted by the `influencer_score` value. -** *`start` (Optional, string | Unit)*: Returns influencers with timestamps after this time. The default value -means it is unset and results are not limited to specific timestamps. - -[discrete] -==== get_job_stats -Get anomaly detection jobs usage info. - -{ref}/ml-get-job-stats.html[Endpoint documentation] -[source,ts] ----- -client.ml.getJobStats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (Optional, string)*: Identifier for the anomaly detection job. It can be a job identifier, a -group name, a list of jobs, or a wildcard expression. If -you do not specify one of these options, the API returns information for -all anomaly detection jobs. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no jobs that match. -2. Contains the _all string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -If `true`, the API returns an empty `jobs` array when -there are no matches and the subset of results when there are partial -matches. If `false`, the API returns a `404` status -code when there are no matches or only partial matches. - -[discrete] -==== get_jobs -Get anomaly detection jobs configuration info. -You can get information for multiple anomaly detection jobs in a single API -request by using a group name, a comma-separated list of jobs, or a wildcard -expression. You can get information for all anomaly detection jobs by using -`_all`, by specifying `*` as the ``, or by omitting the ``. - -{ref}/ml-get-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.getJobs({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (Optional, string | string[])*: Identifier for the anomaly detection job. It can be a job identifier, a -group name, or a wildcard expression. If you do not specify one of these -options, the API returns information for all anomaly detection jobs. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no jobs that match. -2. Contains the _all string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -The default value is `true`, which returns an empty `jobs` array when -there are no matches and the subset of results when there are partial -matches. If this parameter is `false`, the request returns a `404` status -code when there are no matches or only partial matches. -** *`exclude_generated` (Optional, boolean)*: Indicates if certain fields should be removed from the configuration on -retrieval. This allows the configuration to be in an acceptable format to -be retrieved and then added to another cluster. - -[discrete] -==== get_memory_stats -Get machine learning memory usage info. -Get information about how machine learning jobs and trained models are using memory, -on each node, both within the JVM heap, and natively, outside of the JVM. - -{ref}/get-ml-memory.html[Endpoint documentation] -[source,ts] ----- -client.ml.getMemoryStats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string)*: The names of particular nodes in the cluster to target. For example, `nodeId1,nodeId2` or -`ml:true` -** *`human` (Optional, boolean)*: Specify this query parameter to include the fields with units in the response. Otherwise only -the `_in_bytes` sizes are returned in the response. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout -expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request -fails and returns an error. - -[discrete] -==== get_model_snapshot_upgrade_stats -Get anomaly detection job model snapshot upgrade usage info. - -{ref}/ml-get-job-model-snapshot-upgrade-stats.html[Endpoint documentation] -[source,ts] ----- -client.ml.getModelSnapshotUpgradeStats({ job_id, snapshot_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`snapshot_id` (string)*: A numerical character string that uniquely identifies the model snapshot. You can get information for multiple -snapshots by using a list or a wildcard expression. You can get all snapshots by using `_all`, -by specifying `*` as the snapshot ID, or by omitting the snapshot ID. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - - - Contains wildcard expressions and there are no jobs that match. - - Contains the _all string or no identifiers and there are no matches. - - Contains wildcard expressions and there are only partial matches. - -The default value is true, which returns an empty jobs array when there are no matches and the subset of results -when there are partial matches. If this parameter is false, the request returns a 404 status code when there are -no matches or only partial matches. - -[discrete] -==== get_model_snapshots -Get model snapshots info. - -{ref}/ml-get-snapshot.html[Endpoint documentation] -[source,ts] ----- -client.ml.getModelSnapshots({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`snapshot_id` (Optional, string)*: A numerical character string that uniquely identifies the model snapshot. You can get information for multiple -snapshots by using a list or a wildcard expression. You can get all snapshots by using `_all`, -by specifying `*` as the snapshot ID, or by omitting the snapshot ID. -** *`desc` (Optional, boolean)*: Refer to the description for the `desc` query parameter. -** *`end` (Optional, string | Unit)*: Refer to the description for the `end` query parameter. -** *`page` (Optional, { from, size })* -** *`sort` (Optional, string)*: Refer to the description for the `sort` query parameter. -** *`start` (Optional, string | Unit)*: Refer to the description for the `start` query parameter. -** *`from` (Optional, number)*: Skips the specified number of snapshots. -** *`size` (Optional, number)*: Specifies the maximum number of snapshots to obtain. - -[discrete] -==== get_overall_buckets -Get overall bucket results. - -Retrievs overall bucket results that summarize the bucket results of -multiple anomaly detection jobs. - -The `overall_score` is calculated by combining the scores of all the -buckets within the overall bucket span. First, the maximum -`anomaly_score` per anomaly detection job in the overall bucket is -calculated. Then the `top_n` of those scores are averaged to result in -the `overall_score`. This means that you can fine-tune the -`overall_score` so that it is more or less sensitive to the number of -jobs that detect an anomaly at the same time. For example, if you set -`top_n` to `1`, the `overall_score` is the maximum bucket score in the -overall bucket. Alternatively, if you set `top_n` to the number of jobs, -the `overall_score` is high only when all jobs detect anomalies in that -overall bucket. If you set the `bucket_span` parameter (to a value -greater than its default), the `overall_score` is the maximum -`overall_score` of the overall buckets that have a span equal to the -jobs' largest bucket span. - -{ref}/ml-get-overall-buckets.html[Endpoint documentation] -[source,ts] ----- -client.ml.getOverallBuckets({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. It can be a job identifier, a -group name, a list of jobs or groups, or a wildcard -expression. - -You can summarize the bucket results for all anomaly detection jobs by -using `_all` or by specifying `*` as the ``. -** *`allow_no_match` (Optional, boolean)*: Refer to the description for the `allow_no_match` query parameter. -** *`bucket_span` (Optional, string | -1 | 0)*: Refer to the description for the `bucket_span` query parameter. -** *`end` (Optional, string | Unit)*: Refer to the description for the `end` query parameter. -** *`exclude_interim` (Optional, boolean)*: Refer to the description for the `exclude_interim` query parameter. -** *`overall_score` (Optional, number | string)*: Refer to the description for the `overall_score` query parameter. -** *`start` (Optional, string | Unit)*: Refer to the description for the `start` query parameter. -** *`top_n` (Optional, number)*: Refer to the description for the `top_n` query parameter. - -[discrete] -==== get_records -Get anomaly records for an anomaly detection job. -Records contain the detailed analytical results. They describe the anomalous -activity that has been identified in the input data based on the detector -configuration. -There can be many anomaly records depending on the characteristics and size -of the input data. In practice, there are often too many to be able to -manually process them. The machine learning features therefore perform a -sophisticated aggregation of the anomaly records into buckets. -The number of record results depends on the number of anomalies found in each -bucket, which relates to the number of time series being modeled and the -number of detectors. - -{ref}/ml-get-record.html[Endpoint documentation] -[source,ts] ----- -client.ml.getRecords({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`desc` (Optional, boolean)*: Refer to the description for the `desc` query parameter. -** *`end` (Optional, string | Unit)*: Refer to the description for the `end` query parameter. -** *`exclude_interim` (Optional, boolean)*: Refer to the description for the `exclude_interim` query parameter. -** *`page` (Optional, { from, size })* -** *`record_score` (Optional, number)*: Refer to the description for the `record_score` query parameter. -** *`sort` (Optional, string)*: Refer to the description for the `sort` query parameter. -** *`start` (Optional, string | Unit)*: Refer to the description for the `start` query parameter. -** *`from` (Optional, number)*: Skips the specified number of records. -** *`size` (Optional, number)*: Specifies the maximum number of records to obtain. - -[discrete] -==== get_trained_models -Get trained model configuration info. - -{ref}/get-trained-models.html[Endpoint documentation] -[source,ts] ----- -client.ml.getTrainedModels({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (Optional, string | string[])*: The unique identifier of the trained model or a model alias. - -You can get information for multiple trained models in a single API -request by using a list of model IDs or a wildcard -expression. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -- Contains wildcard expressions and there are no models that match. -- Contains the _all string or no identifiers and there are no matches. -- Contains wildcard expressions and there are only partial matches. - -If true, it returns an empty array when there are no matches and the -subset of results when there are partial matches. -** *`decompress_definition` (Optional, boolean)*: Specifies whether the included model definition should be returned as a -JSON map (true) or in a custom compressed format (false). -** *`exclude_generated` (Optional, boolean)*: Indicates if certain fields should be removed from the configuration on -retrieval. This allows the configuration to be in an acceptable format to -be retrieved and then added to another cluster. -** *`from` (Optional, number)*: Skips the specified number of models. -** *`include` (Optional, Enum("definition" | "feature_importance_baseline" | "hyperparameters" | "total_feature_importance" | "definition_status"))*: A comma delimited string of optional fields to include in the response -body. -** *`size` (Optional, number)*: Specifies the maximum number of models to obtain. -** *`tags` (Optional, string | string[])*: A comma delimited string of tags. A trained model can have many tags, or -none. When supplied, only trained models that contain all the supplied -tags are returned. - -[discrete] -==== get_trained_models_stats -Get trained models usage info. -You can get usage information for multiple trained -models in a single API request by using a comma-separated list of model IDs or a wildcard expression. - -{ref}/get-trained-models-stats.html[Endpoint documentation] -[source,ts] ----- -client.ml.getTrainedModelsStats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (Optional, string | string[])*: The unique identifier of the trained model or a model alias. It can be a -list or a wildcard expression. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -- Contains wildcard expressions and there are no models that match. -- Contains the _all string or no identifiers and there are no matches. -- Contains wildcard expressions and there are only partial matches. - -If true, it returns an empty array when there are no matches and the -subset of results when there are partial matches. -** *`from` (Optional, number)*: Skips the specified number of models. -** *`size` (Optional, number)*: Specifies the maximum number of models to obtain. - -[discrete] -==== infer_trained_model -Evaluate a trained model. - -{ref}/infer-trained-model.html[Endpoint documentation] -[source,ts] ----- -client.ml.inferTrainedModel({ model_id, docs }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. -** *`docs` (Record[])*: An array of objects to pass to the model for inference. The objects should contain a fields matching your -configured trained model input. Typically, for NLP models, the field name is `text_field`. -Currently, for NLP models, only a single value is allowed. -** *`inference_config` (Optional, { regression, classification, text_classification, zero_shot_classification, fill_mask, ner, pass_through, text_embedding, text_expansion, question_answering })*: The inference configuration updates to apply on the API call -** *`timeout` (Optional, string | -1 | 0)*: Controls the amount of time to wait for inference results. - -[discrete] -==== info -Return ML defaults and limits. -Returns defaults and limits used by machine learning. -This endpoint is designed to be used by a user interface that needs to fully -understand machine learning configurations where some options are not -specified, meaning that the defaults should be used. This endpoint may be -used to find out what those defaults are. It also provides information about -the maximum size of machine learning jobs that could run in the current -cluster configuration. - -{ref}/get-ml-info.html[Endpoint documentation] -[source,ts] ----- -client.ml.info() ----- - - -[discrete] -==== open_job -Open anomaly detection jobs. -An anomaly detection job must be opened to be ready to receive and analyze -data. It can be opened and closed multiple times throughout its lifecycle. -When you open a new job, it starts with an empty model. -When you open an existing job, the most recent model state is automatically -loaded. The job is ready to resume its analysis from where it left off, once -new data is received. - -{ref}/ml-open-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.openJob({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`timeout` (Optional, string | -1 | 0)*: Refer to the description for the `timeout` query parameter. - -[discrete] -==== post_calendar_events -Add scheduled events to the calendar. - -{ref}/ml-post-calendar-event.html[Endpoint documentation] -[source,ts] ----- -client.ml.postCalendarEvents({ calendar_id, events }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (string)*: A string that uniquely identifies a calendar. -** *`events` ({ calendar_id, event_id, description, end_time, start_time, skip_result, skip_model_update, force_time_shift }[])*: A list of one of more scheduled events. The event’s start and end times can be specified as integer milliseconds since the epoch or as a string in ISO 8601 format. - -[discrete] -==== post_data -Send data to an anomaly detection job for analysis. - -IMPORTANT: For each job, data can be accepted from only a single connection at a time. -It is not currently possible to post data to multiple jobs using wildcards or a comma-separated list. - -{ref}/ml-post-data.html[Endpoint documentation] -[source,ts] ----- -client.ml.postData({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. The job must have a state of open to receive and process the data. -** *`data` (Optional, TData[])* -** *`reset_end` (Optional, string | Unit)*: Specifies the end of the bucket resetting range. -** *`reset_start` (Optional, string | Unit)*: Specifies the start of the bucket resetting range. - -[discrete] -==== preview_data_frame_analytics -Preview features used by data frame analytics. -Previews the extracted features used by a data frame analytics config. - -{ref}/preview-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.previewDataFrameAnalytics({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: Identifier for the data frame analytics job. -** *`config` (Optional, { source, analysis, model_memory_limit, max_num_threads, analyzed_fields })*: A data frame analytics config as described in create data frame analytics -jobs. Note that `id` and `dest` don’t need to be provided in the context of -this API. - -[discrete] -==== preview_datafeed -Preview a datafeed. -This API returns the first "page" of search results from a datafeed. -You can preview an existing datafeed or provide configuration details for a datafeed -and anomaly detection job in the API. The preview shows the structure of the data -that will be passed to the anomaly detection engine. -IMPORTANT: When Elasticsearch security features are enabled, the preview uses the credentials of the user that -called the API. However, when the datafeed starts it uses the roles of the last user that created or updated the -datafeed. To get a preview that accurately reflects the behavior of the datafeed, use the appropriate credentials. -You can also use secondary authorization headers to supply the credentials. - -{ref}/ml-preview-datafeed.html[Endpoint documentation] -[source,ts] ----- -client.ml.previewDatafeed({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (Optional, string)*: A numerical character string that uniquely identifies the datafeed. This identifier can contain lowercase -alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start and end with alphanumeric -characters. NOTE: If you use this path parameter, you cannot provide datafeed or anomaly detection job -configuration details in the request body. -** *`datafeed_config` (Optional, { aggregations, chunking_config, datafeed_id, delayed_data_check_config, frequency, indices, indices_options, job_id, max_empty_searches, query, query_delay, runtime_mappings, script_fields, scroll_size })*: The datafeed definition to preview. -** *`job_config` (Optional, { allow_lazy_open, analysis_config, analysis_limits, background_persist_interval, custom_settings, daily_model_snapshot_retention_after_days, data_description, datafeed_config, description, groups, job_id, job_type, model_plot_config, model_snapshot_retention_days, renormalization_window_days, results_index_name, results_retention_days })*: The configuration details for the anomaly detection job that is associated with the datafeed. If the -`datafeed_config` object does not include a `job_id` that references an existing anomaly detection job, you must -supply this `job_config` object. If you include both a `job_id` and a `job_config`, the latter information is -used. You cannot specify a `job_config` object unless you also supply a `datafeed_config` object. -** *`start` (Optional, string | Unit)*: The start time from where the datafeed preview should begin -** *`end` (Optional, string | Unit)*: The end time when the datafeed preview should stop - -[discrete] -==== put_calendar -Create a calendar. - -{ref}/ml-put-calendar.html[Endpoint documentation] -[source,ts] ----- -client.ml.putCalendar({ calendar_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (string)*: A string that uniquely identifies a calendar. -** *`job_ids` (Optional, string[])*: An array of anomaly detection job identifiers. -** *`description` (Optional, string)*: A description of the calendar. - -[discrete] -==== put_calendar_job -Add anomaly detection job to calendar. - -{ref}/ml-put-calendar-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.putCalendarJob({ calendar_id, job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`calendar_id` (string)*: A string that uniquely identifies a calendar. -** *`job_id` (string | string[])*: An identifier for the anomaly detection jobs. It can be a job identifier, a group name, or a list of jobs or groups. - -[discrete] -==== put_data_frame_analytics -Create a data frame analytics job. -This API creates a data frame analytics job that performs an analysis on the -source indices and stores the outcome in a destination index. - -{ref}/put-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.putDataFrameAnalytics({ id, analysis, dest, source }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the data frame analytics job. This identifier can contain -lowercase alphanumeric characters (a-z and 0-9), hyphens, and -underscores. It must start and end with alphanumeric characters. -** *`analysis` ({ classification, outlier_detection, regression })*: The analysis configuration, which contains the information necessary to -perform one of the following types of analysis: classification, outlier -detection, or regression. -** *`dest` ({ index, results_field })*: The destination configuration. -** *`source` ({ index, query, runtime_mappings, _source })*: The configuration of how to source the analysis data. -** *`allow_lazy_start` (Optional, boolean)*: Specifies whether this job can start when there is insufficient machine -learning node capacity for it to be immediately assigned to a node. If -set to `false` and a machine learning node with capacity to run the job -cannot be immediately found, the API returns an error. If set to `true`, -the API does not return an error; the job waits in the `starting` state -until sufficient machine learning node capacity is available. This -behavior is also affected by the cluster-wide -`xpack.ml.max_lazy_ml_nodes` setting. -** *`analyzed_fields` (Optional, { includes, excludes })*: Specifies `includes` and/or `excludes` patterns to select which fields -will be included in the analysis. The patterns specified in `excludes` -are applied last, therefore `excludes` takes precedence. In other words, -if the same field is specified in both `includes` and `excludes`, then -the field will not be included in the analysis. If `analyzed_fields` is -not set, only the relevant fields will be included. For example, all the -numeric fields for outlier detection. -The supported fields vary for each type of analysis. Outlier detection -requires numeric or `boolean` data to analyze. The algorithms don’t -support missing values therefore fields that have data types other than -numeric or boolean are ignored. Documents where included fields contain -missing values, null values, or an array are also ignored. Therefore the -`dest` index may contain documents that don’t have an outlier score. -Regression supports fields that are numeric, `boolean`, `text`, -`keyword`, and `ip` data types. It is also tolerant of missing values. -Fields that are supported are included in the analysis, other fields are -ignored. Documents where included fields contain an array with two or -more values are also ignored. Documents in the `dest` index that don’t -contain a results field are not included in the regression analysis. -Classification supports fields that are numeric, `boolean`, `text`, -`keyword`, and `ip` data types. It is also tolerant of missing values. -Fields that are supported are included in the analysis, other fields are -ignored. Documents where included fields contain an array with two or -more values are also ignored. Documents in the `dest` index that don’t -contain a results field are not included in the classification analysis. -Classification analysis can be improved by mapping ordinal variable -values to a single number. For example, in case of age ranges, you can -model the values as `0-14 = 0`, `15-24 = 1`, `25-34 = 2`, and so on. -** *`description` (Optional, string)*: A description of the job. -** *`max_num_threads` (Optional, number)*: The maximum number of threads to be used by the analysis. Using more -threads may decrease the time necessary to complete the analysis at the -cost of using more CPU. Note that the process may use additional threads -for operational functionality other than the analysis itself. -** *`model_memory_limit` (Optional, string)*: The approximate maximum amount of memory resources that are permitted for -analytical processing. If your `elasticsearch.yml` file contains an -`xpack.ml.max_model_memory_limit` setting, an error occurs when you try -to create data frame analytics jobs that have `model_memory_limit` values -greater than that setting. -** *`headers` (Optional, Record)* -** *`version` (Optional, string)* - -[discrete] -==== put_datafeed -Create a datafeed. -Datafeeds retrieve data from Elasticsearch for analysis by an anomaly detection job. -You can associate only one datafeed with each anomaly detection job. -The datafeed contains a query that runs at a defined interval (`frequency`). -If you are concerned about delayed data, you can add a delay (`query_delay`) at each interval. -When Elasticsearch security features are enabled, your datafeed remembers which roles the user who created it had -at the time of creation and runs the query using those same roles. If you provide secondary authorization headers, -those credentials are used instead. -You must use Kibana, this API, or the create anomaly detection jobs API to create a datafeed. Do not add a datafeed -directly to the `.ml-config` index. Do not give users `write` privileges on the `.ml-config` index. - -{ref}/ml-put-datafeed.html[Endpoint documentation] -[source,ts] ----- -client.ml.putDatafeed({ datafeed_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (string)*: A numerical character string that uniquely identifies the datafeed. -This identifier can contain lowercase alphanumeric characters (a-z and 0-9), hyphens, and underscores. -It must start and end with alphanumeric characters. -** *`aggregations` (Optional, Record)*: If set, the datafeed performs aggregation searches. -Support for aggregations is limited and should be used only with low cardinality data. -** *`chunking_config` (Optional, { mode, time_span })*: Datafeeds might be required to search over long time periods, for several months or years. -This search is split into time chunks in order to ensure the load on Elasticsearch is managed. -Chunking configuration controls how the size of these time chunks are calculated; -it is an advanced configuration option. -** *`delayed_data_check_config` (Optional, { check_window, enabled })*: Specifies whether the datafeed checks for missing data and the size of the window. -The datafeed can optionally search over indices that have already been read in an effort to determine whether -any data has subsequently been added to the index. If missing data is found, it is a good indication that the -`query_delay` is set too low and the data is being indexed after the datafeed has passed that moment in time. -This check runs only on real-time datafeeds. -** *`frequency` (Optional, string | -1 | 0)*: The interval at which scheduled queries are made while the datafeed runs in real time. -The default value is either the bucket span for short bucket spans, or, for longer bucket spans, a sensible -fraction of the bucket span. When `frequency` is shorter than the bucket span, interim results for the last -(partial) bucket are written then eventually overwritten by the full bucket results. If the datafeed uses -aggregations, this value must be divisible by the interval of the date histogram aggregation. -** *`indices` (Optional, string | string[])*: An array of index names. Wildcards are supported. If any of the indices are in remote clusters, the machine -learning nodes must have the `remote_cluster_client` role. -** *`indices_options` (Optional, { allow_no_indices, expand_wildcards, ignore_unavailable, ignore_throttled })*: Specifies index expansion options that are used during search -** *`job_id` (Optional, string)*: Identifier for the anomaly detection job. -** *`max_empty_searches` (Optional, number)*: If a real-time datafeed has never seen any data (including during any initial training period), it automatically -stops and closes the associated job after this many real-time searches return no documents. In other words, -it stops after `frequency` times `max_empty_searches` of real-time operation. If not set, a datafeed with no -end time that sees no data remains started until it is explicitly stopped. By default, it is not set. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: The Elasticsearch query domain-specific language (DSL). This value corresponds to the query object in an -Elasticsearch search POST body. All the options that are supported by Elasticsearch can be used, as this -object is passed verbatim to Elasticsearch. -** *`query_delay` (Optional, string | -1 | 0)*: The number of seconds behind real time that data is queried. For example, if data from 10:04 a.m. might -not be searchable in Elasticsearch until 10:06 a.m., set this property to 120 seconds. The default -value is randomly selected between `60s` and `120s`. This randomness improves the query performance -when there are multiple jobs running on the same node. -** *`runtime_mappings` (Optional, Record)*: Specifies runtime fields for the datafeed search. -** *`script_fields` (Optional, Record)*: Specifies scripts that evaluate custom expressions and returns script fields to the datafeed. -The detector configuration objects in a job can contain functions that use these script fields. -** *`scroll_size` (Optional, number)*: The size parameter that is used in Elasticsearch searches when the datafeed does not use aggregations. -The maximum value is the value of `index.max_result_window`, which is 10,000 by default. -** *`headers` (Optional, Record)* -** *`allow_no_indices` (Optional, boolean)*: If true, wildcard indices expressions that resolve into no concrete indices are ignored. This includes the `_all` -string or when no indices are specified. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. Supports a list of values. -** *`ignore_throttled` (Optional, boolean)*: If true, concrete, expanded, or aliased indices are ignored when frozen. -** *`ignore_unavailable` (Optional, boolean)*: If true, unavailable indices (missing or closed) are ignored. - -[discrete] -==== put_filter -Create a filter. -A filter contains a list of strings. It can be used by one or more anomaly detection jobs. -Specifically, filters are referenced in the `custom_rules` property of detector configuration objects. - -{ref}/ml-put-filter.html[Endpoint documentation] -[source,ts] ----- -client.ml.putFilter({ filter_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`filter_id` (string)*: A string that uniquely identifies a filter. -** *`description` (Optional, string)*: A description of the filter. -** *`items` (Optional, string[])*: The items of the filter. A wildcard `*` can be used at the beginning or the end of an item. -Up to 10000 items are allowed in each filter. - -[discrete] -==== put_job -Create an anomaly detection job. -If you include a `datafeed_config`, you must have read index privileges on the source index. - -{ref}/ml-put-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.putJob({ job_id, analysis_config, data_description }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: The identifier for the anomaly detection job. This identifier can contain lowercase alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start and end with alphanumeric characters. -** *`analysis_config` ({ bucket_span, categorization_analyzer, categorization_field_name, categorization_filters, detectors, influencers, latency, model_prune_window, multivariate_by_fields, per_partition_categorization, summary_count_field_name })*: Specifies how to analyze the data. After you create a job, you cannot change the analysis configuration; all the properties are informational. -** *`data_description` ({ format, time_field, time_format, field_delimiter })*: Defines the format of the input data when you send data to the job by using the post data API. Note that when configure a datafeed, these properties are automatically set. When data is received via the post data API, it is not stored in Elasticsearch. Only the results for anomaly detection are retained. -** *`allow_lazy_open` (Optional, boolean)*: Advanced configuration option. Specifies whether this job can open when there is insufficient machine learning node capacity for it to be immediately assigned to a node. By default, if a machine learning node with capacity to run the job cannot immediately be found, the open anomaly detection jobs API returns an error. However, this is also subject to the cluster-wide `xpack.ml.max_lazy_ml_nodes` setting. If this option is set to true, the open anomaly detection jobs API does not return an error and the job waits in the opening state until sufficient machine learning node capacity is available. -** *`analysis_limits` (Optional, { categorization_examples_limit, model_memory_limit })*: Limits can be applied for the resources required to hold the mathematical models in memory. These limits are approximate and can be set per job. They do not control the memory used by other processes, for example the Elasticsearch Java processes. -** *`background_persist_interval` (Optional, string | -1 | 0)*: Advanced configuration option. The time between each periodic persistence of the model. The default value is a randomized value between 3 to 4 hours, which avoids all jobs persisting at exactly the same time. The smallest allowed value is 1 hour. For very large models (several GB), persistence could take 10-20 minutes, so do not set the `background_persist_interval` value too low. -** *`custom_settings` (Optional, User-defined value)*: Advanced configuration option. Contains custom meta data about the job. -** *`daily_model_snapshot_retention_after_days` (Optional, number)*: Advanced configuration option, which affects the automatic removal of old model snapshots for this job. It specifies a period of time (in days) after which only the first snapshot per day is retained. This period is relative to the timestamp of the most recent snapshot for this job. Valid values range from 0 to `model_snapshot_retention_days`. -** *`datafeed_config` (Optional, { aggregations, chunking_config, datafeed_id, delayed_data_check_config, frequency, indices, indices_options, job_id, max_empty_searches, query, query_delay, runtime_mappings, script_fields, scroll_size })*: Defines a datafeed for the anomaly detection job. If Elasticsearch security features are enabled, your datafeed remembers which roles the user who created it had at the time of creation and runs the query using those same roles. If you provide secondary authorization headers, those credentials are used instead. -** *`description` (Optional, string)*: A description of the job. -** *`groups` (Optional, string[])*: A list of job groups. A job can belong to no groups or many. -** *`model_plot_config` (Optional, { annotations_enabled, enabled, terms })*: This advanced configuration option stores model information along with the results. It provides a more detailed view into anomaly detection. If you enable model plot it can add considerable overhead to the performance of the system; it is not feasible for jobs with many entities. Model plot provides a simplified and indicative view of the model and its bounds. It does not display complex features such as multivariate correlations or multimodal data. As such, anomalies may occasionally be reported which cannot be seen in the model plot. Model plot config can be configured when the job is created or updated later. It must be disabled if performance issues are experienced. -** *`model_snapshot_retention_days` (Optional, number)*: Advanced configuration option, which affects the automatic removal of old model snapshots for this job. It specifies the maximum period of time (in days) that snapshots are retained. This period is relative to the timestamp of the most recent snapshot for this job. By default, snapshots ten days older than the newest snapshot are deleted. -** *`renormalization_window_days` (Optional, number)*: Advanced configuration option. The period over which adjustments to the score are applied, as new data is seen. The default value is the longer of 30 days or 100 bucket spans. -** *`results_index_name` (Optional, string)*: A text string that affects the name of the machine learning results index. By default, the job generates an index named `.ml-anomalies-shared`. -** *`results_retention_days` (Optional, number)*: Advanced configuration option. The period of time (in days) that results are retained. Age is calculated relative to the timestamp of the latest bucket result. If this property has a non-null value, once per day at 00:30 (server time), results that are the specified number of days older than the latest bucket result are deleted from Elasticsearch. The default value is null, which means all results are retained. Annotations generated by the system also count as results for retention purposes; they are deleted after the same number of days as results. Annotations added by users are retained forever. - -[discrete] -==== put_trained_model -Create a trained model. -Enable you to supply a trained model that is not created by data frame analytics. - -{ref}/put-trained-models.html[Endpoint documentation] -[source,ts] ----- -client.ml.putTrainedModel({ model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. -** *`compressed_definition` (Optional, string)*: The compressed (GZipped and Base64 encoded) inference definition of the -model. If compressed_definition is specified, then definition cannot be -specified. -** *`definition` (Optional, { preprocessors, trained_model })*: The inference definition for the model. If definition is specified, then -compressed_definition cannot be specified. -** *`description` (Optional, string)*: A human-readable description of the inference trained model. -** *`inference_config` (Optional, { regression, classification, text_classification, zero_shot_classification, fill_mask, ner, pass_through, text_embedding, text_expansion, question_answering })*: The default configuration for inference. This can be either a regression -or classification configuration. It must match the underlying -definition.trained_model's target_type. For pre-packaged models such as -ELSER the config is not required. -** *`input` (Optional, { field_names })*: The input field names for the model definition. -** *`metadata` (Optional, User-defined value)*: An object map that contains metadata about the model. -** *`model_type` (Optional, Enum("tree_ensemble" | "lang_ident" | "pytorch"))*: The model type. -** *`model_size_bytes` (Optional, number)*: The estimated memory usage in bytes to keep the trained model in memory. -This property is supported only if defer_definition_decompression is true -or the model definition is not supplied. -** *`platform_architecture` (Optional, string)*: The platform architecture (if applicable) of the trained mode. If the model -only works on one platform, because it is heavily optimized for a particular -processor architecture and OS combination, then this field specifies which. -The format of the string must match the platform identifiers used by Elasticsearch, -so one of, `linux-x86_64`, `linux-aarch64`, `darwin-x86_64`, `darwin-aarch64`, -or `windows-x86_64`. For portable models (those that work independent of processor -architecture or OS features), leave this field unset. -** *`tags` (Optional, string[])*: An array of tags to organize the model. -** *`prefix_strings` (Optional, { ingest, search })*: Optional prefix strings applied at inference -** *`defer_definition_decompression` (Optional, boolean)*: If set to `true` and a `compressed_definition` is provided, -the request defers definition decompression and skips relevant -validations. -** *`wait_for_completion` (Optional, boolean)*: Whether to wait for all child operations (e.g. model download) -to complete. - -[discrete] -==== put_trained_model_alias -Create or update a trained model alias. -A trained model alias is a logical name used to reference a single trained -model. -You can use aliases instead of trained model identifiers to make it easier to -reference your models. For example, you can use aliases in inference -aggregations and processors. -An alias must be unique and refer to only a single trained model. However, -you can have multiple aliases for each trained model. -If you use this API to update an alias such that it references a different -trained model ID and the model uses a different type of data frame analytics, -an error occurs. For example, this situation occurs if you have a trained -model for regression analysis and a trained model for classification -analysis; you cannot reassign an alias from one type of trained model to -another. -If you use this API to update an alias and there are very few input fields in -common between the old and new trained models for the model alias, the API -returns a warning. - -{ref}/put-trained-models-aliases.html[Endpoint documentation] -[source,ts] ----- -client.ml.putTrainedModelAlias({ model_alias, model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_alias` (string)*: The alias to create or update. This value cannot end in numbers. -** *`model_id` (string)*: The identifier for the trained model that the alias refers to. -** *`reassign` (Optional, boolean)*: Specifies whether the alias gets reassigned to the specified trained -model if it is already assigned to a different model. If the alias is -already assigned and this parameter is false, the API returns an error. - -[discrete] -==== put_trained_model_definition_part -Create part of a trained model definition. - -{ref}/put-trained-model-definition-part.html[Endpoint documentation] -[source,ts] ----- -client.ml.putTrainedModelDefinitionPart({ model_id, part, definition, total_definition_length, total_parts }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. -** *`part` (number)*: The definition part number. When the definition is loaded for inference the definition parts are streamed in the -order of their part number. The first part must be `0` and the final part must be `total_parts - 1`. -** *`definition` (string)*: The definition part for the model. Must be a base64 encoded string. -** *`total_definition_length` (number)*: The total uncompressed definition length in bytes. Not base64 encoded. -** *`total_parts` (number)*: The total number of parts that will be uploaded. Must be greater than 0. - -[discrete] -==== put_trained_model_vocabulary -Create a trained model vocabulary. -This API is supported only for natural language processing (NLP) models. -The vocabulary is stored in the index as described in `inference_config.*.vocabulary` of the trained model definition. - -{ref}/put-trained-model-vocabulary.html[Endpoint documentation] -[source,ts] ----- -client.ml.putTrainedModelVocabulary({ model_id, vocabulary }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. -** *`vocabulary` (string[])*: The model vocabulary, which must not be empty. -** *`merges` (Optional, string[])*: The optional model merges if required by the tokenizer. -** *`scores` (Optional, number[])*: The optional vocabulary value scores if required by the tokenizer. - -[discrete] -==== reset_job -Reset an anomaly detection job. -All model state and results are deleted. The job is ready to start over as if -it had just been created. -It is not currently possible to reset multiple jobs using wildcards or a -comma separated list. - -{ref}/ml-reset-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.resetJob({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: The ID of the job to reset. -** *`wait_for_completion` (Optional, boolean)*: Should this request wait until the operation has completed before -returning. -** *`delete_user_annotations` (Optional, boolean)*: Specifies whether annotations that have been added by the -user should be deleted along with any auto-generated annotations when the job is -reset. - -[discrete] -==== revert_model_snapshot -Revert to a snapshot. -The machine learning features react quickly to anomalous input, learning new -behaviors in data. Highly anomalous input increases the variance in the -models whilst the system learns whether this is a new step-change in behavior -or a one-off event. In the case where this anomalous input is known to be a -one-off, then it might be appropriate to reset the model state to a time -before this event. For example, you might consider reverting to a saved -snapshot after Black Friday or a critical system failure. - -{ref}/ml-revert-snapshot.html[Endpoint documentation] -[source,ts] ----- -client.ml.revertModelSnapshot({ job_id, snapshot_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`snapshot_id` (string)*: You can specify `empty` as the . Reverting to the empty -snapshot means the anomaly detection job starts learning a new model from -scratch when it is started. -** *`delete_intervening_results` (Optional, boolean)*: Refer to the description for the `delete_intervening_results` query parameter. - -[discrete] -==== set_upgrade_mode -Set upgrade_mode for ML indices. -Sets a cluster wide upgrade_mode setting that prepares machine learning -indices for an upgrade. -When upgrading your cluster, in some circumstances you must restart your -nodes and reindex your machine learning indices. In those circumstances, -there must be no machine learning jobs running. You can close the machine -learning jobs, do the upgrade, then open all the jobs again. Alternatively, -you can use this API to temporarily halt tasks associated with the jobs and -datafeeds and prevent new jobs from opening. You can also use this API -during upgrades that do not require you to reindex your machine learning -indices, though stopping jobs is not a requirement in that case. -You can see the current value for the upgrade_mode setting by using the get -machine learning info API. - -{ref}/ml-set-upgrade-mode.html[Endpoint documentation] -[source,ts] ----- -client.ml.setUpgradeMode({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`enabled` (Optional, boolean)*: When `true`, it enables `upgrade_mode` which temporarily halts all job -and datafeed tasks and prohibits new job and datafeed tasks from -starting. -** *`timeout` (Optional, string | -1 | 0)*: The time to wait for the request to be completed. - -[discrete] -==== start_data_frame_analytics -Start a data frame analytics job. -A data frame analytics job can be started and stopped multiple times -throughout its lifecycle. -If the destination index does not exist, it is created automatically the -first time you start the data frame analytics job. The -`index.number_of_shards` and `index.number_of_replicas` settings for the -destination index are copied from the source index. If there are multiple -source indices, the destination index copies the highest setting values. The -mappings for the destination index are also copied from the source indices. -If there are any mapping conflicts, the job fails to start. -If the destination index exists, it is used as is. You can therefore set up -the destination index in advance with custom settings and mappings. - -{ref}/start-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.startDataFrameAnalytics({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the data frame analytics job. This identifier can contain -lowercase alphanumeric characters (a-z and 0-9), hyphens, and -underscores. It must start and end with alphanumeric characters. -** *`timeout` (Optional, string | -1 | 0)*: Controls the amount of time to wait until the data frame analytics job -starts. - -[discrete] -==== start_datafeed -Start datafeeds. - -A datafeed must be started in order to retrieve data from Elasticsearch. A datafeed can be started and stopped -multiple times throughout its lifecycle. - -Before you can start a datafeed, the anomaly detection job must be open. Otherwise, an error occurs. - -If you restart a stopped datafeed, it continues processing input data from the next millisecond after it was stopped. -If new data was indexed for that exact millisecond between stopping and starting, it will be ignored. - -When Elasticsearch security features are enabled, your datafeed remembers which roles the last user to create or -update it had at the time of creation or update and runs the query using those same roles. If you provided secondary -authorization headers when you created or updated the datafeed, those credentials are used instead. - -{ref}/ml-start-datafeed.html[Endpoint documentation] -[source,ts] ----- -client.ml.startDatafeed({ datafeed_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (string)*: A numerical character string that uniquely identifies the datafeed. This identifier can contain lowercase -alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start and end with alphanumeric -characters. -** *`end` (Optional, string | Unit)*: Refer to the description for the `end` query parameter. -** *`start` (Optional, string | Unit)*: Refer to the description for the `start` query parameter. -** *`timeout` (Optional, string | -1 | 0)*: Refer to the description for the `timeout` query parameter. - -[discrete] -==== start_trained_model_deployment -Start a trained model deployment. -It allocates the model to every machine learning node. - -{ref}/start-trained-model-deployment.html[Endpoint documentation] -[source,ts] ----- -client.ml.startTrainedModelDeployment({ model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. Currently, only PyTorch models are supported. -** *`cache_size` (Optional, number | string)*: The inference cache size (in memory outside the JVM heap) per node for the model. -The default value is the same size as the `model_size_bytes`. To disable the cache, -`0b` can be provided. -** *`deployment_id` (Optional, string)*: A unique identifier for the deployment of the model. -** *`number_of_allocations` (Optional, number)*: The number of model allocations on each node where the model is deployed. -All allocations on a node share the same copy of the model in memory but use -a separate set of threads to evaluate the model. -Increasing this value generally increases the throughput. -If this setting is greater than the number of hardware threads -it will automatically be changed to a value less than the number of hardware threads. -** *`priority` (Optional, Enum("normal" | "low"))*: The deployment priority. -** *`queue_capacity` (Optional, number)*: Specifies the number of inference requests that are allowed in the queue. After the number of requests exceeds -this value, new requests are rejected with a 429 error. -** *`threads_per_allocation` (Optional, number)*: Sets the number of threads used by each model allocation during inference. This generally increases -the inference speed. The inference process is a compute-bound process; any number -greater than the number of available hardware threads on the machine does not increase the -inference speed. If this setting is greater than the number of hardware threads -it will automatically be changed to a value less than the number of hardware threads. -** *`timeout` (Optional, string | -1 | 0)*: Specifies the amount of time to wait for the model to deploy. -** *`wait_for` (Optional, Enum("started" | "starting" | "fully_allocated"))*: Specifies the allocation status to wait for before returning. - -[discrete] -==== stop_data_frame_analytics -Stop data frame analytics jobs. -A data frame analytics job can be started and stopped multiple times -throughout its lifecycle. - -{ref}/stop-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.stopDataFrameAnalytics({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the data frame analytics job. This identifier can contain -lowercase alphanumeric characters (a-z and 0-9), hyphens, and -underscores. It must start and end with alphanumeric characters. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no data frame analytics -jobs that match. -2. Contains the _all string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -The default value is true, which returns an empty data_frame_analytics -array when there are no matches and the subset of results when there are -partial matches. If this parameter is false, the request returns a 404 -status code when there are no matches or only partial matches. -** *`force` (Optional, boolean)*: If true, the data frame analytics job is stopped forcefully. -** *`timeout` (Optional, string | -1 | 0)*: Controls the amount of time to wait until the data frame analytics job -stops. Defaults to 20 seconds. - -[discrete] -==== stop_datafeed -Stop datafeeds. -A datafeed that is stopped ceases to retrieve data from Elasticsearch. A datafeed can be started and stopped -multiple times throughout its lifecycle. - -{ref}/ml-stop-datafeed.html[Endpoint documentation] -[source,ts] ----- -client.ml.stopDatafeed({ datafeed_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (string)*: Identifier for the datafeed. You can stop multiple datafeeds in a single API request by using a comma-separated -list of datafeeds or a wildcard expression. You can close all datafeeds by using `_all` or by specifying `*` as -the identifier. -** *`allow_no_match` (Optional, boolean)*: Refer to the description for the `allow_no_match` query parameter. -** *`force` (Optional, boolean)*: Refer to the description for the `force` query parameter. -** *`timeout` (Optional, string | -1 | 0)*: Refer to the description for the `timeout` query parameter. - -[discrete] -==== stop_trained_model_deployment -Stop a trained model deployment. - -{ref}/stop-trained-model-deployment.html[Endpoint documentation] -[source,ts] ----- -client.ml.stopTrainedModelDeployment({ model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: contains wildcard expressions and there are no deployments that match; -contains the `_all` string or no identifiers and there are no matches; or contains wildcard expressions and -there are only partial matches. By default, it returns an empty array when there are no matches and the subset of results when there are partial matches. -If `false`, the request returns a 404 status code when there are no matches or only partial matches. -** *`force` (Optional, boolean)*: Forcefully stops the deployment, even if it is used by ingest pipelines. You can't use these pipelines until you -restart the model deployment. - -[discrete] -==== update_data_frame_analytics -Update a data frame analytics job. - -{ref}/update-dfanalytics.html[Endpoint documentation] -[source,ts] ----- -client.ml.updateDataFrameAnalytics({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the data frame analytics job. This identifier can contain -lowercase alphanumeric characters (a-z and 0-9), hyphens, and -underscores. It must start and end with alphanumeric characters. -** *`description` (Optional, string)*: A description of the job. -** *`model_memory_limit` (Optional, string)*: The approximate maximum amount of memory resources that are permitted for -analytical processing. If your `elasticsearch.yml` file contains an -`xpack.ml.max_model_memory_limit` setting, an error occurs when you try -to create data frame analytics jobs that have `model_memory_limit` values -greater than that setting. -** *`max_num_threads` (Optional, number)*: The maximum number of threads to be used by the analysis. Using more -threads may decrease the time necessary to complete the analysis at the -cost of using more CPU. Note that the process may use additional threads -for operational functionality other than the analysis itself. -** *`allow_lazy_start` (Optional, boolean)*: Specifies whether this job can start when there is insufficient machine -learning node capacity for it to be immediately assigned to a node. - -[discrete] -==== update_datafeed -Update a datafeed. -You must stop and start the datafeed for the changes to be applied. -When Elasticsearch security features are enabled, your datafeed remembers which roles the user who updated it had at -the time of the update and runs the query using those same roles. If you provide secondary authorization headers, -those credentials are used instead. - -{ref}/ml-update-datafeed.html[Endpoint documentation] -[source,ts] ----- -client.ml.updateDatafeed({ datafeed_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`datafeed_id` (string)*: A numerical character string that uniquely identifies the datafeed. -This identifier can contain lowercase alphanumeric characters (a-z and 0-9), hyphens, and underscores. -It must start and end with alphanumeric characters. -** *`aggregations` (Optional, Record)*: If set, the datafeed performs aggregation searches. Support for aggregations is limited and should be used only -with low cardinality data. -** *`chunking_config` (Optional, { mode, time_span })*: Datafeeds might search over long time periods, for several months or years. This search is split into time -chunks in order to ensure the load on Elasticsearch is managed. Chunking configuration controls how the size of -these time chunks are calculated; it is an advanced configuration option. -** *`delayed_data_check_config` (Optional, { check_window, enabled })*: Specifies whether the datafeed checks for missing data and the size of the window. The datafeed can optionally -search over indices that have already been read in an effort to determine whether any data has subsequently been -added to the index. If missing data is found, it is a good indication that the `query_delay` is set too low and -the data is being indexed after the datafeed has passed that moment in time. This check runs only on real-time -datafeeds. -** *`frequency` (Optional, string | -1 | 0)*: The interval at which scheduled queries are made while the datafeed runs in real time. The default value is -either the bucket span for short bucket spans, or, for longer bucket spans, a sensible fraction of the bucket -span. When `frequency` is shorter than the bucket span, interim results for the last (partial) bucket are -written then eventually overwritten by the full bucket results. If the datafeed uses aggregations, this value -must be divisible by the interval of the date histogram aggregation. -** *`indices` (Optional, string[])*: An array of index names. Wildcards are supported. If any of the indices are in remote clusters, the machine -learning nodes must have the `remote_cluster_client` role. -** *`indices_options` (Optional, { allow_no_indices, expand_wildcards, ignore_unavailable, ignore_throttled })*: Specifies index expansion options that are used during search. -** *`job_id` (Optional, string)* -** *`max_empty_searches` (Optional, number)*: If a real-time datafeed has never seen any data (including during any initial training period), it automatically -stops and closes the associated job after this many real-time searches return no documents. In other words, -it stops after `frequency` times `max_empty_searches` of real-time operation. If not set, a datafeed with no -end time that sees no data remains started until it is explicitly stopped. By default, it is not set. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: The Elasticsearch query domain-specific language (DSL). This value corresponds to the query object in an -Elasticsearch search POST body. All the options that are supported by Elasticsearch can be used, as this -object is passed verbatim to Elasticsearch. Note that if you change the query, the analyzed data is also -changed. Therefore, the time required to learn might be long and the understandability of the results is -unpredictable. If you want to make significant changes to the source data, it is recommended that you -clone the job and datafeed and make the amendments in the clone. Let both run in parallel and close one -when you are satisfied with the results of the job. -** *`query_delay` (Optional, string | -1 | 0)*: The number of seconds behind real time that data is queried. For example, if data from 10:04 a.m. might -not be searchable in Elasticsearch until 10:06 a.m., set this property to 120 seconds. The default -value is randomly selected between `60s` and `120s`. This randomness improves the query performance -when there are multiple jobs running on the same node. -** *`runtime_mappings` (Optional, Record)*: Specifies runtime fields for the datafeed search. -** *`script_fields` (Optional, Record)*: Specifies scripts that evaluate custom expressions and returns script fields to the datafeed. -The detector configuration objects in a job can contain functions that use these script fields. -** *`scroll_size` (Optional, number)*: The size parameter that is used in Elasticsearch searches when the datafeed does not use aggregations. -The maximum value is the value of `index.max_result_window`. -** *`allow_no_indices` (Optional, boolean)*: If `true`, wildcard indices expressions that resolve into no concrete indices are ignored. This includes the -`_all` string or when no indices are specified. -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: 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. Supports a list of values. Valid values are: - -* `all`: Match any data stream or index, including hidden ones. -* `closed`: Match closed, non-hidden indices. Also matches any non-hidden data stream. Data streams cannot be closed. -* `hidden`: Match hidden data streams and hidden indices. Must be combined with `open`, `closed`, or both. -* `none`: Wildcard patterns are not accepted. -* `open`: Match open, non-hidden indices. Also matches any non-hidden data stream. -** *`ignore_throttled` (Optional, boolean)*: If `true`, concrete, expanded or aliased indices are ignored when frozen. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, unavailable indices (missing or closed) are ignored. - -[discrete] -==== update_filter -Update a filter. -Updates the description of a filter, adds items, or removes items from the list. - -{ref}/ml-update-filter.html[Endpoint documentation] -[source,ts] ----- -client.ml.updateFilter({ filter_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`filter_id` (string)*: A string that uniquely identifies a filter. -** *`add_items` (Optional, string[])*: The items to add to the filter. -** *`description` (Optional, string)*: A description for the filter. -** *`remove_items` (Optional, string[])*: The items to remove from the filter. - -[discrete] -==== update_job -Update an anomaly detection job. -Updates certain properties of an anomaly detection job. - -{ref}/ml-update-job.html[Endpoint documentation] -[source,ts] ----- -client.ml.updateJob({ job_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the job. -** *`allow_lazy_open` (Optional, boolean)*: Advanced configuration option. Specifies whether this job can open when -there is insufficient machine learning node capacity for it to be -immediately assigned to a node. If `false` and a machine learning node -with capacity to run the job cannot immediately be found, the open -anomaly detection jobs API returns an error. However, this is also -subject to the cluster-wide `xpack.ml.max_lazy_ml_nodes` setting. If this -option is set to `true`, the open anomaly detection jobs API does not -return an error and the job waits in the opening state until sufficient -machine learning node capacity is available. -** *`analysis_limits` (Optional, { model_memory_limit })* -** *`background_persist_interval` (Optional, string | -1 | 0)*: Advanced configuration option. The time between each periodic persistence -of the model. -The default value is a randomized value between 3 to 4 hours, which -avoids all jobs persisting at exactly the same time. The smallest allowed -value is 1 hour. -For very large models (several GB), persistence could take 10-20 minutes, -so do not set the value too low. -If the job is open when you make the update, you must stop the datafeed, -close the job, then reopen the job and restart the datafeed for the -changes to take effect. -** *`custom_settings` (Optional, Record)*: Advanced configuration option. Contains custom meta data about the job. -For example, it can contain custom URL information as shown in Adding -custom URLs to machine learning results. -** *`categorization_filters` (Optional, string[])* -** *`description` (Optional, string)*: A description of the job. -** *`model_plot_config` (Optional, { annotations_enabled, enabled, terms })* -** *`model_prune_window` (Optional, string | -1 | 0)* -** *`daily_model_snapshot_retention_after_days` (Optional, number)*: Advanced configuration option, which affects the automatic removal of old -model snapshots for this job. It specifies a period of time (in days) -after which only the first snapshot per day is retained. This period is -relative to the timestamp of the most recent snapshot for this job. Valid -values range from 0 to `model_snapshot_retention_days`. For jobs created -before version 7.8.0, the default value matches -`model_snapshot_retention_days`. -** *`model_snapshot_retention_days` (Optional, number)*: Advanced configuration option, which affects the automatic removal of old -model snapshots for this job. It specifies the maximum period of time (in -days) that snapshots are retained. This period is relative to the -timestamp of the most recent snapshot for this job. -** *`renormalization_window_days` (Optional, number)*: Advanced configuration option. The period over which adjustments to the -score are applied, as new data is seen. -** *`results_retention_days` (Optional, number)*: Advanced configuration option. The period of time (in days) that results -are retained. Age is calculated relative to the timestamp of the latest -bucket result. If this property has a non-null value, once per day at -00:30 (server time), results that are the specified number of days older -than the latest bucket result are deleted from Elasticsearch. The default -value is null, which means all results are retained. -** *`groups` (Optional, string[])*: A list of job groups. A job can belong to no groups or many. -** *`detectors` (Optional, { by_field_name, custom_rules, detector_description, detector_index, exclude_frequent, field_name, function, over_field_name, partition_field_name, use_null }[])*: An array of detector update objects. -** *`per_partition_categorization` (Optional, { enabled, stop_on_warn })*: Settings related to how categorization interacts with partition fields. - -[discrete] -==== update_model_snapshot -Update a snapshot. -Updates certain properties of a snapshot. - -{ref}/ml-update-snapshot.html[Endpoint documentation] -[source,ts] ----- -client.ml.updateModelSnapshot({ job_id, snapshot_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`snapshot_id` (string)*: Identifier for the model snapshot. -** *`description` (Optional, string)*: A description of the model snapshot. -** *`retain` (Optional, boolean)*: If `true`, this snapshot will not be deleted during automatic cleanup of -snapshots older than `model_snapshot_retention_days`. However, this -snapshot will be deleted when the job is deleted. - -[discrete] -==== update_trained_model_deployment -Update a trained model deployment. - -{ref}/update-trained-model-deployment.html[Endpoint documentation] -[source,ts] ----- -client.ml.updateTrainedModelDeployment({ model_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`model_id` (string)*: The unique identifier of the trained model. Currently, only PyTorch models are supported. -** *`number_of_allocations` (Optional, number)*: The number of model allocations on each node where the model is deployed. -All allocations on a node share the same copy of the model in memory but use -a separate set of threads to evaluate the model. -Increasing this value generally increases the throughput. -If this setting is greater than the number of hardware threads -it will automatically be changed to a value less than the number of hardware threads. - -[discrete] -==== upgrade_job_snapshot -Upgrade a snapshot. -Upgrades an anomaly detection model snapshot to the latest major version. -Over time, older snapshot formats are deprecated and removed. Anomaly -detection jobs support only snapshots that are from the current or previous -major version. -This API provides a means to upgrade a snapshot to the current major version. -This aids in preparing the cluster for an upgrade to the next major version. -Only one snapshot per anomaly detection job can be upgraded at a time and the -upgraded snapshot cannot be the current snapshot of the anomaly detection -job. - -{ref}/ml-upgrade-job-model-snapshot.html[Endpoint documentation] -[source,ts] ----- -client.ml.upgradeJobSnapshot({ job_id, snapshot_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`job_id` (string)*: Identifier for the anomaly detection job. -** *`snapshot_id` (string)*: A numerical character string that uniquely identifies the model snapshot. -** *`wait_for_completion` (Optional, boolean)*: When true, the API won’t respond until the upgrade is complete. -Otherwise, it responds as soon as the upgrade task is assigned to a node. -** *`timeout` (Optional, string | -1 | 0)*: Controls the time to wait for the request to complete. - -[discrete] -=== monitoring -[discrete] -==== bulk -Used by the monitoring features to send monitoring data. - -{ref}/monitor-elasticsearch-cluster.html[Endpoint documentation] -[source,ts] ----- -client.monitoring.bulk({ system_id, system_api_version, interval }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`system_id` (string)*: Identifier of the monitored system -** *`system_api_version` (string)* -** *`interval` (string | -1 | 0)*: Collection interval (e.g., '10s' or '10000ms') of the payload -** *`type` (Optional, string)*: Default document type for items which don't provide one -** *`operations` (Optional, { index, create, update, delete } | { detect_noop, doc, doc_as_upsert, script, scripted_upsert, _source, upsert } | object[])* - -[discrete] -=== nodes -[discrete] -==== clear_repositories_metering_archive -You can use this API to clear the archived repositories metering information in the cluster. - -{ref}/clear-repositories-metering-archive-api.html[Endpoint documentation] -[source,ts] ----- -client.nodes.clearRepositoriesMeteringArchive({ node_id, max_archive_version }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (string | string[])*: List of node IDs or names used to limit returned information. -All the nodes selective options are explained [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster.html#cluster-nodes). -** *`max_archive_version` (number)*: Specifies the maximum [archive_version](https://www.elastic.co/guide/en/elasticsearch/reference/current/get-repositories-metering-api.html#get-repositories-metering-api-response-body) to be cleared from the archive. - -[discrete] -==== get_repositories_metering_info -You can use the cluster repositories metering API to retrieve repositories metering information in a cluster. -This API exposes monotonically non-decreasing counters and it’s expected that clients would durably store the -information needed to compute aggregations over a period of time. Additionally, the information exposed by this -API is volatile, meaning that it won’t be present after node restarts. - -{ref}/get-repositories-metering-api.html[Endpoint documentation] -[source,ts] ----- -client.nodes.getRepositoriesMeteringInfo({ node_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (string | string[])*: List of node IDs or names used to limit returned information. -All the nodes selective options are explained [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster.html#cluster-nodes). - -[discrete] -==== hot_threads -This API yields a breakdown of the hot threads on each selected node in the cluster. -The output is plain text with a breakdown of each node’s top hot threads. - -{ref}/cluster-nodes-hot-threads.html[Endpoint documentation] -[source,ts] ----- -client.nodes.hotThreads({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: List of node IDs or names used to limit returned information. -** *`ignore_idle_threads` (Optional, boolean)*: If true, known idle threads (e.g. waiting in a socket select, or to get -a task from an empty queue) are filtered out. -** *`interval` (Optional, string | -1 | 0)*: The interval to do the second sampling of threads. -** *`snapshots` (Optional, number)*: Number of samples of thread stacktrace. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response -is received before the timeout expires, the request fails and -returns an error. -** *`threads` (Optional, number)*: Specifies the number of hot threads to provide information for. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received -before the timeout expires, the request fails and returns an error. -** *`type` (Optional, Enum("cpu" | "wait" | "block" | "gpu" | "mem"))*: The type to sample. -** *`sort` (Optional, Enum("cpu" | "wait" | "block" | "gpu" | "mem"))*: The sort order for 'cpu' type (default: total) - -[discrete] -==== info -Returns cluster nodes information. - -{ref}/cluster-nodes-info.html[Endpoint documentation] -[source,ts] ----- -client.nodes.info({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: List of node IDs or names used to limit returned information. -** *`metric` (Optional, string | string[])*: Limits the information returned to the specific metrics. Supports a list, such as http,ingest. -** *`flat_settings` (Optional, boolean)*: If true, returns settings in flat format. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== reload_secure_settings -Reloads the keystore on nodes in the cluster. - -{ref}/secure-settings.html[Endpoint documentation] -[source,ts] ----- -client.nodes.reloadSecureSettings({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: The names of particular nodes in the cluster to target. -** *`secure_settings_password` (Optional, string)*: The password for the Elasticsearch keystore. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== stats -Returns cluster nodes statistics. - -{ref}/cluster-nodes-stats.html[Endpoint documentation] -[source,ts] ----- -client.nodes.stats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: List of node IDs or names used to limit returned information. -** *`metric` (Optional, string | string[])*: Limit the information returned to the specified metrics -** *`index_metric` (Optional, string | string[])*: Limit the information returned for indices metric to the specific index metrics. It can be used only if indices (or all) metric is specified. -** *`completion_fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in fielddata and suggest statistics. -** *`fielddata_fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in fielddata statistics. -** *`fields` (Optional, string | string[])*: List or wildcard expressions of fields to include in the statistics. -** *`groups` (Optional, boolean)*: List of search groups to include in the search statistics. -** *`include_segment_file_sizes` (Optional, boolean)*: If true, the call reports the aggregated disk usage of each one of the Lucene index files (only applies if segment stats are requested). -** *`level` (Optional, Enum("cluster" | "indices" | "shards"))*: Indicates whether statistics are aggregated at the cluster, index, or shard level. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. -** *`types` (Optional, string[])*: A list of document types for the indexing index metric. -** *`include_unloaded_segments` (Optional, boolean)*: If `true`, the response includes information from segments that are not loaded into memory. - -[discrete] -==== usage -Returns information on the usage of features. - -{ref}/cluster-nodes-usage.html[Endpoint documentation] -[source,ts] ----- -client.nodes.usage({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: A list of node IDs or names to limit the returned information; use `_local` to return information from the node you're connecting to, leave empty to get information from all nodes -** *`metric` (Optional, string | string[])*: Limits the information returned to the specific metrics. -A list of the following options: `_all`, `rest_actions`. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -=== query_rules -[discrete] -==== delete_rule -Deletes a query rule within a query ruleset. - -{ref}/delete-query-rule.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.deleteRule({ ruleset_id, rule_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ruleset_id` (string)*: The unique identifier of the query ruleset containing the rule to delete -** *`rule_id` (string)*: The unique identifier of the query rule within the specified ruleset to delete - -[discrete] -==== delete_ruleset -Deletes a query ruleset. - -{ref}/delete-query-ruleset.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.deleteRuleset({ ruleset_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ruleset_id` (string)*: The unique identifier of the query ruleset to delete - -[discrete] -==== get_rule -Returns the details about a query rule within a query ruleset - -{ref}/get-query-rule.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.getRule({ ruleset_id, rule_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ruleset_id` (string)*: The unique identifier of the query ruleset containing the rule to retrieve -** *`rule_id` (string)*: The unique identifier of the query rule within the specified ruleset to retrieve - -[discrete] -==== get_ruleset -Returns the details about a query ruleset - -{ref}/get-query-ruleset.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.getRuleset({ ruleset_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ruleset_id` (string)*: The unique identifier of the query ruleset - -[discrete] -==== list_rulesets -Returns summarized information about existing query rulesets. - -{ref}/list-query-rulesets.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.listRulesets({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`from` (Optional, number)*: Starting offset (default: 0) -** *`size` (Optional, number)*: specifies a max number of results to get - -[discrete] -==== put_rule -Creates or updates a query rule within a query ruleset. - -{ref}/put-query-rule.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.putRule({ ruleset_id, rule_id, type, criteria, actions }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ruleset_id` (string)*: The unique identifier of the query ruleset containing the rule to be created or updated -** *`rule_id` (string)*: The unique identifier of the query rule within the specified ruleset to be created or updated -** *`type` (Enum("pinned" | "exclude"))* -** *`criteria` ({ type, metadata, values } | { type, metadata, values }[])* -** *`actions` ({ ids, docs })* -** *`priority` (Optional, number)* - -[discrete] -==== put_ruleset -Creates or updates a query ruleset. - -{ref}/put-query-ruleset.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.putRuleset({ ruleset_id, rules }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ruleset_id` (string)*: The unique identifier of the query ruleset to be created or updated -** *`rules` ({ rule_id, type, criteria, actions, priority } | { rule_id, type, criteria, actions, priority }[])* - -[discrete] -==== test -Creates or updates a query ruleset. - -{ref}/test-query-ruleset.html[Endpoint documentation] -[source,ts] ----- -client.queryRules.test({ ruleset_id, match_criteria }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ruleset_id` (string)*: The unique identifier of the query ruleset to be created or updated -** *`match_criteria` (Record)* - -[discrete] -=== rollup -[discrete] -==== delete_job -Deletes an existing rollup job. - -{ref}/rollup-delete-job.html[Endpoint documentation] -[source,ts] ----- -client.rollup.deleteJob({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the job. - -[discrete] -==== get_jobs -Retrieves the configuration, stats, and status of rollup jobs. - -{ref}/rollup-get-job.html[Endpoint documentation] -[source,ts] ----- -client.rollup.getJobs({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: Identifier for the rollup job. -If it is `_all` or omitted, the API returns all rollup jobs. - -[discrete] -==== get_rollup_caps -Returns the capabilities of any rollup jobs that have been configured for a specific index or index pattern. - -{ref}/rollup-get-rollup-caps.html[Endpoint documentation] -[source,ts] ----- -client.rollup.getRollupCaps({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: Index, indices or index-pattern to return rollup capabilities for. -`_all` may be used to fetch rollup capabilities from all jobs. - -[discrete] -==== get_rollup_index_caps -Returns the rollup capabilities of all jobs inside of a rollup index (for example, the index where rollup data is stored). - -{ref}/rollup-get-rollup-index-caps.html[Endpoint documentation] -[source,ts] ----- -client.rollup.getRollupIndexCaps({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: Data stream or index to check for rollup capabilities. -Wildcard (`*`) expressions are supported. - -[discrete] -==== put_job -Creates a rollup job. - -{ref}/rollup-put-job.html[Endpoint documentation] -[source,ts] ----- -client.rollup.putJob({ id, cron, groups, index_pattern, page_size, rollup_index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the rollup job. This can be any alphanumeric string and uniquely identifies the -data that is associated with the rollup job. The ID is persistent; it is stored with the rolled -up data. If you create a job, let it run for a while, then delete the job, the data that the job -rolled up is still be associated with this job ID. You cannot create a new job with the same ID -since that could lead to problems with mismatched job configurations. -** *`cron` (string)*: A cron string which defines the intervals when the rollup job should be executed. When the interval -triggers, the indexer attempts to rollup the data in the index pattern. The cron pattern is unrelated -to the time interval of the data being rolled up. For example, you may wish to create hourly rollups -of your document but to only run the indexer on a daily basis at midnight, as defined by the cron. The -cron pattern is defined just like a Watcher cron schedule. -** *`groups` ({ date_histogram, histogram, terms })*: Defines the grouping fields and aggregations that are defined for this rollup job. These fields will then be -available later for aggregating into buckets. These aggs and fields can be used in any combination. Think of -the groups configuration as defining a set of tools that can later be used in aggregations to partition the -data. Unlike raw data, we have to think ahead to which fields and aggregations might be used. Rollups provide -enough flexibility that you simply need to determine which fields are needed, not in what order they are needed. -** *`index_pattern` (string)*: The index or index pattern to roll up. Supports wildcard-style patterns (`logstash-*`). The job attempts to -rollup the entire index or index-pattern. -** *`page_size` (number)*: The number of bucket results that are processed on each iteration of the rollup indexer. A larger value tends -to execute faster, but requires more memory during processing. This value has no effect on how the data is -rolled up; it is merely used for tweaking the speed or memory cost of the indexer. -** *`rollup_index` (string)*: The index that contains the rollup results. The index can be shared with other rollup jobs. The data is stored so that it doesn’t interfere with unrelated jobs. -** *`metrics` (Optional, { field, metrics }[])*: Defines the metrics to collect for each grouping tuple. By default, only the doc_counts are collected for each -group. To make rollup useful, you will often add metrics like averages, mins, maxes, etc. Metrics are defined -on a per-field basis and for each field you configure which metric should be collected. -** *`timeout` (Optional, string | -1 | 0)*: Time to wait for the request to complete. -** *`headers` (Optional, Record)* - -[discrete] -==== rollup_search -Enables searching rolled-up data using the standard Query DSL. - -{ref}/rollup-search.html[Endpoint documentation] -[source,ts] ----- -client.rollup.rollupSearch({ index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (string | string[])*: Enables searching rolled-up data using the standard Query DSL. -** *`aggregations` (Optional, Record)*: Specifies aggregations. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Specifies a DSL query. -** *`size` (Optional, number)*: Must be zero if set, as rollups work on pre-aggregated data. -** *`rest_total_hits_as_int` (Optional, boolean)*: Indicates whether hits.total should be rendered as an integer or an object in the rest search response -** *`typed_keys` (Optional, boolean)*: Specify whether aggregation and suggester names should be prefixed by their respective types in the response - -[discrete] -==== start_job -Starts an existing, stopped rollup job. - -{ref}/rollup-start-job.html[Endpoint documentation] -[source,ts] ----- -client.rollup.startJob({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the rollup job. - -[discrete] -==== stop_job -Stops an existing, started rollup job. - -{ref}/rollup-stop-job.html[Endpoint documentation] -[source,ts] ----- -client.rollup.stopJob({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the rollup job. -** *`timeout` (Optional, string | -1 | 0)*: If `wait_for_completion` is `true`, the API blocks for (at maximum) the specified duration while waiting for the job to stop. -If more than `timeout` time has passed, the API throws a timeout exception. -** *`wait_for_completion` (Optional, boolean)*: If set to `true`, causes the API to block until the indexer state completely stops. -If set to `false`, the API returns immediately and the indexer is stopped asynchronously in the background. - -[discrete] -=== search_application -[discrete] -==== delete -Delete a search application. -Remove a search application and its associated alias. Indices attached to the search application are not removed. - -{ref}/delete-search-application.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.delete({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the search application to delete - -[discrete] -==== delete_behavioral_analytics -Delete a behavioral analytics collection. -The associated data stream is also deleted. - -{ref}/delete-analytics-collection.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.deleteBehavioralAnalytics({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the analytics collection to be deleted - -[discrete] -==== get -Get search application details. - -{ref}/get-search-application.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.get({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the search application - -[discrete] -==== get_behavioral_analytics -Get behavioral analytics collections. - -{ref}/list-analytics-collection.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.getBehavioralAnalytics({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string[])*: A list of analytics collections to limit the returned information - -[discrete] -==== list -Returns the existing search applications. - -{ref}/list-search-applications.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.list({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`q` (Optional, string)*: Query in the Lucene query string syntax. -** *`from` (Optional, number)*: Starting offset. -** *`size` (Optional, number)*: Specifies a max number of results to get. - -[discrete] -==== post_behavioral_analytics_event -Creates a behavioral analytics event for existing collection. - -http://todo.com/tbd[Endpoint documentation] -[source,ts] ----- -client.searchApplication.postBehavioralAnalyticsEvent() ----- - - -[discrete] -==== put -Create or update a search application. - -{ref}/put-search-application.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.put({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the search application to be created or updated. -** *`search_application` (Optional, { indices, analytics_collection_name, template })* -** *`create` (Optional, boolean)*: If `true`, this request cannot replace or update existing Search Applications. - -[discrete] -==== put_behavioral_analytics -Create a behavioral analytics collection. - -{ref}/put-analytics-collection.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.putBehavioralAnalytics({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the analytics collection to be created or updated. - -[discrete] -==== render_query -Renders a query for given search application search parameters - -{ref}/search-application-render-query.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.renderQuery() ----- - - -[discrete] -==== search -Run a search application search. -Generate and run an Elasticsearch query that uses the specified query parameteter and the search template associated with the search application or default template. -Unspecified template parameters are assigned their default values if applicable. - -{ref}/search-application-search.html[Endpoint documentation] -[source,ts] ----- -client.searchApplication.search({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the search application to be searched. -** *`params` (Optional, Record)*: Query parameters specific to this request, which will override any defaults specified in the template. -** *`typed_keys` (Optional, boolean)*: Determines whether aggregation names are prefixed by their respective types in the response. - -[discrete] -=== searchable_snapshots -[discrete] -==== cache_stats -Retrieve node-level cache statistics about searchable snapshots. - -{ref}/searchable-snapshots-apis.html[Endpoint documentation] -[source,ts] ----- -client.searchableSnapshots.cacheStats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: A list of node IDs or names to limit the returned information; use `_local` to return information from the node you're connecting to, leave empty to get information from all nodes -** *`master_timeout` (Optional, string | -1 | 0)* - -[discrete] -==== clear_cache -Clear the cache of searchable snapshots. - -{ref}/searchable-snapshots-apis.html[Endpoint documentation] -[source,ts] ----- -client.searchableSnapshots.clearCache({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: A list of index names -** *`expand_wildcards` (Optional, Enum("all" | "open" | "closed" | "hidden" | "none") | Enum("all" | "open" | "closed" | "hidden" | "none")[])*: Whether to expand wildcard expression to concrete indices that are open, closed or both. -** *`allow_no_indices` (Optional, boolean)*: Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified) -** *`ignore_unavailable` (Optional, boolean)*: Whether specified concrete indices should be ignored when unavailable (missing or closed) -** *`pretty` (Optional, boolean)* -** *`human` (Optional, boolean)* - -[discrete] -==== mount -Mount a snapshot as a searchable index. - -{ref}/searchable-snapshots-api-mount-snapshot.html[Endpoint documentation] -[source,ts] ----- -client.searchableSnapshots.mount({ repository, snapshot, index }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: The name of the repository containing the snapshot of the index to mount -** *`snapshot` (string)*: The name of the snapshot of the index to mount -** *`index` (string)* -** *`renamed_index` (Optional, string)* -** *`index_settings` (Optional, Record)* -** *`ignore_index_settings` (Optional, string[])* -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node -** *`wait_for_completion` (Optional, boolean)*: Should this request wait until the operation has completed before returning -** *`storage` (Optional, string)*: Selects the kind of local storage used to accelerate searches. Experimental, and defaults to `full_copy` - -[discrete] -==== stats -Retrieve shard-level statistics about searchable snapshots. - -{ref}/searchable-snapshots-apis.html[Endpoint documentation] -[source,ts] ----- -client.searchableSnapshots.stats({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`index` (Optional, string | string[])*: A list of index names -** *`level` (Optional, Enum("cluster" | "indices" | "shards"))*: Return stats aggregated at cluster, index or shard level - -[discrete] -=== security -[discrete] -==== activate_user_profile -Activate a user profile. - -Create or update a user profile on behalf of another user. - -{ref}/security-api-activate-user-profile.html[Endpoint documentation] -[source,ts] ----- -client.security.activateUserProfile({ grant_type }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`grant_type` (Enum("password" | "access_token"))* -** *`access_token` (Optional, string)* -** *`password` (Optional, string)* -** *`username` (Optional, string)* - -[discrete] -==== authenticate -Authenticate a user. - -Authenticates a user and returns information about the authenticated user. -Include the user information in a [basic auth header](https://en.wikipedia.org/wiki/Basic_access_authentication). -A successful call returns a JSON structure that shows user information such as their username, the roles that are assigned to the user, any assigned metadata, and information about the realms that authenticated and authorized the user. -If the user cannot be authenticated, this API returns a 401 status code. - -{ref}/security-api-authenticate.html[Endpoint documentation] -[source,ts] ----- -client.security.authenticate() ----- - - -[discrete] -==== bulk_delete_role -Bulk delete roles. - -The role management APIs are generally the preferred way to manage roles, rather than using file-based role management. -The bulk delete roles API cannot delete roles that are defined in roles files. - -{ref}/security-api-bulk-delete-role.html[Endpoint documentation] -[source,ts] ----- -client.security.bulkDeleteRole({ names }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`names` (string[])*: An array of role names to delete -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== bulk_put_role -Bulk create or update roles. - -The role management APIs are generally the preferred way to manage roles, rather than using file-based role management. -The bulk create or update roles API cannot update roles that are defined in roles files. - -{ref}/security-api-bulk-put-role.html[Endpoint documentation] -[source,ts] ----- -client.security.bulkPutRole({ roles }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`roles` (Record)*: A dictionary of role name to RoleDescriptor objects to add or update -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== bulk_update_api_keys -Updates the attributes of multiple existing API keys. - -{ref}/security-api-bulk-update-api-keys.html[Endpoint documentation] -[source,ts] ----- -client.security.bulkUpdateApiKeys() ----- - - -[discrete] -==== change_password -Change passwords. - -Change the passwords of users in the native realm and built-in users. - -{ref}/security-api-change-password.html[Endpoint documentation] -[source,ts] ----- -client.security.changePassword({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`username` (Optional, string)*: The user whose password you want to change. If you do not specify this -parameter, the password is changed for the current user. -** *`password` (Optional, string)*: The new password value. Passwords must be at least 6 characters long. -** *`password_hash` (Optional, string)*: A hash of the new password value. This must be produced using the same -hashing algorithm as has been configured for password storage. For more details, -see the explanation of the `xpack.security.authc.password_hashing.algorithm` -setting. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== clear_api_key_cache -Clear the API key cache. - -Evict a subset of all entries from the API key cache. -The cache is also automatically cleared on state changes of the security index. - -{ref}/security-api-clear-api-key-cache.html[Endpoint documentation] -[source,ts] ----- -client.security.clearApiKeyCache({ ids }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`ids` (string | string[])*: List of API key IDs to evict from the API key cache. -To evict all API keys, use `*`. -Does not support other wildcard patterns. - -[discrete] -==== clear_cached_privileges -Clear the privileges cache. - -Evict privileges from the native application privilege cache. -The cache is also automatically cleared for applications that have their privileges updated. - -{ref}/security-api-clear-privilege-cache.html[Endpoint documentation] -[source,ts] ----- -client.security.clearCachedPrivileges({ application }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`application` (string)*: A list of application names - -[discrete] -==== clear_cached_realms -Clear the user cache. - -Evict users from the user cache. You can completely clear the cache or evict specific users. - -{ref}/security-api-clear-cache.html[Endpoint documentation] -[source,ts] ----- -client.security.clearCachedRealms({ realms }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`realms` (string | string[])*: List of realms to clear -** *`usernames` (Optional, string[])*: List of usernames to clear from the cache - -[discrete] -==== clear_cached_roles -Clear the roles cache. - -Evict roles from the native role cache. - -{ref}/security-api-clear-role-cache.html[Endpoint documentation] -[source,ts] ----- -client.security.clearCachedRoles({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string | string[])*: Role name - -[discrete] -==== clear_cached_service_tokens -Clear service account token caches. - -Evict a subset of all entries from the service account token caches. - -{ref}/security-api-clear-service-token-caches.html[Endpoint documentation] -[source,ts] ----- -client.security.clearCachedServiceTokens({ namespace, service, name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`namespace` (string)*: An identifier for the namespace -** *`service` (string)*: An identifier for the service name -** *`name` (string | string[])*: A list of service token names - -[discrete] -==== create_api_key -Create an API key. - -Create an API key for access without requiring basic authentication. -A successful request returns a JSON structure that contains the API key, its unique id, and its name. -If applicable, it also returns expiration information for the API key in milliseconds. -NOTE: By default, API keys never expire. You can specify expiration information when you create the API keys. - -{ref}/security-api-create-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.createApiKey({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`expiration` (Optional, string | -1 | 0)*: Expiration time for the API key. By default, API keys never expire. -** *`name` (Optional, string)*: Specifies the name for this API key. -** *`role_descriptors` (Optional, Record)*: An array of role descriptors for this API key. This parameter is optional. When it is not specified or is an empty array, then the API key will have a point in time snapshot of permissions of the authenticated user. If you supply role descriptors then the resultant permissions would be an intersection of API keys permissions and authenticated user’s permissions thereby limiting the access scope for API keys. The structure of role descriptor is the same as the request for create role API. For more details, see create or update roles API. -** *`metadata` (Optional, Record)*: Arbitrary metadata that you want to associate with the API key. It supports nested data structure. Within the metadata object, keys beginning with `_` are reserved for system usage. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== create_cross_cluster_api_key -Create a cross-cluster API key. - -Create an API key of the `cross_cluster` type for the API key based remote cluster access. -A `cross_cluster` API key cannot be used to authenticate through the REST interface. - -IMPORTANT: To authenticate this request you must use a credential that is not an API key. Even if you use an API key that has the required privilege, the API returns an error. - -Cross-cluster API keys are created by the Elasticsearch API key service, which is automatically enabled. - -NOTE: Unlike REST API keys, a cross-cluster API key does not capture permissions of the authenticated user. The API key’s effective permission is exactly as specified with the `access` property. - -A successful request returns a JSON structure that contains the API key, its unique ID, and its name. If applicable, it also returns expiration information for the API key in milliseconds. - -By default, API keys never expire. You can specify expiration information when you create the API keys. - -Cross-cluster API keys can only be updated with the update cross-cluster API key API. -Attempting to update them with the update REST API key API or the bulk update REST API keys API will result in an error. - -{ref}/security-api-create-cross-cluster-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.createCrossClusterApiKey({ access, name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`access` ({ replication, search })*: The access to be granted to this API key. -The access is composed of permissions for cross-cluster search and cross-cluster replication. -At least one of them must be specified. - -NOTE: No explicit privileges should be specified for either search or replication access. -The creation process automatically converts the access specification to a role descriptor which has relevant privileges assigned accordingly. -** *`name` (string)*: Specifies the name for this API key. -** *`expiration` (Optional, string | -1 | 0)*: Expiration time for the API key. -By default, API keys never expire. -** *`metadata` (Optional, Record)*: Arbitrary metadata that you want to associate with the API key. -It supports nested data structure. -Within the metadata object, keys beginning with `_` are reserved for system usage. - -[discrete] -==== create_service_token -Create a service account token. - -Create a service accounts token for access without requiring basic authentication. - -{ref}/security-api-create-service-token.html[Endpoint documentation] -[source,ts] ----- -client.security.createServiceToken({ namespace, service }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`namespace` (string)*: An identifier for the namespace -** *`service` (string)*: An identifier for the service name -** *`name` (Optional, string)*: An identifier for the token name -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` then refresh the affected shards to make this operation visible to search, if `wait_for` (the default) then wait for a refresh to make this operation visible to search, if `false` then do nothing with refreshes. - -[discrete] -==== delete_privileges -Delete application privileges. - -{ref}/security-api-delete-privilege.html[Endpoint documentation] -[source,ts] ----- -client.security.deletePrivileges({ application, name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`application` (string)*: Application name -** *`name` (string | string[])*: Privilege name -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== delete_role -Delete roles. - -Delete roles in the native realm. - -{ref}/security-api-delete-role.html[Endpoint documentation] -[source,ts] ----- -client.security.deleteRole({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Role name -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== delete_role_mapping -Delete role mappings. - -{ref}/security-api-delete-role-mapping.html[Endpoint documentation] -[source,ts] ----- -client.security.deleteRoleMapping({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Role-mapping name -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== delete_service_token -Delete service account tokens. - -Delete service account tokens for a service in a specified namespace. - -{ref}/security-api-delete-service-token.html[Endpoint documentation] -[source,ts] ----- -client.security.deleteServiceToken({ namespace, service, name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`namespace` (string)*: An identifier for the namespace -** *`service` (string)*: An identifier for the service name -** *`name` (string)*: An identifier for the token name -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` then refresh the affected shards to make this operation visible to search, if `wait_for` (the default) then wait for a refresh to make this operation visible to search, if `false` then do nothing with refreshes. - -[discrete] -==== delete_user -Delete users. - -Delete users from the native realm. - -{ref}/security-api-delete-user.html[Endpoint documentation] -[source,ts] ----- -client.security.deleteUser({ username }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`username` (string)*: username -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== disable_user -Disable users. - -Disable users in the native realm. - -{ref}/security-api-disable-user.html[Endpoint documentation] -[source,ts] ----- -client.security.disableUser({ username }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`username` (string)*: The username of the user to disable -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== disable_user_profile -Disable a user profile. - -Disable user profiles so that they are not visible in user profile searches. - -{ref}/security-api-disable-user-profile.html[Endpoint documentation] -[source,ts] ----- -client.security.disableUserProfile({ uid }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`uid` (string)*: Unique identifier for the user profile. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If 'true', Elasticsearch refreshes 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' do nothing with refreshes. - -[discrete] -==== enable_user -Enable users. - -Enable users in the native realm. - -{ref}/security-api-enable-user.html[Endpoint documentation] -[source,ts] ----- -client.security.enableUser({ username }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`username` (string)*: The username of the user to enable -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== enable_user_profile -Enable a user profile. - -Enable user profiles to make them visible in user profile searches. - -{ref}/security-api-enable-user-profile.html[Endpoint documentation] -[source,ts] ----- -client.security.enableUserProfile({ uid }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`uid` (string)*: Unique identifier for the user profile. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If 'true', Elasticsearch refreshes 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' do nothing with refreshes. - -[discrete] -==== enroll_kibana -Enroll Kibana. - -Enable a Kibana instance to configure itself for communication with a secured Elasticsearch cluster. - -{ref}/security-api-kibana-enrollment.html[Endpoint documentation] -[source,ts] ----- -client.security.enrollKibana() ----- - - -[discrete] -==== enroll_node -Enroll a node. - -Enroll a new node to allow it to join an existing cluster with security features enabled. - -{ref}/security-api-node-enrollment.html[Endpoint documentation] -[source,ts] ----- -client.security.enrollNode() ----- - - -[discrete] -==== get_api_key -Get API key information. - -Retrieves information for one or more API keys. -NOTE: If you have only the `manage_own_api_key` privilege, this API returns only the API keys that you own. -If you have `read_security`, `manage_api_key` or greater privileges (including `manage_security`), this API returns all API keys regardless of ownership. - -{ref}/security-api-get-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.getApiKey({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: An API key id. -This parameter cannot be used with any of `name`, `realm_name` or `username`. -** *`name` (Optional, string)*: An API key name. -This parameter cannot be used with any of `id`, `realm_name` or `username`. -It supports prefix search with wildcard. -** *`owner` (Optional, boolean)*: A boolean flag that can be used to query API keys owned by the currently authenticated user. -The `realm_name` or `username` parameters cannot be specified when this parameter is set to `true` as they are assumed to be the currently authenticated ones. -** *`realm_name` (Optional, string)*: The name of an authentication realm. -This parameter cannot be used with either `id` or `name` or when `owner` flag is set to `true`. -** *`username` (Optional, string)*: The username of a user. -This parameter cannot be used with either `id` or `name` or when `owner` flag is set to `true`. -** *`with_limited_by` (Optional, boolean)*: 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. -** *`active_only` (Optional, boolean)*: A boolean flag that can be used to query API keys that are currently active. An API key is considered active if it is neither invalidated, nor expired at query time. You can specify this together with other parameters such as `owner` or `name`. If `active_only` is false, the response will include both active and inactive (expired or invalidated) keys. -** *`with_profile_uid` (Optional, boolean)*: Determines whether to also retrieve the profile uid, for the API key owner principal, if it exists. - -[discrete] -==== get_builtin_privileges -Get builtin privileges. - -Get the list of cluster privileges and index privileges that are available in this version of Elasticsearch. - -{ref}/security-api-get-builtin-privileges.html[Endpoint documentation] -[source,ts] ----- -client.security.getBuiltinPrivileges() ----- - - -[discrete] -==== get_privileges -Get application privileges. - -{ref}/security-api-get-privileges.html[Endpoint documentation] -[source,ts] ----- -client.security.getPrivileges({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`application` (Optional, string)*: Application name -** *`name` (Optional, string | string[])*: Privilege name - -[discrete] -==== get_role -Get roles. - -Get roles in the native realm. - -{ref}/security-api-get-role.html[Endpoint documentation] -[source,ts] ----- -client.security.getRole({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string | string[])*: The name of the role. You can specify multiple roles as a list. If you do not specify this parameter, the API returns information about all roles. - -[discrete] -==== get_role_mapping -Get role mappings. - -Role mappings define which roles are assigned to each user. -The role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. -The get role mappings API cannot retrieve role mappings that are defined in role mapping files. - -{ref}/security-api-get-role-mapping.html[Endpoint documentation] -[source,ts] ----- -client.security.getRoleMapping({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string | string[])*: The distinct name that identifies the role mapping. The name is used solely as an identifier to facilitate interaction via the API; it does not affect the behavior of the mapping in any way. You can specify multiple mapping names as a list. If you do not specify this parameter, the API returns information about all role mappings. - -[discrete] -==== get_service_accounts -Get service accounts. - -Get a list of service accounts that match the provided path parameters. - -{ref}/security-api-get-service-accounts.html[Endpoint documentation] -[source,ts] ----- -client.security.getServiceAccounts({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`namespace` (Optional, string)*: Name of the namespace. Omit this parameter to retrieve information about all service accounts. If you omit this parameter, you must also omit the `service` parameter. -** *`service` (Optional, string)*: Name of the service name. Omit this parameter to retrieve information about all service accounts that belong to the specified `namespace`. - -[discrete] -==== get_service_credentials -Get service account credentials. - -{ref}/security-api-get-service-credentials.html[Endpoint documentation] -[source,ts] ----- -client.security.getServiceCredentials({ namespace, service }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`namespace` (string)*: Name of the namespace. -** *`service` (string)*: Name of the service name. - -[discrete] -==== get_settings -Retrieve settings for the security system indices - -{ref}/security-api-get-settings.html[Endpoint documentation] -[source,ts] ----- -client.security.getSettings() ----- - - -[discrete] -==== get_token -Get a token. - -Create a bearer token for access without requiring basic authentication. - -{ref}/security-api-get-token.html[Endpoint documentation] -[source,ts] ----- -client.security.getToken({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`grant_type` (Optional, Enum("password" | "client_credentials" | "_kerberos" | "refresh_token"))* -** *`scope` (Optional, string)* -** *`password` (Optional, string)* -** *`kerberos_ticket` (Optional, string)* -** *`refresh_token` (Optional, string)* -** *`username` (Optional, string)* - -[discrete] -==== get_user -Get users. - -Get information about users in the native realm and built-in users. - -{ref}/security-api-get-user.html[Endpoint documentation] -[source,ts] ----- -client.security.getUser({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`username` (Optional, string | string[])*: An identifier for the user. You can specify multiple usernames as a list. If you omit this parameter, the API retrieves information about all users. -** *`with_profile_uid` (Optional, boolean)*: If true will return the User Profile ID for a user, if any. - -[discrete] -==== get_user_privileges -Get user privileges. - -{ref}/security-api-get-user-privileges.html[Endpoint documentation] -[source,ts] ----- -client.security.getUserPrivileges({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`application` (Optional, string)*: The name of the application. Application privileges are always associated with exactly one application. If you do not specify this parameter, the API returns information about all privileges for all applications. -** *`priviledge` (Optional, string)*: The name of the privilege. If you do not specify this parameter, the API returns information about all privileges for the requested application. -** *`username` (Optional, string | null)* - -[discrete] -==== get_user_profile -Get a user profile. - -Get a user's profile using the unique profile ID. - -{ref}/security-api-get-user-profile.html[Endpoint documentation] -[source,ts] ----- -client.security.getUserProfile({ uid }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`uid` (string | string[])*: A unique identifier for the user profile. -** *`data` (Optional, string | string[])*: List of filters for the `data` field of the profile document. -To return all content use `data=*`. To return a subset of content -use `data=` to retrieve content nested under the specified ``. -By default returns no `data` content. - -[discrete] -==== grant_api_key -Grant an API key. - -Create an API key on behalf of another user. -This API is similar to the create API keys API, however it creates the API key for a user that is different than the user that runs the API. -The caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created. -It is not possible to use this API to create an API key without that user’s credentials. -The user, for whom the authentication credentials is provided, can optionally "run as" (impersonate) another user. -In this case, the API key will be created on behalf of the impersonated user. - -This API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf. - -A successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name. -If applicable, it also returns expiration information for the API key in milliseconds. - -By default, API keys never expire. You can specify expiration information when you create the API keys. - -{ref}/security-api-grant-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.grantApiKey({ api_key, grant_type }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`api_key` ({ name, expiration, role_descriptors, metadata })*: Defines the API key. -** *`grant_type` (Enum("access_token" | "password"))*: The type of grant. Supported grant types are: `access_token`, `password`. -** *`access_token` (Optional, string)*: The user’s access token. -If you specify the `access_token` grant type, this parameter is required. -It is not valid with other grant types. -** *`username` (Optional, string)*: The user name that identifies the user. -If you specify the `password` grant type, this parameter is required. -It is not valid with other grant types. -** *`password` (Optional, string)*: The user’s password. If you specify the `password` grant type, this parameter is required. -It is not valid with other grant types. -** *`run_as` (Optional, string)*: The name of the user to be impersonated. - -[discrete] -==== has_privileges -Check user privileges. - -Determine whether the specified user has a specified list of privileges. - -{ref}/security-api-has-privileges.html[Endpoint documentation] -[source,ts] ----- -client.security.hasPrivileges({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`user` (Optional, string)*: Username -** *`application` (Optional, { application, privileges, resources }[])* -** *`cluster` (Optional, Enum("all" | "cancel_task" | "create_snapshot" | "cross_cluster_replication" | "cross_cluster_search" | "delegate_pki" | "grant_api_key" | "manage" | "manage_api_key" | "manage_autoscaling" | "manage_behavioral_analytics" | "manage_ccr" | "manage_data_frame_transforms" | "manage_data_stream_global_retention" | "manage_enrich" | "manage_ilm" | "manage_index_templates" | "manage_inference" | "manage_ingest_pipelines" | "manage_logstash_pipelines" | "manage_ml" | "manage_oidc" | "manage_own_api_key" | "manage_pipeline" | "manage_rollup" | "manage_saml" | "manage_search_application" | "manage_search_query_rules" | "manage_search_synonyms" | "manage_security" | "manage_service_account" | "manage_slm" | "manage_token" | "manage_transform" | "manage_user_profile" | "manage_watcher" | "monitor" | "monitor_data_frame_transforms" | "monitor_data_stream_global_retention" | "monitor_enrich" | "monitor_inference" | "monitor_ml" | "monitor_rollup" | "monitor_snapshot" | "monitor_text_structure" | "monitor_transform" | "monitor_watcher" | "none" | "post_behavioral_analytics_event" | "read_ccr" | "read_fleet_secrets" | "read_ilm" | "read_pipeline" | "read_security" | "read_slm" | "transport_client" | "write_connector_secrets" | "write_fleet_secrets")[])*: A list of the cluster privileges that you want to check. -** *`index` (Optional, { names, privileges, allow_restricted_indices }[])* - -[discrete] -==== has_privileges_user_profile -Check user profile privileges. - -Determine whether the users associated with the specified user profile IDs have all the requested privileges. - -{ref}/security-api-has-privileges-user-profile.html[Endpoint documentation] -[source,ts] ----- -client.security.hasPrivilegesUserProfile({ uids, privileges }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`uids` (string[])*: A list of profile IDs. The privileges are checked for associated users of the profiles. -** *`privileges` ({ application, cluster, index })* - -[discrete] -==== invalidate_api_key -Invalidate API keys. - -This API invalidates API keys created by the create API key or grant API key APIs. -Invalidated API keys fail authentication, but they can still be viewed using the get API key information and query API key information APIs, for at least the configured retention period, until they are automatically deleted. -The `manage_api_key` privilege allows deleting any API keys. -The `manage_own_api_key` only allows deleting API keys that are owned by the user. -In addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats: -- Set the parameter `owner=true`. -- Or, set both `username` and `realm_name` to match the user’s identity. -- Or, if the request is issued by an API key, that is to say an API key invalidates itself, specify its ID in the `ids` field. - -{ref}/security-api-invalidate-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.invalidateApiKey({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)* -** *`ids` (Optional, string[])*: A list of API key ids. -This parameter cannot be used with any of `name`, `realm_name`, or `username`. -** *`name` (Optional, string)*: An API key name. -This parameter cannot be used with any of `ids`, `realm_name` or `username`. -** *`owner` (Optional, boolean)*: Can be used to query API keys owned by the currently authenticated user. -The `realm_name` or `username` parameters cannot be specified when this parameter is set to `true` as they are assumed to be the currently authenticated ones. -** *`realm_name` (Optional, string)*: The name of an authentication realm. -This parameter cannot be used with either `ids` or `name`, or when `owner` flag is set to `true`. -** *`username` (Optional, string)*: The username of a user. -This parameter cannot be used with either `ids` or `name`, or when `owner` flag is set to `true`. - -[discrete] -==== invalidate_token -Invalidate a token. - -The access tokens returned by the get token API have a finite period of time for which they are valid. -After that time period, they can no longer be used. -The time period is defined by the `xpack.security.authc.token.timeout` setting. - -The refresh tokens returned by the get token API are only valid for 24 hours. They can also be used exactly once. -If you want to invalidate one or more access or refresh tokens immediately, use this invalidate token API. - -{ref}/security-api-invalidate-token.html[Endpoint documentation] -[source,ts] ----- -client.security.invalidateToken({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`token` (Optional, string)* -** *`refresh_token` (Optional, string)* -** *`realm_name` (Optional, string)* -** *`username` (Optional, string)* - -[discrete] -==== oidc_authenticate -Exchanges an OpenID Connection authentication response message for an Elasticsearch access token and refresh token pair - -{ref}/security-api-oidc-authenticate.html[Endpoint documentation] -[source,ts] ----- -client.security.oidcAuthenticate() ----- - - -[discrete] -==== oidc_logout -Invalidates a refresh token and access token that was generated from the OpenID Connect Authenticate API - -{ref}/security-api-oidc-logout.html[Endpoint documentation] -[source,ts] ----- -client.security.oidcLogout() ----- - - -[discrete] -==== oidc_prepare_authentication -Creates an OAuth 2.0 authentication request as a URL string - -{ref}/security-api-oidc-prepare-authentication.html[Endpoint documentation] -[source,ts] ----- -client.security.oidcPrepareAuthentication() ----- - - -[discrete] -==== put_privileges -Create or update application privileges. - -{ref}/security-api-put-privileges.html[Endpoint documentation] -[source,ts] ----- -client.security.putPrivileges({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`privileges` (Optional, Record>)* -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== put_role -Create or update roles. - -The role management APIs are generally the preferred way to manage roles in the native realm, rather than using file-based role management. -The create or update roles API cannot update roles that are defined in roles files. -File-based role management is not available in Elastic Serverless. - -{ref}/security-api-put-role.html[Endpoint documentation] -[source,ts] ----- -client.security.putRole({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: The name of the role that is being created or updated. On Elasticsearch Serverless, the role name must begin with a letter or digit and can only contain letters, digits and the characters '_', '-', and '.'. Each role must have a unique name, as this will serve as the identifier for that role. -** *`applications` (Optional, { application, privileges, resources }[])*: A list of application privilege entries. -** *`cluster` (Optional, Enum("all" | "cancel_task" | "create_snapshot" | "cross_cluster_replication" | "cross_cluster_search" | "delegate_pki" | "grant_api_key" | "manage" | "manage_api_key" | "manage_autoscaling" | "manage_behavioral_analytics" | "manage_ccr" | "manage_data_frame_transforms" | "manage_data_stream_global_retention" | "manage_enrich" | "manage_ilm" | "manage_index_templates" | "manage_inference" | "manage_ingest_pipelines" | "manage_logstash_pipelines" | "manage_ml" | "manage_oidc" | "manage_own_api_key" | "manage_pipeline" | "manage_rollup" | "manage_saml" | "manage_search_application" | "manage_search_query_rules" | "manage_search_synonyms" | "manage_security" | "manage_service_account" | "manage_slm" | "manage_token" | "manage_transform" | "manage_user_profile" | "manage_watcher" | "monitor" | "monitor_data_frame_transforms" | "monitor_data_stream_global_retention" | "monitor_enrich" | "monitor_inference" | "monitor_ml" | "monitor_rollup" | "monitor_snapshot" | "monitor_text_structure" | "monitor_transform" | "monitor_watcher" | "none" | "post_behavioral_analytics_event" | "read_ccr" | "read_fleet_secrets" | "read_ilm" | "read_pipeline" | "read_security" | "read_slm" | "transport_client" | "write_connector_secrets" | "write_fleet_secrets")[])*: A list of cluster privileges. These privileges define the cluster-level actions for users with this role. -** *`global` (Optional, Record)*: An object defining global privileges. A global privilege is a form of cluster privilege that is request-aware. Support for global privileges is currently limited to the management of application privileges. -** *`indices` (Optional, { field_security, names, privileges, query, allow_restricted_indices }[])*: A list of indices permissions entries. -** *`remote_indices` (Optional, { clusters, field_security, names, privileges, query, allow_restricted_indices }[])*: A list of remote indices permissions entries. -** *`metadata` (Optional, Record)*: Optional metadata. Within the metadata object, keys that begin with an underscore (`_`) are reserved for system use. -** *`run_as` (Optional, string[])*: A list of users that the owners of this role can impersonate. *Note*: in Serverless, the run-as feature is disabled. For API compatibility, you can still specify an empty `run_as` field, but a non-empty list will be rejected. -** *`description` (Optional, string)*: Optional description of the role descriptor -** *`transient_metadata` (Optional, Record)*: Indicates roles that might be incompatible with the current cluster license, specifically roles with document and field level security. When the cluster license doesn’t allow certain features for a given role, this parameter is updated dynamically to list the incompatible features. If `enabled` is `false`, the role is ignored, but is still listed in the response from the authenticate API. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== put_role_mapping -Create or update role mappings. - -Role mappings define which roles are assigned to each user. -Each mapping has rules that identify users and a list of roles that are granted to those users. -The role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The create or update role mappings API cannot update role mappings that are defined in role mapping files. - -This API does not create roles. Rather, it maps users to existing roles. -Roles can be created by using the create or update roles API or roles files. - -{ref}/security-api-put-role-mapping.html[Endpoint documentation] -[source,ts] ----- -client.security.putRoleMapping({ name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (string)*: Role-mapping name -** *`enabled` (Optional, boolean)* -** *`metadata` (Optional, Record)* -** *`roles` (Optional, string[])* -** *`role_templates` (Optional, { format, template }[])* -** *`rules` (Optional, { any, all, field, except })* -** *`run_as` (Optional, string[])* -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== put_user -Create or update users. - -A password is required for adding a new user but is optional when updating an existing user. -To change a user’s password without updating any other fields, use the change password API. - -{ref}/security-api-put-user.html[Endpoint documentation] -[source,ts] ----- -client.security.putUser({ username }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`username` (string)*: The username of the User -** *`email` (Optional, string | null)* -** *`full_name` (Optional, string | null)* -** *`metadata` (Optional, Record)* -** *`password` (Optional, string)* -** *`password_hash` (Optional, string)* -** *`roles` (Optional, string[])* -** *`enabled` (Optional, boolean)* -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If `true` (the default) 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` then do nothing with refreshes. - -[discrete] -==== query_api_keys -Find API keys with a query. - -Get a paginated list of API keys and their information. You can optionally filter the results with a query. - -{ref}/security-api-query-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.queryApiKeys({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`aggregations` (Optional, Record)*: Any aggregations to run over the corpus of returned API keys. -Aggregations and queries work together. Aggregations are computed only on the API keys that match the query. -This supports only a subset of aggregation types, namely: `terms`, `range`, `date_range`, `missing`, -`cardinality`, `value_count`, `composite`, `filter`, and `filters`. -Additionally, aggregations only run over the same subset of fields that query works with. -** *`query` (Optional, { bool, exists, ids, match, match_all, prefix, range, simple_query_string, term, terms, wildcard })*: A query to filter which API keys to return. -If the query parameter is missing, it is equivalent to a `match_all` query. -The query supports a subset of query types, including `match_all`, `bool`, `term`, `terms`, `match`, -`ids`, `prefix`, `wildcard`, `exists`, `range`, and `simple_query_string`. -You can query the following public information associated with an API key: `id`, `type`, `name`, -`creation`, `expiration`, `invalidated`, `invalidation`, `username`, `realm`, and `metadata`. -** *`from` (Optional, number)*: Starting document offset. -By default, you cannot page through more than 10,000 hits using the from and size parameters. -To page through more hits, use the `search_after` parameter. -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])*: Other than `id`, all public fields of an API key are eligible for sorting. -In addition, sort can also be applied to the `_doc` field to sort by index order. -** *`size` (Optional, number)*: The number of hits to return. -By default, you cannot page through more than 10,000 hits using the `from` and `size` parameters. -To page through more hits, use the `search_after` parameter. -** *`search_after` (Optional, number | number | string | boolean | null | User-defined value[])*: Search after definition -** *`with_limited_by` (Optional, boolean)*: 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. -** *`with_profile_uid` (Optional, boolean)*: Determines whether to also retrieve the profile uid, for the API key owner principal, if it exists. -** *`typed_keys` (Optional, boolean)*: Determines whether aggregation names are prefixed by their respective types in the response. - -[discrete] -==== query_role -Find roles with a query. - -Get roles in a paginated manner. You can optionally filter the results with a query. - -{ref}/security-api-query-role.html[Endpoint documentation] -[source,ts] ----- -client.security.queryRole({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`query` (Optional, { bool, exists, ids, match, match_all, prefix, range, simple_query_string, term, terms, wildcard })*: A query to filter which roles to return. -If the query parameter is missing, it is equivalent to a `match_all` query. -The query supports a subset of query types, including `match_all`, `bool`, `term`, `terms`, `match`, -`ids`, `prefix`, `wildcard`, `exists`, `range`, and `simple_query_string`. -You can query the following information associated with roles: `name`, `description`, `metadata`, -`applications.application`, `applications.privileges`, `applications.resources`. -** *`from` (Optional, number)*: Starting document offset. -By default, you cannot page through more than 10,000 hits using the from and size parameters. -To page through more hits, use the `search_after` parameter. -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])*: All public fields of a role are eligible for sorting. -In addition, sort can also be applied to the `_doc` field to sort by index order. -** *`size` (Optional, number)*: The number of hits to return. -By default, you cannot page through more than 10,000 hits using the `from` and `size` parameters. -To page through more hits, use the `search_after` parameter. -** *`search_after` (Optional, number | number | string | boolean | null | User-defined value[])*: Search after definition - -[discrete] -==== query_user -Find users with a query. - -Get information for users in a paginated manner. -You can optionally filter the results with a query. - -{ref}/security-api-query-user.html[Endpoint documentation] -[source,ts] ----- -client.security.queryUser({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`query` (Optional, { ids, bool, exists, match, match_all, prefix, range, simple_query_string, term, terms, wildcard })*: A query to filter which users to return. -If the query parameter is missing, it is equivalent to a `match_all` query. -The query supports a subset of query types, including `match_all`, `bool`, `term`, `terms`, `match`, -`ids`, `prefix`, `wildcard`, `exists`, `range`, and `simple_query_string`. -You can query the following information associated with user: `username`, `roles`, `enabled` -** *`from` (Optional, number)*: Starting document offset. -By default, you cannot page through more than 10,000 hits using the from and size parameters. -To page through more hits, use the `search_after` parameter. -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])*: Fields eligible for sorting are: username, roles, enabled -In addition, sort can also be applied to the `_doc` field to sort by index order. -** *`size` (Optional, number)*: The number of hits to return. -By default, you cannot page through more than 10,000 hits using the `from` and `size` parameters. -To page through more hits, use the `search_after` parameter. -** *`search_after` (Optional, number | number | string | boolean | null | User-defined value[])*: Search after definition -** *`with_profile_uid` (Optional, boolean)*: If true will return the User Profile ID for the users in the query result, if any. - -[discrete] -==== saml_authenticate -Authenticate SAML. - -Submits a SAML response message to Elasticsearch for consumption. - -{ref}/security-api-saml-authenticate.html[Endpoint documentation] -[source,ts] ----- -client.security.samlAuthenticate({ content, ids }) ----- - +=== client.security.clearCachedServiceTokens [discrete] -==== Arguments - -* *Request (object):* -** *`content` (string)*: The SAML response as it was sent by the user’s browser, usually a Base64 encoded XML document. -** *`ids` (string | string[])*: A json array with all the valid SAML Request Ids that the caller of the API has for the current user. -** *`realm` (Optional, string)*: The name of the realm that should authenticate the SAML response. Useful in cases where many SAML realms are defined. - -[discrete] -==== saml_complete_logout -Logout of SAML completely. - -Verifies the logout response sent from the SAML IdP. - -{ref}/security-api-saml-complete-logout.html[Endpoint documentation] -[source,ts] ----- -client.security.samlCompleteLogout({ realm, ids }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`realm` (string)*: The name of the SAML realm in Elasticsearch for which the configuration is used to verify the logout response. -** *`ids` (string | string[])*: A json array with all the valid SAML Request Ids that the caller of the API has for the current user. -** *`query_string` (Optional, string)*: If the SAML IdP sends the logout response with the HTTP-Redirect binding, this field must be set to the query string of the redirect URI. -** *`content` (Optional, string)*: If the SAML IdP sends the logout response with the HTTP-Post binding, this field must be set to the value of the SAMLResponse form parameter from the logout response. - -[discrete] -==== saml_invalidate -Invalidate SAML. - -Submits a SAML LogoutRequest message to Elasticsearch for consumption. - -{ref}/security-api-saml-invalidate.html[Endpoint documentation] -[source,ts] ----- -client.security.samlInvalidate({ query_string }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`query_string` (string)*: The query part of the URL that the user was redirected to by the SAML IdP to initiate the Single Logout. -This query should include a single parameter named SAMLRequest that contains a SAML logout request that is deflated and Base64 encoded. -If the SAML IdP has signed the logout request, the URL should include two extra parameters named SigAlg and Signature that contain the algorithm used for the signature and the signature value itself. -In order for Elasticsearch to be able to verify the IdP’s signature, the value of the query_string field must be an exact match to the string provided by the browser. -The client application must not attempt to parse or process the string in any way. -** *`acs` (Optional, string)*: The Assertion Consumer Service URL that matches the one of the SAML realm in Elasticsearch that should be used. You must specify either this parameter or the realm parameter. -** *`realm` (Optional, string)*: The name of the SAML realm in Elasticsearch the configuration. You must specify either this parameter or the acs parameter. - -[discrete] -==== saml_logout -Logout of SAML. - -Submits a request to invalidate an access token and refresh token. - -{ref}/security-api-saml-logout.html[Endpoint documentation] -[source,ts] ----- -client.security.samlLogout({ token }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`token` (string)*: The access token that was returned as a response to calling the SAML authenticate API. -Alternatively, the most recent token that was received after refreshing the original one by using a refresh_token. -** *`refresh_token` (Optional, string)*: The refresh token that was returned as a response to calling the SAML authenticate API. -Alternatively, the most recent refresh token that was received after refreshing the original access token. - -[discrete] -==== saml_prepare_authentication -Prepare SAML authentication. - -Creates a SAML authentication request (``) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch. - -{ref}/security-api-saml-prepare-authentication.html[Endpoint documentation] -[source,ts] ----- -client.security.samlPrepareAuthentication({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`acs` (Optional, string)*: The Assertion Consumer Service URL that matches the one of the SAML realms in Elasticsearch. -The realm is used to generate the authentication request. You must specify either this parameter or the realm parameter. -** *`realm` (Optional, string)*: The name of the SAML realm in Elasticsearch for which the configuration is used to generate the authentication request. -You must specify either this parameter or the acs parameter. -** *`relay_state` (Optional, string)*: A string that will be included in the redirect URL that this API returns as the RelayState query parameter. -If the Authentication Request is signed, this value is used as part of the signature computation. - -[discrete] -==== saml_service_provider_metadata -Create SAML service provider metadata. - -Generate SAML metadata for a SAML 2.0 Service Provider. - -{ref}/security-api-saml-sp-metadata.html[Endpoint documentation] -[source,ts] ----- -client.security.samlServiceProviderMetadata({ realm_name }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`realm_name` (string)*: The name of the SAML realm in Elasticsearch. - -[discrete] -==== suggest_user_profiles -Suggest a user profile. - -Get suggestions for user profiles that match specified search criteria. - -{ref}/security-api-suggest-user-profile.html[Endpoint documentation] -[source,ts] ----- -client.security.suggestUserProfiles({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`name` (Optional, string)*: Query string used to match name-related fields in user profile documents. -Name-related fields are the user's `username`, `full_name`, and `email`. -** *`size` (Optional, number)*: Number of profiles to return. -** *`data` (Optional, string | string[])*: List of filters for the `data` field of the profile document. -To return all content use `data=*`. To return a subset of content -use `data=` to retrieve content nested under the specified ``. -By default returns no `data` content. -** *`hint` (Optional, { uids, labels })*: Extra search criteria to improve relevance of the suggestion result. -Profiles matching the spcified hint are ranked higher in the response. -Profiles not matching the hint don't exclude the profile from the response -as long as the profile matches the `name` field query. - -[discrete] -==== update_api_key -Update an API key. - -Updates attributes of an existing API key. -Users can only update API keys that they created or that were granted to them. -Use this API to update API keys created by the create API Key or grant API Key APIs. -If you need to apply the same update to many API keys, you can use bulk update API Keys to reduce overhead. -It’s not possible to update expired API keys, or API keys that have been invalidated by invalidate API Key. -This API supports updates to an API key’s access scope and metadata. -The access scope of an API key is derived from the `role_descriptors` you specify in the request, and a snapshot of the owner user’s permissions at the time of the request. -The snapshot of the owner’s permissions is updated automatically on every call. -If you don’t specify `role_descriptors` in the request, a call to this API might still change the API key’s access scope. -This change can occur if the owner user’s permissions have changed since the API key was created or last modified. -To update another user’s API key, use the `run_as` feature to submit a request on behalf of another user. -IMPORTANT: It’s not possible to use an API key as the authentication credential for this API. -To update an API key, the owner user’s credentials are required. - -{ref}/security-api-update-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.updateApiKey({ id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: The ID of the API key to update. -** *`role_descriptors` (Optional, Record)*: An array of role descriptors for this API key. This parameter is optional. When it is not specified or is an empty array, then the API key will have a point in time snapshot of permissions of the authenticated user. If you supply role descriptors then the resultant permissions would be an intersection of API keys permissions and authenticated user’s permissions thereby limiting the access scope for API keys. The structure of role descriptor is the same as the request for create role API. For more details, see create or update roles API. -** *`metadata` (Optional, Record)*: Arbitrary metadata that you want to associate with the API key. It supports nested data structure. Within the metadata object, keys beginning with _ are reserved for system usage. -** *`expiration` (Optional, string | -1 | 0)*: Expiration time for the API key. - -[discrete] -==== update_cross_cluster_api_key -Update a cross-cluster API key. - -Update the attributes of an existing cross-cluster API key, which is used for API key based remote cluster access. - -{ref}/security-api-update-cross-cluster-api-key.html[Endpoint documentation] -[source,ts] ----- -client.security.updateCrossClusterApiKey({ id, access }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: The ID of the cross-cluster API key to update. -** *`access` ({ replication, search })*: The access to be granted to this API key. -The access is composed of permissions for cross cluster search and cross cluster replication. -At least one of them must be specified. -When specified, the new access assignment fully replaces the previously assigned access. -** *`expiration` (Optional, string | -1 | 0)*: Expiration time for the API key. -By default, API keys never expire. This property can be omitted to leave the value unchanged. -** *`metadata` (Optional, Record)*: Arbitrary metadata that you want to associate with the API key. -It supports nested data structure. -Within the metadata object, keys beginning with `_` are reserved for system usage. -When specified, this information fully replaces metadata previously associated with the API key. - -[discrete] -==== update_settings -Update settings for the security system index - -{ref}/security-api-update-settings.html[Endpoint documentation] -[source,ts] ----- -client.security.updateSettings() ----- - - -[discrete] -==== update_user_profile_data -Update user profile data. - -Update specific data for the user profile that is associated with a unique ID. - -{ref}/security-api-update-user-profile-data.html[Endpoint documentation] -[source,ts] ----- -client.security.updateUserProfileData({ uid }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`uid` (string)*: A unique identifier for the user profile. -** *`labels` (Optional, Record)*: Searchable data that you want to associate with the user profile. This -field supports a nested data structure. -** *`data` (Optional, Record)*: Non-searchable data that you want to associate with the user profile. -This field supports a nested data structure. -** *`if_seq_no` (Optional, number)*: Only perform the operation if the document has this sequence number. -** *`if_primary_term` (Optional, number)*: Only perform the operation if the document has this primary term. -** *`refresh` (Optional, Enum(true | false | "wait_for"))*: If 'true', Elasticsearch refreshes 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' do nothing with refreshes. - -[discrete] -=== shutdown -[discrete] -==== delete_node -Removes a node from the shutdown list. Designed for indirect use by ECE/ESS and ECK. Direct use is not supported. - -https://www.elastic.co/guide/en/elasticsearch/reference/current[Endpoint documentation] -[source,ts] ----- -client.shutdown.deleteNode({ node_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (string)*: The node id of node to be removed from the shutdown state -** *`master_timeout` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== get_node -Retrieve status of a node or nodes that are currently marked as shutting down. Designed for indirect use by ECE/ESS and ECK. Direct use is not supported. - -https://www.elastic.co/guide/en/elasticsearch/reference/current[Endpoint documentation] -[source,ts] ----- -client.shutdown.getNode({ ... }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (Optional, string | string[])*: Which node for which to retrieve the shutdown status -** *`master_timeout` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -==== put_node -Adds a node to be shut down. Designed for indirect use by ECE/ESS and ECK. Direct use is not supported. - -https://www.elastic.co/guide/en/elasticsearch/reference/current[Endpoint documentation] -[source,ts] ----- -client.shutdown.putNode({ node_id, type, reason }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`node_id` (string)*: The node id of node to be shut down -** *`type` (Enum("restart" | "remove" | "replace"))*: Valid values are restart, remove, or replace. -Use restart when you need to temporarily shut down a node to perform an upgrade, make configuration changes, or perform other maintenance. -Because the node is expected to rejoin the cluster, data is not migrated off of the node. -Use remove when you need to permanently remove a node from the cluster. -The node is not marked ready for shutdown until data is migrated off of the node Use replace to do a 1:1 replacement of a node with another node. -Certain allocation decisions will be ignored (such as disk watermarks) in the interest of true replacement of the source node with the target node. -During a replace-type shutdown, rollover and index creation may result in unassigned shards, and shrink may fail until the replacement is complete. -** *`reason` (string)*: A human-readable reason that the node is being shut down. -This field provides information for other cluster operators; it does not affect the shut down process. -** *`allocation_delay` (Optional, string)*: Only valid if type is restart. -Controls how long Elasticsearch will wait for the node to restart and join the cluster before reassigning its shards to other nodes. -This works the same as delaying allocation with the index.unassigned.node_left.delayed_timeout setting. -If you specify both a restart allocation delay and an index-level allocation delay, the longer of the two is used. -** *`target_node_name` (Optional, string)*: Only valid if type is replace. -Specifies the name of the node that is replacing the node being shut down. -Shards from the shut down node are only allowed to be allocated to the target node, and no other data will be allocated to the target node. -During relocation of data certain allocation rules are ignored, such as disk watermarks or user attribute filtering rules. -** *`master_timeout` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, Enum("nanos" | "micros" | "ms" | "s" | "m" | "h" | "d"))*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - -[discrete] -=== simulate -[discrete] -==== ingest -Simulates running ingest with example documents. - -{ref}/simulate-ingest-api.html[Endpoint documentation] -[source,ts] ----- -client.simulate.ingest() ----- - - -[discrete] -=== slm -[discrete] -==== delete_lifecycle -Deletes an existing snapshot lifecycle policy. - -{ref}/slm-api-delete-policy.html[Endpoint documentation] -[source,ts] ----- -client.slm.deleteLifecycle({ policy_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`policy_id` (string)*: The id of the snapshot lifecycle policy to remove - -[discrete] -==== execute_lifecycle -Immediately creates a snapshot according to the lifecycle policy, without waiting for the scheduled time. - -{ref}/slm-api-execute-lifecycle.html[Endpoint documentation] -[source,ts] ----- -client.slm.executeLifecycle({ policy_id }) ----- - -[discrete] -==== Arguments - -* *Request (object):* -** *`policy_id` (string)*: The id of the snapshot lifecycle policy to be executed - -[discrete] -==== execute_retention -Deletes any snapshots that are expired according to the policy's retention rules. - -{ref}/slm-api-execute-retention.html[Endpoint documentation] -[source,ts] ----- -client.slm.executeRetention() ----- - - -[discrete] -==== get_lifecycle -Retrieves one or more snapshot lifecycle policy definitions and information about the latest snapshot attempts. - -{ref}/slm-api-get-policy.html[Endpoint documentation] -[source,ts] ----- -client.slm.getLifecycle({ ... }) ----- - +=== client.security.createApiKey [discrete] -==== Arguments - -* *Request (object):* -** *`policy_id` (Optional, string | string[])*: List of snapshot lifecycle policies to retrieve - +=== client.security.createCrossClusterApiKey [discrete] -==== get_stats -Returns global and policy-level statistics about actions taken by snapshot lifecycle management. - -{ref}/slm-api-get-stats.html[Endpoint documentation] -[source,ts] ----- -client.slm.getStats() ----- - - +=== client.security.createServiceToken [discrete] -==== get_status -Retrieves the status of snapshot lifecycle management (SLM). - -{ref}/slm-api-get-status.html[Endpoint documentation] -[source,ts] ----- -client.slm.getStatus() ----- - - +=== client.security.deletePrivileges [discrete] -==== put_lifecycle -Creates or updates a snapshot lifecycle policy. - -{ref}/slm-api-put-policy.html[Endpoint documentation] -[source,ts] ----- -client.slm.putLifecycle({ policy_id }) ----- - +=== client.security.deleteRole [discrete] -==== Arguments - -* *Request (object):* -** *`policy_id` (string)*: ID for the snapshot lifecycle policy you want to create or update. -** *`config` (Optional, { ignore_unavailable, indices, include_global_state, feature_states, metadata, partial })*: Configuration for each snapshot created by the policy. -** *`name` (Optional, string)*: Name automatically assigned to each snapshot created by the policy. Date math is supported. To prevent conflicting snapshot names, a UUID is automatically appended to each snapshot name. -** *`repository` (Optional, string)*: Repository used to store snapshots created by this policy. This repository must exist prior to the policy’s creation. You can create a repository using the snapshot repository API. -** *`retention` (Optional, { expire_after, max_count, min_count })*: Retention rules used to retain and delete snapshots created by the policy. -** *`schedule` (Optional, string)*: Periodic or absolute schedule at which the policy creates snapshots. SLM applies schedule changes immediately. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.security.deleteRoleMapping [discrete] -==== start -Turns on snapshot lifecycle management (SLM). - -{ref}/slm-api-start.html[Endpoint documentation] -[source,ts] ----- -client.slm.start() ----- - - +=== client.security.deleteServiceToken [discrete] -==== stop -Turns off snapshot lifecycle management (SLM). - -{ref}/slm-api-stop.html[Endpoint documentation] -[source,ts] ----- -client.slm.stop() ----- - - +=== client.security.deleteUser [discrete] -=== snapshot +=== client.security.disableUser [discrete] -==== cleanup_repository -Triggers the review of a snapshot repository’s contents and deletes any stale data not referenced by existing snapshots. - -{ref}/clean-up-snapshot-repo-api.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.cleanupRepository({ repository }) ----- - +=== client.security.disableUserProfile [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: Snapshot repository to clean up. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. - +=== client.security.enableUser [discrete] -==== clone -Clones indices from one snapshot into another snapshot in the same repository. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.clone({ repository, snapshot, target_snapshot, indices }) ----- - +=== client.security.enableUserProfile [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: A repository name -** *`snapshot` (string)*: The name of the snapshot to clone from -** *`target_snapshot` (string)*: The name of the cloned snapshot to create -** *`indices` (string)* -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node -** *`timeout` (Optional, string | -1 | 0)* - +=== client.security.enrollKibana [discrete] -==== create -Creates a snapshot in a repository. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.create({ repository, snapshot }) ----- - +=== client.security.enrollNode [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: Repository for the snapshot. -** *`snapshot` (string)*: Name of the snapshot. Must be unique in the repository. -** *`ignore_unavailable` (Optional, boolean)*: If `true`, the request ignores data streams and indices in `indices` that are missing or closed. If `false`, the request returns an error for any data stream or index that is missing or closed. -** *`include_global_state` (Optional, boolean)*: If `true`, the current cluster state is included in the snapshot. The cluster state includes persistent cluster settings, composable index templates, legacy index templates, ingest pipelines, and ILM policies. It also includes data stored in system indices, such as Watches and task records (configurable via `feature_states`). -** *`indices` (Optional, string | string[])*: Data streams and indices to include in the snapshot. Supports multi-target syntax. Includes all data streams and indices by default. -** *`feature_states` (Optional, string[])*: Feature states to include in the snapshot. Each feature state includes one or more system indices containing related data. You can view a list of eligible features using the get features API. If `include_global_state` is `true`, all current feature states are included by default. If `include_global_state` is `false`, no feature states are included by default. -** *`metadata` (Optional, Record)*: Optional metadata for the snapshot. May have any contents. Must be less than 1024 bytes. This map is not automatically generated by Elasticsearch. -** *`partial` (Optional, boolean)*: If `true`, allows restoring a partial snapshot of indices with unavailable shards. Only shards that were successfully included in the snapshot will be restored. All missing shards will be recreated as empty. If `false`, the entire restore operation will fail if one or more indices included in the snapshot do not have all primary shards available. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_completion` (Optional, boolean)*: If `true`, the request returns a response when the snapshot is complete. If `false`, the request returns a response when the snapshot initializes. - +=== client.security.getApiKey [discrete] -==== create_repository -Creates a repository. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.createRepository({ repository }) ----- - +=== client.security.getBuiltinPrivileges [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: A repository name -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout -** *`verify` (Optional, boolean)*: Whether to verify the repository after creation - +=== client.security.getPrivileges [discrete] -==== delete -Deletes one or more snapshots. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.delete({ repository, snapshot }) ----- - +=== client.security.getRole [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: A repository name -** *`snapshot` (string)*: A list of snapshot names -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node - +=== client.security.getRoleMapping [discrete] -==== delete_repository -Deletes a repository. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.deleteRepository({ repository }) ----- - +=== client.security.getServiceAccounts [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string | string[])*: Name of the snapshot repository to unregister. Wildcard (`*`) patterns are supported. -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout - +=== client.security.getServiceCredentials [discrete] -==== get -Returns information about a snapshot. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.get({ repository, snapshot }) ----- - +=== client.security.getSettings [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: List of snapshot repository names used to limit the request. Wildcard (*) expressions are supported. -** *`snapshot` (string | string[])*: List of snapshot names to retrieve. Also accepts wildcards (*). -- To get information about all snapshots in a registered repository, use a wildcard (*) or _all. -- To get information about any snapshots that are currently running, use _current. -** *`ignore_unavailable` (Optional, boolean)*: If false, the request returns an error for any snapshots that are unavailable. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`verbose` (Optional, boolean)*: If true, returns additional information about each snapshot such as the version of Elasticsearch which took the snapshot, the start and end times of the snapshot, and the number of shards snapshotted. -** *`index_details` (Optional, boolean)*: If true, returns additional information about each index in the snapshot comprising the number of shards in the index, the total size of the index in bytes, and the maximum number of segments per shard in the index. Defaults to false, meaning that this information is omitted. -** *`index_names` (Optional, boolean)*: If true, returns the name of each index in each snapshot. -** *`include_repository` (Optional, boolean)*: If true, returns the repository name in each snapshot. -** *`sort` (Optional, Enum("start_time" | "duration" | "name" | "index_count" | "repository" | "shard_count" | "failed_shard_count"))*: Allows setting a sort order for the result. Defaults to start_time, i.e. sorting by snapshot start time stamp. -** *`size` (Optional, number)*: Maximum number of snapshots to return. Defaults to 0 which means return all that match the request without limit. -** *`order` (Optional, Enum("asc" | "desc"))*: Sort order. Valid values are asc for ascending and desc for descending order. Defaults to asc, meaning ascending order. -** *`after` (Optional, string)*: Offset identifier to start pagination from as returned by the next field in the response body. -** *`offset` (Optional, number)*: Numeric offset to start pagination from based on the snapshots matching this request. Using a non-zero value for this parameter is mutually exclusive with using the after parameter. Defaults to 0. -** *`from_sort_value` (Optional, string)*: Value of the current sort column at which to start retrieval. Can either be a string snapshot- or repository name when sorting by snapshot or repository name, a millisecond time value or a number when sorting by index- or shard count. -** *`slm_policy_filter` (Optional, string)*: Filter snapshots by a list of SLM policy names that snapshots belong to. Also accepts wildcards (*) and combinations of wildcards followed by exclude patterns starting with -. To include snapshots not created by an SLM policy you can use the special pattern _none that will match all snapshots without an SLM policy. - +=== client.security.getToken [discrete] -==== get_repository -Returns information about a repository. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.getRepository({ ... }) ----- - +=== client.security.getUser [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (Optional, string | string[])*: A list of repository names -** *`local` (Optional, boolean)*: Return local information, do not retrieve the state from master node (default: false) -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node - +=== client.security.getUserPrivileges [discrete] -==== repository_analyze -Analyzes a repository for correctness and performance - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.repositoryAnalyze() ----- - - +=== client.security.getUserProfile [discrete] -==== restore -Restores a snapshot. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.restore({ repository, snapshot }) ----- - +=== client.security.grantApiKey [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: A repository name -** *`snapshot` (string)*: A snapshot name -** *`feature_states` (Optional, string[])* -** *`ignore_index_settings` (Optional, string[])* -** *`ignore_unavailable` (Optional, boolean)* -** *`include_aliases` (Optional, boolean)* -** *`include_global_state` (Optional, boolean)* -** *`index_settings` (Optional, { index, mode, routing_path, soft_deletes, sort, number_of_shards, number_of_replicas, number_of_routing_shards, check_on_startup, codec, routing_partition_size, load_fixed_bitset_filters_eagerly, hidden, auto_expand_replicas, merge, search, refresh_interval, max_result_window, max_inner_result_window, max_rescore_window, max_docvalue_fields_search, max_script_fields, max_ngram_diff, max_shingle_diff, blocks, max_refresh_listeners, analyze, highlight, max_terms_count, max_regex_length, routing, gc_deletes, default_pipeline, final_pipeline, lifecycle, provided_name, creation_date, creation_date_string, uuid, version, verified_before_close, format, max_slices_per_scroll, translog, query_string, priority, top_metrics_max_size, analysis, settings, time_series, queries, similarity, mapping, indexing.slowlog, indexing_pressure, store })* -** *`indices` (Optional, string | string[])* -** *`partial` (Optional, boolean)* -** *`rename_pattern` (Optional, string)* -** *`rename_replacement` (Optional, string)* -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node -** *`wait_for_completion` (Optional, boolean)*: Should this request wait until the operation has completed before returning - +=== client.security.hasPrivileges [discrete] -==== status -Returns information about the status of a snapshot. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.status({ ... }) ----- - +=== client.security.hasPrivilegesUserProfile [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (Optional, string)*: A repository name -** *`snapshot` (Optional, string | string[])*: A list of snapshot names -** *`ignore_unavailable` (Optional, boolean)*: Whether to ignore unavailable snapshots, defaults to false which means a SnapshotMissingException is thrown -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node - +=== client.security.invalidateApiKey [discrete] -==== verify_repository -Verifies a repository. - -{ref}/modules-snapshots.html[Endpoint documentation] -[source,ts] ----- -client.snapshot.verifyRepository({ repository }) ----- - +=== client.security.invalidateToken [discrete] -==== Arguments - -* *Request (object):* -** *`repository` (string)*: A repository name -** *`master_timeout` (Optional, string | -1 | 0)*: Explicit operation timeout for connection to master node -** *`timeout` (Optional, string | -1 | 0)*: Explicit operation timeout - +=== client.security.oidcAuthenticate [discrete] -=== sql +=== client.security.oidcLogout [discrete] -==== clear_cursor -Clears the SQL cursor - -{ref}/clear-sql-cursor-api.html[Endpoint documentation] -[source,ts] ----- -client.sql.clearCursor({ cursor }) ----- - +=== client.security.oidcPrepareAuthentication [discrete] -==== Arguments - -* *Request (object):* -** *`cursor` (string)*: Cursor to clear. - +=== client.security.putPrivileges [discrete] -==== delete_async -Deletes an async SQL search or a stored synchronous SQL search. If the search is still running, the API cancels it. - -{ref}/delete-async-sql-search-api.html[Endpoint documentation] -[source,ts] ----- -client.sql.deleteAsync({ id }) ----- - +=== client.security.putRole [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the search. - +=== client.security.putRoleMapping [discrete] -==== get_async -Returns the current status and available results for an async SQL search or stored synchronous SQL search - -{ref}/get-async-sql-search-api.html[Endpoint documentation] -[source,ts] ----- -client.sql.getAsync({ id }) ----- - +=== client.security.putUser [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the search. -** *`delimiter` (Optional, string)*: Separator for CSV results. The API only supports this parameter for CSV responses. -** *`format` (Optional, string)*: Format for the response. You must specify a format using this parameter or the -Accept HTTP header. If you specify both, the API uses this parameter. -** *`keep_alive` (Optional, string | -1 | 0)*: Retention period for the search and its results. Defaults -to the `keep_alive` period for the original SQL search. -** *`wait_for_completion_timeout` (Optional, string | -1 | 0)*: Period to wait for complete results. Defaults to no timeout, -meaning the request waits for complete search results. - +=== client.security.queryApiKeys [discrete] -==== get_async_status -Returns the current status of an async SQL search or a stored synchronous SQL search - -{ref}/get-async-sql-search-status-api.html[Endpoint documentation] -[source,ts] ----- -client.sql.getAsyncStatus({ id }) ----- - +=== client.security.queryRole [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Identifier for the search. - +=== client.security.queryUser [discrete] -==== query -Executes a SQL request - -{ref}/sql-search-api.html[Endpoint documentation] -[source,ts] ----- -client.sql.query({ ... }) ----- - +=== client.security.samlAuthenticate [discrete] -==== Arguments - -* *Request (object):* -** *`catalog` (Optional, string)*: Default catalog (cluster) for queries. If unspecified, the queries execute on the data in the local cluster only. -** *`columnar` (Optional, boolean)*: If true, the results in a columnar fashion: one row represents all the values of a certain column from the current page of results. -** *`cursor` (Optional, string)*: Cursor used to retrieve a set of paginated results. -If you specify a cursor, the API only uses the `columnar` and `time_zone` request body parameters. -It ignores other request body parameters. -** *`fetch_size` (Optional, number)*: The maximum number of rows (or entries) to return in one response -** *`filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Elasticsearch query DSL for additional filtering. -** *`query` (Optional, string)*: SQL query to run. -** *`request_timeout` (Optional, string | -1 | 0)*: The timeout before the request fails. -** *`page_timeout` (Optional, string | -1 | 0)*: The timeout before a pagination request fails. -** *`time_zone` (Optional, string)*: ISO-8601 time zone ID for the search. -** *`field_multi_value_leniency` (Optional, boolean)*: Throw an exception when encountering multiple values for a field (default) or be lenient and return the first value from the list (without any guarantees of what that will be - typically the first in natural ascending order). -** *`runtime_mappings` (Optional, Record)*: Defines one or more runtime fields in the search request. These fields take -precedence over mapped fields with the same name. -** *`wait_for_completion_timeout` (Optional, string | -1 | 0)*: Period to wait for complete results. Defaults to no timeout, meaning the request waits for complete search results. If the search doesn’t finish within this period, the search becomes async. -** *`params` (Optional, Record)*: Values for parameters in the query. -** *`keep_alive` (Optional, string | -1 | 0)*: Retention period for an async or saved synchronous search. -** *`keep_on_completion` (Optional, boolean)*: If true, Elasticsearch stores synchronous searches if you also specify the wait_for_completion_timeout parameter. If false, Elasticsearch only stores async searches that don’t finish before the wait_for_completion_timeout. -** *`index_using_frozen` (Optional, boolean)*: If true, the search can run on frozen indices. Defaults to false. -** *`format` (Optional, Enum("csv" | "json" | "tsv" | "txt" | "yaml" | "cbor" | "smile"))*: Format for the response. - +=== client.security.samlCompleteLogout [discrete] -==== translate -Translates SQL into Elasticsearch queries - -{ref}/sql-translate-api.html[Endpoint documentation] -[source,ts] ----- -client.sql.translate({ query }) ----- - +=== client.security.samlInvalidate [discrete] -==== Arguments - -* *Request (object):* -** *`query` (string)*: SQL query to run. -** *`fetch_size` (Optional, number)*: The maximum number of rows (or entries) to return in one response. -** *`filter` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Elasticsearch query DSL for additional filtering. -** *`time_zone` (Optional, string)*: ISO-8601 time zone ID for the search. - +=== client.security.samlLogout [discrete] -=== ssl +=== client.security.samlPrepareAuthentication [discrete] -==== certificates -Get SSL certificates. - -Get information about the X.509 certificates that are used to encrypt communications in the cluster. -The API returns a list that includes certificates from all TLS contexts including: - -- Settings for transport and HTTP interfaces -- TLS settings that are used within authentication realms -- TLS settings for remote monitoring exporters - -The list includes certificates that are used for configuring trust, such as those configured in the `xpack.security.transport.ssl.truststore` and `xpack.security.transport.ssl.certificate_authorities` settings. -It also includes certificates that are used for configuring server identity, such as `xpack.security.http.ssl.keystore` and `xpack.security.http.ssl.certificate settings`. - -The list does not include certificates that are sourced from the default SSL context of the Java Runtime Environment (JRE), even if those certificates are in use within Elasticsearch. - -NOTE: When a PKCS#11 token is configured as the truststore of the JRE, the API returns all the certificates that are included in the PKCS#11 token irrespective of whether these are used in the Elasticsearch TLS configuration. - -If Elasticsearch is configured to use a keystore or truststore, the API output includes all certificates in that store, even though some of the certificates might not be in active use within the cluster. - -{ref}/security-api-ssl.html[Endpoint documentation] -[source,ts] ----- -client.ssl.certificates() ----- - - +=== client.security.samlServiceProviderMetadata [discrete] -=== synonyms +=== client.security.suggestUserProfiles [discrete] -==== delete_synonym -Deletes a synonym set - -{ref}/delete-synonyms-set.html[Endpoint documentation] -[source,ts] ----- -client.synonyms.deleteSynonym({ id }) ----- - +=== client.security.updateApiKey [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: The id of the synonyms set to be deleted - +=== client.security.updateCrossClusterApiKey [discrete] -==== delete_synonym_rule -Deletes a synonym rule in a synonym set - -{ref}/delete-synonym-rule.html[Endpoint documentation] -[source,ts] ----- -client.synonyms.deleteSynonymRule({ set_id, rule_id }) ----- - +=== client.security.updateSettings [discrete] -==== Arguments - -* *Request (object):* -** *`set_id` (string)*: The id of the synonym set to be updated -** *`rule_id` (string)*: The id of the synonym rule to be deleted - +=== client.security.updateUserProfileData [discrete] -==== get_synonym -Retrieves a synonym set - -{ref}/get-synonyms-set.html[Endpoint documentation] -[source,ts] ----- -client.synonyms.getSynonym({ id }) ----- - +=== client.shutdown.deleteNode [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: "The id of the synonyms set to be retrieved -** *`from` (Optional, number)*: Starting offset for query rules to be retrieved -** *`size` (Optional, number)*: specifies a max number of query rules to retrieve - +=== client.shutdown.getNode [discrete] -==== get_synonym_rule -Retrieves a synonym rule from a synonym set - -{ref}/get-synonym-rule.html[Endpoint documentation] -[source,ts] ----- -client.synonyms.getSynonymRule({ set_id, rule_id }) ----- - +=== client.shutdown.putNode [discrete] -==== Arguments - -* *Request (object):* -** *`set_id` (string)*: The id of the synonym set to retrieve the synonym rule from -** *`rule_id` (string)*: The id of the synonym rule to retrieve - +=== client.simulate.ingest [discrete] -==== get_synonyms_sets -Retrieves a summary of all defined synonym sets - -{ref}/list-synonyms-sets.html[Endpoint documentation] -[source,ts] ----- -client.synonyms.getSynonymsSets({ ... }) ----- - +=== client.slm.deleteLifecycle [discrete] -==== Arguments - -* *Request (object):* -** *`from` (Optional, number)*: Starting offset -** *`size` (Optional, number)*: specifies a max number of results to get - +=== client.slm.executeLifecycle [discrete] -==== put_synonym -Creates or updates a synonym set. - -{ref}/put-synonyms-set.html[Endpoint documentation] -[source,ts] ----- -client.synonyms.putSynonym({ id, synonyms_set }) ----- - +=== client.slm.executeRetention [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: The id of the synonyms set to be created or updated -** *`synonyms_set` ({ id, synonyms } | { id, synonyms }[])*: The synonym set information to update - +=== client.slm.getLifecycle [discrete] -==== put_synonym_rule -Creates or updates a synonym rule in a synonym set - -{ref}/put-synonym-rule.html[Endpoint documentation] -[source,ts] ----- -client.synonyms.putSynonymRule({ set_id, rule_id, synonyms }) ----- - +=== client.slm.getStats [discrete] -==== Arguments - -* *Request (object):* -** *`set_id` (string)*: The id of the synonym set to be updated with the synonym rule -** *`rule_id` (string)*: The id of the synonym rule to be updated or created -** *`synonyms` (string)* - +=== client.slm.getStatus [discrete] -=== tasks +=== client.slm.putLifecycle [discrete] -==== cancel -Cancels a task, if it can be cancelled through an API. - -{ref}/tasks.html[Endpoint documentation] -[source,ts] ----- -client.tasks.cancel({ ... }) ----- - +=== client.slm.start [discrete] -==== Arguments - -* *Request (object):* -** *`task_id` (Optional, string | number)*: ID of the task. -** *`actions` (Optional, string | string[])*: List or wildcard expression of actions used to limit the request. -** *`nodes` (Optional, string[])*: List of node IDs or names used to limit the request. -** *`parent_task_id` (Optional, string)*: Parent task ID used to limit the tasks. -** *`wait_for_completion` (Optional, boolean)*: Should the request block until the cancellation of the task and its descendant tasks is completed. Defaults to false - +=== client.slm.stop [discrete] -==== get -Get task information. -Returns information about the tasks currently executing in the cluster. - -{ref}/tasks.html[Endpoint documentation] -[source,ts] ----- -client.tasks.get({ task_id }) ----- - +=== client.snapshot.cleanupRepository [discrete] -==== Arguments - -* *Request (object):* -** *`task_id` (string)*: ID of the task. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. -If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_completion` (Optional, boolean)*: If `true`, the request blocks until the task has completed. - +=== client.snapshot.clone [discrete] -==== list -The task management API returns information about tasks currently executing on one or more nodes in the cluster. - -{ref}/tasks.html[Endpoint documentation] -[source,ts] ----- -client.tasks.list({ ... }) ----- - +=== client.snapshot.create [discrete] -==== Arguments - -* *Request (object):* -** *`actions` (Optional, string | string[])*: List or wildcard expression of actions used to limit the request. -** *`detailed` (Optional, boolean)*: If `true`, the response includes detailed information about shard recoveries. -** *`group_by` (Optional, Enum("nodes" | "parents" | "none"))*: Key used to group tasks in the response. -** *`node_id` (Optional, string[])*: List of node IDs or names used to limit returned information. -** *`parent_task_id` (Optional, string)*: Parent task ID used to limit returned information. To return all tasks, omit this parameter or use a value of `-1`. -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. -** *`wait_for_completion` (Optional, boolean)*: If `true`, the request blocks until the operation is complete. - +=== client.snapshot.createRepository [discrete] -=== text_structure +=== client.snapshot.delete [discrete] -==== find_field_structure -Finds the structure of a text field in an index. - -{ref}/find-field-structure.html[Endpoint documentation] -[source,ts] ----- -client.textStructure.findFieldStructure() ----- - - +=== client.snapshot.deleteRepository [discrete] -==== find_message_structure -Finds the structure of a list of messages. The messages must contain data that is suitable to be ingested into Elasticsearch. - -{ref}/find-message-structure.html[Endpoint documentation] -[source,ts] ----- -client.textStructure.findMessageStructure() ----- - - +=== client.snapshot.get [discrete] -==== find_structure -Finds the structure of a text file. The text file must contain data that is suitable to be ingested into Elasticsearch. - -{ref}/find-structure.html[Endpoint documentation] -[source,ts] ----- -client.textStructure.findStructure({ ... }) ----- - +=== client.snapshot.getRepository [discrete] -==== Arguments - -* *Request (object):* -** *`text_files` (Optional, TJsonDocument[])* -** *`charset` (Optional, string)*: The text’s character set. It must be a character set that is supported by the JVM that Elasticsearch uses. For example, UTF-8, UTF-16LE, windows-1252, or EUC-JP. If this parameter is not specified, the structure finder chooses an appropriate character set. -** *`column_names` (Optional, string)*: If you have set format to delimited, you can specify the column names in a list. If this parameter is not specified, the structure finder uses the column names from the header row of the text. If the text does not have a header role, columns are named "column1", "column2", "column3", etc. -** *`delimiter` (Optional, string)*: If you have set format to delimited, you can specify the character used to delimit the values in each row. Only a single character is supported; the delimiter cannot have multiple characters. By default, the API considers the following possibilities: comma, tab, semi-colon, and pipe (|). In this default scenario, all rows must have the same number of fields for the delimited format to be detected. If you specify a delimiter, up to 10% of the rows can have a different number of columns than the first row. -** *`ecs_compatibility` (Optional, string)*: The mode of compatibility with ECS compliant Grok patterns (disabled or v1, default: disabled). -** *`explain` (Optional, boolean)*: If this parameter is set to true, the response includes a field named explanation, which is an array of strings that indicate how the structure finder produced its result. -** *`format` (Optional, string)*: The high level structure of the text. Valid values are ndjson, xml, delimited, and semi_structured_text. By default, the API chooses the format. In this default scenario, all rows must have the same number of fields for a delimited format to be detected. If the format is set to delimited and the delimiter is not set, however, the API tolerates up to 5% of rows that have a different number of columns than the first row. -** *`grok_pattern` (Optional, string)*: If you have set format to semi_structured_text, you can specify a Grok pattern that is used to extract fields from every message in the text. The name of the timestamp field in the Grok pattern must match what is specified in the timestamp_field parameter. If that parameter is not specified, the name of the timestamp field in the Grok pattern must match "timestamp". If grok_pattern is not specified, the structure finder creates a Grok pattern. -** *`has_header_row` (Optional, boolean)*: If you have set format to delimited, you can use this parameter to indicate whether the column names are in the first row of the text. If this parameter is not specified, the structure finder guesses based on the similarity of the first row of the text to other rows. -** *`line_merge_size_limit` (Optional, number)*: The maximum number of characters in a message when lines are merged to form messages while analyzing semi-structured text. If you have extremely long messages you may need to increase this, but be aware that this may lead to very long processing times if the way to group lines into messages is misdetected. -** *`lines_to_sample` (Optional, number)*: The number of lines to include in the structural analysis, starting from the beginning of the text. The minimum is 2; If the value of this parameter is greater than the number of lines in the text, the analysis proceeds (as long as there are at least two lines in the text) for all of the lines. -** *`quote` (Optional, string)*: If you have set format to delimited, you can specify the character used to quote the values in each row if they contain newlines or the delimiter character. Only a single character is supported. If this parameter is not specified, the default value is a double quote ("). If your delimited text format does not use quoting, a workaround is to set this argument to a character that does not appear anywhere in the sample. -** *`should_trim_fields` (Optional, boolean)*: If you have set format to delimited, you can specify whether values between delimiters should have whitespace trimmed from them. If this parameter is not specified and the delimiter is pipe (|), the default value is true. Otherwise, the default value is false. -** *`timeout` (Optional, string | -1 | 0)*: Sets the maximum amount of time that the structure analysis make take. If the analysis is still running when the timeout expires then it will be aborted. -** *`timestamp_field` (Optional, string)*: Optional parameter to specify the timestamp field in the file -** *`timestamp_format` (Optional, string)*: The Java time format of the timestamp field in the text. - +=== client.snapshot.repositoryAnalyze [discrete] -==== test_grok_pattern -Tests a Grok pattern on some text. - -{ref}/test-grok-pattern.html[Endpoint documentation] -[source,ts] ----- -client.textStructure.testGrokPattern({ grok_pattern, text }) ----- - +=== client.snapshot.restore [discrete] -==== Arguments - -* *Request (object):* -** *`grok_pattern` (string)*: Grok pattern to run on the text. -** *`text` (string[])*: Lines of text to run the Grok pattern on. -** *`ecs_compatibility` (Optional, string)*: The mode of compatibility with ECS compliant Grok patterns (disabled or v1, default: disabled). - +=== client.snapshot.status [discrete] -=== transform +=== client.snapshot.verifyRepository [discrete] -==== delete_transform -Delete a transform. -Deletes a transform. - -{ref}/delete-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.deleteTransform({ transform_id }) ----- - +=== client.sql.clearCursor [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string)*: Identifier for the transform. -** *`force` (Optional, boolean)*: If this value is false, the transform must be stopped before it can be deleted. If true, the transform is -deleted regardless of its current state. -** *`delete_dest_index` (Optional, boolean)*: If this value is true, the destination index is deleted together with the transform. If false, the destination -index will not be deleted -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.sql.deleteAsync [discrete] -==== get_node_stats -Retrieves transform usage information for transform nodes. -[source,ts] ----- -client.transform.getNodeStats() ----- - - +=== client.sql.getAsync [discrete] -==== get_transform -Get transforms. -Retrieves configuration information for transforms. - -{ref}/get-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.getTransform({ ... }) ----- - +=== client.sql.getAsyncStatus [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (Optional, string | string[])*: Identifier for the transform. It can be a transform identifier or a -wildcard expression. You can get information for all transforms by using -`_all`, by specifying `*` as the ``, or by omitting the -``. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no transforms that match. -2. Contains the _all string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -If this parameter is false, the request returns a 404 status code when -there are no matches or only partial matches. -** *`from` (Optional, number)*: Skips the specified number of transforms. -** *`size` (Optional, number)*: Specifies the maximum number of transforms to obtain. -** *`exclude_generated` (Optional, boolean)*: Excludes fields that were automatically added when creating the -transform. This allows the configuration to be in an acceptable format to -be retrieved and then added to another cluster. - +=== client.sql.query [discrete] -==== get_transform_stats -Get transform stats. -Retrieves usage information for transforms. - -{ref}/get-transform-stats.html[Endpoint documentation] -[source,ts] ----- -client.transform.getTransformStats({ transform_id }) ----- - +=== client.sql.translate [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string | string[])*: Identifier for the transform. It can be a transform identifier or a -wildcard expression. You can get information for all transforms by using -`_all`, by specifying `*` as the ``, or by omitting the -``. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: - -1. Contains wildcard expressions and there are no transforms that match. -2. Contains the _all string or no identifiers and there are no matches. -3. Contains wildcard expressions and there are only partial matches. - -If this parameter is false, the request returns a 404 status code when -there are no matches or only partial matches. -** *`from` (Optional, number)*: Skips the specified number of transforms. -** *`size` (Optional, number)*: Specifies the maximum number of transforms to obtain. -** *`timeout` (Optional, string | -1 | 0)*: Controls the time to wait for the stats - +=== client.ssl.certificates [discrete] -==== preview_transform -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. - -{ref}/preview-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.previewTransform({ ... }) ----- - +=== client.synonyms.deleteSynonym [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (Optional, string)*: Identifier for the transform to preview. If you specify this path parameter, you cannot provide transform -configuration details in the request body. -** *`dest` (Optional, { index, op_type, pipeline, routing, version_type })*: The destination for the transform. -** *`description` (Optional, string)*: Free text description of the transform. -** *`frequency` (Optional, string | -1 | 0)*: The interval between checks for changes in the source indices when the -transform is running continuously. Also determines the retry interval in -the event of transient failures while the transform is searching or -indexing. The minimum value is 1s and the maximum is 1h. -** *`pivot` (Optional, { aggregations, group_by })*: The pivot method transforms the data by aggregating and grouping it. -These objects define the group by fields and the aggregation to reduce -the data. -** *`source` (Optional, { index, query, remote, size, slice, sort, _source, runtime_mappings })*: The source of the data for the transform. -** *`settings` (Optional, { align_checkpoints, dates_as_epoch_millis, deduce_mappings, docs_per_second, max_page_search_size, unattended })*: Defines optional transform settings. -** *`sync` (Optional, { time })*: Defines the properties transforms require to run continuously. -** *`retention_policy` (Optional, { time })*: Defines a retention policy for the transform. Data that meets the defined -criteria is deleted from the destination index. -** *`latest` (Optional, { sort, unique_key })*: The latest method transforms the data by finding the latest document for -each unique key. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the -timeout expires, the request fails and returns an error. - +=== client.synonyms.deleteSynonymRule [discrete] -==== put_transform -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. - -{ref}/put-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.putTransform({ transform_id, dest, source }) ----- - +=== client.synonyms.getSynonym [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string)*: Identifier for the transform. This identifier can contain lowercase alphanumeric characters (a-z and 0-9), -hyphens, and underscores. It has a 64 character limit and must start and end with alphanumeric characters. -** *`dest` ({ index, op_type, pipeline, routing, version_type })*: The destination for the transform. -** *`source` ({ index, query, remote, size, slice, sort, _source, runtime_mappings })*: The source of the data for the transform. -** *`description` (Optional, string)*: Free text description of the transform. -** *`frequency` (Optional, string | -1 | 0)*: The interval between checks for changes in the source indices when the transform is running continuously. Also -determines the retry interval in the event of transient failures while the transform is searching or indexing. -The minimum value is `1s` and the maximum is `1h`. -** *`latest` (Optional, { sort, unique_key })*: The latest method transforms the data by finding the latest document for each unique key. -** *`_meta` (Optional, Record)*: Defines optional transform metadata. -** *`pivot` (Optional, { aggregations, group_by })*: The pivot method transforms the data by aggregating and grouping it. These objects define the group by fields -and the aggregation to reduce the data. -** *`retention_policy` (Optional, { time })*: Defines a retention policy for the transform. Data that meets the defined criteria is deleted from the -destination index. -** *`settings` (Optional, { align_checkpoints, dates_as_epoch_millis, deduce_mappings, docs_per_second, max_page_search_size, unattended })*: Defines optional transform settings. -** *`sync` (Optional, { time })*: Defines the properties transforms require to run continuously. -** *`defer_validation` (Optional, boolean)*: When the transform is created, a series of validations occur to ensure its success. For example, there is a -check for the existence of the source indices and a check that the destination index is not part of the source -index pattern. You can use this parameter to skip the checks, for example when the source index does not exist -until after the transform is created. The validations are always run when you start the transform, however, with -the exception of privilege checks. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.synonyms.getSynonymRule [discrete] -==== reset_transform -Reset a transform. -Resets 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. - -{ref}/reset-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.resetTransform({ transform_id }) ----- - +=== client.synonyms.getSynonymsSets [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string)*: Identifier for the transform. This identifier can contain lowercase alphanumeric characters (a-z and 0-9), -hyphens, and underscores. It has a 64 character limit and must start and end with alphanumeric characters. -** *`force` (Optional, boolean)*: If this value is `true`, the transform is reset regardless of its current state. If it's `false`, the transform -must be stopped before it can be reset. - +=== client.synonyms.putSynonym [discrete] -==== schedule_now_transform -Schedule a transform to start now. -Instantly runs a transform to process data. - -If you _schedule_now a transform, it will process the new data instantly, -without waiting for the configured frequency interval. After _schedule_now API is called, -the transform will be processed again at now + frequency unless _schedule_now API -is called again in the meantime. - -{ref}/schedule-now-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.scheduleNowTransform({ transform_id }) ----- - +=== client.synonyms.putSynonymRule [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string)*: Identifier for the transform. -** *`timeout` (Optional, string | -1 | 0)*: Controls the time to wait for the scheduling to take place - +=== client.tasks.cancel [discrete] -==== start_transform -Start a transform. -Starts 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. - -{ref}/start-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.startTransform({ transform_id }) ----- - +=== client.tasks.get [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string)*: Identifier for the transform. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. -** *`from` (Optional, string)*: Restricts the set of transformed entities to those changed after this time. Relative times like now-30d are supported. Only applicable for continuous transforms. - +=== client.tasks.list [discrete] -==== stop_transform -Stop transforms. -Stops one or more transforms. - -{ref}/stop-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.stopTransform({ transform_id }) ----- - +=== client.termsEnum [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string)*: Identifier for the transform. To stop multiple transforms, use a list or a wildcard expression. -To stop all transforms, use `_all` or `*` as the identifier. -** *`allow_no_match` (Optional, boolean)*: Specifies what to do when the request: contains wildcard expressions and there are no transforms that match; -contains the `_all` string or no identifiers and there are no matches; contains wildcard expressions and there -are only partial matches. - -If it is true, the API returns a successful acknowledgement message when there are no matches. When there are -only partial matches, the API stops the appropriate transforms. - -If it is false, the request returns a 404 status code when there are no matches or only partial matches. -** *`force` (Optional, boolean)*: If it is true, the API forcefully stops the transforms. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response when `wait_for_completion` is `true`. If no response is received before the -timeout expires, the request returns a timeout exception. However, the request continues processing and -eventually moves the transform to a STOPPED state. -** *`wait_for_checkpoint` (Optional, boolean)*: If it is true, the transform does not completely stop until the current checkpoint is completed. If it is false, -the transform stops as soon as possible. -** *`wait_for_completion` (Optional, boolean)*: If it is true, the API blocks until the indexer state completely stops. If it is false, the API returns -immediately and the indexer is stopped asynchronously in the background. - +=== client.termvectors [discrete] -==== update_transform -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. - -{ref}/update-transform.html[Endpoint documentation] -[source,ts] ----- -client.transform.updateTransform({ transform_id }) ----- - +=== client.textStructure.findFieldStructure [discrete] -==== Arguments - -* *Request (object):* -** *`transform_id` (string)*: Identifier for the transform. -** *`dest` (Optional, { index, op_type, pipeline, routing, version_type })*: The destination for the transform. -** *`description` (Optional, string)*: Free text description of the transform. -** *`frequency` (Optional, string | -1 | 0)*: The interval between checks for changes in the source indices when the -transform is running continuously. Also determines the retry interval in -the event of transient failures while the transform is searching or -indexing. The minimum value is 1s and the maximum is 1h. -** *`_meta` (Optional, Record)*: Defines optional transform metadata. -** *`source` (Optional, { index, query, remote, size, slice, sort, _source, runtime_mappings })*: The source of the data for the transform. -** *`settings` (Optional, { align_checkpoints, dates_as_epoch_millis, deduce_mappings, docs_per_second, max_page_search_size, unattended })*: Defines optional transform settings. -** *`sync` (Optional, { time })*: Defines the properties transforms require to run continuously. -** *`retention_policy` (Optional, { time } | null)*: Defines a retention policy for the transform. Data that meets the defined -criteria is deleted from the destination index. -** *`defer_validation` (Optional, boolean)*: When true, deferrable validations are not run. This behavior may be -desired if the source index does not exist until after the transform is -created. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the -timeout expires, the request fails and returns an error. - +=== client.textStructure.findMessageStructure [discrete] -==== upgrade_transforms -Upgrades all transforms. -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. - -{ref}/upgrade-transforms.html[Endpoint documentation] -[source,ts] ----- -client.transform.upgradeTransforms({ ... }) ----- - +=== client.textStructure.findStructure [discrete] -==== Arguments - -* *Request (object):* -** *`dry_run` (Optional, boolean)*: When true, the request checks for updates but does not run them. -** *`timeout` (Optional, string | -1 | 0)*: Period to wait for a response. If no response is received before the timeout expires, the request fails and -returns an error. - +=== client.textStructure.testGrokPattern [discrete] -=== watcher +=== client.transform.deleteTransform [discrete] -==== ack_watch -Acknowledges a watch, manually throttling the execution of the watch's actions. - -{ref}/watcher-api-ack-watch.html[Endpoint documentation] -[source,ts] ----- -client.watcher.ackWatch({ watch_id }) ----- - +=== client.transform.getNodeStats [discrete] -==== Arguments - -* *Request (object):* -** *`watch_id` (string)*: Watch ID -** *`action_id` (Optional, string | string[])*: A list of the action ids to be acked - +=== client.transform.getTransform [discrete] -==== activate_watch -Activates a currently inactive watch. - -{ref}/watcher-api-activate-watch.html[Endpoint documentation] -[source,ts] ----- -client.watcher.activateWatch({ watch_id }) ----- - +=== client.transform.getTransformStats [discrete] -==== Arguments - -* *Request (object):* -** *`watch_id` (string)*: Watch ID - +=== client.transform.previewTransform [discrete] -==== deactivate_watch -Deactivates a currently active watch. - -{ref}/watcher-api-deactivate-watch.html[Endpoint documentation] -[source,ts] ----- -client.watcher.deactivateWatch({ watch_id }) ----- - +=== client.transform.putTransform [discrete] -==== Arguments - -* *Request (object):* -** *`watch_id` (string)*: Watch ID - +=== client.transform.resetTransform [discrete] -==== delete_watch -Removes a watch from Watcher. - -{ref}/watcher-api-delete-watch.html[Endpoint documentation] -[source,ts] ----- -client.watcher.deleteWatch({ id }) ----- - +=== client.transform.scheduleNowTransform [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Watch ID - +=== client.transform.startTransform [discrete] -==== execute_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 execute the watch without executing 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 execution. - -{ref}/watcher-api-execute-watch.html[Endpoint documentation] -[source,ts] ----- -client.watcher.executeWatch({ ... }) ----- - +=== client.transform.stopTransform [discrete] -==== Arguments - -* *Request (object):* -** *`id` (Optional, string)*: Identifier for the watch. -** *`action_modes` (Optional, Record)*: Determines how to handle the watch actions as part of the watch execution. -** *`alternative_input` (Optional, Record)*: When present, the watch uses this object as a payload instead of executing its own input. -** *`ignore_condition` (Optional, boolean)*: When set to `true`, the watch execution uses the always condition. This can also be specified as an HTTP parameter. -** *`record_execution` (Optional, boolean)*: When set to `true`, the watch record representing the watch execution result is persisted to the `.watcher-history` index for the current time. In addition, the status of the watch is updated, possibly throttling subsequent executions. This can also be specified as an HTTP parameter. -** *`simulated_actions` (Optional, { actions, all, use_all })* -** *`trigger_data` (Optional, { scheduled_time, triggered_time })*: This structure is parsed as the data of the trigger event that will be used during the watch execution -** *`watch` (Optional, { actions, condition, input, metadata, status, throttle_period, throttle_period_in_millis, transform, trigger })*: When present, this watch is used instead of the one specified in the request. This watch is not persisted to the index and record_execution cannot be set. -** *`debug` (Optional, boolean)*: Defines whether the watch runs in debug mode. - +=== client.transform.updateTransform [discrete] -==== get_settings -Retrieve settings for the watcher system index - -{ref}/watcher-api-get-settings.html[Endpoint documentation] -[source,ts] ----- -client.watcher.getSettings() ----- - - +=== client.transform.upgradeTransforms [discrete] -==== get_watch -Retrieves a watch by its ID. - -{ref}/watcher-api-get-watch.html[Endpoint documentation] -[source,ts] ----- -client.watcher.getWatch({ id }) ----- - +=== client.update [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Watch ID - +=== client.updateByQuery [discrete] -==== put_watch -Creates a new watch, or updates an existing one. - -{ref}/watcher-api-put-watch.html[Endpoint documentation] -[source,ts] ----- -client.watcher.putWatch({ id }) ----- - +=== client.updateByQueryRethrottle [discrete] -==== Arguments - -* *Request (object):* -** *`id` (string)*: Watch ID -** *`actions` (Optional, Record)* -** *`condition` (Optional, { always, array_compare, compare, never, script })* -** *`input` (Optional, { chain, http, search, simple })* -** *`metadata` (Optional, Record)* -** *`throttle_period` (Optional, string)* -** *`transform` (Optional, { chain, script, search })* -** *`trigger` (Optional, { schedule })* -** *`active` (Optional, boolean)*: Specify whether the watch is in/active by default -** *`if_primary_term` (Optional, number)*: only update the watch if the last operation that has changed the watch has the specified primary term -** *`if_seq_no` (Optional, number)*: only update the watch if the last operation that has changed the watch has the specified sequence number -** *`version` (Optional, number)*: Explicit version number for concurrency control - +=== client.watcher.ackWatch [discrete] -==== query_watches -Retrieves stored watches. - -{ref}/watcher-api-query-watches.html[Endpoint documentation] -[source,ts] ----- -client.watcher.queryWatches({ ... }) ----- - +=== client.watcher.activateWatch [discrete] -==== Arguments - -* *Request (object):* -** *`from` (Optional, number)*: The offset from the first result to fetch. Needs to be non-negative. -** *`size` (Optional, number)*: The number of hits to return. Needs to be non-negative. -** *`query` (Optional, { bool, boosting, common, combined_fields, constant_score, dis_max, distance_feature, exists, function_score, fuzzy, geo_bounding_box, geo_distance, geo_polygon, geo_shape, has_child, has_parent, ids, intervals, knn, match, match_all, match_bool_prefix, match_none, match_phrase, match_phrase_prefix, more_like_this, multi_match, nested, parent_id, percolate, pinned, prefix, query_string, range, rank_feature, regexp, rule, script, script_score, semantic, shape, simple_query_string, span_containing, span_field_masking, span_first, span_multi, span_near, span_not, span_or, span_term, span_within, sparse_vector, term, terms, terms_set, text_expansion, weighted_tokens, wildcard, wrapper, type })*: Optional, query filter watches to be returned. -** *`sort` (Optional, string | { _score, _doc, _geo_distance, _script } | string | { _score, _doc, _geo_distance, _script }[])*: Optional sort definition. -** *`search_after` (Optional, number | number | string | boolean | null | User-defined value[])*: Optional search After to do pagination using last hit’s sort values. - +=== client.watcher.deactivateWatch [discrete] -==== start -Starts Watcher if it is not already running. - -{ref}/watcher-api-start.html[Endpoint documentation] -[source,ts] ----- -client.watcher.start() ----- - - +=== client.watcher.deleteWatch [discrete] -==== stats -Retrieves the current Watcher metrics. - -{ref}/watcher-api-stats.html[Endpoint documentation] -[source,ts] ----- -client.watcher.stats({ ... }) ----- - +=== client.watcher.executeWatch [discrete] -==== Arguments - -* *Request (object):* -** *`metric` (Optional, Enum("_all" | "queued_watches" | "current_watches" | "pending_watches") | Enum("_all" | "queued_watches" | "current_watches" | "pending_watches")[])*: Defines which additional metrics are included in the response. -** *`emit_stacktraces` (Optional, boolean)*: Defines whether stack traces are generated for each watch that is running. - +=== client.watcher.getSettings [discrete] -==== stop -Stops Watcher if it is running. - -{ref}/watcher-api-stop.html[Endpoint documentation] -[source,ts] ----- -client.watcher.stop() ----- - - +=== client.watcher.getWatch [discrete] -==== update_settings -Update settings for the watcher system index - -{ref}/watcher-api-update-settings.html[Endpoint documentation] -[source,ts] ----- -client.watcher.updateSettings() ----- - - +=== client.watcher.putWatch [discrete] -=== xpack +=== client.watcher.queryWatches [discrete] -==== info -Provides general information about the installed X-Pack features. - -{ref}/info-api.html[Endpoint documentation] -[source,ts] ----- -client.xpack.info({ ... }) ----- - +=== client.watcher.start [discrete] -==== Arguments - -* *Request (object):* -** *`categories` (Optional, Enum("build" | "features" | "license")[])*: A list of the information categories to include in the response. For example, `build,license,features`. -** *`accept_enterprise` (Optional, boolean)*: If this param is used it must be set to true -** *`human` (Optional, boolean)*: Defines whether additional human-readable information is included in the response. In particular, it adds descriptions and a tag line. - +=== client.watcher.stats [discrete] -==== usage -This API provides information about which features are currently enabled and available under the current license and some usage statistics. - -{ref}/usage-api.html[Endpoint documentation] -[source,ts] ----- -client.xpack.usage({ ... }) ----- - +=== client.watcher.stop [discrete] -==== Arguments - -* *Request (object):* -** *`master_timeout` (Optional, string | -1 | 0)*: Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. - +=== client.watcher.updateSettings +[discrete] +=== client.xpack.info +[discrete] +=== client.xpack.usage