You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Composite aggregations provide a way to stream all buckets similar to scroll search. For Terms aggs this means high cardinality fields can be used in the datafeed without some of those terms being lost due to the limitation the size parameter.
The text was updated successfully, but these errors were encountered:
For supporting composite aggs, I am working on it with the following restrictions:
The composite agg MUST be the top level agg
Only ONE composite agg is allowed
The composite agg must contain exactly ONE date_histogram data source
The other aggregation restrictions of requiring a max agg on the timstamp field remains.
The other bucketing sources of the composite agg can be used as fields in the detectors. Meaning having a terms group by source, the terms field could be a partition field or influencer.
I am not 100% about supporting the geotile_grid data source for composite aggs. We can allow it, but there won't be any special handling yet. So the values would just be written out as x/y/zoom strings (just like the bucket key value).
Composite aggregations provide a way to stream all buckets similar to scroll search. For Terms aggs this means high cardinality fields can be used in the datafeed without some of those terms being lost due to the limitation the size parameter.
The text was updated successfully, but these errors were encountered: