Merge remote-tracking branch 'origin/main' into feature/hugging-face-chat-completion-integration

# Conflicts:
#	output/schema/schema-serverless.json
#	output/schema/schema.json

Author: Jan-Kazlouski-elastic

docs/modeling-guide.md

@@ -671,6 +671,9 @@ class Request {
 }
 ```
 
+You can see the existing tag values in [elasticsearch-shared-overlays.yaml](https://github.com/elastic/elasticsearch-specification/blob/main/docs/overlays/elasticsearch-shared-overlays.yaml).
+If you add a new tag value in your specification, you must also add it to this file.
+
 NOTE: In the OpenAPI specification, operations can have multiple tags. However, we currently support only a single tag.
 
 

output/openapi/elasticsearch-openapi.json

@@ -25,6 +25,11 @@
       ]
     },
     "params": {
+      "dry_run": {
+        "type": "boolean",
+        "description": "Perform a dry run but do not actually change any settings",
+        "default": false
+      },
       "timeout": {
         "type": "time",
         "description": "Specify timeout for acknowledging the cluster state update"

output/openapi/elasticsearch-serverless-openapi.json

@@ -585,6 +585,8 @@ export class CohereServiceSettings {
   api_key: string
   /**
    * For a `text_embedding` task, the types of embeddings you want to get back.
+   * Use `binary` for binary embeddings, which are encoded as bytes with signed int8 precision.
+   * Use `bit` for binary embeddings, which are encoded as bytes with signed int8 precision (this is a synonym of `binary`).
    * Use `byte` for signed int8 embeddings (this is a synonym of `int8`).
    * Use `float` for the default float embeddings.
    * Use `int8` for signed int8 embeddings.
@@ -625,6 +627,8 @@ export enum CohereServiceType {
 }
 
 export enum CohereEmbeddingType {
+  binary,
+  bit,
   byte,
   float,
   int8

output/schema/schema-serverless.json

@@ -24,23 +24,31 @@ import { Duration } from '@_types/Time'
 
 /**
  * Analyze a snapshot repository.
- * Analyze the performance characteristics and any incorrect behaviour found in a repository.
  *
- * The response exposes implementation details of the analysis which may change from version to version.
- * The response body format is therefore not considered stable and may be different in newer versions.
+ * Performs operations on a snapshot repository in order to check for incorrect behaviour.
  *
  * There are a large number of third-party storage systems available, not all of which are suitable for use as a snapshot repository by Elasticsearch.
- * Some storage systems behave incorrectly, or perform poorly, especially when accessed concurrently by multiple clients as the nodes of an Elasticsearch cluster do. This API performs a collection of read and write operations on your repository which are designed to detect incorrect behaviour and to measure the performance characteristics of your storage system.
+ * Some storage systems behave incorrectly, or perform poorly, especially when accessed concurrently by multiple clients as the nodes of an Elasticsearch cluster do.
+ * This API performs a collection of read and write operations on your repository which are designed to detect incorrect behaviour and to measure the performance characteristics of your storage system.
  *
  * The default values for the parameters are deliberately low to reduce the impact of running an analysis inadvertently and to provide a sensible starting point for your investigations.
  * Run your first analysis with the default parameter values to check for simple problems.
- * If successful, run a sequence of increasingly large analyses until you encounter a failure or you reach a `blob_count` of at least `2000`, a `max_blob_size` of at least `2gb`, a `max_total_data_size` of at least `1tb`, and a `register_operation_count` of at least `100`.
+ * Some repositories may behave correctly when lightly loaded but incorrectly under production-like workloads.
+ * If the first analysis is successful, run a sequence of increasingly large analyses until you encounter a failure or you reach a `blob_count` of at least `2000`, a `max_blob_size` of at least `2gb`, a `max_total_data_size` of at least `1tb`, and a `register_operation_count` of at least `100`.
  * Always specify a generous timeout, possibly `1h` or longer, to allow time for each analysis to run to completion.
+ * Some repositories may behave correctly when accessed by a small number of Elasticsearch nodes but incorrectly when accessed concurrently by a production-scale cluster.
  * Perform the analyses using a multi-node cluster of a similar size to your production cluster so that it can detect any problems that only arise when the repository is accessed by many nodes at once.
  *
  * If the analysis fails, Elasticsearch detected that your repository behaved unexpectedly.
  * This usually means you are using a third-party storage system with an incorrect or incompatible implementation of the API it claims to support.
  * If so, this storage system is not suitable for use as a snapshot repository.
+ * Repository analysis triggers conditions that occur only rarely when taking snapshots in a production system.
+ * Snapshotting to unsuitable storage may appear to work correctly most of the time despite repository analysis failures.
+ * However your snapshot data is at risk if you store it in a snapshot repository that does not reliably pass repository analysis.
+ * You can demonstrate that the analysis failure is due to an incompatible storage implementation by verifying that Elasticsearch does not detect the same problem when analysing the reference implementation of the storage protocol you are using.
+ * For instance, if you are using storage that offers an API which the supplier claims to be compatible with AWS S3, verify that repositories in AWS S3 do not fail repository analysis.
+ * This allows you to demonstrate to your storage supplier that a repository analysis failure must only be caused by an incompatibility with AWS S3 and cannot be attributed to a problem in Elasticsearch.
+ * Please do not report Elasticsearch issues involving third-party storage systems unless you can demonstrate that the same issue exists when analysing a repository that uses the reference implementation of the same storage protocol.
  * You will need to work with the supplier of your storage system to address the incompatibilities that Elasticsearch detects.
  *
  * If the analysis is successful, the API returns details of the testing process, optionally including how long each operation took.
@@ -72,7 +80,9 @@ import { Duration } from '@_types/Time'
  * You must ensure this load does not affect other users of these systems.
  * Analyses respect the repository settings `max_snapshot_bytes_per_sec` and `max_restore_bytes_per_sec` if available and the cluster setting `indices.recovery.max_bytes_per_sec` which you can use to limit the bandwidth they consume.
  *
- * NOTE: This API is intended for exploratory use by humans. You should expect the request parameters and the response format to vary in future versions.
+ * NOTE: This API is intended for exploratory use by humans.
+ * You should expect the request parameters and the response format to vary in future versions.
+ * The response exposes immplementation details of the analysis which may change from version to version.
  *
  * NOTE: Different versions of Elasticsearch may perform different checks for repository compatibility, with newer versions typically being stricter than older ones.
  * A storage system that passes repository analysis with one version of Elasticsearch may fail with a different version.
@@ -83,7 +93,8 @@ import { Duration } from '@_types/Time'
  *
  * *Implementation details*
  *
- * NOTE: This section of documentation describes how the repository analysis API works in this version of Elasticsearch, but you should expect the implementation to vary between versions. The request parameters and response format depend on details of the implementation so may also be different in newer versions.
+ * NOTE: This section of documentation describes how the repository analysis API works in this version of Elasticsearch, but you should expect the implementation to vary between versions.
+ * The request parameters and response format depend on details of the implementation so may also be different in newer versions.
  *
  * The analysis comprises a number of blob-level tasks, as set by the `blob_count` parameter and a number of compare-and-exchange operations on linearizable registers, as set by the `register_operation_count` parameter.
  * These tasks are distributed over the data and master-eligible nodes in the cluster for execution.