Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[SAVED_OBJECTS] [AGGS] Step I to add aggregations in the find of saved objects #64002
[SAVED_OBJECTS] [AGGS] Step I to add aggregations in the find of saved objects #64002
Changes from 8 commits
b699c70
3819cd5
1c4bac9
6feca9b
8dda821
0904a0e
44dcb25
560b63b
699d0a1
0f57677
d7cb38e
ec2a69d
817a3ef
f7faa18
a54f440
2aef7fd
e698b0e
09565d8
c16e72b
5a12d44
c4eff53
1eaafca
f04ab64
8f64144
2209d12
4f667d4
433a71c
37ad64d
2fb9a2c
48dcdda
2dc3ff8
f1f437b
b23eac7
462d87e
4e319b3
ba55542
16de875
cb7ada3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick thoughts about multi-types aggregation: I think that, with current implementation, allowing to use aggregations when using
find
with multiple types does not make any sense, as we enforce that the fields we are performing the aggregations against follow the{type}.attributes.{field}
format. I don't see what kind of aggregations we could be performing when searching for multiple types with this 'limitation', as each type got their own isolated attributes?Should we just throw an error when a developers tries to use aggregations when using
find
with multiple types? Or should we just not care and let him do?Second question, in the opposite direction: we we want to allow to perform aggregations on 'global' fields at some point (not asking for this PR, but a mid/long term)? such as
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should just not care but if you all feel strongly about it, I can add it