Knowledge Check
You turn MMR on and your Recall@10 drops. Is MMR broken?
No. MMR spends result slots on documents further from the query, so a measure that only counts relevance goes down while the page stops repeating itself. Check what those slots held before: if they were eight versions of one story, the drop bought something your metric cannot see. If they were eight distinct relevant documents, lower diversity.
Your formula boosts newer articles on top of a hybrid query, and recency now decides every ranking. Why?
A decay term reaching 1.0 is the same size as the entire RRF score it is being added to, so it decides every comparison on its own. That ceiling rises with each extra prefetch, so measure your own fused scores rather than assuming 1.0.
You group results by document_id on a Qdrant Cloud cluster and the request returns a 400. What is missing?
A keyword payload index on document_id. Strict mode rejects the request without it, so the fix belongs on the field rather than in the query.
A reader clicks "more like this" on an article. You pass its point ID to the Recommendation API as a positive example, and the article itself never comes back. Is something broken?
No. A point passed in by ID is left out of the results, and here that is what you want, since the reader is already looking at it. When you do need it back, look the point up and pass its raw vector.
Where to Go After the Course
- Qdrant Essentials goes deeper on HNSW tuning, quantization and rescoring, high-throughput ingestion, and the full Query API.
- Multi-Vector Search covers ColBERT and ColPali, including MaxSim scoring, pooling, and MUVERA indexing.
- Tutorials walk through complete, code-first implementations of the features in this module.
- Qdrant Cloud has a free cluster to run any of this on.