Documentation

SELECT statement

Use the SELECT statement to query data from one or more measurements. The SELECT statement requires a SELECT clause and a FROM clause.

Syntax

SELECT field_expression[, ..., field_expression_n[, tag_expression[, ..., tag_expression_n]]] FROM measurement_expression[, ..., measurement_expression_n]

SELECT clause

The SELECT clause supports several formats for identifying data to query. It requires one or more field expressions and optional tag expressions.

  • field_expression: Expression to identify one or more fields to return in query results. Can be a field key, constant, regular expression, wildcard (*), or function expression and any combination of arithmetic operators.
  • tag_expression: Expression to identify one or more tags to return in query results. Can be a tag key or constant.

Select clause behaviors

  • SELECT field_key - Returns a specific field.
  • SELECT field_key1, field_key2 - Returns two specific fields.
  • SELECT field_key, tag_key - Returns a specific field and tag.
  • SELECT * - Returns all fields and tags. See Wildcard expressions.
  • SELECT /^[t]/ - Returns all fields and tags with keys that match the regular expression. At least one field key must match the regular expression. If no field keys match the regular expression, no results are returned.

FROM clause

The FROM clause specifies the measurement to query. It requires one or more comma-delimited measurement expressions.

  • measurement_expression

    Expression to identify one or more measurements to query. Can be a measurement name, fully-qualified measurement, constant, or regular expression.

    • Measurement name
      FROM measurement
      
    • Fully-qualified measurement
      FROM database.retention_policy.measurement
      
      -- Fully-qualified measurement with default retention policy
      FROM database..measurement
      

      InfluxDB retention policies

      In InfluxDB Cloud Dedicated, retention policies are not part of the data model like they are in InfluxDB 1.x. Each InfluxDB Cloud Dedicated database has a retention period which defines the maximum age of data to retain in the database. To use fully-qualified measurements in InfluxQL queries, use the following naming convention when creating a database:

      database_name/retention_policy
      

Notable SELECT statement behaviors

Must query at least one field

A query requires at least one field key in the SELECT clause to return data. If the SELECT clause includes only tag keys, the query returns an empty result. When using regular expressions in the SELECT clause, if regular expression matches only tag keys and no field keys, the query returns an empty result.

To return data associated with tag keys, include at least one field key in the SELECT clause.

Wildcard expressions

When using a wildcard expression (*) in the SELECT clause, the query returns all tags and fields. If a function is applied to a wildcard expression, the query returns all fields with the function applied, but does not return tags unless they are included in the SELECT clause.

Cannot include both aggregate and non-aggregate field expressions

The SELECT statement cannot include an aggregate field expression (one that uses an aggregate or selector function) and a non-aggregate field expression. For example, in the following query, an aggregate function is applied to one field, but not the other:

SELECT mean(temp), hum FROM home

This query returns an error. For more information, see error about mixing aggregate and non-aggregate queries.

Data types and casting operations

The SELECT clause supports specifying a field’s type and basic casting operations with the :: syntax.

SELECT field_expression::type FROM measurement_expression

The :: syntax allows users to perform basic cast operations in queries. Currently, InfluxQL supports casting numeric field values to other numeric types. Casting to an identifier type acts as a filter on results and returns only columns of that specific identifier type along with the time column.

Numeric types
  • float
  • integer
  • unsigned
Non-numeric types
  • string
  • boolean
Identifier types
  • field
  • tag

InfluxQL returns no data if the query attempts to cast a numeric value to a non-numeric type and vice versa.

When casting a float value to an integer or unsigned integer, the float value is truncated at the decimal point. No rounding is performed.

SELECT statement examples

The examples below use the following sample data sets:

Select all fields and tags from a measurement

Select specific tags and fields from a measurement

Select all fields from a measurement

Select a field from a measurement and perform basic arithmetic

Select all data from more than one measurement

Select all data from a fully-qualified measurement (with default retention policy)

Type-casting examples

Cast an integer field to a float

Cast a float field to an integer

Cast a float field to an unsigned integer


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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: