Questions
3 of 18
1Why did Qdrant consolidate search, recommend, and discovery operations into the Universal Query API?
2What is a prefetch stage in Qdrant's Universal Query API, and why would you use multiple prefetches?
3How do Reciprocal Rank Fusion and Distribution-Based Score Fusion differ when combining Qdrant prefetch results?
4How would you retrieve 500 candidates with dense vectors and rerank them using a ColBERT multivector?
5What is Qdrant's recommend query mode, and how is it different from plain similarity search?
6How does Qdrant combine vector similarity search with structured payload filters?
7What are must, should, and must_not clauses in a Qdrant payload filter?
8Why can filtering after an ANN search return too few results when the filter is highly selective?
9How does Qdrant's filtered vector search avoid the classic post-filtering problem?
10How would you implement a geo-radius search for similar items within 5 km of a location in Qdrant?
11Why should you create payload indexes for fields that are filtered frequently at scale?
12What payload index types does Qdrant support, and how would you choose one for tags versus price?
13What is a full-text payload index used for, and how does it differ from an exact-match keyword index?
14What is the cost of creating too many payload indexes on a high-write Qdrant collection?
15Why should point uploads be batched instead of sending one upsert request per point?
16What is Qdrant's Scroll API used for, and why is it preferable to vector search when iterating through matching points?
17How does Qdrant Scroll pagination avoid the main performance problem of large SQL OFFSET pagination?
18What is a realistic batch size for bulk-loading millions of Qdrant points, and what factors should influence it?
03 / 18

How do Reciprocal Rank Fusion and Distribution-Based Score Fusion differ when combining Qdrant prefetch results?

Rank fusion versus score fusion

Reciprocal Rank Fusion, or RRF, combines results primarily from their ranks. A candidate receives a contribution based on its position in each result list, so the absolute score values do not need to be comparable across retrieval systems.

Distribution-Based Score Fusion, or DBSF, instead uses the score distributions of the result sets to normalize their scores before combining them. That allows score magnitude to contribute, but it also means the result distribution can influence the final ranking.

The trade-off is robustness versus score information. RRF is attractive when dense and sparse systems produce incompatible score scales or when you want a simple rank-based ensemble. DBSF can be useful when relative score distributions contain meaningful information and the result sets have enough statistical stability.

A common mistake is treating a larger raw score as inherently comparable across prefetches. Dense cosine scores, sparse scores, and other ranking functions can have very different scales. Fusion should explicitly account for that. Exact fusion behavior and parameter details should be checked against the Qdrant version in use.

javascript
  1. 1

    RRF is based on result rank and does not require comparable raw scores

  2. 2

    DBSF uses normalized score distributions

  3. 3

    RRF is often robust for heterogeneous retrieval signals

  4. 4

    Fusion choice should be evaluated on representative relevance data

Difficulty: 8/10
Topics: RRF, DBSF, Score fusion

Scenario Questions

0-2 years experience
  1. 1

    Dense and sparse searches return scores on completely different scales. Why is simply adding the raw scores unsafe?

  2. 2

    What information does RRF use if it does not rely on comparable raw score magnitudes?

2-5 years experience
  1. 1

    Your RRF results are stable across queries but DBSF performs better on a well-labeled dataset. What would you investigate before choosing DBSF?

  2. 2

    A sparse retriever suddenly changes its score distribution after a model upgrade. Which fusion strategy would you expect to be more sensitive to that change?

5-8 years experience
  1. 1

    Your dense retriever returns tightly clustered scores while the sparse retriever has a wide score range. How would that affect your evaluation of RRF versus DBSF?

  2. 2

    You need to combine three retrieval systems with different score semantics. How would you design an experiment to select the fusion strategy?

8+ years experience
  1. 1

    A global search platform uses multiple retrievers whose score distributions drift over time. How would you choose and monitor a fusion strategy that remains robust?

  2. 2

    Offline evaluation shows DBSF wins on average but occasionally produces severe ranking regressions for certain query classes. How would you decide whether to use RRF, DBSF, or a query-dependent strategy?

Follow-up Questions

  • When would RRF be safer than score-based fusion?
  • What assumptions does DBSF make about the score distributions of its inputs?