-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Nested field support #1084
Copy link
Copy link
Open
Labels
Feature:AggregationsAggregation infrastructure (AggConfig, esaggs, ...)Aggregation infrastructure (AggConfig, esaggs, ...)Feature:New Field TypeAdd support for an Elasticsearch field type in KibanaAdd support for an Elasticsearch field type in KibanaTeam:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//high hanging fruitimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:x-largeExtra Large Level of EffortExtra Large Level of Effortrelease_note:enhancement
Description
Metadata
Metadata
Assignees
Labels
Feature:AggregationsAggregation infrastructure (AggConfig, esaggs, ...)Aggregation infrastructure (AggConfig, esaggs, ...)Feature:New Field TypeAdd support for an Elasticsearch field type in KibanaAdd support for an Elasticsearch field type in KibanaTeam:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//high hanging fruitimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:x-largeExtra Large Level of EffortExtra Large Level of Effortrelease_note:enhancement
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is sort of a duplicate of some other issues I searched for but I haven't seen this particular aspect discussed, so I thought this was worth a separate issue.
You read the _mapping field, so you should know when a particular field is nested, so can it not automatically apply the correct nested facet/query when such a field is selected in queries or facets?
(Alternatively/in addition as suggested by #532, you could have a checkbox to allow users to select it themselves, perhaps as an interim measure)
I'm sure there are some cases where this gets complicated, but there are also a bunch of cases where it's a straightforward changing of one block of JSON to another.
Latest update: #1084 (comment)