# Possible Bug? Percolator still matching deleted queries **URL:** \ **Category:** Elasticsearch\ **Created:** [January 25, 2012, 2:18pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494 "2012-01-25T14:18:48Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Onilton\_Maciel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/onilton_maciel/32/2500_2.png) [@Onilton\_Maciel](https://discuss.elastic.co/u/Onilton_Maciel)\ **Post date:** [January 25, 2012, 2:18pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/1 "2012-01-25T14:18:48Z")
I'm using elastic search 0.17.6 and percolator. The problem happens when I delete the \_percolator for an index . Then when I run a document through percolate, percolate still return the ids of the queries that were supposed to be deleted, even when I deleted the whole \_percolator index. If I restart elastic search everything works fine. Step by Step to reproduce: Create percolator queries setting an id (mine is incremental) Percolate a document (it works) Delete all the \_percolator index. Percolate a document (it returns deleted queries) Restart elastic search Percolate a document (works again) Not sure if this happens only when deleting all the \_percolator index or happens for any percolator deleted query. Is this a bug, or something meant to be this way? ---
**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:** [January 25, 2012, 4:44pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/2 "2012-01-25T16:44:57Z")
Can you gist a curl recreation of it? Verify that it still happens on latest (0.18.7). See how here: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/help). On Wednesday, January 25, 2012 at 4:18 PM, Onilton Maciel wrote: > I'm using Elasticsearch 0.17.6 and percolator. > > The problem happens when I delete the \_percolator for an index . Then > when I run a document through percolate, percolate still return the > ids of the queries that were supposed to be deleted, even when I > deleted the whole \_percolator index. > > If I restart Elasticsearch everything works fine. > > Step by Step to reproduce: > Create percolator queries setting an id (mine is incremental) > Percolate a document (it works) > Delete all the \_percolator index. > Percolate a document (it returns deleted queries) > Restart Elasticsearch > Percolate a document (works again) > > Not sure if this happens only when deleting all the \_percolator index > or happens for any percolator deleted query. > > Is this a bug, or something meant to be this way? ---
**Author:** ![Onilton\_Maciel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/onilton_maciel/32/2500_2.png) [@Onilton\_Maciel](https://discuss.elastic.co/u/Onilton_Maciel)\ **Post date:** [January 25, 2012, 7:45pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/3 "2012-01-25T19:45:42Z")
Ok, now I am using 0.18.7 I was able to narrow down the error: The error doesn't happen when I delete the queries one by one. It only happens when you delete the percolator index itself for a index. This is the gist: > On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > Can you gist a curl recreation of it? Verify that it still happens on > latest (0.18.7). See how here: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/help). > > On Wednesday, January 25, 2012 at 4:18 PM, Onilton Maciel wrote: > > I'm using Elasticsearch 0.17.6 and percolator. > > The problem happens when I delete the \_percolator for an index . Then > when I run a document through percolate, percolate still return the > ids of the queries that were supposed to be deleted, even when I > deleted the whole \_percolator index. > > If I restart Elasticsearch everything works fine. > > Step by Step to reproduce: > Create percolator queries setting an id (mine is incremental) > Percolate a document (it works) > Delete all the \_percolator index. > Percolate a document (it returns deleted queries) > Restart Elasticsearch > Percolate a document (works again) > > Not sure if this happens only when deleting all the \_percolator index > or happens for any percolator deleted query. > > Is this a bug, or something meant to be this way? ---
**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:** [January 25, 2012, 9:53pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/4 "2012-01-25T21:53:31Z")
Yea, it looks like a bug, where delete by query does not properly refresh the parsed queries to percolate, open an issue? On Wednesday, January 25, 2012 at 9:45 PM, Onilton Maciel wrote: > Ok, now I am using 0.18.7 > > I was able to narrow down the error: > > The error doesn't happen when I delete the queries one by one. > > It only happens when you delete the percolator index itself for a index. > > This is the gist: > > [Reproduce possible percolator bug · GitHub](https://gist.github.com/1678150) > > On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon \<[kimchy@gmail.com](mailto:kimchy@gmail.com) ([mailto:kimchy@gmail.com](mailto:kimchy@gmail.com))\> wrote: > > > Can you gist a curl recreation of it? Verify that it still happens on latest (0.18.7). See how here: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/help). > > > > On Wednesday, January 25, 2012 at 4:18 PM, Onilton Maciel wrote: > > > > > I'm using Elasticsearch 0.17.6 and percolator. > > > > > > The problem happens when I delete the \_percolator for an index . Then > > > when I run a document through percolate, percolate still return the > > > ids of the queries that were supposed to be deleted, even when I > > > deleted the whole \_percolator index. > > > > > > If I restart Elasticsearch everything works fine. > > > > > > Step by Step to reproduce: > > > Create percolator queries setting an id (mine is incremental) > > > Percolate a document (it works) > > > Delete all the \_percolator index. > > > Percolate a document (it returns deleted queries) > > > Restart Elasticsearch > > > Percolate a document (works again) > > > > > > Not sure if this happens only when deleting all the \_percolator index > > > or happens for any percolator deleted query. > > > > > > Is this a bug, or something meant to be this way? ---
**Author:** ![Tim\_J](https://avatars.discourse-cdn.com/v4/letter/t/f17d59/32.png) [@Tim\_J](https://discuss.elastic.co/u/Tim_J)\ **Post date:** [February 16, 2012, 7:54pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/5 "2012-02-16T19:54:25Z")
Anyone know if a bug was actually created for this issue? I've been unable to turn up anything like it in the issue list. Thanks, -Tim On Jan 25, 4:53 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > Yea, it looks like a bug, where delete by query does not properly refresh the parsed queries to percolate, open an issue? > > On Wednesday, January 25, 2012 at 9:45 PM, Onilton Maciel wrote: > > > Ok, now I am using 0.18.7 > > > I was able to narrow down the error: > > > The error doesn't happen when I delete the queries one by one. > > > It only happens when you delete the percolator index itself for a index. > > > This is the gist: > > > [Reproduce possible percolator bug · GitHub](https://gist.github.com/1678150) > > > On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon \<[kim...@gmail.com](mailto:kim...@gmail.com) ([mailto:kim...@gmail.com](mailto:kim...@gmail.com))\> wrote: > > > > > Can you gist a curl recreation of it? Verify that it still happens on latest (0.18.7). See how here:[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/help). > > > > On Wednesday, January 25, 2012 at 4:18 PM, Onilton Maciel wrote: > > > > > I'm using Elasticsearch 0.17.6 and percolator. > > > > > The problem happens when I delete the \_percolator for an index . Then > > > > when I run a document through percolate, percolate still return the > > > > ids of the queries that were supposed to be deleted, even when I > > > > deleted the whole \_percolator index. > > > > > If I restart Elasticsearch everything works fine. > > > > > Step by Step to reproduce: > > > > Create percolator queries setting an id (mine is incremental) > > > > Percolate a document (it works) > > > > Delete all the \_percolator index. > > > > Percolate a document (it returns deleted queries) > > > > Restart Elasticsearch > > > > Percolate a document (works again) > > > > > Not sure if this happens only when deleting all the \_percolator index > > > > or happens for any percolator deleted query. > > > > > Is this a bug, or something meant to be this way? ---
**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:** [February 16, 2012, 8:22pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/6 "2012-02-16T20:22:41Z")
I don't think an issue was opened. On Wednesday, January 25, 2012 at 9:45 PM, Onilton Maciel wrote: > Ok, now I am using 0.18.7 > > I was able to narrow down the error: > > The error doesn't happen when I delete the queries one by one. > > It only happens when you delete the percolator index itself for a index. > > This is the gist: > > [Reproduce possible percolator bug · GitHub](https://gist.github.com/1678150) > > On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon \<[kimchy@gmail.com](mailto:kimchy@gmail.com) ([mailto:kimchy@gmail.com](mailto:kimchy@gmail.com))\> wrote: > > > Can you gist a curl recreation of it? Verify that it still happens on latest (0.18.7). See how here: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/help). > > > > On Wednesday, January 25, 2012 at 4:18 PM, Onilton Maciel wrote: > > > > > I'm using Elasticsearch 0.17.6 and percolator. > > > > > > The problem happens when I delete the \_percolator for an index . Then > > > when I run a document through percolate, percolate still return the > > > ids of the queries that were supposed to be deleted, even when I > > > deleted the whole \_percolator index. > > > > > > If I restart Elasticsearch everything works fine. > > > > > > Step by Step to reproduce: > > > Create percolator queries setting an id (mine is incremental) > > > Percolate a document (it works) > > > Delete all the \_percolator index. > > > Percolate a document (it returns deleted queries) > > > Restart Elasticsearch > > > Percolate a document (works again) > > > > > > Not sure if this happens only when deleting all the \_percolator index > > > or happens for any percolator deleted query. > > > > > > Is this a bug, or something meant to be this way? ---
**Author:** ![Onilton\_Maciel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/onilton_maciel/32/2500_2.png) [@Onilton\_Maciel](https://discuss.elastic.co/u/Onilton_Maciel)\ **Post date:** [February 16, 2012, 9:51pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/7 "2012-02-16T21:51:41Z")
I forgot to open an issue. Now here it is: > > > The error doesn't happen when I delete the queries one by one. > > It only happens …when you delete the percolator index itself for a index. > > Gist for reproducing the error: > > https://gist.github.com/1678150 On Thu, Feb 16, 2012 at 4:22 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > I don't think an issue was opened. > > On Wednesday, January 25, 2012 at 9:45 PM, Onilton Maciel wrote: > > Ok, now I am using 0.18.7 > > I was able to narrow down the error: > > The error doesn't happen when I delete the queries one by one. > > It only happens when you delete the percolator index itself for a index. > > This is the gist: > > [Reproduce possible percolator bug · GitHub](https://gist.github.com/1678150) > > On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > Can you gist a curl recreation of it? Verify that it still happens on > latest (0.18.7). See how here: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/help). > > On Wednesday, January 25, 2012 at 4:18 PM, Onilton Maciel wrote: > > I'm using Elasticsearch 0.17.6 and percolator. > > The problem happens when I delete the \_percolator for an index . Then > when I run a document through percolate, percolate still return the > ids of the queries that were supposed to be deleted, even when I > deleted the whole \_percolator index. > > If I restart Elasticsearch everything works fine. > > Step by Step to reproduce: > Create percolator queries setting an id (mine is incremental) > Percolate a document (it works) > Delete all the \_percolator index. > Percolate a document (it returns deleted queries) > Restart Elasticsearch > Percolate a document (works again) > > Not sure if this happens only when deleting all the \_percolator index > or happens for any percolator deleted query. > > Is this a bug, or something meant to be this way? ---
**Author:** ![Tim\_J](https://avatars.discourse-cdn.com/v4/letter/t/f17d59/32.png) [@Tim\_J](https://discuss.elastic.co/u/Tim_J)\ **Post date:** [February 17, 2012, 3:36pm UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/8 "2012-02-17T15:36:08Z")
Much appreciated! On Feb 16, 4:51 pm, Onilton Maciel [oniltonmac...@gmail.com](mailto:oniltonmac...@gmail.com) wrote: > I forgot to open an issue. > > Now here it is: > > [Percolators: Support delete-by-query · Issue #1712 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1712) > > On Thu, Feb 16, 2012 at 4:22 PM, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > I don't think an issue was opened. > > > On Wednesday, January 25, 2012 at 9:45 PM, Onilton Maciel wrote: > > > Ok, now I am using 0.18.7 > > > I was able to narrow down the error: > > > The error doesn't happen when I delete the queries one by one. > > > It only happens when you delete the percolator index itself for a index. > > > This is the gist: > > > [Reproduce possible percolator bug · GitHub](https://gist.github.com/1678150) > > > On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > Can you gist a curl recreation of it? Verify that it still happens on > > latest (0.18.7). See how here:[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/help). > > > On Wednesday, January 25, 2012 at 4:18 PM, Onilton Maciel wrote: > > > I'm using Elasticsearch 0.17.6 and percolator. > > > The problem happens when I delete the \_percolator for an index . Then > > when I run a document through percolate, percolate still return the > > ids of the queries that were supposed to be deleted, even when I > > deleted the whole \_percolator index. > > > If I restart Elasticsearch everything works fine. > > > Step by Step to reproduce: > > Create percolator queries setting an id (mine is incremental) > > Percolate a document (it works) > > Delete all the \_percolator index. > > Percolate a document (it returns deleted queries) > > Restart Elasticsearch > > Percolate a document (works again) > > > Not sure if this happens only when deleting all the \_percolator index > > or happens for any percolator deleted query. > > > Is this a bug, or something meant to be this way? ---
**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, 3:38am UTC](https://discuss.elastic.co/t/possible-bug-percolator-still-matching-deleted-queries/6494/9 "2017-07-06T03:38:54Z")