I can't seem to reproduce the error with curl recreations. When I run
the query against my dataset, there are a lot of offending documents.
However, when I created a new index with the data of a few of the
offending documents, everything works great. The documents that
wrongly match the query in my original dataset are correctly filtered
when I create the new index (even though I only indexed 3 documents to
test). I'm completely stumped. I have around 600 indexed documents
(each one around 20kB, and am running elasticsearch on 64Mb of memory,
far below the recommended standard configuration. Could malformed
data in a few of my documents cause the query to not match? Could
running on 64Mb of memory be the issue?
On Sep 11, 3:49 am, Shay Banon kim...@gmail.com wrote:
This should work. Can you post a recreation (no need for the custom score
query you use, just use match_all). Seehttp://www.elasticsearch.org/help
On Sun, Sep 11, 2011 at 4:55 AM, Chris
I've been trying to get these types of queries working for a while,
but no luck. I'm trying to filter documents based on a boolean value
(basically only show documents where show == true).
Here's my query:
Documents are being matched where show == false. Any ideas why this
would happen even though I explicitly say to filter them out?