Releases: qdrant/qdrant-client
Releases · qdrant/qdrant-client
v0.10.0
Changelog
- Support for qdrant v0.10.0 + v0.10.1
betterproto
grpc library replaces withgrpcio
, which perwords up to 20x faster serialization and doe snot require asyncio runtime- One drawback of
grpcio
is less intuitive datatypes, but we encourage you to use data structures provided by Pydantic instead, it includes better validation and easy-to-use interface. Pydantic structures will be automatically converted into protobuf ones.
- One drawback of
Version compatibility | client v0.9.x | client v0.10.0 | client v0.10.1 |
---|---|---|---|
qdrant v0.9.1 | + | - | - |
qdrant v0.10.0 | + | + | |
qdrant v0.10.1 | - | + | + |
API changes:
vector_size
anddistance
are replaced withvectors_config
field_type
replaced withfield_schema
in payload indexing requestwith_vector
param replaced withwith_vectors
, allowing to specify which exact vector to returnvector
replaced withvectors
and according data structure in point update APIs
v0.8.7
v0.8.3
v0.8.0
Change log
- Support for Qdrant v0.8.0
What's Changed
- All methods are now have custom implementation in the
QdrantClient
- E.g. use
client.get_collection("my_collection")
instead ofclient.http.collections_api.get_collection("my_collection")
- E.g. use
- Points update and query APIs are now supporting gPRC mode
- gPRC and REST structures are automatically inter-convertible
Bug Fixes
- bool parsing in conditions filter fixed
v0.7.0
Change log
- Support for Qdrant v0.7.0
What's Changed
-
Any JSON is now supported as a Payload
- Payload schema is no loner required, payload index requires specification of the field type instead.
-
New condition filters
Match
condition refactored to also supportbool
condition, see exampleIsEmpty
- filter by the presence of the valueValuesCount
- filter by the number of stored values
Bug Fixes
- Proper multiprocessing shutdown in case of parallel upload errors
v0.6.1
Improvements
- This release includes initial support for the GRPC interface to the Qdrant engine.
- In our benchmarks, we found out that it is about 3 times faster than the REST interface in the initial upload.
Notes
v0.6.0
Change log
- Support API of Qdrant v0.6.x
Breaking changes
- Collection name parameter unified across all API methods. Now it is called
collection_name
(old version:name
) - Match request is now separated into
MatchKeyword
andMatchInteger
- See test diff for migration examples: b3474b7#diff-58894b5fdecb917cdf60a0d1e9dbecae4fb31921be7ca7561642be4f44c0889f