[ES|QL] Add support for STATS BY nested function#175288
[ES|QL] Add support for STATS BY nested function#175288dej611 merged 12 commits intoelastic:mainfrom
Conversation
|
/ci |
|
/ci |
|
/ci |
|
Pinging @elastic/kibana-visualizations (Team:Visualizations) |
|
@elasticmachine merge upstream |
|
/ci |
|
@dej611 as this is a very cool feature, can we suggest also all the eval functions (as they are supported).
|
|
I wasn't sure whether to suggest them or not, but I can enable that.
Does it make sense to you @stratoula ? |
|
Yes!!! I think is cool to suggest them even if the list goes long! |
|
/ci |
stratoula
left a comment
There was a problem hiding this comment.
This looks great Marco! LGTM, thanx a ton
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: |
|
I've completely missed the support for nested functions in the |
## Summary This is the second part of #175288 where nested expressions are supported in STATS scope as well. I've tweaked the previous test suite here to check all agg functions with nested expressions in various scenarios. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
## Summary Add support for the validation and autocomplete engine for the feature introduced in elastic/elasticsearch#104387 The validation engine should not mark the syntax as invalid now. The autocomplete changes are a little bit more subtle: * after the `by` option command a `varX` and functions are now suggested in additions to `[columns]` * when typing an expression within the `by` scope the autocomplete should now understand and help with that, without promoting it when not needed.  ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary This is the second part of elastic#175288 where nested expressions are supported in STATS scope as well. I've tweaked the previous test suite here to check all agg functions with nested expressions in various scenarios. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
## Summary This is the second part of elastic#175288 where nested expressions are supported in STATS scope as well. I've tweaked the previous test suite here to check all agg functions with nested expressions in various scenarios. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>


Summary
Add support for the validation and autocomplete engine for the feature introduced in elastic/elasticsearch#104387
The validation engine should not mark the syntax as invalid now.
The autocomplete changes are a little bit more subtle:
byoption command avarXand functions are now suggested in additions to[columns]byscope the autocomplete should now understand and help with that, without promoting it when not needed.Checklist