elastic/elasticsearch

Fail sorting when the field is under a nested object but no `nested_path` is specified

Open

#21704 opened on Nov 21, 2016

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (76,700 stars) (25,882 forks)batch import
:Search Relevance/Search>enhancementTeam:Search Relevancehelp wanted

Description

Follow-up to #21685. Maybe we should fail queries when a sort field is under a nested object and this nested object does not copy data to the parent/root (include_in_parent) since that would always be a mistake?

Contributor guide

Tech stack
javarest api
Domain
backendsearch
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Elasticsearch nested fieldsFamiliarity with sorting in Elasticsearch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the sorting implementation in Elasticsearch, particularly how nested fields are handled. Look at the linked issue #21685 and the relevant source files for sort parsing. The fix likely involves adding a validation check when a sort field is under a nested object without 'include in parent' or 'nested path' specified.