You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/changelog/106068.yaml
+16
Original file line number
Diff line number
Diff line change
@@ -3,3 +3,19 @@ summary: Add `modelId` and `modelText` to `KnnVectorQueryBuilder`
3
3
area: Search
4
4
type: enhancement
5
5
issues: []
6
+
highlight:
7
+
title: Query phase KNN now supports query_vector_builder
8
+
body: |-
9
+
It is now possible to pass `model_text` and `model_id` within a `knn` query
10
+
in the [query DSL](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-knn-query.html) to convert a text query into a dense vector and run the
11
+
nearest neighbor query on it, instead of requiring the dense vector to be
12
+
directly passed (within the `query_vector` parameter). Similar to the
13
+
[top-level knn query](https://www.elastic.co/guide/en/elasticsearch/reference/current/knn-search.html) (executed in the DFS phase), it is possible to supply
14
+
a `query_vector_builder` object containing a `text_embedding` object with
15
+
`model_text` (the text query to be converted into a dense vector) and
16
+
`model_id` (the identifier of a deployed model responsible for transforming
17
+
the text query into a dense vector). Note that an embedding model with the
18
+
referenced `model_id` needs to be [deployed on a ML node](https://www.elastic.co/guide/en/machine-learning/current/ml-nlp-deploy-models.html).
0 commit comments