# Fuzziness parameter disables cutoff\_frequency in match query

**URL:** <https://discuss.elastic.co/t/fuzziness-parameter-disables-cutoff-frequency-in-match-query/60934>\
**Category:** Elasticsearch\
**Created:** [September 19, 2016, 6:59pm UTC](https://discuss.elastic.co/t/fuzziness-parameter-disables-cutoff-frequency-in-match-query/60934 "2016-09-19T18:59:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![francesconero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/francesconero/32/11981_2.png) [@francesconero](https://discuss.elastic.co/u/francesconero)\
**Post date:** [September 19, 2016, 6:59pm UTC](https://discuss.elastic.co/t/fuzziness-parameter-disables-cutoff-frequency-in-match-query/60934/1 "2016-09-19T18:59:29Z")

</div>

As in the title, setting a value to fuzziness (even 0) will make the match query ignore the cutoff\_frequency parameter.

In fact setting fuzziness to 0 and a cutoff\_frequency, will return the same results of a match query with neither of them set.

Is this the default behavior or a bug?

I'm trying it on an index with only one shard and elasticsearch 2.3.5

---

<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:19pm UTC](https://discuss.elastic.co/t/fuzziness-parameter-disables-cutoff-frequency-in-match-query/60934/2 "2017-07-05T22:19:03Z")

</div>