Fill null values in data

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.

For more information, see Token hashing.

Use fill() to replace null values with:

data
    |> fill(usePrevious: true)

// OR

data
    |> fill(value: 0.0)

Fill empty windows of time

The fill() function does not fill empty windows of time. It only replaces null values in existing data. Filling empty windows of time requires time interpolation (see influxdata/flux#2428).

Fill with the previous value

To fill null values with the previous non-null value, set the usePrevious parameter to true.

Values remain null if there is no previous non-null value in the table.

data
    |> fill(usePrevious: true)

Given the following input:

_time_value
2020-01-01T00:01:00Znull
2020-01-01T00:02:00Z0.8
2020-01-01T00:03:00Znull
2020-01-01T00:04:00Znull
2020-01-01T00:05:00Z1.4

fill(usePrevious: true) returns:

_time_value
2020-01-01T00:01:00Znull
2020-01-01T00:02:00Z0.8
2020-01-01T00:03:00Z0.8
2020-01-01T00:04:00Z0.8
2020-01-01T00:05:00Z1.4

Fill with a specified value

To fill null values with a specified value, use the value parameter to specify the fill value. The fill value must match the data type of the column.

data
    |> fill(value: 0.0)

Given the following input:

_time_value
2020-01-01T00:01:00Znull
2020-01-01T00:02:00Z0.8
2020-01-01T00:03:00Znull
2020-01-01T00:04:00Znull
2020-01-01T00:05:00Z1.4

fill(value: 0.0) returns:

_time_value
2020-01-01T00:01:00Z0.0
2020-01-01T00:02:00Z0.8
2020-01-01T00:03:00Z0.0
2020-01-01T00:04:00Z0.0
2020-01-01T00:05:00Z1.4

Was this page helpful?

Thank you for your feedback!