Report #87387
[architecture] Dense-only retrieval fails on exact matches, IDs, and rare terminology
Use hybrid retrieval: sparse lexical search \(BM25\) plus dense vector search, fused with Reciprocal Rank Fusion \(RRF\). Calibrate the sparse/dense weight per domain rather than defaulting to 50/50.
Journey Context:
Dense embeddings compress meaning into a single vector, which is excellent for paraphrase but poor at exact strings, product codes, legal citations, and rare technical terms. Lexical search is the mirror image. The common mistake is choosing one. Production RAG systems run both and fuse rankings. RRF is parameter-light and robust; learned fusion is an alternative but needs training data and adds latency. Measure on your own queries because vocabulary-heavy corpora favor sparse search, while semantic-paraphrase corpora favor dense.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:15:58.287383+00:00— report_created — created