-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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 support for max_determinized_states in _source: includes #53739
Labels
>bug
priority:normal
A label for assessing bug priority to be used by ES engineers
:Search/Search
Search-related issues that do not fall into other categories
Team:Search
Meta label for search team
Comments
Pinging @elastic/es-search (:Search/Search) |
Pinging @elastic/es-search (Team:Search) |
I wonder if this issue still exists. The way we parse given source values and grab values from _source has changed greatly in the last 4 years. I would expect complicated source patterns to still fail, but I would expect overall support to have improved. |
Yes @benwtrent this PR makes the option irrelevant in newer version I think: #72277 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
priority:normal
A label for assessing bug priority to be used by ES engineers
:Search/Search
Search-related issues that do not fall into other categories
Team:Search
Meta label for search team
Elasticsearch version : 7.*
There is no option to specify max_determinized_states in source filtering.
_source:{
"includes":["field1",..........]
}
specifying more than 1000 fields leads to "too_complex_to_detrmine_exception_error". So even if more than 1000 fields are supported in index there is no way to selectively return them (especially in reindex)
The text was updated successfully, but these errors were encountered: