join.time() function

join.time() joins two table streams together exclusively on the _time column.

This function calls join.tables() with the on parameter set to (l, r) => l._time == r._time.

Function type signature
    <-left: stream[{A with _time: B}],
    as: (l: {A with _time: B}, r: {C with _time: D}) => E,
    right: stream[{C with _time: D}],
    ?method: string,
) => stream[E] where B: Equatable, D: Equatable, E: Record
For more information, see Function type signatures.



Left input stream. Default is piped-forward data (<-).

(Required) Right input stream.


(Required) Function that takes a left and a right record (l and r respectively), and returns a record. The returned record is included in the final output.


String that specifies the join method. Default is inner.

Supported methods:

  • inner
  • left
  • right
  • full


Join two tables by timestamp

import "sampledata"
import "join"

ints =
strings = sampledata.string()

join.time(left: ints, right: strings, as: (l, r) => ({l with label: r._value}))

View example output

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: