v1.16: `page` and `hitsPerPage` return correct values when used with `rankingScoreThreshold`

[guimachiavelli]

Prior to v1.16, when using the rankingScoreThreshold, Meilisearch stops calculating the total number of hits once it reaches the number of hits configured by limit and hitsPerPage, whether subsequent search results are above or below the score threshold. This causes the number of total hits and the facet distribution to always be incorrect, no matter if users are paginating results with page/hitsPerPage or limit/offset.

With v1.16, when processing search requests with hitsPerPage, Meilisearch computes whether all documents are below or above the ranking score threshold. This negatively impacts performance, but ensures totalHits is accurate when using page/hitsPerPage.

Tasks

• Update rankingScoreThreshold warning box text

References

• SME: @Mubelotix
• Engine PR: Fix Total Hits being wrong when rankingScoreThreshold is used meilisearch#5725