mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 09:28:55 -04:00
DOCS: Correct explanation of percentiles_bucket (#116499)
Corrects the explanation of `percentiles_bucket` so it's clear that it returns the `nth` largest item always, and it rounds `n` towards infinity. That's how it's worked since 2016 but the docs talked about "not greater than" which I don't think is particularly clear.
This commit is contained in:
parent
1da6ea4c54
commit
b285204fde
1 changed files with 4 additions and 3 deletions
|
@ -127,10 +127,11 @@ And the following may be the response:
|
|||
|
||||
==== Percentiles_bucket implementation
|
||||
|
||||
The Percentile Bucket returns the nearest input data point that is not greater than the requested percentile; it does not
|
||||
interpolate between data points.
|
||||
|
||||
The percentiles are calculated exactly and is not an approximation (unlike the Percentiles Metric). This means
|
||||
the implementation maintains an in-memory, sorted list of your data to compute the percentiles, before discarding the
|
||||
data. You may run into memory pressure issues if you attempt to calculate percentiles over many millions of
|
||||
data-points in a single `percentiles_bucket`.
|
||||
|
||||
The Percentile Bucket returns the nearest input data point to the requested percentile, rounding indices toward
|
||||
positive infinity; it does not interpolate between data points. For example, if there are eight data points and
|
||||
you request the `50%th` percentile, it will return the `4th` item because `ROUND_UP(.50 * (8-1))` is `4`.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue