# MinShouldMatch and synonyms

**URL:** <https://discuss.elastic.co/t/minshouldmatch-and-synonyms/94373>\
**Category:** Elasticsearch\
**Created:** [July 24, 2017, 5:20pm UTC](https://discuss.elastic.co/t/minshouldmatch-and-synonyms/94373 "2017-07-24T17:20:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmcginty](https://avatars.discourse-cdn.com/v4/letter/j/e9bcb4/32.png) [@jmcginty](https://discuss.elastic.co/u/jmcginty)\
**Post date:** [July 24, 2017, 5:20pm UTC](https://discuss.elastic.co/t/minshouldmatch-and-synonyms/94373/1 "2017-07-24T17:20:27Z")

</div>

We have a synonym filter configured in the analyzer used for queries (but not in the analyzer used for indexing).

If I do a Match query on a single search term with a minShouldMatch value of "2\<75%", the query will not return results if the single term has multiple synonyms. Seems like the expanded synonym terms are affecting the minShouldMatch calculation.

If I don't include the synonym filter in the query analyzer it works, or if I change minShouldMatch to "1\<75% 2\<75%" it works.

More info: This only seems to happen using a Common Terms query - a Match query works OK. This is on ElasticSearch 5.4,

---

<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:** [August 21, 2017, 5:20pm UTC](https://discuss.elastic.co/t/minshouldmatch-and-synonyms/94373/2 "2017-08-21T17:20:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.