mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-26 01:48:45 +00:00
Document that pipeline aggs are not compatible with composite agg (#44180)
This commit is contained in:
parent
8fdcf28fac
commit
3fa677ce79
@ -590,3 +590,13 @@ GET /_search
|
|||||||
}
|
}
|
||||||
--------------------------------------------------
|
--------------------------------------------------
|
||||||
// TESTRESPONSE[s/\.\.\.//]
|
// TESTRESPONSE[s/\.\.\.//]
|
||||||
|
|
||||||
|
==== Pipeline aggregations
|
||||||
|
|
||||||
|
The composite agg is not currently compatible with pipeline aggregations, nor does it make sense in most cases.
|
||||||
|
E.g. due to the paging nature of composite aggs, a single logical partition (one day for example) might be spread
|
||||||
|
over multiple pages. Since pipeline aggregations are purely post-processing on the final list of buckets,
|
||||||
|
running something like a derivative on a composite page could lead to inaccurate results as it is only taking into
|
||||||
|
account a "partial" result on that page.
|
||||||
|
|
||||||
|
Pipeline aggs that are self contained to a single bucket (such as `bucket_selector`) might be supported in the future.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user