mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-01 08:58:31 +02:00
Mention inference on points and Vectors concepts pages
This commit is contained in:
@@ -89,6 +89,8 @@ or record-oriented equivalent:
|
||||
|
||||
{{< code-snippet path="/documentation/headless/snippets/insert-points/list-of-points-simple/" >}}
|
||||
|
||||
### Python client optimizations
|
||||
|
||||
The Python client has additional features for loading points, which include:
|
||||
|
||||
- Parallelization
|
||||
@@ -152,6 +154,8 @@ client.upload_points(
|
||||
)
|
||||
```
|
||||
|
||||
### Idempotence
|
||||
|
||||
All APIs in Qdrant, including point loading, are idempotent.
|
||||
It means that executing the same method several times in a row is equivalent to a single execution.
|
||||
|
||||
@@ -160,6 +164,8 @@ In this case, it means that points with the same id will be overwritten when re-
|
||||
Idempotence property is useful if you use, for example, a message queue that doesn't provide an exactly-ones guarantee.
|
||||
Even with such a system, Qdrant ensures data consistency.
|
||||
|
||||
### Named vectors
|
||||
|
||||
[_Available as of v0.10.0_](#create-vector-name)
|
||||
|
||||
If the collection was created with multiple vectors, each vector data can be provided using the vector's name:
|
||||
@@ -177,6 +183,8 @@ then it is inserted with just the specified vectors. In other words, the entire
|
||||
point is replaced, and any unspecified vectors are set to null. To keep existing
|
||||
vectors unchanged and only update specified vectors, see [update vectors](#update-vectors).
|
||||
|
||||
### Sparse vectors
|
||||
|
||||
_Available as of v1.7.0_
|
||||
|
||||
Points can contain dense and sparse vectors.
|
||||
@@ -217,6 +225,16 @@ Sparse vectors must be named and can be uploaded in the same way as dense vector
|
||||
|
||||
{{< code-snippet path="/documentation/headless/snippets/insert-points/sparse-vectors/" >}}
|
||||
|
||||
### Inference
|
||||
|
||||
Instead of providing vectors explicitly, Qdrant can also generate vectors using a process called [inference](/documentation/inference/). Inference is the process of creating vector embeddings from text, images, or other data types using a machine learning model.
|
||||
|
||||
You can use inference in the API wherever you can use regular vectors. For example, while upserting points, you can provide the text or image and the embedding model:
|
||||
|
||||
{{< code-snippet path="/documentation/headless/snippets/inference/ingest/" >}}
|
||||
|
||||
Qdrant uses the model to generate the embeddings and store the point with the resulting vector.
|
||||
|
||||
## Modify points
|
||||
|
||||
To change a point, you can modify its vectors or its payload. There are several
|
||||
|
||||
@@ -166,6 +166,20 @@ To search with named vectors (available in `query` API):
|
||||
|
||||
{{< code-snippet path="/documentation/headless/snippets/query-points/named-vector/" >}}
|
||||
|
||||
## Inference
|
||||
|
||||
Instead of providing vectors explicitly when ingesting or querying data, Qdrant can also generate vectors using a process called [inference](/documentation/inference/). Inference is the process of creating vector embeddings from text, images, or other data types using a machine learning model.
|
||||
|
||||
You can use inference in the API wherever you can use regular vectors. For example, while upserting points, you can provide the text or image and the embedding model:
|
||||
|
||||
{{< code-snippet path="/documentation/headless/snippets/inference/ingest/" >}}
|
||||
|
||||
Qdrant uses the model to generate the embeddings and store the point with the resulting vector.
|
||||
|
||||
Similarly, you can use inference at query time by providing the text or image to query with and the embedding model:
|
||||
|
||||
{{< code-snippet path="/documentation/headless/snippets/inference/query/" >}}
|
||||
|
||||
## Datatypes
|
||||
|
||||
Newest versions of embeddings models generate vectors with very large dimentionalities.
|
||||
|
||||
Reference in New Issue
Block a user