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!


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