I'm not really sure how I'd research the history of this issue, or if it
is in fact an issue or ignorance on my part, but it's nature is elusive as
far as I can tell and so I'm elaborating here...
I have a query in my percolator index that I expect to match a given
I percolate the document and the query is not returned.
I retrieve the query, via a get request; and then dump the body of the
query into a file.
I then index the contents of that file, without modifying it, into the same
index's '.percolator' type, with a different id.
(In other words, I've re-indexed the afflicted query without modifying it.)
Re-percolating the same document now returns the newly indexed query, while
still excluding the original identical query.
The only thing I can think of is that, perhaps somehow the mapping for
.percolator was different at the time of indexing the original query, and
thus there's something different stored in lucene for that query compared
to what's stored for the new query. But I don't have a good enough
understanding of how mappings and storage works for the percolator, and as
far as I've read this isn't commented on in the documentation. Is the above
- elasticsearch version 1.1.0
- 2 nodes, 1 shard, 0 replicas (it's testing environment)
- // Query
"random field", "random_field_2", "random_field_3"
- The document percolated includes the word "gasoline".
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/44a1e697-02ee-42fa-b715-14d832a3cd8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.