Documentation

experimental.fill() function

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

experimental.fill() replaces all null values in the _value column with a non-null value.

Function type signature
(<-tables: stream[{B with _value: A}], ?usePrevious: bool, ?value: A) => stream[{B with _value: A}]

For more information, see Function type signatures.

Parameters

value

Value to replace null values with. Data type must match the type of the _value column.

usePrevious

Replace null values with the value of the previous non-null row.

tables

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

Examples

Fill null values with a specified non-null value

import "experimental"
import "sampledata"

sampledata.int(includeNull: true)
    |> experimental.fill(value: 0)

View example input and output

Fill null values with the previous non-null value

import "experimental"
import "sampledata"

sampledata.int(includeNull: true)
    |> experimental.fill(usePrevious: true)

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 February 3, 2026, 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