No suggestions?
/A
On Thursday, November 13, 2014 4:44:35 PM UTC+1, Alexander Jiteg wrote:
>
> Follow up question; What If I change the terms in the looked up filter
> after the percolator has been created? Seems that the terms are cached but
> even though I have experimented with cache invali
Follow up question; What If I change the terms in the looked up filter
after the percolator has been created? Seems that the terms are cached but
even though I have experimented with cache invalidation the only thing I
got working so far is deleting/recreating the percolator for the new terms
t
Ok. Thanks for the clarification.
On Monday, November 3, 2014 10:20:38 AM UTC+1, Martijn v Groningen wrote:
>
> In the case of percolator queries are indexed before actual data is
> evaluated, which triggers the automatic addition of fields in mappings.
> Most of the times this is ok, but there
In the case of percolator queries are indexed before actual data is
evaluated, which triggers the automatic addition of fields in mappings.
Most of the times this is ok, but there are a number of queries that
require the field mapping to exist before the percolator query is indexed.
Because of thi
Seems that If I index a document with the given type first, it works. That
is probably why my second run works but not the first.
On Thursday, October 30, 2014 9:59:49 AM UTC+1, Alexander Jiteg wrote:
>
> Hi!
>
> I'm trying to use a lookup terms filter for percolation but for some
> reason I'm
Hi!
I'm trying to use a lookup terms filter for percolation but for some reason
I'm not getting any matches when percolating documents that should match
the registered percolator.
Example:
https://gist.github.com/alexndr79/760314b8b5f49157a839#file-percolation_with_terms_lookup-txt
I have not
