Documentation

int() function

int() converts a value to an integer type.

int() behavior depends on the input data type:

Input 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
(v: A) => int
For more information, see Function type signatures.

Parameters

v

(Required) Value to convert.

Examples

Convert basic types to integers

int(v: 10.12)

// Returns 10
int(v: "3")

// Returns 3
int(v: true)

// Returns 1
int(v: 1m)

// Returns 160000000000
int(v: 2022-01-01T00:00:00Z)// Returns 1640995200000000000

Convert all values in a column to integers

If converting the _value column to integer types, use toInt(). If converting columns other than _value, use map() to iterate over each row and int() to convert a column value to a integer type.

data
    |> map(fn: (r) => ({r with exampleCol: int(v: r.exampleCol)}))

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: