# iS their a better way than this fuzzy search for multi-match?
**URL:** https://discuss.elastic.co/t/is-their-a-better-way-than-this-fuzzy-search-for-multi-match/261193
**Category:** Elasticsearch
**Created:** [January 14, 2021, 11:41pm UTC](https://discuss.elastic.co/t/is-their-a-better-way-than-this-fuzzy-search-for-multi-match/261193 "2021-01-14T23:41:47Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@rajends1](https://discuss.elastic.co/u/rajends1)
#### Post date: [January 14, 2021, 11:41pm UTC](https://discuss.elastic.co/t/is-their-a-better-way-than-this-fuzzy-search-for-multi-match/261193/1 "2021-01-14T23:41:47Z")
```
{
"query": {
"multi_match": {
"fields": ["text", "title"],
"query": "king”,
"fuzziness": "AUTO",
"type": "best_fields"
}
}
}’
```
The fuzziness parameter can be specified as:
• 0, 1, 2 — It is maximum allowed Levenshtein Edit Distance (or number of edits)
• AUTO — It generates an edit distance based on the length of the term. For lengths:
o 0..2 — must match exactly
o 3..5 — one edit allowed
o \> 5 — two edits allowed
AUTO should generally be the preferred value for fuzziness.
multi\_match query also supports fuzziness but only when executing with type best\_fields ((\_score will be calculated from single best matching field.) or most\_fields (\_score will be calculated from the combination of all the fields.):
In Elasticsearch, we generally use multi\_match query that uses best\_fields as its default type
best\_fields is most useful when you are searching for multiple words best found in the same field.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 11, 2021, 11:41pm UTC](https://discuss.elastic.co/t/is-their-a-better-way-than-this-fuzzy-search-for-multi-match/261193/2 "2021-02-11T23:41:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.