Re: Filters: odd behavior

2014-10-21 Thread @mromagnoli
Thanks for answer, Ivan. You were right, I wrapped all my filters inside bool filters and it seems everything is working correctly! Thanks for your time! Marce El sábado, 18 de octubre de 2014 15:36:39 UTC-3, Ivan Brusic escribió: > > The structure of your query is odd. Either it is some for

Re: Filters: odd behavior

2014-10-18 Thread Ivan Brusic
The structure of your query is odd. Either it is some format that I am not aware of or the Elasticsearch parser is not doing a good job at determining it is invalid. Your two filters should be joined via a bool filter. Sometime like (not tested): { "query": { "filtered": { "query": {

Re: Filters: odd behavior

2014-10-18 Thread @mromagnoli
Thanks guys for your responses. My question was due an strange behavior when using 'not' and 'geo_distance' filters. I want to filter some results that have undesirable words, such as 'sex', 'xxx', etc... And then geo filter those good results, but if I place 'not' filter first, then when geo

Re: Filters: odd behavior

2014-10-17 Thread Alexandre Rafalovitch
And there is post-filter as well: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-post-filter.html Regards, Alex. Personal: http://www.outerthoughts.com/ and @arafalov Solr resources and newsletter: http://www.solr-start.com/ and @solrstart Solr popularizer

Re: Filters: odd behavior

2014-10-17 Thread Ivan Brusic
They are indeed executed in the defined order. Filters that are more specific should be placed early on and those that cannot be cached (geo/timebased) should be placed last. Cheers, Ivan On Thu, Oct 16, 2014 at 5:16 AM, @mromagnoli wrote: > Hi everyone, > I have a doubt about Filters. > > If

Filters: odd behavior

2014-10-16 Thread @mromagnoli
Hi everyone, I have a doubt about Filters. If I have more than one filter, in a filtered query, are they executed in the defined order? And, are they filtering in a 'chain' mode, i.e. using the results of the previous filters? Thanks in advance as always. -- You received this message becaus