hybrid search
technique judged 100% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2024-W25 | 1 | 1 |
| 2024-W26 | 1 | 1 |
| 2025-W19 | 1 | 1 |
| 2025-W22 | 1 | 1 |
| 2025-W23 | 2 | 1 |
| 2025-W24 | 1 | 1 |
| 2026-W04 | 1 | 1 |
| 2026-W09 | 4 | 1 |
| 2026-W11 | 8 | 1 |
| 2026-W13 | 2 | 2 |
| 2026-W15 | 1 | 1 |
| 2026-W18 | 1 | 1 |
| 2026-W19 | 1 | 1 |
| 2026-W20 | 1 | 1 |
| 2026-W22 | 1 | 1 |
| 2026-W24 | 3 | 1 |
| 2026-W25 | 1 | 1 |
| 2026-W32 | 2 | 2 |
| 2026-W36 | 1 | 1 |
| 2026-W38 | 1 | 1 |
| 2026-W40 | 6 | 3 |
| 2026-W41 | 1 | 1 |
In their words
score } for r in results ] def hybrid_search ( self , query_vector : List [ float ], query_text : str , limit : int = 10 , sparse_weight : float = 0.3 ) -> List [ dict ]: """ Combine dense + sparse (BM25) search.
Putting it together A sensible order of operations: build the evaluation set first, get a simple baseline with recursive chunking and a good embedding model, and add hybrid search and reranking next since they tend to pay off early.
In production, these shifts are the most important: Hybrid search + reranking.
Held-out strategy MRR@5 Lexical 0.7532 Vector with fake embedder 0.4375 Hybrid with fake embedder 0.6306 Lexical retrieval outperformed hybrid retrieval in this experiment.
toolsets: - type: mcp ref: docker:duckduckgodocker agent run agent.yaml - Multi-agent architecture — Create teams of specialized agents that delegate tasks automatically - Rich tool ecosystem — Built-in tools + any MCP server (local, remote, or Docker-based) - AI provider agnostic — OpenAI, Anthropic, Gemini, AWS Bedrock, Mistral, xAI, Docker Model Runner, and more - YAML configuration — Declarati
Weaviate Vector, keyword, and hybrid search with reranking integrations Useful when hybrid retrieval is central; schema and search tuning still need ownership.
That's the signal for the next improvements, such as hybrid search to catch exact terms that embeddings blur, and reranking to reorder candidates with a more precise model.
Why Lucy Chose Qdrant for Hybrid Search and Metadata Filtering Lucy did not run a formal head-to-head benchmark against every alternative.