Documentation

v1.fieldKeys() function

Deprecated

v1.fieldKeys() was deprecated in Flux v0.88.0 in favor of schema.fieldKeys().

v1.fieldKeys() returns field keys in a bucket.

Results include a single table with a single column, _value.

Note: FieldKeys is a special application of `tagValues that returns field keys in a given bucket.

Function type signature
(
    bucket: string,
    ?predicate: (
        r: {
            A with
            _value: B,
            _time: time,
            _stop: time,
            _start: time,
            _measurement: string,
            _field: string,
        },
    ) => bool,
    ?start: C,
    ?stop: D,
) => stream[E] where E: Record

For more information, see Function type signatures.

Parameters

bucket

(Required) Bucket to list field keys from.

predicate

Predicate function that filters field keys. Default is (r) => true.

start

Oldest time to include in results. Default is -30d.

stop

Newest time include in results. The stop time is exclusive, meaning values with a time equal to stop time are excluded from the results. Default is now().

Relative start times are defined using negative durations. Negative durations are relative to now(). Absolute start times are defined using time values.

Examples

Query field keys from an InfluxDB bucket

import "influxdata/influxdb/schema"

schema.fieldKeys(bucket: "example-bucket")

Not supported in the Flux REPL

v1 functions can retrieve schema information when executed within the context of InfluxDB, but not from the Flux REPL.


Was this page helpful?

Thank you for your feedback!


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: