Documentation

influx transpile

Removed in InfluxDB OSS 2.0.5

The influx transpile command was removed in InfluxDB 2.0.5. Use InfluxQL to query InfluxDB. For information about manually converting InfluxQL queries to Flux, see:

The influx transpile command transpiles an InfluxQL query to Flux source code. The transpiled query assumes the bucket name is <database>/<retention policy> and includes absolute time ranges using the provided --now time.

Usage

influx transpile [InfluxQL query] [flags]

The InfluxQL query must be valid and contain both a database and measurement. See the InfluxQL documentation for more information.

Flags

FlagDescription
-h--helpHelp for the transpile command
--nowRFC3339Nano timestamp to use as now() time (default is current UTC time)

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Transpile InfluxQL queries to Flux
## Transpile an InfluxQL query that specifies the database,
## retention policy, and measurement.
influx transpile 'SELECT example-field FROM db.rp.measurement'

## Transpile InfluxQL query using default retention policy
influx transpile 'SELECT example-field FROM db..measurement'

Was this page helpful?

Thank you for your feedback!


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: