Possible Bug? Percolator still matching deleted queries

Elastic Stack Elasticsearch
1

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?

2

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.

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?

3

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 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.

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?

4

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

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.

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?

5

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 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

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.

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?

6

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

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.

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?

7

I forgot to open an issue.

Now here it is:

On Thu, Feb 16, 2012 at 4:22 PM, Shay Banon 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

On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon 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.

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?

8

Much appreciated!

On Feb 16, 4:51 pm, Onilton Maciel oniltonmac...@gmail.com wrote:

I forgot to open an issue.

Now here it is:

Percolators: Support delete-by-query · Issue #1712 · elastic/elasticsearch · GitHub

On Thu, Feb 16, 2012 at 4:22 PM, Shay Banon 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

On Wed, Jan 25, 2012 at 12:44 PM, Shay Banon 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.

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?