Documentation

Flux

debug.opaque() function

debug.opaque() works like pass in that it passes any incoming tables directly to the following transformation, save for its type signature does not indicate that the input type has any correlation with the output type.

Function type signature
(<-tables: stream[A]) => stream[B] where A: Record, B: Record

For more information, see Function type signatures.

Parameters

tables

Stream to pass unmodified to next transformation.

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

InfluxDB support for debug.opaque()

InfluxDB Cloud

InfluxDB Open Source (OSS)

InfluxDB 1.7

InfluxDB 1.8

InfluxDB 1.11

InfluxDB 2.0

InfluxDB 2.1

InfluxDB 2.2

InfluxDB 2.3

InfluxDB 2.4

InfluxDB 2.5

InfluxDB 2.6

InfluxDB 2.7

InfluxDB Enterprise

InfluxDB Enterprise 1.7

InfluxDB Enterprise 1.8

InfluxDB Enterprise 1.9

InfluxDB Enterprise 1.10

InfluxDB Enterprise 1.11

  • Pending (may not be fully deployed or available in the build yet)
  • Deprecated in this version of InfluxDB

For information about what version of Flux is available in each version of InfluxDB, see Flux versions in InfluxDB.

New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, 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