-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Sorting by unmapped nested field #33644
Labels
Comments
Pinging @elastic/es-search-aggs |
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
May 23, 2019
Previously sorting on a missing nested field would fail with an Exception: `[nested_field] failed to find nested object under path [nested_path]` despite `unmapped_type` being set on the query. Fixes: elastic#33644
matriv
added a commit
that referenced
this issue
May 24, 2019
Previously sorting on a missing nested field would fail with an Exception: `[nested_field] failed to find nested object under path [nested_path]` despite `unmapped_type` being set on the query. Fixes: #33644
gurkankaymak
pushed a commit
to gurkankaymak/elasticsearch
that referenced
this issue
May 27, 2019
Previously sorting on a missing nested field would fail with an Exception: `[nested_field] failed to find nested object under path [nested_path]` despite `unmapped_type` being set on the query. Fixes: elastic#33644
37 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Elasticsearch version (
bin/elasticsearch --version
): 6.4.0Plugins installed: []
JVM version (
java -version
): 1.8.0_171OS version (
uname -a
if on a Unix-like system): Windows 10Description of the problem including expected versus actual behavior:
Field
unmapped_type
in sort section inside query doesn't work properly in case of nested properties. If I query for the data sorted by non-existing (unmapped) nested field I getquery_shard_exception
. The behavior I expect is to sort the data without nested field by a default value of a type specified inunmapped_type
field. It would be consistent with current behavior for non-nested fields.Steps to reproduce:
Let's say I have 2 indices (One with nested field and one without):
The query for sorted data from both indices:
Only data from index-nested are returned, all shards belonging to indices without nested field are failing:
The text was updated successfully, but these errors were encountered: