Generate heading IDs

Author: JoshMock

docs/reference-async_search-delete.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.asyncSearch.delete]]
 === 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.

docs/reference-async_search-get.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.asyncSearch.get]]
 === 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.
@@ -65,7 +66,7 @@ interface AsyncSearchGetRequest extends <<RequestBase>> {
 ++++
 <pre>
 ++++
-type AsyncSearchGetResponse<TDocument = unknown, TAggregations = Record<<<AggregateName>>, AggregationsAggregate>> = AsyncSearchAsyncSearchDocumentResponseBase<TDocument, TAggregations>
+type AsyncSearchGetResponse<TDocument = unknown, TAggregations = Record<<<AggregateName>>, <<AggregationsAggregate>>>> = AsyncSearchAsyncSearchDocumentResponseBase<TDocument, TAggregations>
 
 [pass]
 ++++

docs/reference-async_search-status.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.asyncSearch.status]]
 === 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.

docs/reference-async_search-submit.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.asyncSearch.submit]]
 === 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.
@@ -58,7 +59,7 @@ interface AsyncSearchSubmitRequest extends <<RequestBase>> {
   analyze_wildcard?: boolean
   batched_reduce_size?: <<_long, long>>
   ccs_minimize_roundtrips?: boolean
-  default_operator?: QueryDslOperator
+  default_operator?: <<QueryDslOperator>>
   df?: string
   expand_wildcards?: <<ExpandWildcards>>
   ignore_throttled?: boolean
@@ -81,30 +82,30 @@ interface AsyncSearchSubmitRequest extends <<RequestBase>> {
   _source_excludes?: <<Fields>>
   _source_includes?: <<Fields>>
   q?: string
-  aggregations?: Record<string, AggregationsAggregationContainer>
+  aggregations?: Record<string, <<AggregationsAggregationContainer>>>
   pass:[/**] @alias aggregations */
-  aggs?: Record<string, AggregationsAggregationContainer>
+  aggs?: Record<string, <<AggregationsAggregationContainer>>>
   collapse?: SearchFieldCollapse
   explain?: boolean
   ext?: Record<string, any>
   from?: <<_integer, integer>>
   highlight?: SearchHighlight
   track_total_hits?: SearchTrackHits
   indices_boost?: Record<<<IndexName>>, <<_double, double>>>[]
-  docvalue_fields?: (QueryDslFieldAndFormat | <<Field>>)[]
+  docvalue_fields?: (<<QueryDslFieldAndFormat>> | <<Field>>)[]
   knn?: <<KnnSearch>> | <<KnnSearch>>[]
   min_score?: <<_double, double>>
-  post_filter?: QueryDslQueryContainer
+  post_filter?: <<QueryDslQueryContainer>>
   profile?: boolean
-  query?: QueryDslQueryContainer
+  query?: <<QueryDslQueryContainer>>
   rescore?: SearchRescore | SearchRescore[]
   script_fields?: Record<string, <<ScriptField>>>
   search_after?: <<SortResults>>
   size?: <<_integer, integer>>
   slice?: <<SlicedScroll>>
   sort?: <<Sort>>
   _source?: SearchSourceConfig
-  fields?: (QueryDslFieldAndFormat | <<Field>>)[]
+  fields?: (<<QueryDslFieldAndFormat>> | <<Field>>)[]
   suggest?: SearchSuggester
   terminate_after?: <<_long, long>>
   timeout?: string
@@ -113,7 +114,7 @@ interface AsyncSearchSubmitRequest extends <<RequestBase>> {
   seq_no_primary_term?: boolean
   stored_fields?: <<Fields>>
   pit?: SearchPointInTimeReference
-  runtime_mappings?: MappingRuntimeFields
+  runtime_mappings?: <<MappingRuntimeFields>>
   stats?: string[]
 }
 
@@ -128,7 +129,7 @@ interface AsyncSearchSubmitRequest extends <<RequestBase>> {
 ++++
 <pre>
 ++++
-type AsyncSearchSubmitResponse<TDocument = unknown, TAggregations = Record<<<AggregateName>>, AggregationsAggregate>> = AsyncSearchAsyncSearchDocumentResponseBase<TDocument, TAggregations>
+type AsyncSearchSubmitResponse<TDocument = unknown, TAggregations = Record<<<AggregateName>>, <<AggregationsAggregate>>>> = AsyncSearchAsyncSearchDocumentResponseBase<TDocument, TAggregations>
 
 [pass]
 ++++

docs/reference-autoscaling-delete_autoscaling_policy.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.autoscaling.deleteAutoscalingPolicy]]
 === 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.

docs/reference-autoscaling-get_autoscaling_capacity.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.autoscaling.getAutoscalingCapacity]]
 === 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.

docs/reference-autoscaling-get_autoscaling_policy.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.autoscaling.getAutoscalingPolicy]]
 === 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.

docs/reference-autoscaling-put_autoscaling_policy.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.autoscaling.putAutoscalingPolicy]]
 === 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.

docs/reference-bulk.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.bulk]]
 === 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.

docs/reference-cat-aliases.asciidoc

@@ -26,6 +26,7 @@
 ////////
 
 [discrete]
+[[client.cat.aliases]]
 === 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.