qdrant/docs/roadmap

Qdrant v1.0 Roadmap

Hi! This document is our plan for Qdrant development till its first enterprise-ready release.

Goals of the release:

• Make API and Storage stable - ensure backward compatibility for at least one major version back.
  • Starting from the release, breaking changes in API should only be done with a proper deprecation notice
  • Storage should be compatible between any two consequent major versions
• Achieve horizontal scalability - distributed deployment able to serve billions of points
• Easy integration - make the user experience as smooth as possible
• Resource efficiency - push Qdrant performance on the single machine to the limit

To build a solid foundation for future development, we decided to keep Qdrant as legacy-free as possible. That means that while switching to v1.0, some breaking changes are likely.

ETA of v1.0-rc is Q3 2022

How to contribute

If you are a Qdrant user - Data Scientist, ML Engineer, or MLOps, the best contribution would be the feedback on your experience with Qdrant. Let us know whenever you have a problem, face an unexpected behavior, or see a lack of documentation. You can do it in any convenient way - create an issue, start a discussion, or drop up a message. If you use Qdrant or Metric Learning in your projects, we'd love to hear your story! Feel free to share articles and demos in our community.

For those familiar with Rust - check out our contribution guide. If you have problems with code or architecture understanding - reach us at any time. Feeling confident and want to contribute more? - Come to work with us!

Milestones

• 🌎 Distributed Deployment
  • Distributed querying
  • Integration of raft for distributed consistency
  • Sharding - group segments into shards
  • Cluster scaling
  • Replications - automatic segment replication between nodes in cluster

---

• 🔌 Integration & Interfaces
  • gPRC version of each REST API endpoint
  • Split REST Endpoints for better documentation and client generation

---

• 🚚 Payload Processing

  • Support storing any JSON as a Payload
  • Support more payload types, e.g.
    • Data-time
  • Support for Null values
  • Enable more types of filtering queries, e.g.
    • Filter by Score
    • Filter by number of stored elements
    • isNull or isEmpty query conditions

• Additionally

  • Full-text filtering support
  • Multiple vectors per record support

---

• 🏎️ Performance improvements
  • Indexing of geo-payload
  • On the fly payload index
  • Multiprocessing segment optimization
  • Fine-tuned HNSW index configuration