[codegen] update to latest spec

Author: l-trotta

java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchAsyncClient.java

@@ -4933,58 +4933,6 @@ public final <TDocument> CompletableFuture<SearchResponse<TDocument>> search(
 	 * labels, so that, for example, multi-polygons will have only one label.</li>
 	 * </ul>
 	 * <p>
-	 * For example, Elasticsearch may translate a vector tile search API request
-	 * with a <code>grid_agg</code> argument of <code>geotile</code> and an
-	 * <code>exact_bounds</code> argument of <code>true</code> into the following
-	 * search
-	 * 
-	 * <pre>
-	 * <code>GET my-index/_search
-	 * {
-	 *   &quot;size&quot;: 10000,
-	 *   &quot;query&quot;: {
-	 *     &quot;geo_bounding_box&quot;: {
-	 *       &quot;my-geo-field&quot;: {
-	 *         &quot;top_left&quot;: {
-	 *           &quot;lat&quot;: -40.979898069620134,
-	 *           &quot;lon&quot;: -45
-	 *         },
-	 *         &quot;bottom_right&quot;: {
-	 *           &quot;lat&quot;: -66.51326044311186,
-	 *           &quot;lon&quot;: 0
-	 *         }
-	 *       }
-	 *     }
-	 *   },
-	 *   &quot;aggregations&quot;: {
-	 *     &quot;grid&quot;: {
-	 *       &quot;geotile_grid&quot;: {
-	 *         &quot;field&quot;: &quot;my-geo-field&quot;,
-	 *         &quot;precision&quot;: 11,
-	 *         &quot;size&quot;: 65536,
-	 *         &quot;bounds&quot;: {
-	 *           &quot;top_left&quot;: {
-	 *             &quot;lat&quot;: -40.979898069620134,
-	 *             &quot;lon&quot;: -45
-	 *           },
-	 *           &quot;bottom_right&quot;: {
-	 *             &quot;lat&quot;: -66.51326044311186,
-	 *             &quot;lon&quot;: 0
-	 *           }
-	 *         }
-	 *       }
-	 *     },
-	 *     &quot;bounds&quot;: {
-	 *       &quot;geo_bounds&quot;: {
-	 *         &quot;field&quot;: &quot;my-geo-field&quot;,
-	 *         &quot;wrap_longitude&quot;: false
-	 *       }
-	 *     }
-	 *   }
-	 * }
-	 * </code>
-	 * </pre>
-	 * <p>
 	 * The API returns results as a binary Mapbox vector tile. Mapbox vector tiles
 	 * are encoded as Google Protobufs (PBF). By default, the tile contains three
 	 * layers:
@@ -5264,6 +5212,11 @@ public final <TDocument> CompletableFuture<SearchResponse<TDocument>> search(
 	 * each resolution with the average density of tile bins at each zoom level.
 	 * Elasticsearch uses the H3 resolution that is closest to the corresponding
 	 * geotile density.
+	 * <p>
+	 * Learn how to use the vector tile search API with practical examples in the
+	 * <a href=
+	 * "https://www.elastic.co/docs/reference/elasticsearch/rest-apis/vector-tile-search">Vector
+	 * tile search examples</a> guide.
 	 * 
 	 * @see <a href=
 	 *      "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search-mvt">Documentation
@@ -5304,58 +5257,6 @@ public CompletableFuture<BinaryResponse> searchMvt(SearchMvtRequest request) {
 	 * labels, so that, for example, multi-polygons will have only one label.</li>
 	 * </ul>
 	 * <p>
-	 * For example, Elasticsearch may translate a vector tile search API request
-	 * with a <code>grid_agg</code> argument of <code>geotile</code> and an
-	 * <code>exact_bounds</code> argument of <code>true</code> into the following
-	 * search
-	 * 
-	 * <pre>
-	 * <code>GET my-index/_search
-	 * {
-	 *   &quot;size&quot;: 10000,
-	 *   &quot;query&quot;: {
-	 *     &quot;geo_bounding_box&quot;: {
-	 *       &quot;my-geo-field&quot;: {
-	 *         &quot;top_left&quot;: {
-	 *           &quot;lat&quot;: -40.979898069620134,
-	 *           &quot;lon&quot;: -45
-	 *         },
-	 *         &quot;bottom_right&quot;: {
-	 *           &quot;lat&quot;: -66.51326044311186,
-	 *           &quot;lon&quot;: 0
-	 *         }
-	 *       }
-	 *     }
-	 *   },
-	 *   &quot;aggregations&quot;: {
-	 *     &quot;grid&quot;: {
-	 *       &quot;geotile_grid&quot;: {
-	 *         &quot;field&quot;: &quot;my-geo-field&quot;,
-	 *         &quot;precision&quot;: 11,
-	 *         &quot;size&quot;: 65536,
-	 *         &quot;bounds&quot;: {
-	 *           &quot;top_left&quot;: {
-	 *             &quot;lat&quot;: -40.979898069620134,
-	 *             &quot;lon&quot;: -45
-	 *           },
-	 *           &quot;bottom_right&quot;: {
-	 *             &quot;lat&quot;: -66.51326044311186,
-	 *             &quot;lon&quot;: 0
-	 *           }
-	 *         }
-	 *       }
-	 *     },
-	 *     &quot;bounds&quot;: {
-	 *       &quot;geo_bounds&quot;: {
-	 *         &quot;field&quot;: &quot;my-geo-field&quot;,
-	 *         &quot;wrap_longitude&quot;: false
-	 *       }
-	 *     }
-	 *   }
-	 * }
-	 * </code>
-	 * </pre>
-	 * <p>
 	 * The API returns results as a binary Mapbox vector tile. Mapbox vector tiles
 	 * are encoded as Google Protobufs (PBF). By default, the tile contains three
 	 * layers:
@@ -5635,6 +5536,11 @@ public CompletableFuture<BinaryResponse> searchMvt(SearchMvtRequest request) {
 	 * each resolution with the average density of tile bins at each zoom level.
 	 * Elasticsearch uses the H3 resolution that is closest to the corresponding
 	 * geotile density.
+	 * <p>
+	 * Learn how to use the vector tile search API with practical examples in the
+	 * <a href=
+	 * "https://www.elastic.co/docs/reference/elasticsearch/rest-apis/vector-tile-search">Vector
+	 * tile search examples</a> guide.
 	 * 
 	 * @param fn
 	 *            a function that initializes a builder to create the
@@ -6039,7 +5945,8 @@ public final <TDocument> CompletableFuture<TermvectorsResponse> termvectors(
 	 * to <code>_source</code>, you can access the following variables through the
 	 * <code>ctx</code> map: <code>_index</code>, <code>_type</code>,
 	 * <code>_id</code>, <code>_version</code>, <code>_routing</code>, and
-	 * <code>_now</code> (the current timestamp).
+	 * <code>_now</code> (the current timestamp). For usage examples such as partial
+	 * updates, upserts, and scripted updates, see the External documentation.
 	 * 
 	 * @see <a href=
 	 *      "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update">Documentation
@@ -6083,7 +5990,8 @@ public <TDocument, TPartialDocument> CompletableFuture<UpdateResponse<TDocument>
 	 * to <code>_source</code>, you can access the following variables through the
 	 * <code>ctx</code> map: <code>_index</code>, <code>_type</code>,
 	 * <code>_id</code>, <code>_version</code>, <code>_routing</code>, and
-	 * <code>_now</code> (the current timestamp).
+	 * <code>_now</code> (the current timestamp). For usage examples such as partial
+	 * updates, upserts, and scripted updates, see the External documentation.
 	 * 
 	 * @param fn
 	 *            a function that initializes a builder to create the
@@ -6126,7 +6034,8 @@ public final <TDocument, TPartialDocument> CompletableFuture<UpdateResponse<TDoc
 	 * to <code>_source</code>, you can access the following variables through the
 	 * <code>ctx</code> map: <code>_index</code>, <code>_type</code>,
 	 * <code>_id</code>, <code>_version</code>, <code>_routing</code>, and
-	 * <code>_now</code> (the current timestamp).
+	 * <code>_now</code> (the current timestamp). For usage examples such as partial
+	 * updates, upserts, and scripted updates, see the External documentation.
 	 * 
 	 * @see <a href=
 	 *      "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update">Documentation
@@ -6170,7 +6079,8 @@ public <TDocument, TPartialDocument> CompletableFuture<UpdateResponse<TDocument>
 	 * to <code>_source</code>, you can access the following variables through the
 	 * <code>ctx</code> map: <code>_index</code>, <code>_type</code>,
 	 * <code>_id</code>, <code>_version</code>, <code>_routing</code>, and
-	 * <code>_now</code> (the current timestamp).
+	 * <code>_now</code> (the current timestamp). For usage examples such as partial
+	 * updates, upserts, and scripted updates, see the External documentation.
 	 * 
 	 * @param fn
 	 *            a function that initializes a builder to create the
@@ -6228,6 +6138,34 @@ public final <TDocument, TPartialDocument> CompletableFuture<UpdateResponse<TDoc
 	 * are shown in the response. Any update requests that completed successfully
 	 * still stick, they are not rolled back.
 	 * <p>
+	 * <strong>Refreshing shards</strong>
+	 * <p>
+	 * Specifying the <code>refresh</code> parameter refreshes all shards once the
+	 * request completes. This is different to the update API's <code>refresh</code>
+	 * parameter, which causes only the shard that received the request to be
+	 * refreshed. Unlike the update API, it does not support <code>wait_for</code>.
+	 * <p>
+	 * <strong>Running update by query asynchronously</strong>
+	 * <p>
+	 * If the request contains <code>wait_for_completion=false</code>, Elasticsearch
+	 * performs some preflight checks, launches the request, and returns a <a href=
+	 * "https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks">task</a>
+	 * you can use to cancel or get the status of the task. Elasticsearch creates a
+	 * record of this task as a document at <code>.tasks/task/${taskId}</code>.
+	 * <p>
+	 * <strong>Waiting for active shards</strong>
+	 * <p>
+	 * <code>wait_for_active_shards</code> controls how many copies of a shard must
+	 * be active before proceeding with the request. See <a href=
+	 * "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-create#operation-create-wait_for_active_shards"><code>wait_for_active_shards</code></a>
+	 * for details. <code>timeout</code> controls how long each write request waits
+	 * for unavailable shards to become available. Both work exactly the way they
+	 * work in the <a href=
+	 * "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk">Bulk
+	 * API</a>. Update by query uses scrolled searches, so you can also specify the
+	 * <code>scroll</code> parameter to control how long it keeps the search context
+	 * alive, for example <code>?scroll=10m</code>. The default is 5 minutes.
+	 * <p>
 	 * <strong>Throttling update requests</strong>
 	 * <p>
 	 * To control the rate at which update by query issues batches of update
@@ -6305,27 +6243,9 @@ public final <TDocument, TPartialDocument> CompletableFuture<UpdateResponse<TDoc
 	 * </ul>
 	 * <p>
 	 * Whether query or update performance dominates the runtime depends on the
-	 * documents being reindexed and cluster resources.
-	 * <p>
-	 * <strong>Update the document source</strong>
-	 * <p>
-	 * Update by query supports scripts to update the document source. As with the
-	 * update API, you can set <code>ctx.op</code> to change the operation that is
-	 * performed.
-	 * <p>
-	 * Set <code>ctx.op = &quot;noop&quot;</code> if your script decides that it
-	 * doesn't have to make any changes. The update by query operation skips
-	 * updating the document and increments the <code>noop</code> counter.
-	 * <p>
-	 * Set <code>ctx.op = &quot;delete&quot;</code> if your script decides that the
-	 * document should be deleted. The update by query operation deletes the
-	 * document and increments the <code>deleted</code> counter.
-	 * <p>
-	 * Update by query supports only <code>index</code>, <code>noop</code>, and
-	 * <code>delete</code>. Setting <code>ctx.op</code> to anything else is an
-	 * error. Setting any other field in <code>ctx</code> is an error. This API
-	 * enables you to only modify the source of matching documents; you cannot move
-	 * them.
+	 * documents being reindexed and cluster resources. Refer to the linked
+	 * documentation for examples of how to update documents using the
+	 * <code>_update_by_query</code> API:
 	 * 
 	 * @see <a href=
 	 *      "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-update-by-query">Documentation
@@ -6379,6 +6299,34 @@ public CompletableFuture<UpdateByQueryResponse> updateByQuery(UpdateByQueryReque
 	 * are shown in the response. Any update requests that completed successfully
 	 * still stick, they are not rolled back.
 	 * <p>
+	 * <strong>Refreshing shards</strong>
+	 * <p>
+	 * Specifying the <code>refresh</code> parameter refreshes all shards once the
+	 * request completes. This is different to the update API's <code>refresh</code>
+	 * parameter, which causes only the shard that received the request to be
+	 * refreshed. Unlike the update API, it does not support <code>wait_for</code>.
+	 * <p>
+	 * <strong>Running update by query asynchronously</strong>
+	 * <p>
+	 * If the request contains <code>wait_for_completion=false</code>, Elasticsearch
+	 * performs some preflight checks, launches the request, and returns a <a href=
+	 * "https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks">task</a>
+	 * you can use to cancel or get the status of the task. Elasticsearch creates a
+	 * record of this task as a document at <code>.tasks/task/${taskId}</code>.
+	 * <p>
+	 * <strong>Waiting for active shards</strong>
+	 * <p>
+	 * <code>wait_for_active_shards</code> controls how many copies of a shard must
+	 * be active before proceeding with the request. See <a href=
+	 * "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-create#operation-create-wait_for_active_shards"><code>wait_for_active_shards</code></a>
+	 * for details. <code>timeout</code> controls how long each write request waits
+	 * for unavailable shards to become available. Both work exactly the way they
+	 * work in the <a href=
+	 * "https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-bulk">Bulk
+	 * API</a>. Update by query uses scrolled searches, so you can also specify the
+	 * <code>scroll</code> parameter to control how long it keeps the search context
+	 * alive, for example <code>?scroll=10m</code>. The default is 5 minutes.
+	 * <p>
 	 * <strong>Throttling update requests</strong>
 	 * <p>
 	 * To control the rate at which update by query issues batches of update
@@ -6456,27 +6404,9 @@ public CompletableFuture<UpdateByQueryResponse> updateByQuery(UpdateByQueryReque
 	 * </ul>
 	 * <p>
 	 * Whether query or update performance dominates the runtime depends on the
-	 * documents being reindexed and cluster resources.
-	 * <p>
-	 * <strong>Update the document source</strong>
-	 * <p>
-	 * Update by query supports scripts to update the document source. As with the
-	 * update API, you can set <code>ctx.op</code> to change the operation that is
-	 * performed.
-	 * <p>
-	 * Set <code>ctx.op = &quot;noop&quot;</code> if your script decides that it
-	 * doesn't have to make any changes. The update by query operation skips
-	 * updating the document and increments the <code>noop</code> counter.
-	 * <p>
-	 * Set <code>ctx.op = &quot;delete&quot;</code> if your script decides that the
-	 * document should be deleted. The update by query operation deletes the
-	 * document and increments the <code>deleted</code> counter.
-	 * <p>
-	 * Update by query supports only <code>index</code>, <code>noop</code>, and
-	 * <code>delete</code>. Setting <code>ctx.op</code> to anything else is an
-	 * error. Setting any other field in <code>ctx</code> is an error. This API
-	 * enables you to only modify the source of matching documents; you cannot move
-	 * them.
+	 * documents being reindexed and cluster resources. Refer to the linked
+	 * documentation for examples of how to update documents using the
+	 * <code>_update_by_query</code> API:
 	 * 
 	 * @param fn
 	 *            a function that initializes a builder to create the