# Bug with minimum\_number\_should\_match or is this incorrect usage? **URL:** \ **Category:** Elasticsearch\ **Created:** [November 3, 2010, 8:57pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512 "2010-11-03T20:57:33Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Diptamay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diptamay/32/2805_2.png) [@Diptamay](https://discuss.elastic.co/u/Diptamay)\ **Post date:** [November 3, 2010, 8:57pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/1 "2010-11-03T20:57:33Z")
Hi I have this test data [https://gist.github.com/661688](https://gist.github.com/661688), against which I am running my test cases. Here are the queries that I am firing. If you see the difference between the working (returns results) versions and the non-working (no results) ones, I am just adding "minimum\_number\_should\_match" : 1 to the search clause: 1. [https://gist.github.com/661685](https://gist.github.com/661685) : has both the working and non- working version. 2. [https://gist.github.com/661680](https://gist.github.com/661680) : has both the working and non- working version. I understand in this specific query a "should" clause is not there but I would assume "minimum\_number\_should\_match" should be ignored here. Is this a bug or am I missing something? Thanks Diptamay ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 3, 2010, 10:24pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/2 "2010-11-03T22:24:11Z")
I am not sure I managed to understad whats not working and working since its hard to understand if a certain query should match or not. If you set minimum\_number\_should\_match, it relates to the required number of should/optional clauses that will have to match. If you have not should clauses, and set it to a higher value, then no doc will match. Is it not working as expected? On Wed, Nov 3, 2010 at 10:57 PM, diptamay [diptamay@gmail.com](mailto:diptamay@gmail.com) wrote: > Hi > > I have this test data [661688’s gists · GitHub](https://gist.github.com/661688), against which I > am running my test cases. > > Here are the queries that I am firing. If you see the difference > between the working (returns results) versions and the non-working (no > results) ones, I am just adding "minimum\_number\_should\_match" : 1 to > the search clause: > > 1. [https://gist.github.com/661685](https://gist.github.com/661685) : has both the working and non- > working version. > 2. [Working... · GitHub](https://gist.github.com/661680) : has both the working and non- > working version. I understand in this specific query a "should" clause > is not there but I would assume "minimum\_number\_should\_match" should > be ignored here. > > Is this a bug or am I missing something? > > Thanks > Diptamay ---
**Author:** ![Diptamay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diptamay/32/2805_2.png) [@Diptamay](https://discuss.elastic.co/u/Diptamay)\ **Post date:** [November 3, 2010, 10:44pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/3 "2010-11-03T22:44:56Z")
If you look at the queries that I attached, the only difference is the working and the non-working version is the presence minimum\_number\_should\_match and set to 1. Yes, I am expecting results to be returned when its set. As an example, if one runs the queries in [https://gist.github.com/661685](https://gist.github.com/661685), the results from either should return only one document, whose id is 10990513, listed under [661688’s gists · GitHub](https://gist.github.com/661688). However, only one of the queries (the working one) is returning the result, while the resulting (or expected) document matches all the criteria set in the non-working one as well. -Diptamay On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > I am not sure I managed to understad whats not working and working since its > hard to understand if a certain query should match or not. If you set > minimum\_number\_should\_match, it relates to the required number of > should/optional clauses that will have to match. If you have not should > clauses, and set it to a higher value, then no doc will match. Is it not > working as expected? > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > Hi > > > I have this test datahttps://gist.github.com/661688, against which I > > am running my test cases. > > > Here are the queries that I am firing. If you see the difference > > between the working (returns results) versions and the non-working (no > > results) ones, I am just adding "minimum\_number\_should\_match" : 1 to > > the search clause: > > 1)[https://gist.github.com/661685:](https://gist.github.com/661685:) has both the working and non- > > working version. > > 2)[https://gist.github.com/661680:](https://gist.github.com/661680:) has both the working and non- > > working version. I understand in this specific query a "should" clause > > is not there but I would assume "minimum\_number\_should\_match" should > > be ignored here. > > > Is this a bug or am I missing something? > > > Thanks > > Diptamay ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 3, 2010, 11:12pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/4 "2010-11-03T23:12:07Z")
I think I manage to see what you mean, and it does seem strange (unless I am missing something). Is there a chance that you can create a simple curl recreation, with simpler docs (2-3 fields)? You can probably extract them that from the relevant docs and then use similar/same question. I will have a look at it tomorrow. -shay.banon On Thu, Nov 4, 2010 at 12:44 AM, diptamay [diptamay@gmail.com](mailto:diptamay@gmail.com) wrote: > If you look at the queries that I attached, the only difference is the > working and the non-working version is the presence > minimum\_number\_should\_match and set to 1. Yes, I am expecting results > to be returned when its set. > > As an example, if one runs the queries in [https://gist.github.com/661685](https://gist.github.com/661685), > the results from either should return only one document, whose id is > 10990513, listed under [661688’s gists · GitHub](https://gist.github.com/661688). However, only > one of the queries (the working one) is returning the result, while > the resulting (or expected) document matches all the criteria set in > the non-working one as well. > > -Diptamay > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > I am not sure I managed to understad whats not working and working since > > its > > hard to understand if a certain query should match or not. If you set > > minimum\_number\_should\_match, it relates to the required number of > > should/optional clauses that will have to match. If you have not should > > clauses, and set it to a higher value, then no doc will match. Is it not > > working as expected? > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > Hi > > > > > I have this test datahttps://gist.github.com/661688, against which I > > > am running my test cases. > > > > > Here are the queries that I am firing. If you see the difference > > > between the working (returns results) versions and the non-working (no > > > results) ones, I am just adding "minimum\_number\_should\_match" : 1 to > > > the search clause: > > > 1)[https://gist.github.com/661685:](https://gist.github.com/661685:) has both the working and non- > > > working version. > > > 2)[https://gist.github.com/661680:](https://gist.github.com/661680:) has both the working and non- > > > working version. I understand in this specific query a "should" clause > > > is not there but I would assume "minimum\_number\_should\_match" should > > > be ignored here. > > > > > Is this a bug or am I missing something? > > > > > Thanks > > > Diptamay ---
**Author:** ![Diptamay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diptamay/32/2805_2.png) [@Diptamay](https://discuss.elastic.co/u/Diptamay)\ **Post date:** [November 3, 2010, 11:32pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/5 "2010-11-03T23:32:18Z")
Yep, will do. On Nov 3, 7:12 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > I think I manage to see what you mean, and it does seem strange (unless I am > missing something). Is there a chance that you can create a simple curl > recreation, with simpler docs (2-3 fields)? You can probably extract them > that from the relevant docs and then use similar/same question. I will have > a look at it tomorrow. > > -shay.banon > > On Thu, Nov 4, 2010 at 12:44 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > If you look at the queries that I attached, the only difference is the > > working and the non-working version is the presence > > minimum\_number\_should\_match and set to 1. Yes, I am expecting results > > to be returned when its set. > > > As an example, if one runs the queries inhttps://gist.github.com/661685, > > the results from either should return only one document, whose id is > > 10990513, listed underhttps://gist.github.com/661688. However, only > > one of the queries (the working one) is returning the result, while > > the resulting (or expected) document matches all the criteria set in > > the non-working one as well. > > > -Diptamay > > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > I am not sure I managed to understad whats not working and working since > > > its > > > hard to understand if a certain query should match or not. If you set > > > minimum\_number\_should\_match, it relates to the required number of > > > should/optional clauses that will have to match. If you have not should > > > clauses, and set it to a higher value, then no doc will match. Is it not > > > working as expected? > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > > > Hi > > > > > I have this test datahttps://gist.github.com/661688, against which I > > > > am running my test cases. > > > > > Here are the queries that I am firing. If you see the difference > > > > between the working (returns results) versions and the non-working (no > > > > results) ones, I am just adding "minimum\_number\_should\_match" : 1 to > > > > the search clause: > > > > 1)[https://gist.github.com/661685:has](https://gist.github.com/661685:has) both the working and non- > > > > working version. > > > > 2)[https://gist.github.com/661680:has](https://gist.github.com/661680:has) both the working and non- > > > > working version. I understand in this specific query a "should" clause > > > > is not there but I would assume "minimum\_number\_should\_match" should > > > > be ignored here. > > > > > Is this a bug or am I missing something? > > > > > Thanks > > > > Diptamay ---
**Author:** ![Diptamay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diptamay/32/2805_2.png) [@Diptamay](https://discuss.elastic.co/u/Diptamay)\ **Post date:** [November 4, 2010, 1:59am UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/6 "2010-11-04T01:59:54Z")
Hi Shay Please take checkout [GitHub - diptamay/es-issue: Sample code to communicate issues with ES](https://github.com/diptamay/es-issue) I have simplified the data quite a bit, though it isn't exactly 2-3 fields yet :). Please follow the readme to curl the data in and to run the queries. Thanks Diptamay On Nov 3, 7:12 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > I think I manage to see what you mean, and it does seem strange (unless I am > missing something). Is there a chance that you can create a simple curl > recreation, with simpler docs (2-3 fields)? You can probably extract them > that from the relevant docs and then use similar/same question. I will have > a look at it tomorrow. > > -shay.banon > > On Thu, Nov 4, 2010 at 12:44 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > If you look at the queries that I attached, the only difference is the > > working and the non-working version is the presence > > minimum\_number\_should\_match and set to 1. Yes, I am expecting results > > to be returned when its set. > > > As an example, if one runs the queries inhttps://gist.github.com/661685, > > the results from either should return only one document, whose id is > > 10990513, listed underhttps://gist.github.com/661688. However, only > > one of the queries (the working one) is returning the result, while > > the resulting (or expected) document matches all the criteria set in > > the non-working one as well. > > > -Diptamay > > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > I am not sure I managed to understad whats not working and working since > > > its > > > hard to understand if a certain query should match or not. If you set > > > minimum\_number\_should\_match, it relates to the required number of > > > should/optional clauses that will have to match. If you have not should > > > clauses, and set it to a higher value, then no doc will match. Is it not > > > working as expected? > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > > > Hi > > > > > I have this test datahttps://gist.github.com/661688, against which I > > > > am running my test cases. > > > > > Here are the queries that I am firing. If you see the difference > > > > between the working (returns results) versions and the non-working (no > > > > results) ones, I am just adding "minimum\_number\_should\_match" : 1 to > > > > the search clause: > > > > 1)[https://gist.github.com/661685:has](https://gist.github.com/661685:has) both the working and non- > > > > working version. > > > > 2)[https://gist.github.com/661680:has](https://gist.github.com/661680:has) both the working and non- > > > > working version. I understand in this specific query a "should" clause > > > > is not there but I would assume "minimum\_number\_should\_match" should > > > > be ignored here. > > > > > Is this a bug or am I missing something? > > > > > Thanks > > > > Diptamay ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 4, 2010, 9:10am UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/7 "2010-11-04T09:10:58Z")
Hi, ran the test, seems to work for me. This [https://github.com/diptamay/es-issue/blob/master/not\_working.sh](https://github.com/diptamay/es-issue/blob/master/not_working.sh) script, The first curl search request returns a single result, which is good. And matches the same one in matching. This is because the should clause does produce a single match, so having it required by setting the minimum should match to 1 is good. the second one does not return a result, simply because there are no should clauses, and you specify that there should be at least one that should match, so, no results... . (ran this on 0.12.1). -shay.banon On Thu, Nov 4, 2010 at 3:59 AM, diptamay [diptamay@gmail.com](mailto:diptamay@gmail.com) wrote: > Hi Shay > > Please take checkout [GitHub - diptamay/es-issue: Sample code to communicate issues with ES](https://github.com/diptamay/es-issue) > > I have simplified the data quite a bit, though it isn't exactly 2-3 > fields yet :). Please follow the readme to curl the data in and to run > the queries. > > Thanks > Diptamay > > On Nov 3, 7:12 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > I think I manage to see what you mean, and it does seem strange (unless I > > am > > missing something). Is there a chance that you can create a simple curl > > recreation, with simpler docs (2-3 fields)? You can probably extract them > > that from the relevant docs and then use similar/same question. I will > > have > > a look at it tomorrow. > > > > -shay.banon > > > > On Thu, Nov 4, 2010 at 12:44 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > If you look at the queries that I attached, the only difference is the > > > working and the non-working version is the presence > > > minimum\_number\_should\_match and set to 1. Yes, I am expecting results > > > to be returned when its set. > > > > > As an example, if one runs the queries inhttps:// > > > [gist.github.com/661685](http://gist.github.com/661685), > > > the results from either should return only one document, whose id is > > > 10990513, listed underhttps://gist.github.com/661688. However, only > > > one of the queries (the working one) is returning the result, while > > > the resulting (or expected) document matches all the criteria set in > > > the non-working one as well. > > > > > -Diptamay > > > > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > > > I am not sure I managed to understad whats not working and working > > > > since > > > > its > > > > hard to understand if a certain query should match or not. If you set > > > > minimum\_number\_should\_match, it relates to the required number of > > > > should/optional clauses that will have to match. If you have not > > > > should > > > > clauses, and set it to a higher value, then no doc will match. Is it > > > > not > > > > working as expected? > > > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) > > > > wrote: > > > > > > > > > Hi > > > > > > > I have this test datahttps://gist.github.com/661688, against which > > > > > I > > > > > am running my test cases. > > > > > > > Here are the queries that I am firing. If you see the difference > > > > > between the working (returns results) versions and the non-working > > > > > (no > > > > > results) ones, I am just adding "minimum\_number\_should\_match" : 1 > > > > > to > > > > > the search clause: > > > > > 1)[https://gist.github.com/661685:has](https://gist.github.com/661685:has) both the working and non- > > > > > working version. > > > > > 2)[https://gist.github.com/661680:has](https://gist.github.com/661680:has) both the working and non- > > > > > working version. I understand in this specific query a "should" > > > > > clause > > > > > is not there but I would assume "minimum\_number\_should\_match" > > > > > should > > > > > be ignored here. > > > > > > > Is this a bug or am I missing something? > > > > > > > Thanks > > > > > Diptamay ---
**Author:** ![Diptamay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diptamay/32/2805_2.png) [@Diptamay](https://discuss.elastic.co/u/Diptamay)\ **Post date:** [November 4, 2010, 3:15pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/8 "2010-11-04T15:15:54Z")
Hi Don't know what to tell you :). This just wasn't working for me yesterday. Today, the thing I did was delete my snapshots folder, making this a completely clean run and it started working for me then in the first run. Earlier, I was indexing/deleting/searching through the REST api. But then, I thought, how could I still reproduce it. So this is reproducible, not consistently though. Please take the latest from [git@github.com](mailto:git@github.com):diptamay/es-issue.git Then, run ./automate.sh a) This will create an es-test index and load the sample data. b) Then it fire ./not\_working.sh to run the query which is not working always. c) It will then delete the documents. This will run in an infinite loop, unless you stop it. You will see that the search is inconsistent and sometimes it returns the results and sometimes not. Thanks for looking into it. -Diptamay On Nov 4, 5:10 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > Hi, ran the test, seems to work for me. Thishttps://github.com/diptamay/es-issue/blob/master/not\_working.shscript, > > The first curl search request returns a single result, which is good. And > matches the same one in matching. This is because the should clause does > produce a single match, so having it required by setting the minimum should > match to 1 is good. > > the second one does not return a result, simply because there are no should > clauses, and you specify that there should be at least one that should > match, so, no results... . > > (ran this on 0.12.1). > > -shay.banon > > On Thu, Nov 4, 2010 at 3:59 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > Hi Shay > > > Please take checkouthttps://github.com/diptamay/es-issue > > > I have simplified the data quite a bit, though it isn't exactly 2-3 > > fields yet :). Please follow the readme to curl the data in and to run > > the queries. > > > Thanks > > Diptamay > > > On Nov 3, 7:12 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > I think I manage to see what you mean, and it does seem strange (unless I > > > am > > > missing something). Is there a chance that you can create a simple curl > > > recreation, with simpler docs (2-3 fields)? You can probably extract them > > > that from the relevant docs and then use similar/same question. I will > > > have > > > a look at it tomorrow. > > > > -shay.banon > > > > On Thu, Nov 4, 2010 at 12:44 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > > > If you look at the queries that I attached, the only difference is the > > > > working and the non-working version is the presence > > > > minimum\_number\_should\_match and set to 1. Yes, I am expecting results > > > > to be returned when its set. > > > > > As an example, if one runs the queries inhttps:// > > > > [gist.github.com/661685](http://gist.github.com/661685), > > > > the results from either should return only one document, whose id is > > > > 10990513, listed underhttps://gist.github.com/661688. However, only > > > > one of the queries (the working one) is returning the result, while > > > > the resulting (or expected) document matches all the criteria set in > > > > the non-working one as well. > > > > > -Diptamay > > > > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > > > > > I am not sure I managed to understad whats not working and working > > > > > since > > > > > its > > > > > hard to understand if a certain query should match or not. If you set > > > > > minimum\_number\_should\_match, it relates to the required number of > > > > > should/optional clauses that will have to match. If you have not > > > > > should > > > > > clauses, and set it to a higher value, then no doc will match. Is it > > > > > not > > > > > working as expected? > > > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) > > > > > wrote: > > > > > > > > > > > Hi > > > > > > > I have this test datahttps://gist.github.com/661688, against which > > > > > > I > > > > > > am running my test cases. > > > > > > > Here are the queries that I am firing. If you see the difference > > > > > > between the working (returns results) versions and the non-working > > > > > > (no > > > > > > results) ones, I am just adding "minimum\_number\_should\_match" : 1 > > > > > > to > > > > > > the search clause: > > > > > > 1)[https://gist.github.com/661685:hasboth](https://gist.github.com/661685:hasboth) the working and non- > > > > > > working version. > > > > > > 2)[https://gist.github.com/661680:hasboth](https://gist.github.com/661680:hasboth) the working and non- > > > > > > working version. I understand in this specific query a "should" > > > > > > clause > > > > > > is not there but I would assume "minimum\_number\_should\_match" > > > > > > should > > > > > > be ignored here. > > > > > > > Is this a bug or am I missing something? > > > > > > > Thanks > > > > > > Diptamay ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 4, 2010, 6:10pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/9 "2010-11-04T18:10:44Z")
Hi, Before I run it, have you factored in the fact that elasticsearch is near real time? Can you try and execute a refresh before you search and see if it happens? -shay.banon On Thu, Nov 4, 2010 at 5:15 PM, diptamay [diptamay@gmail.com](mailto:diptamay@gmail.com) wrote: > Hi > > Don't know what to tell you :). This just wasn't working for me > yesterday. Today, the thing I did was delete my snapshots folder, > making this a completely clean run and it started working for me then > in the first run. Earlier, I was indexing/deleting/searching through > the REST api. > > But then, I thought, how could I still reproduce it. So this is > reproducible, not consistently though. Please take the latest from > [git@github.com](mailto:git@github.com):diptamay/es-issue.git > Then, run ./automate.sh > a) This will create an es-test index and load the sample data. > b) Then it fire ./not\_working.sh to run the query which is not > working always. > c) It will then delete the documents. > This will run in an infinite loop, unless you stop it. You will see > that the search is inconsistent and sometimes it returns the results > and sometimes not. > > Thanks for looking into it. > > -Diptamay > > On Nov 4, 5:10 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > Hi, ran the test, seems to work for me. Thishttps:// > > [github.com/diptamay/es-issue/blob/master/not\_working.shscript](http://github.com/diptamay/es-issue/blob/master/not_working.shscript), > > > > The first curl search request returns a single result, which is good. And > > matches the same one in matching. This is because the should clause does > > produce a single match, so having it required by setting the minimum > > should > > match to 1 is good. > > > > the second one does not return a result, simply because there are no > > should > > clauses, and you specify that there should be at least one that should > > match, so, no results... . > > > > (ran this on 0.12.1). > > > > -shay.banon > > > > On Thu, Nov 4, 2010 at 3:59 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > Hi Shay > > > > > Please take checkouthttps://github.com/diptamay/es-issue > > > > > I have simplified the data quite a bit, though it isn't exactly 2-3 > > > fields yet :). Please follow the readme to curl the data in and to run > > > the queries. > > > > > Thanks > > > Diptamay > > > > > On Nov 3, 7:12 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > > > I think I manage to see what you mean, and it does seem strange > > > > (unless I > > > > am > > > > missing something). Is there a chance that you can create a simple > > > > curl > > > > recreation, with simpler docs (2-3 fields)? You can probably extract > > > > them > > > > that from the relevant docs and then use similar/same question. I > > > > will > > > > have > > > > a look at it tomorrow. > > > > > > -shay.banon > > > > > > On Thu, Nov 4, 2010 at 12:44 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) > > > > wrote: > > > > > > > > > If you look at the queries that I attached, the only difference is > > > > > the > > > > > working and the non-working version is the presence > > > > > minimum\_number\_should\_match and set to 1. Yes, I am expecting > > > > > results > > > > > to be returned when its set. > > > > > > > As an example, if one runs the queries inhttps:// > > > > > [gist.github.com/661685](http://gist.github.com/661685), > > > > > the results from either should return only one document, whose id > > > > > is > > > > > 10990513, listed underhttps://gist.github.com/661688. However, > > > > > only > > > > > one of the queries (the working one) is returning the result, while > > > > > the resulting (or expected) document matches all the criteria set > > > > > in > > > > > the non-working one as well. > > > > > > > -Diptamay > > > > > > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) > > > > > wrote: > > > > > > > > > > > I am not sure I managed to understad whats not working and > > > > > > working > > > > > > since > > > > > > its > > > > > > hard to understand if a certain query should match or not. If you > > > > > > set > > > > > > minimum\_number\_should\_match, it relates to the required number of > > > > > > should/optional clauses that will have to match. If you have not > > > > > > should > > > > > > clauses, and set it to a higher value, then no doc will match. Is > > > > > > it > > > > > > not > > > > > > working as expected? > > > > > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) > > > > > > wrote: > > > > > > > > > > > > > Hi > > > > > > > > > I have this test datahttps://gist.github.com/661688, against > > > > > > > which > > > > > > > I > > > > > > > am running my test cases. > > > > > > > > > Here are the queries that I am firing. If you see the > > > > > > > difference > > > > > > > between the working (returns results) versions and the > > > > > > > non-working > > > > > > > (no > > > > > > > results) ones, I am just adding "minimum\_number\_should\_match" : > > > > > > > 1 > > > > > > > to > > > > > > > the search clause: > > > > > > > 1)[https://gist.github.com/661685:hasboth](https://gist.github.com/661685:hasboth) the working and non- > > > > > > > working version. > > > > > > > 2)[https://gist.github.com/661680:hasboth](https://gist.github.com/661680:hasboth) the working and non- > > > > > > > working version. I understand in this specific query a "should" > > > > > > > clause > > > > > > > is not there but I would assume "minimum\_number\_should\_match" > > > > > > > should > > > > > > > be ignored here. > > > > > > > > > Is this a bug or am I missing something? > > > > > > > > > Thanks > > > > > > > Diptamay ---
**Author:** ![Diptamay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diptamay/32/2805_2.png) [@Diptamay](https://discuss.elastic.co/u/Diptamay)\ **Post date:** [November 4, 2010, 6:32pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/10 "2010-11-04T18:32:32Z")
Hi My bad. Sorry about that. Seems the refresh makes it work consistently. Whats the default time set for the refresh to take place? Thanks Diptamay On Nov 4, 2:10 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > Hi, > > Before I run it, have you factored in the fact that elasticsearch is near > real time? Can you try and execute a refresh before you search and see if it > happens? > > -shay.banon > > On Thu, Nov 4, 2010 at 5:15 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > Hi > > > Don't know what to tell you :). This just wasn't working for me > > yesterday. Today, the thing I did was delete my snapshots folder, > > making this a completely clean run and it started working for me then > > in the first run. Earlier, I was indexing/deleting/searching through > > the REST api. > > > But then, I thought, how could I still reproduce it. So this is > > reproducible, not consistently though. Please take the latest from > > [g...@github.com](mailto:g...@github.com):diptamay/es-issue.git > > Then, run ./automate.sh > > a) This will create an es-test index and load the sample data. > > b) Then it fire ./not\_working.sh to run the query which is not > > working always. > > c) It will then delete the documents. > > This will run in an infinite loop, unless you stop it. You will see > > that the search is inconsistent and sometimes it returns the results > > and sometimes not. > > > Thanks for looking into it. > > > -Diptamay > > > On Nov 4, 5:10 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > Hi, ran the test, seems to work for me. Thishttps:// > > > [github.com/diptamay/es-issue/blob/master/not\_working.shscript](http://github.com/diptamay/es-issue/blob/master/not_working.shscript), > > > > The first curl search request returns a single result, which is good. And > > > matches the same one in matching. This is because the should clause does > > > produce a single match, so having it required by setting the minimum > > > should > > > match to 1 is good. > > > > the second one does not return a result, simply because there are no > > > should > > > clauses, and you specify that there should be at least one that should > > > match, so, no results... . > > > > (ran this on 0.12.1). > > > > -shay.banon > > > > On Thu, Nov 4, 2010 at 3:59 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > > > Hi Shay > > > > > Please take checkouthttps://github.com/diptamay/es-issue > > > > > I have simplified the data quite a bit, though it isn't exactly 2-3 > > > > fields yet :). Please follow the readme to curl the data in and to run > > > > the queries. > > > > > Thanks > > > > Diptamay > > > > > On Nov 3, 7:12 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > > > > > I think I manage to see what you mean, and it does seem strange > > > > > (unless I > > > > > am > > > > > missing something). Is there a chance that you can create a simple > > > > > curl > > > > > recreation, with simpler docs (2-3 fields)? You can probably extract > > > > > them > > > > > that from the relevant docs and then use similar/same question. I > > > > > will > > > > > have > > > > > a look at it tomorrow. > > > > > > -shay.banon > > > > > > On Thu, Nov 4, 2010 at 12:44 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) > > > > > wrote: > > > > > > > > > > > If you look at the queries that I attached, the only difference is > > > > > > the > > > > > > working and the non-working version is the presence > > > > > > minimum\_number\_should\_match and set to 1. Yes, I am expecting > > > > > > results > > > > > > to be returned when its set. > > > > > > > As an example, if one runs the queries inhttps:// > > > > > > [gist.github.com/661685](http://gist.github.com/661685), > > > > > > the results from either should return only one document, whose id > > > > > > is > > > > > > 10990513, listed underhttps://gist.github.com/661688. However, > > > > > > only > > > > > > one of the queries (the working one) is returning the result, while > > > > > > the resulting (or expected) document matches all the criteria set > > > > > > in > > > > > > the non-working one as well. > > > > > > > -Diptamay > > > > > > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) > > > > > > wrote: > > > > > > > > > > > > > I am not sure I managed to understad whats not working and > > > > > > > working > > > > > > > since > > > > > > > its > > > > > > > hard to understand if a certain query should match or not. If you > > > > > > > set > > > > > > > minimum\_number\_should\_match, it relates to the required number of > > > > > > > should/optional clauses that will have to match. If you have not > > > > > > > should > > > > > > > clauses, and set it to a higher value, then no doc will match. Is > > > > > > > it > > > > > > > not > > > > > > > working as expected? > > > > > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) > > > > > > > wrote: > > > > > > > > > > > > > > > Hi > > > > > > > > > I have this test datahttps://gist.github.com/661688, against > > > > > > > > which > > > > > > > > I > > > > > > > > am running my test cases. > > > > > > > > > Here are the queries that I am firing. If you see the > > > > > > > > difference > > > > > > > > between the working (returns results) versions and the > > > > > > > > non-working > > > > > > > > (no > > > > > > > > results) ones, I am just adding "minimum\_number\_should\_match" : > > > > > > > > 1 > > > > > > > > to > > > > > > > > the search clause: > > > > > > > > 1)[https://gist.github.com/661685:hasboththe](https://gist.github.com/661685:hasboththe) working and non- > > > > > > > > working version. > > > > > > > > 2)[https://gist.github.com/661680:hasboththe](https://gist.github.com/661680:hasboththe) working and non- > > > > > > > > working version. I understand in this specific query a "should" > > > > > > > > clause > > > > > > > > is not there but I would assume "minimum\_number\_should\_match" > > > > > > > > should > > > > > > > > be ignored here. > > > > > > > > > Is this a bug or am I missing something? > > > > > > > > > Thanks > > > > > > > > Diptamay ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 4, 2010, 6:39pm UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/11 "2010-11-04T18:39:51Z")
Its set by default to 1 second. cheers, -shay.banon On Thu, Nov 4, 2010 at 8:32 PM, diptamay [diptamay@gmail.com](mailto:diptamay@gmail.com) wrote: > Hi > > My bad. Sorry about that. Seems the refresh makes it work > consistently. Whats the default time set for the refresh to take > place? > > Thanks > Diptamay > > On Nov 4, 2:10 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > Hi, > > > > Before I run it, have you factored in the fact that elasticsearch is > > near > > real time? Can you try and execute a refresh before you search and see if > > it > > happens? > > > > -shay.banon > > > > On Thu, Nov 4, 2010 at 5:15 PM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > Hi > > > > > Don't know what to tell you :). This just wasn't working for me > > > yesterday. Today, the thing I did was delete my snapshots folder, > > > making this a completely clean run and it started working for me then > > > in the first run. Earlier, I was indexing/deleting/searching through > > > the REST api. > > > > > But then, I thought, how could I still reproduce it. So this is > > > reproducible, not consistently though. Please take the latest from > > > [g...@github.com](mailto:g...@github.com):diptamay/es-issue.git > > > Then, run ./automate.sh > > > a) This will create an es-test index and load the sample data. > > > b) Then it fire ./not\_working.sh to run the query which is not > > > working always. > > > c) It will then delete the documents. > > > This will run in an infinite loop, unless you stop it. You will see > > > that the search is inconsistent and sometimes it returns the results > > > and sometimes not. > > > > > Thanks for looking into it. > > > > > -Diptamay > > > > > On Nov 4, 5:10 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > > > Hi, ran the test, seems to work for me. Thishttps:// > > > > [github.com/diptamay/es-issue/blob/master/not\_working.shscript](http://github.com/diptamay/es-issue/blob/master/not_working.shscript), > > > > > > The first curl search request returns a single result, which is good. > > > > And > > > > matches the same one in matching. This is because the should clause > > > > does > > > > produce a single match, so having it required by setting the minimum > > > > should > > > > match to 1 is good. > > > > > > the second one does not return a result, simply because there are no > > > > should > > > > clauses, and you specify that there should be at least one that > > > > should > > > > match, so, no results... . > > > > > > (ran this on 0.12.1). > > > > > > -shay.banon > > > > > > On Thu, Nov 4, 2010 at 3:59 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) wrote: > > > > > > > > > Hi Shay > > > > > > > Please take checkouthttps://github.com/diptamay/es-issue > > > > > > > I have simplified the data quite a bit, though it isn't exactly 2-3 > > > > > fields yet :). Please follow the readme to curl the data in and to > > > > > run > > > > > the queries. > > > > > > > Thanks > > > > > Diptamay > > > > > > > On Nov 3, 7:12 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) > > > > > wrote: > > > > > > > > > > > I think I manage to see what you mean, and it does seem strange > > > > > > (unless I > > > > > > am > > > > > > missing something). Is there a chance that you can create a > > > > > > simple > > > > > > curl > > > > > > recreation, with simpler docs (2-3 fields)? You can probably > > > > > > extract > > > > > > them > > > > > > that from the relevant docs and then use similar/same question. I > > > > > > will > > > > > > have > > > > > > a look at it tomorrow. > > > > > > > > -shay.banon > > > > > > > > On Thu, Nov 4, 2010 at 12:44 AM, diptamay [dipta...@gmail.com](mailto:dipta...@gmail.com) > > > > > > wrote: > > > > > > > > > > > > > If you look at the queries that I attached, the only difference > > > > > > > is > > > > > > > the > > > > > > > working and the non-working version is the presence > > > > > > > minimum\_number\_should\_match and set to 1. Yes, I am expecting > > > > > > > results > > > > > > > to be returned when its set. > > > > > > > > > As an example, if one runs the queries inhttps:// > > > > > > > [gist.github.com/661685](http://gist.github.com/661685), > > > > > > > the results from either should return only one document, whose > > > > > > > id > > > > > > > is > > > > > > > 10990513, listed underhttps://gist.github.com/661688. However, > > > > > > > only > > > > > > > one of the queries (the working one) is returning the result, > > > > > > > while > > > > > > > the resulting (or expected) document matches all the criteria > > > > > > > set > > > > > > > in > > > > > > > the non-working one as well. > > > > > > > > > -Diptamay > > > > > > > > > On Nov 3, 6:24 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) > > > > > > > wrote: > > > > > > > > > > > > > > > I am not sure I managed to understad whats not working and > > > > > > > > working > > > > > > > > since > > > > > > > > its > > > > > > > > hard to understand if a certain query should match or not. If > > > > > > > > you > > > > > > > > set > > > > > > > > minimum\_number\_should\_match, it relates to the required > > > > > > > > number of > > > > > > > > should/optional clauses that will have to match. If you have > > > > > > > > not > > > > > > > > should > > > > > > > > clauses, and set it to a higher value, then no doc will > > > > > > > > match. Is > > > > > > > > it > > > > > > > > not > > > > > > > > working as expected? > > > > > > > > > > On Wed, Nov 3, 2010 at 10:57 PM, diptamay \< > > > > > > > > [dipta...@gmail.com](mailto:dipta...@gmail.com)\> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > I have this test datahttps://gist.github.com/661688, > > > > > > > > > against > > > > > > > > > which > > > > > > > > > I > > > > > > > > > am running my test cases. > > > > > > > > > > > Here are the queries that I am firing. If you see the > > > > > > > > > difference > > > > > > > > > between the working (returns results) versions and the > > > > > > > > > non-working > > > > > > > > > (no > > > > > > > > > results) ones, I am just adding > > > > > > > > > "minimum\_number\_should\_match" : > > > > > > > > > 1 > > > > > > > > > to > > > > > > > > > the search clause: > > > > > > > > > 1)[https://gist.github.com/661685:hasboththe](https://gist.github.com/661685:hasboththe) working and > > > > > > > > > non- > > > > > > > > > working version. > > > > > > > > > 2)[https://gist.github.com/661680:hasboththe](https://gist.github.com/661680:hasboththe) working and > > > > > > > > > non- > > > > > > > > > working version. I understand in this specific query a > > > > > > > > > "should" > > > > > > > > > clause > > > > > > > > > is not there but I would assume > > > > > > > > > "minimum\_number\_should\_match" > > > > > > > > > should > > > > > > > > > be ignored here. > > > > > > > > > > > Is this a bug or am I missing something? > > > > > > > > > > > Thanks > > > > > > > > > Diptamay ---
**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, 4:17am UTC](https://discuss.elastic.co/t/bug-with-minimum-number-should-match-or-is-this-incorrect-usage/3512/12 "2017-07-06T04:17:10Z")