Hi! It's our v1.0 release! 🎉

• We stabilized the core API, filled in missing pieces, and prepared an extendable platform for upcoming features (yes, we have a new roadmap!)
• Mastered upgrades and migrations. Now it's easy to upgrade Qdrant to the latest version
• Plan each new release with compatibility to the previous one, so you can upgrade Qdrant zero downtime
• Delivered full horizontal scalability for both size and speed
• Achieved best-on-market performance, see benchmarks
• Launched Qdrant Cloud (beta), a fully managed vector search as a service. Free tier available!

Change log

Features 🏂

• #1363 - new API to list collection aliases
• #1377 - new API to delete snapshots
• #1364 - new API to initialize a collection from another collection. Useful for quick experiments over different indexing parameters. In combination with aliases, it allows to seamlessly scale number of shards in the cluster.
• #1381 - read operations have new opt-in consistencies guarantees, ensures consistent reads even from inconsistent cluster
• #1405 - write operations have new opt-in ordering guarantees, ensures that the writes are ordered from parallel overlapping requests

Improvements 🥐

• #1432 - Windows support (Windows is a group of several proprietary graphical operating system families developed and marketed by Microsoft.)
• #1352 - run consistency checks only on service startup
• #1347 - quick stop the node startup if the node cannot recover in a distributed setup
• #1353 - speed up snapshot creation, prevent blocking the execution thread
• #1391 - recover dead shards pro-actively
• #1415 - enable on disk payload option by default
• #1416 - improve error reporting for malformed point ids
• #1425 - allow to overwrite max number of cpus with env variable, useful for docker containers and kubernetes
• #1398 - decrease number of Tokio runtimes, improve performance
• #1431 - use performance optimized linker setup, up to 20% performance improvement on some workloads

Bug fixes 🎳

• #1365 - do not abort a succesful shard transfer

Telemetry 📡

• #1401 - Qdrant now collects anonymized telemetry data. It is enabled by default, but is simply disabled with CLI or ENV variable. The data is collected anonymously and is used to improve Qdrant. You can read more about it in the docs.

Future plans 🔮

This release concludes our 2022 roadmap. We covered even more features than we planned, and we are very happy with the results.
Now we have already started working on the 2023 roadmap, aiming to make vector search even faster, billion-scale deployments affordable and extend vector similarity beyond just search.

Thanks for all our contributors, users and supporters! ❤️

Special thanks to people who contributed to this release:

@agourlay, @ffuugoo, @joein, @coszio, @csko