You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tested this without a nested object and it operates as I would expect. At first I thought perhaps the match_all was doing something strange to the percolator but when it wasn't a nested object it worked fine.
The text was updated successfully, but these errors were encountered:
bejs
changed the title
Percolator query not behaving the same as stand-alone query
Query returns wrong/different results when in a percolator
Aug 28, 2014
First up, I'm using Elasticsearch v1.1.1
I am getting an unexpected result from a percolator. I have broken it down to it's simplest parts and it still not working as I it should.
Firstly I create a new index with mapping:
Then I create two objects for testing:
Then I create a query that I would expect to match on the second record only:
So far everything is working as expected. The query returns the second record, the first one being excluded by the filter.
I then use the same query to create a percolator:
And test against both records:
They both return the same result:
I have tested this without a nested object and it operates as I would expect. At first I thought perhaps the match_all was doing something strange to the percolator but when it wasn't a nested object it worked fine.
The text was updated successfully, but these errors were encountered: