fuzzy search and typos
See original GitHub issueIs there any way to support typos/misspellings of a word? Like a hamilton distance search where anything with a small distance is also included? eg: if I misspell tetx
instead text
. Is this supported?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:26
- Comments:9 (1 by maintainers)
Top Results From Across the Web
What is fuzzy search? - Typesense
A fuzzy matching search algorithm will be able to find relevant strings even if your original string contains typo errors and misspellings.
Read more >How to Handle Typos in Elasticsearch Using Fuzzy Query
Typo is something that often happens and can reduce user's experience, fortunately, Elasticsearch can handle it easily with Fuzzy Query.
Read more >What is a Fuzzy Search? - TechTarget
Learn how fuzzy search uses a fuzzy matching algorithm to return results based on likely relevance even though spellings may not be an...
Read more >Fuzzy Search - Micro Focus
The fuzzy algorithm uses a proprietary model to match correct documents even when spelling mistakes occurred in the query Text. It determines the...
Read more >Fuzzy search - Open Semantic Search
Fuzzy search. How to find results despite incomplete or imperfect search queries, misspelled names, typos and low text quality or low OCR quality....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ts-thomas With a fuzzy search you will make every other search libraries obselete. Can you imagine the impact on society ? Every release would be showcased at the Las Vegas flexsearch conference, you could have your own TV show, who knows?
Please, we crave this feature.
Could be interesting to mention this on the README. Why would you include fuzzy search libraries in the benchmarks if flexsearch does not even support it?