Documentation

findRecord() function

findRecord() returns a row at a specified index as a record from the first table in a stream of tables that matches the specified predicate function.

The function returns an empty record if no table is found or if the index is out of bounds.

Function type signature
(<-tables: stream[B], fn: (key: A) => bool, idx: int) => B where A: Record, B: Record

For more information, see Function type signatures.

Parameters

idx

(Required) Index of the record to extract.

fn

(Required) Predicate function to evaluate input table group keys.

findColumn() uses the first table that resolves as true. The predicate function requires a key argument that represents each input table’s group key as a record.

tables

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

Examples

Extract a row as a record

import "sampledata"

sampledata.int()
    |> findRecord(
        fn: (key) => key.tag == "t1",
        idx: 0,
    )// Returns {_time: 2021-01-01T00:00:00.000000000Z, _value: -2, tag: t1}

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