experimental.diff() function

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

experimental.diff() takes two table streams as input and produces a diff.

experimental.diff() compares tables with the same group key. If compared tables are different, the function returns a table for that group key with one or more rows. If there are no differences, the function does not return a table for that group key.

Note: experimental.diff() cannot tell the difference between an empty table and a non-existent table.

Important: The output format of the diff is not considered stable and the algorithm used to produce the diff may change. The only guarantees are those mentioned above.

Function type signature
(<-got: stream[A], want: stream[A]) => stream[{A with _diff: string}]
For more information, see Function type signatures.



(Required) Input stream for the - side of the diff.


Input stream for the + side of the diff.


Output a diff between two streams of tables

import "sampledata"
import "experimental"

want =
got =
        |> map(fn: (r) => ({r with _value: if r._value > 15 then r._value + 1 else r._value}))

experimental.diff(got: got, want: want)

View example input

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

import "experimental"

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

from(bucket: "example-bucket")
    |> range(start: -5m)
    |> experimental.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: