As discussed in the backend senate, the bucket limiting that takes place before report evaluation in the backend should be removed as it's becoming hard to maintain and adds unnecessary complexity. Instead, we should handle the "too many buckets exception" that Elasticsearch throws better and display it in the UI in a user friendly way (e.g. with suggestions of what filters to apply to resolve the issue).
- The bucket limiting in the backend is removed
- The ES exception is handled in a more use friendly way (
- We might not need the isComplete flag anymore, if so we should remove it from the result (needs FE adjustment too)