You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope its intentional the usage of null value set to true on hte missing filter, and not really have a null value on the mapping. It is a bug, which happens because the missing filter returns a null filter which ends up not matching anything with a filtered query, compared to top level filter.
when parsing a filter, we use null to indicate that this filter should not match anything, the top level filter doesn't take it into account
fixes#3356
when parsing a filter, we use null to indicate that this filter should not match anything, the top level filter doesn't take it into account
fixeselastic#3356
Given the following script: https://gist.github.com/dakrone/6034875
I was expecting the same output for both queries (no documents matched), but instead I get:
The text was updated successfully, but these errors were encountered: