Documentation

uint() function

uint() converts a value to an unsigned integer type.

uint() behavior depends on the input data type:

Input typeReturned value
bool1 (true) or 0 (false)
durationNumber of nanoseconds in the specified duration
floatUInteger equivalent of the float value truncated at the decimal
intUInteger equivalent of the integer
stringUInteger equivalent of the numeric string
timeEquivalent nanosecond epoch timestamp
Function type signature
(v: A) => uint

For more information, see Function type signatures.

Parameters

v

(Required) Value to convert.

Examples

Convert basic types to unsigned integers

uint(v: "3")

// Returns 3
uint(v: 1m)

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

// Returns 1640995200000000000
uint(v: 10.12)

// Returns 10
uint(v: -100)// Returns 18446744073709551516

Convert all values in a column to unsigned integers

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

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

View example input and output


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 February 3, 2026, 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