Documentation

experimental.histogramQuantile() function

experimental.histogramQuantile() is subject to change at any time.

experimental.histogramQuantile() approximates a quantile given a histogram with the cumulative distribution of the dataset.

Each input table represents a single histogram. Input tables must have two columns: a count column (_value) and an upper bound column (le). Neither column can be part of the group key.

The count is the number of values that are less than or equal to the upper bound value (le). Input tables can have an unlimited number of records; each record represents an entry in the histogram. The counts must be monotonically increasing when sorted by upper bound (le). If any values in the _value or le columns are null, the function returns an error.

Linear interpolation between the two closest bounds is used to compute the quantile. If the either of the bounds used in interpolation are infinite, then the other finite bound is used and no interpolation is performed.

The output table has the same group key as the input table. The function returns the value of the specified quantile from the histogram in the _value column and drops all columns not part of the group key.

Function type signature
(
    <-tables: stream[{A with le: float, _value: float}],
    ?minValue: float,
    ?quantile: float,
) => stream[{A with _value: float}]

For more information, see Function type signatures.

Parameters

quantile

Quantile to compute ([0.0 - 1.0]).

minValue

Assumed minimum value of the dataset. Default is 0.0.

When the quantile falls below the lowest upper bound, the function interpolates values between minValue and the lowest upper bound. If minValue is equal to negative infinity, the lowest upper bound is used.

tables

Input data. Default is piped-forward data (<-).

Examples

Compute the 90th percentile of a histogram

import "experimental"

histogramData
    |> experimental.histogramQuantile(quantile: 0.9)

View example input and output


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: