Flux vs InfluxQL

InfluxQL has never supported joins. Although you can use a join in a TICKscript, TICKscript’s join capabilities are limited. Flux’s lets you join data from any bucket, any measurement, and on any columns as long as each data set includes the columns to join on.

For an in-depth walkthrough of using the function, see how to join data with Flux.

Math across measurements

Being able to perform joins across measurements lets you calculate data from separate measurements. The example below takes data from two measurements, mem and processes, joins them, and then calculates the average amount of memory used per running process:

  1. // Memory used (in bytes)
  2. memUsed = from(bucket: "example-bucket")
  3.     |> range(start: -1h)
  5. // Total processes running
  6. procTotal = from(bucket: "example-bucket")
  7.     |> range(start: -1h)
  8.     |> filter(fn: (r) => r._measurement == "processes" and r._field == "total")
  10. // Join memory used with total processes to calculate
  11. // the average memory (in MB) used for running processes.
  12. join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
  13.     |> map(fn: (r) => ({_time: r._time, _value: r._value_mem / r._value_proc / 1000000}))

Sort by tags

InfluxQL’s sorting capabilities only let you control the sort order of time using the ORDER BY time clause. The Flux sorts records based on a list of columns. Depending on the column type, Flux sorts records lexicographically, numerically, or chronologically.

  1. from(bucket: "example-bucket")
  2.     |> range(start: -12h)
  3.     |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
  4.     |> sort(columns: ["region", "host", "_value"])

Group by any column

InfluxQL lets you group by tags or time intervals only. Flux lets you group data by any column, including _value. Use the Flux to define which columns to group data by.

  1. from(bucket:"example-bucket")
  2.     |> range(start: -12h)
  3.     |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime" )
  4.     |> group(columns:["host", "_value"])

Work with multiple data sources

InfluxQL can only query data stored in InfluxDB. Flux can query data from other data sources such as CSV, PostgreSQL, MySQL, Google BigTable, and more. Join that data with data in InfluxDB to enrich query results.

  1. import "csv"
  2. import "sql"
  4. csvData = csv.from(csv: rawCSV)
  6. sqlData = sql.from(
  7.     driverName: "postgres",
  8.     dataSourceName: "postgresql://user:password@localhost",
  9.     query: "SELECT * FROM example_table",
  10. )
  12. data = from(bucket: "example-bucket")
  13.     |> range(start: -24h)
  14.     |> filter(fn: (r) => r._measurement == "sensor")
  16. enrichedData = join(tables: {data: data, aux: auxData}, on: ["sensor_id"])
  18. enrichedData
  19.     |> yield(name: "enriched_data")

For an in-depth walkthrough of querying SQL data, see Query SQL data sources.

DatePart-like queries

InfluxQL doesn’t support DatePart-like queries that only return results during specified hours of the day. The Flux hourSelection function returns only data with time values in a specified hour range.

  1. from(bucket: "example-bucket")
  2.     |> range(start: -1h)
  3.     |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
  4.     |> hourSelection(start: 9, stop: 17)

Pivot

Pivoting data tables isn’t supported in InfluxQL. Use the Flux pivot() function to pivot data tables by rowKey, columnKey, and parameters.

  1. from(bucket: "example-bucket")
  2.     |> range(start: -1h)
  3.     |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
  4.     |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")

Generating histograms isn’t supported in InfluxQL. Use the Flux to generate a cumulative histogram.

Covariance

Flux provides functions for simple covariance calculations. Use the to calculate the covariance between two columns and the cov() function to calculate the covariance between two data streams.

Covariance between two columns
  1. from(bucket: "example-bucket")
  2.     |> range(start:-5m)
  3.     |> covariance(columns: ["x", "y"])
Covariance between two streams of data
  1. table1 = from(bucket: "example-bucket")
  2.     |> range(start: -15m)
  3.     |> filter(fn: (r) => r._measurement == "measurement_1")
  5. table2 = from(bucket: "example-bucket")
  6.     |> range(start: -15m)
  7.     |> filter(fn: (r) => r._measurement == "measurement_2")
  9. cov(x: table1, y: table2, on: ["_time", "_field"])

Cast booleans to integers

InfluxQL supports type casting for numeric data types (floats to integers and vice versa) only. Use Flux type conversion functions to perform many more type conversions, including casting boolean values to integers.

Cast boolean field values to integers
  1. from(bucket: "example-bucket")
  2.     |> range(start: -1h)
  3.     |> filter(fn: (r) => r._measurement == "m" and r._field == "bool_field")
  4.     |> toInt()

String manipulation and data shaping

InfluxQL doesn’t support string manipulation when querying data. Use functions to operate on string data. Combine functions in this package with the map() function to perform operations like sanitizing and normalizing strings.

InfluxQL doesn’t support working with geo-temporal data. The is a collection of functions that let you shape, filter, and group geo-temporal data.

  1. import "experimental/geo"
  3. from(bucket: "geo/autogen")
  4.     |> range(start: -1w)
  5.     |> filter(fn: (r) => r._measurement == "taxi")
  6.     |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 20)
  7.     |> geo.filterRows(region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0}, strict: true)

InfluxQL and Flux parity

We’re continuing to add functions to complete parity between Flux and InfluxQL. The table below shows InfluxQL statements, clauses, and functions along with their equivalent Flux functions.