mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-13 15:22:30 +00:00
Jack Ye
b21fb2a4dc
The pages describing this code lived in lancedb/docs, a repository with ten stars that neither contributing guide mentioned. A user who hit a wrong page while reading the source had to find a separate, near-invisible repository to fix it. These 102 pages now sit beside the code, and a documentation fix is a pull request in the repository the reader already had open. `docs/web` is a complete Mintlify site: `cd docs/web && mint dev` serves it with no other checkout. Enterprise pages stay private and are merged in when the published site is assembled, so links into them do not resolve here — every open-source page does. `docs/web-tests` holds the tests the code examples are extracted from. They ran against a published wheel before; here they can run against this repository's own SDK, so an example that stops compiling fails the pull request that broke it rather than being noticed later. Both directories sit beside `docs/src` and are invisible to it: mkdocs reads `docs_dir: src`, so the SDK reference builds and deploys exactly as before.
49 lines
2.5 KiB
Plaintext
49 lines
2.5 KiB
Plaintext
---
|
||
title: MRR Reranker
|
||
sidebarTitle: "MRR Algorithm"
|
||
description: Combine and rerank search results using Mean Reciprocal Rank (MRR) algorithm in LanceDB. Supports weighted scoring for hybrid and multivector search.
|
||
|
||
---
|
||
|
||
import { PyRerankingMrrUsage } from '/snippets/integrations.mdx';
|
||
|
||
# MRR Reranker
|
||
|
||
This reranker uses the Mean Reciprocal Rank (MRR) algorithm to combine and rerank search results from vector and full-text search. You can use this reranker by passing `MRRReranker()` to the `rerank()` method. The MRR algorithm calculates the average of reciprocal ranks across different search results, providing a balanced way to merge results from multiple ranking systems.
|
||
|
||
> **Note:** Supported query types – Hybrid and Multivector search.
|
||
|
||
<CodeGroup>
|
||
<CodeBlock filename="Python" language="Python" icon="python">
|
||
{PyRerankingMrrUsage}
|
||
</CodeBlock>
|
||
</CodeGroup>
|
||
|
||
## Accepted Arguments {#accepted-arguments}
|
||
| Argument | Type | Default | Description |
|
||
| --- | --- | --- | --- |
|
||
| `weight_vector` | `float` | `0.5` | Weight for vector search results (0.0 to 1.0). |
|
||
| `weight_fts` | `float` | `0.5` | Weight for FTS search results (0.0 to 1.0). |
|
||
| `return_score` | `str` | `"relevance"` | Options are "relevance" or "all". The type of score to return. If "relevance", will return only the `_relevance_score`. If "all", will return all scores from the vector and FTS search along with the relevance score. |
|
||
|
||
**Note:** `weight_vector` + `weight_fts` must equal 1.0.
|
||
|
||
For multivector reranking, input result sets need `_rowid` so LanceDB can identify the same row
|
||
across the ranked lists. Add `.with_row_id(True)` to each vector search before passing the results
|
||
to the reranker.
|
||
|
||
## Supported Scores for each query type {#supported-scores-for-each-query-type}
|
||
You can specify the type of scores you want the reranker to return. The following are the supported scores for each query type:
|
||
|
||
### Hybrid Search {#hybrid-search}
|
||
|`return_score`| Status | Description |
|
||
| --- | --- | --- |
|
||
| `relevance` | ✅ Supported | Results only have the `_relevance_score` column. |
|
||
| `all` | ✅ Supported | Results have vector(`_distance`) and FTS(`score`) along with Hybrid Search score(`_relevance_score`). |
|
||
|
||
### Multivector Search {#multivector-search}
|
||
|`return_score`| Status | Description |
|
||
| --- | --- | --- |
|
||
| `relevance` | ✅ Supported | Results only have the `_relevance_score` column. |
|
||
| `all` | ✅ Supported | Results have vector distances from all searches along with `_relevance_score`. |
|