-
Notifications
You must be signed in to change notification settings - Fork 21
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
Backend migration: When adding multiple groupBy terms, only the last group works #391
Comments
Hi @LoLZeS666 and @difi80211g from initial debugging, I managed to reproduce the error. It looks like it's caused by the number of buckets created being higher than maximum for Open Search. If you set the min_interval in the Query options for the panel to be higher (1h for example - @difi80211g I see in your panel it's |
I was grouping by a term called name, which gives a result of around 150 rows. My opensearch cluster has buckets set at 100000. So I don't think this is related to the bucket limit. |
Hi again, @difi80211g, I have a few questions on your bug:
Thanks for helping us debug this! |
@LoLZeS666 I managed to reproduce your problem, and I indeed see only the latest term aggregation. Adding this to our pipeline. For whoever picks this up: We're building the query correctly and getting all the aggregations from OpenSearch, but not processing the response correctly. |
We had a bug report in one of the comments to the migration PR: #375 (comment) related to groupBy clause:
The text was updated successfully, but these errors were encountered: