mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
a46e532cda
It makes sense to allow more than one KNN search clause per individual search request. It may be that different documents have separate vector spaces or that a single doc is index with more than one vector space. In both of these scenarios, users may want to retrieve a resulting set that takes into account all their indexed vector spaces. A prime example here would be searching a semantic text embedding along with searching an image embedding. closes https://github.com/elastic/elasticsearch/issues/91187 |
||
|---|---|---|
| .. | ||
| search-your-data | ||
| suggesters | ||
| async-search.asciidoc | ||
| clear-scroll-api.asciidoc | ||
| count.asciidoc | ||
| explain.asciidoc | ||
| field-caps.asciidoc | ||
| knn-search.asciidoc | ||
| multi-search-template-api.asciidoc | ||
| multi-search.asciidoc | ||
| point-in-time-api.asciidoc | ||
| profile.asciidoc | ||
| rank-eval.asciidoc | ||
| render-search-template-api.asciidoc | ||
| scroll-api.asciidoc | ||
| search-shards.asciidoc | ||
| search-template-api.asciidoc | ||
| search-vector-tile-api.asciidoc | ||
| search.asciidoc | ||
| semantic-search.asciidoc | ||
| suggesters.asciidoc | ||
| terms-enum.asciidoc | ||
| validate.asciidoc | ||