Current field list in kibana pick up all document types.
Nested aggregates across fields from document types
don't work (returns no result) as appropriate.
However, if there is a parent-child document relationship,
the filters should work using the appropriate has_parent/child
in the query DSL.
You already have the _parent data in mapping, so you can
create a "forest" that have the parent/child types properly
linked. So by walking this large "tree", we should be able
to place the related filter clauses in the appropriate locations for
a query.
Thanks
Any update on parent-child support? Missing this is a crucial for using ElasticSearch fully.
+1
+1
+1. Parent/Child and Nested Documents are critical for more complicated ElasticSearch use cases.
+1
Having this support would enable Kibana to be the UI used in IT Operations with complex relationships that require advanced usage. +1
Pinging @elastic/kibana-app-arch (Team:AppArch)
+1
Most helpful comment
Any update on parent-child support? Missing this is a crucial for using ElasticSearch fully.