-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Nested Filter does not allow .Filter only filter #880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I will submit a fix via pull request shortly |
Philo
added a commit
to Philo/elasticsearch-net
that referenced
this issue
Aug 14, 2014
…lter does not result in a conditionless NEST filter (leading to its exclusion from generated json query)
I can confirm that the issue exists, and I can also confirm the workaround of adding ".Query(q => q.MatchAll())" Here is my non-working search:
Here is the working:
|
Thanks for confirming @jayhilden. #881 will fix this, just waiting for the CLA so I can merge it in. |
gmarz
added a commit
that referenced
this issue
Aug 19, 2014
re #880 - Ensures that a nested filter consisting of only a filter does ...
Closed by #881 |
Tasteful
pushed a commit
to Tasteful/elasticsearch-net
that referenced
this issue
Aug 26, 2014
…lter does not result in a conditionless NEST filter (leading to its exclusion from generated json query)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The below query should be supported by NEST, however it results in a conditionless filter being produced.
A workaround is to ensure that you include a .Query(q => q.MatchAll()) within your nested filter.
The text was updated successfully, but these errors were encountered: