Changelog

Features :cake:

• Replication support - Now Qdrant can provide a high availability setup with distributed deployment out of the box. Replications in combination with sharding allow horizontally scaling of both - the collection's size and the cluster's throughput. While at the same time eliminating a single point of failure problem. Read more in the docs :book:
• https://github.com/qdrant/qdrant/issues/1119 - New administration API allows disabling write operations to the service. Useful in situations where search availability is more critical than updates. It will enable blocking updates if, e.g., the memory usage watermark is reached. Docs :book:
• https://github.com/qdrant/qdrant/pull/1164 - Report indexed payload points in info API, allows to verify that payload values was properly formatted for indexing
• https://github.com/qdrant/qdrant/pull/1150 - New exact search parameter allows to force exact search of the vectors, even if ANN index is built. Useful for validating accuracy of the current HNSW configuration.

Improvements :seedling:

• https://github.com/qdrant/qdrant/pull/1157 - Disable logging for healthchecks
• https://github.com/qdrant/qdrant/pull/1152 - Move connection errors logging into /cluster status API. Prevents flood of error messages in case of other node failure in cluster

Bug fixes :imp:

• https://github.com/qdrant/qdrant/pull/1172 - fix issue with consensus WAL, leading to panic on recover in some rare cases

Compatibility :dancers:

• This release is backward compatible with v0.10.5 storage in single node deployment.
• Distributed deployment is, unfortunately, incompatible with previous versions due to the large amount of changes, required for replica set implementation.
• Clients are tested for backward compatibility with v0.10.x service

Further work :astronaut:

This release finalizes the feature-set of the first road-map of Qdrant. Further updates before v1.0 will be focused on maintainability and stability of the service. The next road-map will be published soon!

Thanks to @IvanPleshkov, @agourlay, and @e-ivkov for contributing into this release