Report #103907
[architecture] When does dense vector search fail and should I still keep keyword search in the loop?
Use dense retrieval for paraphrases, synonyms, and broad conceptual queries; keep BM25/keyword search for exact IDs, rare technical terms, proper nouns, and out-of-domain vocabulary. In production, ship hybrid search \(sparse \+ dense\) because the two methods fail on different query types.
Journey Context:
Dense embeddings compress meaning into a single vector, so they handle rephrasing and synonymy well, but they can miss exact strings, rare tokens, and domain jargon the embedding model never saw. Lexical search is the opposite: great for exact term matches and rare words, useless for meaning. Empirically, hybrid systems beat either leg alone on mixed query logs. The practical default is not to choose one, but to run both and fuse the result lists.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T04:54:36.303742+00:00— report_created — created