Changelog

Features :ferris_wheel:

• https://github.com/qdrant/qdrant/pull/958 - Multiple Vectors per Point. - Docs
  • It is now possible to assign multiple vectors for each point in collection. Update and search APIs now accepts either one anonymous vector (same as before), or multiple named vectors. This functionality might be useful if some object could be represented from multiple aspects by different neural encoders (e.g. image + text, title + abstract).

PUT /collections/{collection_name}/points

{
    "points": [
        {
            "id": 1,
            "vectors": {
                "image": [0.9, 0.1, 0.1, 0.2],
                "text": [0.4, 0.7, 0.1, 0.8, 0.1, 0.1, 0.9, 0.2]
            }
        }
   ]
}

• https://github.com/qdrant/qdrant/pull/813 & https://github.com/qdrant/qdrant/pull/954 - Batch Search and Recommendation API - Docs
  • Allows more efficient search for multiple queries in a single request. Significantly decreases networking overhead and shares the result of filtering computation among batched queries.

POST /collections/{collection_name}/points/search/batch

{
    "searches": [
        { "vector": [0.2, 0.1, 0.9, 0.7], "limit": 3 },
        { "vector": [0.5, 0.3, 0.2, 0.3], "limit": 3 }
    ]
}

• https://github.com/qdrant/qdrant/pull/963 - Full-Text Filtering - Docs
  • Adds minimal full-text search capabilities into all filterable APIs. Specify ngram-prefix or word tokenizer to make queries only among records which contain specified words.

Improvements :mortar_board:

• https://github.com/qdrant/qdrant/pull/1000 - Multi-platform builds for x86_64 and aarch64 - allows natively run Qdrant on arm-based CPUs. Pushes price/performance ratio even further. - DockerHub
• https://github.com/qdrant/qdrant/pull/949 - Use Jemallocator instead of default one. Significantly improves memory usage, prevents heap fragmentation. - Read more
• https://github.com/qdrant/qdrant/pull/1003 - Improve scroll API performance for strict filters. In some cases up to 1000x speed improvement.

Bug fixes :space_invader:

• https://github.com/qdrant/qdrant/pull/973 - fix for snapshot api, do not fail if FS does not support last-update timestamp
• https://github.com/qdrant/qdrant/pull/990 - fix telemetry API (not stabilized yet)
• https://github.com/qdrant/qdrant/pull/1023 - assign proper response code on non-specified payload index type

Compatibility :electric_plug:

There are a lot of fundamental changes in qdrant segment storage and API, but we did our best to make a transition process as smooth as possible. The v0.10 release be performed in 2 steps: on the first step we upgrade qdrant into transition version v0.10.0 which support both - old and new version of the interface. The second update v0.10.1 will remove deprecated fields from the API.

Proposed update process with minimal downtime:

1. Update qdrant from v0.9.1 -> v0.10.0
2. Update qdrant client to v0.10.0
3. Update qdrant to v0.10.1
4. Update qdrant client to v0.10.1

Don't forget to make backups and test the process in development environment!

See API changes in client releases:

• Python
• Rust
• Go

Further work :hammer:

Next release will be primarily focused on the Replication Support.

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