Skip to content

Commit 4280a4d

Browse files
v1.16: rankingScoreThreshold no longer affects totalHits accuracy (#3322)
--------- Co-authored-by: Mubelotix <[email protected]>
1 parent 1508511 commit 4280a4d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

reference/api/search.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1141,7 +1141,9 @@ Excludes results below the specified ranking score.
11411141
Excluded results do not count towards `estimatedTotalHits`, `totalHits`, and facet distribution.
11421142

11431143
<Warning>
1144-
For performance reasons, if the number of documents above `rankingScoreThreshold` is higher than `limit`, Meilisearch does not evaluate the ranking score of the remaining documents. Results ranking below the threshold are not immediately removed from the set of candidates. In this case, Meilisearch may overestimate the count of `estimatedTotalHits`, `totalHits` and facet distribution.
1144+
Using `rankingScoreThreshold` with `page` and `hitsPerPage` forces Meilisearch to evaluate the ranking score of all matching documents to return an accurate `totalHits`. This may negatively impact search performance.
1145+
1146+
Queries with `limit` and `offset` avoid this overhead when using `rankingScoreThreshold`.
11451147
</Warning>
11461148

11471149
#### Example

0 commit comments

Comments
 (0)