# Q re Deprecated field minimum\_number\_should\_match

**URL:** <https://discuss.elastic.co/t/q-re-deprecated-field-minimum-number-should-match/77343>\
**Category:** Elasticsearch\
**Created:** [March 3, 2017, 5:16pm UTC](https://discuss.elastic.co/t/q-re-deprecated-field-minimum-number-should-match/77343 "2017-03-03T17:16:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jasona](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jasona](https://discuss.elastic.co/u/jasona)\
**Post date:** [March 3, 2017, 5:16pm UTC](https://discuss.elastic.co/t/q-re-deprecated-field-minimum-number-should-match/77343/1 "2017-03-03T17:16:54Z")

</div>

We're trying ES5.2.0 in place of ES5.1.1, and I'm seeing alot of these messages:

[org.elasticsearch.deprecation.common.ParseField] Deprecated field [minimum\_number\_should\_match] used, expected [minimum\_should\_match] instead

Q: Is minimum\_should\_match back-compatible with 5.1.1, or would we be required to be running 5.2.0 in order to be using the new name, minimum\_should\_match ?

---

<div class="post-metadata">

**Author:** ![jasona](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jasona](https://discuss.elastic.co/u/jasona)\
**Post date:** [March 3, 2017, 5:30pm UTC](https://discuss.elastic.co/t/q-re-deprecated-field-minimum-number-should-match/77343/2 "2017-03-03T17:30:38Z")

</div>

I see description of `minimum_should_match` back in the 2.4 docs: [https://www.elastic.co/guide/en/elasticsearch/reference/2.4/query-dsl-minimum-should-match.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/query-dsl-minimum-should-match.html)

Is `minimum_should_match` a directly 1-for-1 replacement of `minimum_number_should_match` ?

---

<div class="post-metadata">

**Author:** ![joegallo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joegallo/32/14287_2.png) [@joegallo](https://discuss.elastic.co/u/joegallo)\
**Post date:** [March 3, 2017, 8:06pm UTC](https://discuss.elastic.co/t/q-re-deprecated-field-minimum-number-should-match/77343/3 "2017-03-03T20:06:34Z")

</div>

Yes, `minimum_number_should_match` is deprecated and will be removed in 6.0, you should use `minimum_should_match` instead, and it is fine to use in all versions of ES 5.x.

I'm going to re-categorize this question to 'Elasticsearch' rather than 'Elastic Cloud', just in case anybody on the Elasticsearch team would like to comment.

---

<div class="post-metadata">

**Author:** ![jasona](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jasona](https://discuss.elastic.co/u/jasona)\
**Post date:** [March 3, 2017, 9:45pm UTC](https://discuss.elastic.co/t/q-re-deprecated-field-minimum-number-should-match/77343/4 "2017-03-03T21:45:29Z")

</div>

So it was just a rename and there were no semantic changes? Why even bother.

---

<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:** [March 6, 2017, 9:45pm UTC](https://discuss.elastic.co/t/q-re-deprecated-field-minimum-number-should-match/77343/5 "2017-03-06T21:45:52Z")

</div>

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