-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
NPE when using bool query with min_score #43497
Comments
Pinging @elastic/es-search |
The same error, here is my configuration and index settings: ES version which i use: 7.1.0 docker-compose.yml:
Index settings:
Mapping settings:
Data from Elasticsearch log:
So, from the top line i noticed that error appears in the file ReqOptSumScorer.java:299 and on the 299 line i see next: variable is defined on line 54:
so i assume that in my case it goes to "else" section and variable is NULL. query which i use:
The problem appears only sometimes so i assume it depends somehow on the index data. For example with different "min_score" the error can appear or not, or with different "birth_year" and so on. |
This change fixes the score mode of the minimum score collector to be set based on the score mode of the child collector (top docs). Closes elastic#43497
This change fixes the score mode of the minimum score collector to be set based on the score mode of the child collector (top docs). Closes #43497
This change fixes the score mode of the minimum score collector to be set based on the score mode of the child collector (top docs). Closes #43497
This change fixes the score mode of the minimum score collector to be set based on the score mode of the child collector (top docs). Closes #43497
Elasticsearch version 7.0.0 - 7.2.2
Plugins installed: defaults
JVM version
OS version
Description of the problem including expected versus actual behavior:
Experiencing NPEs in elasticsearch with bool queries using min_score
More context in the discussion forums:
https://discuss.elastic.co/t/null-pointer-exception-when-use-bool-query/186831
The text was updated successfully, but these errors were encountered: