Documentation

toUInt() function

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

Supported types and behaviors

toUInt() behavior depends on the _value column type:

_value typeReturned value
stringUInteger equivalent of the numeric string
bool1 (true) or 0 (false)
durationNumber of nanoseconds in the specified duration
timeEquivalent nanosecond epoch timestamp
floatValue truncated at the decimal
intUInteger equivalent of the integer
Function type signature
(<-tables: stream[{A with _value: B}]) => stream[{A with _value: B, _value: uint}]

For more information, see Function type signatures.

Parameters

tables

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

Examples

Convert a float _value column to uintegers

import "sampledata"

sampledata.float()
    |> toUInt()

View example input and output

Convert a boolean _value column to uintegers

import "sampledata"

sampledata.bool()
    |> toUInt()

View example input and output

Convert a uinteger _value column to an uintegers

import "sampledata"

sampledata.uint()
    |> toUInt()

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 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