L3 - Default
OPT-3428 we addressed a potential bucket size limit (default 10k) error for definition queries. However, this limit can be hit for any unbounded bucket aggregation.
We need to investigate which of our other aggregations are prone to exceeding the limit as well (e.g. group by assignee). Theoretically, all unbounded aggregations are. And decide case by case how likely and whether we should prevent it using e.g. composite aggregations.
We may also consider limiting the aggregation size manually to prevent server errors with the limitation of just returning an incomplete result
What makes this even more complicated is that the limit seems to apply to not one layer of aggregations but to the whole number of buckets for all nested aggregations.
- there is a basic helper class available that assists with scrolling through the composite aggregation
- the events count endpoint uses the composite aggregation
- the duration outlier analysis uses the composite aggregation
Known additional Affected Queries/Endpoints:
- the variables endpoint may hit this issue for the rather unlikely case of 10k different variables being present for one process ->
- process parts aggregation is likely to hit the limit if there are more than 10 000 process instances in the filter ->