Documentation

join package

The join package provides functions that join two table streams together. Import the join package:

import "join"

Outer joins

The join transformation supports left, right, and full outer joins.

  • Left outer joins generate at least one output row for each record in the left input stream. If a record in the left input stream does not have a match in the right input stream, r is substituted with a default record in the as function.
  • Right outer joins generate at least one output row for each record in the right input stream. If a record in the right input stream does not have a match in the left input stream, l is substituted with a default record in the as function.
  • Full outer joins generate at least one output row for each record in both input streams. If a record in either input stream doesn’t have a match in the other input stream, one of the arguments to the as function is substituted with a default record (either l or r, depending on which one is missing the matching record)

A default record has the same columns as the records in the corresponding input table, but only group key columns are populated with a value. All other columns are null.

Inner joins

Inner joins drop any records that don’t have a match in the other input stream. There is no need to account for default or unmatched records when performing an inner join.

Functions


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: