-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Nested field support in Visualize #58175
Comments
Pinging @elastic/kibana-app-arch (Team:AppArch) |
Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment. |
Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations) |
+1 to supporting nested docs in Visualize |
+1 doesn't OpenSearch support this already? |
+1 we have some use cases for this feature too |
+1 please reopen this. nested objects are very useful. |
+1 |
+1 Reopen this isssue |
+1 |
1 similar comment
+1 |
+20 |
+2*10^10000 |
digging with Vega with poor support isn't a good solution for visualise nested values... |
+1 |
1 similar comment
+1 |
+1 |
1 similar comment
+1 |
I really need this feature! |
+1 |
2 similar comments
+1 |
+1 |
+1 Please reopen this issue. |
+1 |
Part of #1084
Similar to querying, aggregating on nested fields requires users to make some choices depending on what info seek. Imagine doing a terms aggregation on a nested field with a simple "count" metric. For each bucket, do you want to count the number of nested documents that match, or the number of parent documents? We can do either one and both might be useful depending on the question you're trying to answer. The Visualize editor will need to give the user a choice in a way that is easy to understand.
For non-count metrics that require selecting a specific field, I think we can handle things in a way that's transparent to the user. By selecting a field, you're already implicitly telling us whether to do the aggregation at the parent or child level.
Nested fields come along with two special aggregations for working with them, nested and reverse_nested. We'll need to use both to fully support nested fields in Visualize. Except in the case of the "count" metric (as mentioned above), we should be able to generate the necessary
nested
andreverse_nested
wrappers using nested field information in the index pattern. I think the trickiest bit of the implementation will be keeping track of the current level of nesting as we generate the aggregation DSL, because we don't currently have a precedent in the visualize code for child aggs that know anything about their parents.The text was updated successfully, but these errors were encountered: