---
title: "Comment by AI Developer on \"Hybrid Search and Reranking: Fixing Retrieval After Vector Search Falls Short\" | Hashnode"
description: "The point that a reranker can't recover a document cut at position 51 is the one I'd test directly: log the pre-rerank rank of whatever the reranker ends up put"
url: "https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9/comment/6aeaa0e2ead8145b951529fe"
---

[Discussion](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9)

Comment [Hybrid Search and Reranking: Fixing Retrieval After Vector Search Falls Short](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9)

[AI Developer](https://hashnode.com/@lycore)

[Nov 4](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9/comment/6aeaa0e2ead8145b951529fe)

The point that a reranker can't recover a document cut at position 51 is the one I'd test directly: log the pre-rerank rank of whatever the reranker ends up putting first, and if a meaningful share come from deep in the candidate list, widen the window before changing the model. It's also worth checking recall@50 of the fused list on its own, separate from final ranking quality, since that number caps everything after it. For identifier-style queries like calculate\_tax\_v2, BM25's default tokenizer may split on underscores or digits, so a code-aware analyzer (or an extra n-gram field) can matter more than the fusion weights. Since RRF ignores scores, have you considered weighting the keyword list more heavily for queries that look like identifiers or error codes, and measuring whether that beats plain k=60?

[Nagappan S](https://hashnode.com/@imkarthik03)

[Nov 9](https://hashnode.com/posts/hybrid-search-and-reranking-fixing-retrieval-after-vector-search-falls-short/6ae9d62e3b872791f3339ce9/comment/6aeaa0e2ead8145b951529fe#reply-6af1a5cb4b4391b4b0718317)

Logging the pre-rerank rank of whatever the reranker puts first is a cheap way to tell whether the window is the bottleneck, and recall@50 of the fused list is the number that caps everything after it. The tokenizer point on identifiers like calculate\_tax\_v2 isn't in the post and matters. On weighting the keyword list for identifier-style queries instead of plain k=60: I haven't tested it. The post only says to keep k=60 unless you have labelled relevance data, so I'd try it against a labelled query set before trusting it.
