Add a way to force search results to be exhaustive #335
Replies: 6 comments 9 replies
-
I would like this feature as I'm using Meilisearch as the primary method of querying/filtering/sorting data in my stack, a small performance penalty would be an acceptable compromise and I will implement a cache in any case. Another reason I would like this feature is in order to retrieve a definitive list of all the IDs in an index for verification that everything has synced from the primary database. Alternatively, a simple method just to get those IDs would work. |
Beta Was this translation helpful? Give feedback.
-
More explanation about why the |
Beta Was this translation helpful? Give feedback.
-
Hello @homerjam! |
Beta Was this translation helpful? Give feedback.
-
on our end, the now the numbers are off by ~20% having the option to tell the search that we want to receive an exact count would be great. possible fixes to work around this issue:
|
Beta Was this translation helpful? Give feedback.
-
Hey everyone 👋
📚 More information here. |
Beta Was this translation helpful? Give feedback.
-
Hey everyone 👋 I'm locking that discussion. Please open a new discussion if you want to share feedback / ask for a feature request. Thank you! 🙇♂️ |
Beta Was this translation helpful? Give feedback.
-
Description
We are opening this discussion to gather and consolidate feedback that are related to the fact that it is not possible to force MeiliSearch to return an exhaustive number of results.
The initial idea would be to have a way to force the search to return exhaustive results knowing that it will impact performance in a negative way.
Related discussions
nbHits
with differentoffset
meilisearch#1993Beta Was this translation helpful? Give feedback.
All reactions