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.



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


(Required) Stream that contains data to test against.


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


Include detailed differences in output. Default is false.


Consider NaN float values equal. Default is false.


Output a diff between two streams of tables

import "sampledata"
import "testing"

want =
got =
        |> 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!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.