Merge branch 'main' into add-descriptions-to-schemas

Author: miguelgrinberg

output/openapi/elasticsearch-openapi.json

@@ -14,6 +14,7 @@ analysis-tokenizers,https://www.elastic.co/docs/reference/text-analysis/tokenize
 analysis,https://www.elastic.co/docs/manage-data/data-store/text-analysis
 analyze-repository,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-repository-analyze
 analyzer-anatomy,https://www.elastic.co/docs/manage-data/data-store/text-analysis/anatomy-of-an-analyzer
+analyzer-update-existing,https://www.elastic.co/docs/manage-data/data-store/text-analysis/specify-an-analyzer#update-analyzers-on-existing-indices
 anthropic-messages,https://docs.anthropic.com/en/api/messages
 anthropic-models,https://docs.anthropic.com/en/docs/about-claude/models/all-models#model-names
 api-date-math-index-names,https://www.elastic.co/docs/reference/elasticsearch/rest-apis/api-conventions#api-date-math-index-names
@@ -320,6 +321,7 @@ indices-put-data-stream-settings,https://www.elastic.co/docs/api/doc/elasticsear
 indices-put-mapping,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-mapping
 indices-recovery,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-recovery
 indices-refresh,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-refresh
+indices-refresh-disable,https://www.elastic.co/docs/deploy-manage/production-guidance/optimize-performance/indexing-speed#disable-refresh-interval
 indices-reload-analyzers,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-reload-search-analyzers
 indices-resolve-cluster-api,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-cluster
 indices-resolve-index-api,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index

output/openapi/elasticsearch-serverless-openapi.json

@@ -140,10 +140,14 @@ import { OperationContainer, UpdateAction } from './types'
  * Imagine a `_bulk?refresh=wait_for` request with three documents in it that happen to be routed to different shards in an index with five shards.
  * The request will only wait for those three shards to refresh.
  * The other two shards that make up the index do not participate in the `_bulk` request at all.
+ *
+ * You might want to disable the refresh interval temporarily to improve indexing throughput for large bulk requests.
+ * Refer to the linked documentation for step-by-step instructions using the index settings API.
  * @rest_spec_name bulk
  * @availability stack stability=stable
  * @availability serverless stability=stable visibility=public
  * @doc_id docs-bulk
+ * @ext_doc_id indices-refresh-disable
  * @doc_tag document
  *
  */

output/schema/schema.json

@@ -125,6 +125,8 @@ export class IndexSettings
   max_refresh_listeners?: integer
   /**
    * Settings to define analyzers, tokenizers, token filters and character filters.
+   * Refer to the linked documentation for step-by-step examples of updating analyzers on existing indices.
+   * @ext_doc_id analyzer-update-existing
    */
   analyze?: SettingsAnalyze
   highlight?: SettingsHighlight

specification/_doc_ids/table.csv

@@ -31,7 +31,9 @@ import { IndexSettings } from '@indices/_types/IndexSettings'
  * The list of per-index settings that can be updated dynamically on live indices can be found in index settings documentation.
  * To preserve existing settings from being updated, set the `preserve_existing` parameter to `true`.
  *
- *  There are multiple valid ways to represent index settings in the request body. You can specify only the setting, for example:
+ * For performance optimization during bulk indexing, you can disable the refresh interval.
+ * Refer to [disable refresh interval](https://www.elastic.co/docs/deploy-manage/production-guidance/optimize-performance/indexing-speed#disable-refresh-interval) for an example.
+ * There are multiple valid ways to represent index settings in the request body. You can specify only the setting, for example:
  *
  * ```
  * {
@@ -75,6 +77,7 @@ import { IndexSettings } from '@indices/_types/IndexSettings'
  * This affects searches and any new data added to the stream after the rollover.
  * However, it does not affect the data stream's backing indices or their existing data.
  * To change the analyzer for existing backing indices, you must create a new data stream and reindex your data into it.
+ * Refer to [updating analyzers on existing indices](https://www.elastic.co/docs/manage-data/data-store/text-analysis/specify-an-analyzer#update-analyzers-on-existing-indices) for step-by-step examples.
  * @rest_spec_name indices.put_settings
  * @availability stack stability=stable
  * @availability serverless stability=stable visibility=public