Documentation

testing.diff() function

testing.diff() produces a diff between two streams.

The function matches tables from each stream based on group keys. For each matched table, it produces a diff. Any added or removed rows are added to the table as a row. An additional string column with the name diff is created and contains a - if the row was present in the got table and not in the want table or + if the opposite is true.

diff() function emits at least one row if the tables are different and no rows if the tables are the same. The exact diff produced may change. diff() can be used to perform in-line diffs in a query.

Function type signature
(  <-got: stream[A],  want: stream[A],  ?epsilon: B,  ?nansEqual: C,  ?verbose: D, ) => stream[{A with _diff: string}]

For more information, see Function type signatures.

Parameters

got

Stream containing data to test. Default is piped-forward data (<-).

want

(Required) Stream that contains data to test against.

epsilon

Specify how far apart two float values can be, but still considered equal. Defaults to 0.000000001.

verbose

Include detailed differences in output. Default is false.

nansEqual

Consider NaN float values equal. Default is false.

Examples

Output a diff between two streams of tables

import "sampledata" import "testing"  want = sampledata.int() got =  sampledata.int()  |> map(fn: (r) => ({r with _value: if r._value > 15 then r._value + 1 else r._value}))  testing.diff(got: got, want: want)

View example input

Return a diff between a stream of tables an the expected output

import "testing"  want = from(bucket: "backup-example-bucket") |> range(start: -5m)  from(bucket: "example-bucket")  |> range(start: -5m)  |> testing.diff(want: want)

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