Don't consider typo rule on numbers #688
Replies: 2 comments 2 replies
-
Hello @macraig,
This would allow us in the future to index numbers differently when tokenizing documents with Charabia during the indexing process |
Beta Was this translation helpful? Give feedback.
-
Hello everyone 👋 We have just released the first RC (release candidate) of Meilisearch containing this feature!
You are welcome to leave your feedback in this discussion. If you encounter any bugs, please report them here. 🎉 Official and stable release containing this change will be available on |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Feedback from @JamesToothill in meilisearch/meilisearch#3999
Feature description
When you have typo tolerance enabled with a
oneTypo
setting (in our case of4
), numeric typos are always considered.This means a search for example for:
"2001"
Gets results such as:
"2001: A Space Odyssey"
"2001: A Space Travesty"
"Dracula 2000"
"Fantasia 2000"
Current behaviour
Steps to reproduce the behaviour:
oneTypo
setting to4
(or less)Expected behavior
Algolia has a setting to disable this behaviour
allowTyposOnNumericTokens
which is defaulttrue
but which we would set tofalse
.This allows us to search for:
"2001"
And get results such as:
"2001: A Space Odyssey"
"2001: A Space Travesty"
But not irrelevant results such as:
"Dracula 2000"
"Fantasia 2000"
Meilisearch version:
v1.2.0
Beta Was this translation helpful? Give feedback.
All reactions