Total hits incorrect when using pagination backend

[Antsiscool]

Description
When using a pagination backend, the total hits is capped at 200. I tried this with will_paginate, but it should also happen with kaminari.

When a pagination backend is set, the limit parameter is set to 200 with no option to override in MeiliSearch::Rails::ClassMethods#ms_search.
Later in the method total hits is calculated by total_hits = json['hits'].length. This is capped at 200 due to the limit set earlier.
total_hits should instead be set to the value of nbHits.

Expected behavior
When more than 200 documents match the search, the total hits count should be match the value returned.
What you expected to happen.

Current behavior
Currently the total number of hits is capped at 200.

Environment (please complete the following information):

• meilisearch-rails version: 0.5.1

[brunoocasali]

Hi @Antsiscool thanks for reporting this bug!

I'll be looking into it during this week, or if you want to, you can open a PR :)

[curquiza]

Hello @Antsiscool sorry for the huge delay

This 200 fetch is currently expected to ensure we know the total number of matches, so know that total number of pages. Currently, there is no other way with Meilisearch (the core engine) to provide a "finite" pagination (e.g. being able to access another page other than the next one).

Here is some resources regarding this

• a "guide" for pagination using Meilisearch. A real and fresh new one is planned for July.
• Why you cannot use the nbHits parameters in the Meilisearch response to define the number of pages, so access to the last page.

We know some of our users would love to use efficient finite pagination with Meilisearch and that's why we are currently thinking about adding this feature in a future version. Once it's implemented, the issue you raise will be definitely fixed!

Thanks again for your report, and sorry for this!

[brunoocasali]

Hey @Antsiscool, this issue is fixed in the new version of Meilisearch v0.30!

To use it, you must update your rails gem and your Meilisearch instance. If you use pagy you'll have to wait a little bit, because the finite pagination will only be available in the next major version.

Check this #214 for more info regarding the implementation of finite pagination.

Also: https://github.com/meilisearch/meilisearch-rails/releases/tag/v0.8.0
And https://github.com/meilisearch/meilisearch/releases/tag/v0.30.0