Adding bbq index types to specification (#4181)

Author: benwtrent

output/openapi/elasticsearch-openapi.json

@@ -1,6 +1,6 @@
 {
   "dependencies": {
-    "@redocly/cli": "^1.34.0",
+    "@redocly/cli": "^1.34.1",
     "@stoplight/spectral-cli": "^6.14.2"
   }
 }

output/openapi/elasticsearch-serverless-openapi.json

@@ -144,14 +144,14 @@ export class DenseVectorIndexOptions {
   /**
    * The number of candidates to track while assembling the list of nearest neighbors for each new node.
    *
-   * Only applicable to `hnsw`, `int8_hnsw`, and `int4_hnsw` index types.
+   * Only applicable to `hnsw`, `int8_hnsw`, `bbq_hnsw`, and `int4_hnsw` index types.
    * @server_default 100
    */
   ef_construction?: integer
   /**
    * The number of neighbors each node will be connected to in the HNSW graph.
    *
-   * Only applicable to `hnsw`, `int8_hnsw`, and `int4_hnsw` index types.
+   * Only applicable to `hnsw`, `int8_hnsw`, `bbq_hnsw`, and `int4_hnsw` index types.
    * @server_default 16
    */
   m?: integer
@@ -162,6 +162,18 @@ export class DenseVectorIndexOptions {
 }
 
 export enum DenseVectorIndexOptionsType {
+  /**
+   * This utilizes a brute-force search algorithm in addition to automatically quantizing to binary vectors.
+   * Only supports `element_type` of `float`.
+   */
+  bbq_flat,
+  /**
+   * This utilizes the HNSW algorithm in addition to automatic binary quantization for scalable approximate kNN
+   * search with `element_type` of `float`.
+   *
+   * This can reduce the memory footprint by nearly 32x at the cost of some accuracy.
+   */
+  bbq_hnsw,
   /**
    * This utilizes a brute-force search algorithm for exact kNN search. This supports all `element_type` values.
    */