Skip to content
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

custom_score could support a filter directly #3167

Closed
q42jaap opened this Issue Jun 12, 2013 · 0 comments

Comments

Projects
None yet
2 participants
@q42jaap
Copy link

commented Jun 12, 2013

custom_score only supports a query, but lot's of scripts probably don't use the _score variable anyway. So it makes sense to use a filter (no scoring overhead and better caching).

It would be nice if you could use a filter directly instead of wrapping it in a filtered query (see an example in #3165), it looks better and could be a little bit more optimized (maybe).

@ghost ghost assigned martijnvg Jun 12, 2013

@martijnvg martijnvg closed this in a2de34e Jun 12, 2013

martijnvg added a commit that referenced this issue Jun 12, 2013

martijnvg added a commit that referenced this issue Jun 13, 2013

martijnvg added a commit that referenced this issue Jun 13, 2013

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.