Use fuzzy search for collections search #3092
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The collections search returns results with exact matches only. Users do however expect the search to be fuzzy by default, i.e. "Romania" should also match "Romanian" etc. By changing the query type from
query_string
tomulti_match
, we can use fuzzy search by default.The advantage of using fuzzy search is that it is applied at search time, i.e. we do not need to change the index configuration or re-index contents.
The main disadvantage is that it doesn't cover all variations that would be covered if we used proper stemming. For example, the following variations are not matched:
Also, fuzzy search cannot be combined with prefix search (for example "Open" does not match "OpenContracting").
Fix #2109