# Percolator Behaves Differently In Different Indices

I have a percolator that is not matching when expected. I attempted
to create a simple example illustrating the problem; however, I could
not replicate. For some reason, only this percolator does not match
when expected. I can't understand why.

I was able to create a gist that shows this percolator not matching
when an identical one does match. http://gist.github.com/1003363

Notice that the gist contains the following steps:

1. Fetch percolator A (just to show what it is)
2. Percolate document X against percolators A's index
3. Percolator A is returned as a match
4. Fetch percolator B (just to show what it is)
5. Percolate document X against percolators B's index
6. Percolator B is NOT returned as a match

Notice that the query for percolator A and percolator B are
identical. Notice also that the document percolated against each is
identical. Why would these behave differently?

Which version are you using?

On Thursday, June 2, 2011 at 12:39 AM, Tim Scott wrote:

I have a percolator that is not matching when expected. I attempted
to create a simple example illustrating the problem; however, I could
not replicate. For some reason, only this percolator does not match
when expected. I can't understand why.

I was able to create a gist that shows this percolator not matching
when an identical one does match. The same percolator behaves differently in different indicies · GitHub

Notice that the gist contains the following steps:

1. Fetch percolator A (just to show what it is)
2. Percolate document X against percolators A's index
3. Percolator A is returned as a match
4. Fetch percolator B (just to show what it is)
5. Percolate document X against percolators B's index
6. Percolator B is NOT returned as a match

Notice that the query for percolator A and percolator B are
identical. Notice also that the document percolated against each is
identical. Why would these behave differently?

0.16. An interesting thing is that it seems to be working in
production. The problem is only seen on my dev machine. Something
corrupted?

On Jun 2, 2:36 am, Shay Banon shay.ba...@elasticsearch.com wrote:

Which version are you using?

On Thursday, June 2, 2011 at 12:39 AM, Tim Scott wrote:

I have a percolator that is not matching when expected. I attempted
to create a simple example illustrating the problem; however, I could
not replicate. For some reason, only this percolator does not match
when expected. I can't understand why.

I was able to create a gist that shows this percolator not matching
when an identical one does match.The same percolator behaves differently in different indicies · GitHub

Notice that the gist contains the following steps:

1. Fetch percolator A (just to show what it is)
2. Percolate document X against percolators A's index
3. Percolator A is returned as a match
4. Fetch percolator B (just to show what it is)
5. Percolate document X against percolators B's index
6. Percolator B is NOT returned as a match

Notice that the query for percolator A and percolator B are
identical. Notice also that the document percolated against each is
identical. Why would these behave differently?

Which 0.16? There were fixes in this area up to 0.16.2.

On Thursday, June 2, 2011 at 4:44 PM, Tim Scott wrote:

0.16. An interesting thing is that it seems to be working in
production. The problem is only seen on my dev machine. Something
corrupted?

On Jun 2, 2:36 am, Shay Banon <shay.ba...@elasticsearch.com (http://elasticsearch.com)> wrote:

Which version are you using?

On Thursday, June 2, 2011 at 12:39 AM, Tim Scott wrote:

I have a percolator that is not matching when expected. I attempted
to create a simple example illustrating the problem; however, I could
not replicate. For some reason, only this percolator does not match
when expected. I can't understand why.

I was able to create a gist that shows this percolator not matching
when an identical one does match.The same percolator behaves differently in different indicies · GitHub

Notice that the gist contains the following steps:

1. Fetch percolator A (just to show what it is)
2. Percolate document X against percolators A's index
3. Percolator A is returned as a match
4. Fetch percolator B (just to show what it is)
5. Percolate document X against percolators B's index
6. Percolator B is NOT returned as a match

Notice that the query for percolator A and percolator B are
identical. Notice also that the document percolated against each is
identical. Why would these behave differently?

0.16.0.

I will upgrade to 0.16.2 and see if that cures it. Thanks.

On Jun 2, 8:54 am, Shay Banon shay.ba...@elasticsearch.com wrote:

Which 0.16? There were fixes in this area up to 0.16.2.

On Thursday, June 2, 2011 at 4:44 PM, Tim Scott wrote:

0.16. An interesting thing is that it seems to be working in
production. The problem is only seen on my dev machine. Something
corrupted?

On Jun 2, 2:36 am, Shay Banon <shay.ba...@elasticsearch.com (http://elasticsearch.com)> wrote:

Which version are you using?

On Thursday, June 2, 2011 at 12:39 AM, Tim Scott wrote:

I have a percolator that is not matching when expected. I attempted
to create a simple example illustrating the problem; however, I could
not replicate. For some reason, only this percolator does not match
when expected. I can't understand why.

I was able to create a gist that shows this percolator not matching
when an identical one does match.The same percolator behaves differently in different indicies · GitHub

Notice that the gist contains the following steps:

1. Fetch percolator A (just to show what it is)
2. Percolate document X against percolators A's index
3. Percolator A is returned as a match
4. Fetch percolator B (just to show what it is)
5. Percolate document X against percolators B's index
6. Percolator B is NOT returned as a match

Notice that the query for percolator A and percolator B are
identical. Notice also that the document percolated against each is
identical. Why would these behave differently?