Documentation

toInt() function

toInt() converts all values in the _value column to integer types.

Supported types and behaviors

toInt() behavior depends on the _value column type:

_value type Returned value
string Integer equivalent of the numeric string
bool 1 (true) or 0 (false)
duration Number of nanoseconds in the specified duration
time Equivalent nanosecond epoch timestamp
float Value truncated at the decimal
uint Integer equivalent of the unsigned integer
Function type signature
(<-tables: stream[{A with _value: B}]) => stream[{A with _value: B, _value: int}]
For more information, see Function type signatures.

Parameters

tables

Input data. Default is piped-forward data (<-).

Examples

Convert a float _value column to integers

import "sampledata"

sampledata.float()
    |> toInt()

View example input and output

Convert a boolean _value column to integers

import "sampledata"

sampledata.bool()
    |> toInt()

View example input and output

Convert a uinteger _value column to an integers

import "sampledata"

sampledata.uint()
    |> toInt()

View example input and output


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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: