Documentation

Work with booleans

A boolean type represents a truth value (true or false).

Type name: bool

Boolean syntax

Boolean literals are represented by the following:

true
false

Convert data types to booleans

Use the bool() function to convert the following basic types to booleans:

  • string: value must be "true" or "false".
  • float: value must be 0.0 (false) or 1.0 (true).
  • int: value must be 0 (false) or 1 (true).
  • uint: value must be 0 (false) or 1 (true).
bool(v: "true")
// Returns true

bool(v: 0.0)
// Returns false

bool(v: 0)
// Returns false

bool(v: uint(v: 1))
// Returns true

Convert columns to booleans

Flux lets you iterate over rows in a stream of tables and convert columns to booleans.

To convert the _value column to booleans, use the toBool() function.

toBool() only operates on the _value column.

data
    |> toBool()
Given the following input data:
_time_value (float)
2021-01-01T00:00:00Z1.0
2021-01-01T02:00:00Z0.0
2021-01-01T03:00:00Z0.0
2021-01-01T04:00:00Z1.0
The example above returns:
_time_value (bool)
2021-01-01T00:00:00Ztrue
2021-01-01T02:00:00Zfalse
2021-01-01T03:00:00Zfalse
2021-01-01T04:00:00Ztrue

To convert any column to booleans:

  1. Use map() to iterate over and rewrite rows.
  2. Use bool() to convert columns values to booleans.
data
    |> map(fn: (r) => ({ r with running: bool(v: r.running) }))
Given the following input data:
_timerunning (int)
2021-01-01T00:00:00Z1
2021-01-01T02:00:00Z0
2021-01-01T03:00:00Z0
2021-01-01T04:00:00Z1
The example above returns:
_timerunning (bool)
2021-01-01T00:00:00Ztrue
2021-01-01T02:00:00Zfalse
2021-01-01T03:00:00Zfalse
2021-01-01T04:00:00Ztrue

Negate boolean values

To negate boolean values, use the not logical operator.

not true
// Returns false

not false
// Returns true

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