# Fuzziness not working as expected

**URL:** <https://discuss.elastic.co/t/fuzziness-not-working-as-expected/59583>\
**Category:** Elasticsearch\
**Created:** [September 1, 2016, 5:06pm UTC](https://discuss.elastic.co/t/fuzziness-not-working-as-expected/59583 "2016-09-01T17:06:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anacicconi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anacicconi/32/11222_2.png) [@anacicconi](https://discuss.elastic.co/u/anacicconi)\
**Post date:** [September 1, 2016, 5:06pm UTC](https://discuss.elastic.co/t/fuzziness-not-working-as-expected/59583/1 "2016-09-01T17:06:40Z")

</div>

I have a query where I search for a string in a field of a document that should be a book or a film. The word must be present in one of the properties of a nested object called 'translations' or in another nested objecte called translations of a nested object called myproperty. It should be published in a certain range of dates. Moreover, it must match the locale 'en'.

With fuzziness auto I have strange results. If I look for "leade" I get 3 results. All of them get the word "leader". However, if I look for "leader" I get 5 results because now I get the word "leaders" too.

How is it possible? Is Elastic looking only for the next letter after the string I search? Is there a way to tell him to show "leader", "leaders" or even "leadership" if I search for "leade"?

I'm kind of new to more complicated Elastic queries and maybe I misunderstood something. Thanks 😉

`{ "query": { "filtered": { "query": { "bool": { "should": [{ "match": { "_type": "books" } }, { "match": { "_type": "films" } }], "minimum_should_match": 1, "must": [{ "range": { "publishAt": { "gte": "2011-01-01T00:00:00+00:00", "lte": "2011-12-31T23:59:59+00:00" } } }] } }, "filter": { "bool": { "should": [{ "nested": { "path": "translations", "query": { "bool": { "must": [ { "match": { "translations.locale": "en" } }, { "multi_match": { "query": "leader", "fields": [ "translations.*"], "fuzziness": "AUTO" } } ] } }, "inner_hits": { "highlight": { "fields": { "translations.*": {} } } } } } ], { "nested": { "path": "myproperty.translations", "query": { "bool": { "must": [{ "match": { "myproperty.translations.locale": "en" } }, { "multi_match": { "query": "leader", "fields": [ "myproperty.translations.*"] } } ] } }, "inner_hits": { "highlight": { "fields": { "myproperty.translations.*": {} } } } } } } } } }, "aggs": { "content_type": { "terms": { "field": "_type" } } } }`

---

<div class="post-metadata">

**Author:** ![anacicconi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anacicconi/32/11222_2.png) [@anacicconi](https://discuss.elastic.co/u/anacicconi)\
**Post date:** [September 2, 2016, 2:43pm UTC](https://discuss.elastic.co/t/fuzziness-not-working-as-expected/59583/2 "2016-09-02T14:43:50Z")

</div>

I just realised I was using the wrong feature. I need wildcard to achieve this result. I was able to make it work. However, wildcard and fuzziness doesn't work together. Is there a solution to have both in the same query?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:22pm UTC](https://discuss.elastic.co/t/fuzziness-not-working-as-expected/59583/3 "2017-07-05T22:22:51Z")

</div>