Documentation

median() function

median() returns the median _value of an input table or all non-null records in the input table with values that fall within the 0.5 quantile (50th percentile).

Function behavior

median() acts as an aggregate or selector transformation depending on the specified method.

  • Aggregate: When using the estimate_tdigest or exact_mean methods, median() acts as an aggregate transformation and outputs the average of non-null records with values that fall within the 0.5 quantile (50th percentile).
  • Selector: When using the exact_selector method, meidan() acts as a selector selector transformation and outputs the non-null record with the value that represents the 0.5 quantile (50th percentile).
Function type signature
(<-tables: stream[A], ?column: string, ?compression: float, ?method: string) => stream[A] where A: Record

For more information, see Function type signatures.

Parameters

column

Column to use to compute the median. Default is _value.

method

Computation method. Default is estimate_tdigest.

Available methods:

  • estimate_tdigest: Aggregate method that uses a t-digest data structure to compute an accurate median estimate on large data sources.
  • exact_mean: Aggregate method that takes the average of the two points closest to the median value.
  • exact_selector: Selector method that returns the row with the value for which at least 50% of points are less than.

compression

Number of centroids to use when compressing the dataset. Default is 0.0.

A larger number produces a more accurate result at the cost of increased memory requirements.

tables

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

Examples

Use median as an aggregate transformation

import "sampledata"

sampledata.float()
    |> median()

View example input and output

Use median as a selector transformation

import "sampledata"

sampledata.float()
    |> median(method: "exact_selector")

View example input and output


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value cachesβ€”making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2