Bool queries not working as expected in v0.17.x

Elastic Stack Elasticsearch
1

Hi All,

Since upgrading to v0.17.0 some of my searchers with the bool query
have not been working correctly. Specifically when using with the
range query, and the term query that includes searching within a
multi_field mapping type.

range example:

"must" : [{"range" : {"updated_at" : {"from" : 1311163200, "to" :
1311768000}}}] (inside a query => bool objects)

multi_field type in a term query example:

"must" : [{"term" : {"name.terms" : {"Hello World"}}] (inside a
query => bool objects)

These have been working fine through the 0.15.x and 0.16.x versions of
elasticsearch.

Iv looked around the release notes/docs/user group to see if this way
is no longer supported or others with simular experiences, if you guys
could let me know if im just missing something obvious that would be
great!!!

Cheers,
Nick

2

Nothing specific changed in these areas, can you post a recreation? (
Elasticsearch Platform — Find real-time answers at scale | Elastic).

On Thu, Jul 28, 2011 at 11:21 AM, Nick Mason nick@2cu.co.nz wrote:

Hi All,

Since upgrading to v0.17.0 some of my searchers with the bool query
have not been working correctly. Specifically when using with the
range query, and the term query that includes searching within a
multi_field mapping type.

range example:

"must" : [{"range" : {"updated_at" : {"from" : 1311163200, "to" :
1311768000}}}] (inside a query => bool objects)

multi_field type in a term query example:

"must" : [{"term" : {"name.terms" : {"Hello World"}}] (inside a
query => bool objects)

These have been working fine through the 0.15.x and 0.16.x versions of
elasticsearch.

Iv looked around the release notes/docs/user group to see if this way
is no longer supported or others with simular experiences, if you guys
could let me know if im just missing something obvious that would be
great!!!

Cheers,
Nick

3

Shortly after posting i realized that you had release 0.17.2, after
upgrading my queries have started to work again.

Thanks Shay for your fast response,