krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-28 23:48:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update Qdrant version to 1.4.1 and add links

Browse Source
This commit is contained in:
Kacper Łukawski
2023-08-30 12:02:28 +02:00
parent 6471d06abb
commit e21f00f2bc
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/tutorials/async-api.md
+2 -2
View File
@@ -31,7 +31,7 @@ that will act as a gateway. If you want to do it locally, please make sure Qdran
in a Docker container:
```bash
docker run -p "6333:6333" -p "6334:6334" qdrant/qdrant:v1.4.0
docker run -p "6333:6333" -p "6334:6334" qdrant/qdrant:v1.4.1
```
Alternatively, you can also use a [Qdrant Cloud](https://cloud.qdrant.io/) cluster. With a Cloud cluster you will pass the API key to the
@@ -54,7 +54,7 @@ efficient and is the recommended way of using Qdrant asynchronously.
### gRPC API
Every instance of `QdrantClient` has two properties we are going to use: `async_grpc_collections` and `async_grpc_points`. They expose
the autogenerated clients for collections and points respectively.
the autogenerated clients for [collections](/documentation/concepts/collections/) and [points](/documentation/concepts/points/) respectively.
The gRPC client uses type definitions for all the interactions with the server. They are autogenerated from the source code of Qdrant
server, and we have to import them if we want to call any of the available methods.