OFFSET and SOFFSET clauses

API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.

For more information, see Token hashing.

Use OFFSET and SOFFSET to paginate points and series returned.

OFFSET clause

OFFSET <N> paginates N points in the query results.

Syntax

SELECT_clause FROM_clause [WHERE_clause] [GROUP_BY_clause] [ORDER_BY_clause] LIMIT_clause OFFSET <N> [SLIMIT_clause]

N specifies the number of points to paginate. The OFFSET clause requires a LIMIT clause.

Note: InfluxDB returns no results if the WHERE clause includes a time range and the OFFSET clause would cause InfluxDB to return points with timestamps outside of that time range.

Examples

Paginate points

Paginate points and include several clauses

SOFFSET clause

SOFFSET <N> paginates N series in the query results.

Syntax

SELECT_clause FROM_clause [WHERE_clause] GROUP BY *[,time(time_interval)] [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] SLIMIT_clause SOFFSET <N>

N specifies the number of series to paginate. The SOFFSET clause requires an [SLIMIT clause](/influxdb/version/query-data/influxql/explore-data/limit-and-slimit/. Using the SOFFSET clause without an SLIMIT clause can cause inconsistent query results. SLIMIT queries must include GROUP BY *.

Note: InfluxDB returns no results if the SOFFSET clause paginates through more than the total number of series.

Examples

Paginate series

Paginate points and include several clauses


Was this page helpful?

Thank you for your feedback!