# Terms minimum\_match is not allowed in filter **URL:** \ **Category:** Elasticsearch\ **Created:** [January 22, 2013, 10:12pm UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463 "2013-01-22T22:12:26Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![roytmana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roytmana/32/44855_2.png) [@roytmana](https://discuss.elastic.co/u/roytmana)\ **Post date:** [January 22, 2013, 10:12pm UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463/1 "2013-01-22T22:12:26Z")
Might worth while mentioning it in Terms documentation that minimum\_match should not be used in filter. I assume 1 value is used If i try it I get QueryParsingException[[award] [terms] filter does not support [minimum\_match]] -- ---
**Author:** ![roytmana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roytmana/32/44855_2.png) [@roytmana](https://discuss.elastic.co/u/roytmana)\ **Post date:** [January 22, 2013, 10:13pm UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463/2 "2013-01-22T22:13:40Z")
Same goes for Bool minimum\_number\_should\_match On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote: > Might worth while mentioning it in Terms documentation that minimum\_match > should not be used in filter. I assume 1 value is used > > If i try it I get QueryParsingException[[award] [terms] filter does not > support [minimum\_match]] -- ---
**Author:** ![mattweber](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattweber/32/44940_2.png) [@mattweber](https://discuss.elastic.co/u/mattweber)\ **Post date:** [January 22, 2013, 10:48pm UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463/3 "2013-01-22T22:48:27Z")
Yes that is correct. FYI, I have gone though the source code and documented every possible option for each query, filter, and facet in Elasticsearch while I was implementing Elastic.js. You can use the Elastic.js docs even if you are only using the REST api. [http://docs.fullscale.co/elasticjs/](http://docs.fullscale.co/elasticjs/) Elastic.js uses the camelCase options, for the REST api you should use underscore\_notation. You can always write Elastic.js and use the translator ([The domain name Fullscale.co is for sale | Dan.com](http://docs.fullscale.co/translator/)) as well. Note that Elastic.js includes Lucene 4.0 options that are only available in the master branch of Elasticsearch. Thanks, Matt Weber On Tue, Jan 22, 2013 at 2:13 PM, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) wrote: > Same goes for Bool minimum\_number\_should\_match > > On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote: > > > Might worth while mentioning it in Terms documentation that minimum\_match > > should not be used in filter. I assume 1 value is used > > > > If i try it I get QueryParsingException[[award] [terms] filter does not > > support [minimum\_match]] > > -- -- ---
**Author:** ![roytmana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roytmana/32/44855_2.png) [@roytmana](https://discuss.elastic.co/u/roytmana)\ **Post date:** [January 22, 2013, 10:53pm UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463/4 "2013-01-22T22:53:54Z")
Thanks Matt. Are your doc hand written with more info than official ES or a organized ES docs? Have not had chance to try your API with ExtJS yet - just learning and prototyping ES via REST for now. Once I a reasonable understanding what and how I want to do will switch to your API On Tue, Jan 22, 2013 at 5:48 PM, Matt Weber [matt.weber@gmail.com](mailto:matt.weber@gmail.com) wrote: > Yes that is correct. FYI, I have gone though the source code and > documented every possible option for each query, filter, and facet in > Elasticsearch while I was implementing Elastic.js. You can use the > Elastic.js docs even if you are only using the REST api. > > [The domain name Fullscale.co is for sale | Dan.com](http://docs.fullscale.co/elasticjs/) > > Elastic.js uses the camelCase options, for the REST api you should use > underscore\_notation. You can always write Elastic.js and use the > translator ([The domain name Fullscale.co is for sale | Dan.com](http://docs.fullscale.co/translator/)) as well. Note that > Elastic.js includes Lucene 4.0 options that are only available in the > master branch of Elasticsearch. > > Thanks, > Matt Weber > > On Tue, Jan 22, 2013 at 2:13 PM, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) wrote: > > > Same goes for Bool minimum\_number\_should\_match > > > > On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote: > > > > > Might worth while mentioning it in Terms documentation > > > that minimum\_match should not be used in filter. I assume 1 value is used > > > > > > If i try it I get QueryParsingException[[award] [terms] filter does not > > > support [minimum\_match]] > > > > -- > > -- -- ---
**Author:** ![mattweber](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattweber/32/44940_2.png) [@mattweber](https://discuss.elastic.co/u/mattweber)\ **Post date:** [January 22, 2013, 11:04pm UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463/5 "2013-01-22T23:04:15Z")
The Elastic.js documentation covers every possible option for each query, filter, and facet within Elasticsearch. We used a combination of the official Elasticsearch docs, lucene docs, and information we have written to do this. On Tue, Jan 22, 2013 at 2:53 PM, Alex Roytman [roytmana@gmail.com](mailto:roytmana@gmail.com) wrote: > Thanks Matt. > > Are your doc hand written with more info than official ES or > a organized ES docs? > > Have not had chance to try your API with ExtJS yet - just learning and > prototyping ES via REST for now. Once I a reasonable understanding what and > how I want to do will switch to your API > > On Tue, Jan 22, 2013 at 5:48 PM, Matt Weber [matt.weber@gmail.com](mailto:matt.weber@gmail.com) wrote: > > > Yes that is correct. FYI, I have gone though the source code and > > documented every possible option for each query, filter, and facet in > > Elasticsearch while I was implementing Elastic.js. You can use the > > Elastic.js docs even if you are only using the REST api. > > > > [The domain name Fullscale.co is for sale | Dan.com](http://docs.fullscale.co/elasticjs/) > > > > Elastic.js uses the camelCase options, for the REST api you should use > > underscore\_notation. You can always write Elastic.js and use the > > translator ([The domain name Fullscale.co is for sale | Dan.com](http://docs.fullscale.co/translator/)) as well. Note that > > Elastic.js includes Lucene 4.0 options that are only available in the > > master branch of Elasticsearch. > > > > Thanks, > > Matt Weber > > > > On Tue, Jan 22, 2013 at 2:13 PM, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) wrote: > > > > > Same goes for Bool minimum\_number\_should\_match > > > > > > On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote: > > > > > > > Might worth while mentioning it in Terms documentation > > > > that minimum\_match should not be used in filter. I assume 1 value is used > > > > > > > > If i try it I get QueryParsingException[[award] [terms] filter does not > > > > support [minimum\_match]] > > > > > > -- > > > > -- > > -- -- ---
**Author:** ![roytmana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roytmana/32/44855_2.png) [@roytmana](https://discuss.elastic.co/u/roytmana)\ **Post date:** [January 22, 2013, 11:05pm UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463/6 "2013-01-22T23:05:36Z")
cool good job it'll be a great learning resource! On Tue, Jan 22, 2013 at 6:04 PM, Matt Weber [matt.weber@gmail.com](mailto:matt.weber@gmail.com) wrote: > The Elastic.js documentation covers every possible option for each query, > filter, and facet within Elasticsearch. We used a combination of the > official Elasticsearch docs, lucene docs, and information we have written > to do this. > > On Tue, Jan 22, 2013 at 2:53 PM, Alex Roytman [roytmana@gmail.com](mailto:roytmana@gmail.com) wrote: > > > Thanks Matt. > > > > Are your doc hand written with more info than official ES or > > a organized ES docs? > > > > Have not had chance to try your API with ExtJS yet - just learning and > > prototyping ES via REST for now. Once I a reasonable understanding what and > > how I want to do will switch to your API > > > > On Tue, Jan 22, 2013 at 5:48 PM, Matt Weber [matt.weber@gmail.com](mailto:matt.weber@gmail.com) wrote: > > > > > Yes that is correct. FYI, I have gone though the source code and > > > documented every possible option for each query, filter, and facet in > > > Elasticsearch while I was implementing Elastic.js. You can use the > > > Elastic.js docs even if you are only using the REST api. > > > > > > [The domain name Fullscale.co is for sale | Dan.com](http://docs.fullscale.co/elasticjs/) > > > > > > Elastic.js uses the camelCase options, for the REST api you should use > > > underscore\_notation. You can always write Elastic.js and use the > > > translator ([The domain name Fullscale.co is for sale | Dan.com](http://docs.fullscale.co/translator/)) as well. Note that > > > Elastic.js includes Lucene 4.0 options that are only available in the > > > master branch of Elasticsearch. > > > > > > Thanks, > > > Matt Weber > > > > > > On Tue, Jan 22, 2013 at 2:13 PM, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) wrote: > > > > > > > Same goes for Bool minimum\_number\_should\_match > > > > > > > > On Tuesday, January 22, 2013 5:12:26 PM UTC-5, AlexR wrote: > > > > > > > > > Might worth while mentioning it in Terms documentation > > > > > that minimum\_match should not be used in filter. I assume 1 value is used > > > > > > > > > > If i try it I get QueryParsingException[[award] [terms] filter does > > > > > not support [minimum\_match]] > > > > > > > > -- > > > > > > -- > > > > -- > > -- -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:55am UTC](https://discuss.elastic.co/t/terms-minimum-match-is-not-allowed-in-filter/10463/7 "2017-07-06T02:55:05Z")