-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Too many docvalue_fields reported while there is less #63730
Labels
>bug
:Search/Search
Search-related issues that do not fall into other categories
Team:Search
Meta label for search team
Comments
jtibshirani
added
:Search/Search
Search-related issues that do not fall into other categories
and removed
needs:triage
Requires assignment of a team area label
labels
Oct 15, 2020
Pinging @elastic/es-search (:Search/Search) |
I looked at the way we check the limit in |
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 16, 2020
Currently we count every field requested in the search request bodies 'docvalue_fields' section towards the limit defined by the 'max_docvalue_fields_search' index setting which defaults to 100. This can be a problem e.g. if the user searches across several indices with some fields present in one index but not the other and has to add the joint set of field names to the query. We currently trip the limit even if the number of actually mapped fields in each index is below the limit. This change adds a step to distiguish between mappend and unmapped fields and only count the former towards the limit. Closes elastic#63730
cbuescher
pushed a commit
that referenced
this issue
Oct 21, 2020
Currently we count every field requested in the search request bodies 'docvalue_fields' section towards the limit defined by the 'max_docvalue_fields_search' index setting which defaults to 100. This can be a problem e.g. if the user searches across several indices with some fields present in one index but not the other and has to add the joint set of field names to the query. We currently trip the limit even if the number of actually mapped fields in each index is below the limit. This change adds a step to distiguish between mappend and unmapped fields and only count the former towards the limit. Closes #63730
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 21, 2020
Currently we count every field requested in the search request bodies 'docvalue_fields' section towards the limit defined by the 'max_docvalue_fields_search' index setting which defaults to 100. This can be a problem e.g. if the user searches across several indices with some fields present in one index but not the other and has to add the joint set of field names to the query. We currently trip the limit even if the number of actually mapped fields in each index is below the limit. This change adds a step to distiguish between mappend and unmapped fields and only count the former towards the limit. Closes elastic#63730
cbuescher
pushed a commit
that referenced
this issue
Oct 21, 2020
Currently we count every field requested in the search request bodies 'docvalue_fields' section towards the limit defined by the 'max_docvalue_fields_search' index setting which defaults to 100. This can be a problem e.g. if the user searches across several indices with some fields present in one index but not the other and has to add the joint set of field names to the query. We currently trip the limit even if the number of actually mapped fields in each index is below the limit. This change adds a step to distiguish between mappend and unmapped fields and only count the former towards the limit. Closes #63730
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Search/Search
Search-related issues that do not fall into other categories
Team:Search
Meta label for search team
Elasticsearch version (
bin/elasticsearch --version
): 7.9.2Plugins installed: []
JVM version (
java -version
): bundledOS version (
uname -a
if on a Unix-like system): Elastic CloudDescription of the problem including expected versus actual behavior:
Search query requesting more
docvalue_fields
than index configured settingmax_docvalue_fields_search
throws an error even if requested fields do not exist.A non-existent field should not contribute to the limit.
Here is minimal reproduction:
Response:
Expected behavior would be to first check field existence and only then verify the limits.
The text was updated successfully, but these errors were encountered: