# Cutoff\_frequency option changes cross\_fields behaviour

**URL:** <https://discuss.elastic.co/t/cutoff-frequency-option-changes-cross-fields-behaviour/32674>\
**Category:** Elasticsearch\
**Created:** [October 21, 2015, 1:12pm UTC](https://discuss.elastic.co/t/cutoff-frequency-option-changes-cross-fields-behaviour/32674 "2015-10-21T13:12:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander\_Koval](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexander_koval/32/1079_2.png) [@Alexander\_Koval](https://discuss.elastic.co/u/Alexander_Koval)\
**Post date:** [October 21, 2015, 1:12pm UTC](https://discuss.elastic.co/t/cutoff-frequency-option-changes-cross-fields-behaviour/32674/1 "2015-10-21T13:12:42Z")

</div>

Without cutoff\_frequency cross\_fields multi match uses DisjunctionMaxQuery:

> <https://gist.github.com/anti-social/cc77deb8c13e766565bc>

But if there is cutoff\_frequency it suddenly uses BooleanQuery. Also tie\_breaker option is ignored in this case:

> <https://gist.github.com/anti-social/6e566f4b3a5b3d1699dc>

This behaviour is not obvious and documentation doesn't point that.

Why Elasticsearch doesn't use DisjunctionMaxQuery in [BlendedTermQuery.commonTermsBlendedQuery](https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/apache/lucene/queries/BlendedTermQuery.java#L315)?

---

<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, 11:43pm UTC](https://discuss.elastic.co/t/cutoff-frequency-option-changes-cross-fields-behaviour/32674/2 "2017-07-05T23:43:33Z")

</div>