-
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
[TSVB] Geo_point should be excluded from terms aggregation #109210
Conversation
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.
LGTM! Tested locally
Pinging @elastic/kibana-app (Team:KibanaApp) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@VladLasitsa this works fine for the terms aggregation in timeseries, but the issue also mentions the table. We should also apply these restrictions there too in order to close this issue. |
Added restrictions. |
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.
Thanx @VladLasitsa, now it works like a charm! Code LGTM, tested it locally in Chrome.
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @VladLasitsa |
…09210) * Add field type restriction for terms agg * Fix test * Add restriction for 'group by' in table Co-authored-by: Kibana Machine <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…110501) * Add field type restriction for terms agg * Fix test * Add restriction for 'group by' in table Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Uladzislau Lasitsa <[email protected]>
Closes: #103472
Summary
Adds field type restrictions for
terms
aggregation like in data plugin becauseterms
aggregation supports only number, date, string, ip and boolean field types.