-
Notifications
You must be signed in to change notification settings - Fork 25.2k
min_score doesn't seem to prune irrelevant results #14455
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 tried it locally and it worked for me with elasticsearch 2.0. Which version are you running? |
Hi Adrien, This is the version: |
I can replicate this. If you set
With
|
Pinging @elastic/es-search-aggs not sure I understand the concern here: I've updated this example to work on Elasticsearch 6.x here:
with one random response returned as:
is this to mean that you would not expect buckets with terms of a score < |
Related to the original goal -- sub-sampling the result set for improved performance -- the There's a proof-of-concept sampling query that I was working on (#25561) which may help, if we can figure out how to make it work. :) |
Elasticsearch supports now a random sampler aggregation, which would nicely address the initial usecase of this issue which was to execute significant_terms on a subset of documents. |
Scenario: to do significant_terms aggregation on a random subset (10%) of the results. The goal is to speed up computation of the aggregation by taking only a portion of the results.
Issue: setting up score in script_score and applying min_score doesn't seem to influence the final result. The following query has 44k results in the database, and all of them seem to get aggregated.
query:
Result:
Expected:
Aggregation based on ~4400 results, not 44000.
Is this an intended behaviour, and if so, is there a way to exclude results from the final resultset used in aggregation?
The text was updated successfully, but these errors were encountered: