Skip to content

Document nested field caveat for fields, fielddata_fields and docvalue_fields #23766

Closed
@ppf2

Description

@ppf2

ES 2.x and 5.x

Currently when accessing nested fields via top level fields, fielddata_fields or docvalue_fields at the top level using the dot notation (eg. nested_path.field.field, etc..) to represent the nested fields, ES does not validate to determine if the field is nested vs. a field with dots in field name. The end result is that fields, fielddata_fields or docvalue_fields is not returned in the response and the end user will wonder if they have referenced an incorrect field name, if it's a bug, or if it is simply by design and have to be accessed a different way.

For nested fields, fields, fielddata_fields or docvalue_fields can only be accessed via inner_hits. It will be helpful to clarify this at a few locations in the documentation:

Metadata

Metadata

Assignees

Labels

:Search Foundations/MappingIndex mappings, including merging and defining field types>docsGeneral docs changesTeam:Search FoundationsMeta label for the Search Foundations team in Elasticsearch

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions