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

No matched_filters being returned when using named filters #3097

Closed
Mpdreamz opened this Issue May 27, 2013 · 2 comments

Comments

Projects
None yet
3 participants
@Mpdreamz
Member

Mpdreamz commented May 27, 2013

See the request and response here:

https://gist.github.com/Mpdreamz/5656950

I'm not seeing a matched_filters property on any of the hits, am I doing something wrong here?

@ghost ghost assigned javanna Aug 2, 2013

@javanna

This comment has been minimized.

Show comment
Hide comment
@javanna

javanna Aug 2, 2013

Member

Named filters are not currently supported on top-level filters, but only on filters under the main query (using filtered query).

We are most likely going to add soon support for them in the top-level filters too.

Member

javanna commented Aug 2, 2013

Named filters are not currently supported on top-level filters, but only on filters under the main query (using filtered query).

We are most likely going to add soon support for them in the top-level filters too.

javanna added a commit to javanna/elasticsearch that referenced this issue Aug 2, 2013

javanna added a commit to javanna/elasticsearch that referenced this issue Aug 2, 2013

@javanna javanna closed this in 85b7efa Aug 2, 2013

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

@JoshMcCullough

This comment has been minimized.

Show comment
Hide comment
@JoshMcCullough

JoshMcCullough commented Mar 5, 2016

Documentation for this needs to be updated: http://nest.azurewebsites.net/nest/search/named-filters.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment