influxdb/influxql/README.md

790 lines
18 KiB
Markdown
Raw Normal View History

2015-01-08 22:05:17 +00:00
# The Influx Query Language Specification
## Introduction
This is a reference for the Influx Query Language ("InfluxQL").
InfluxQL is a SQL-like query language for interacting with InfluxDB. It has been lovingly crafted to feel familiar to those coming from other SQL or SQL-like environments while providing features specific to storing and analyzing time series data.
2015-01-08 22:05:17 +00:00
## Notation
The syntax is specified using Extended Backus-Naur Form ("EBNF"). EBNF is the same notation used in the [Go](http://golang.org) programming language specification, which can be found [here](https://golang.org/ref/spec). Not so coincidentally, InfluxDB is written in Go.
2015-01-08 22:05:17 +00:00
```
Production = production_name "=" [ Expression ] "." .
Expression = Alternative { "|" Alternative } .
Alternative = Term { Term } .
Term = production_name | token [ "…" token ] | Group | Option | Repetition .
Group = "(" Expression ")" .
Option = "[" Expression "]" .
Repetition = "{" Expression "}" .
```
Notation operators in order of increasing precedence:
```
| alternation
() grouping
[] option (0 or 1 times)
{} repetition (0 to n times)
```
## Query representation
### Characters
InfluxQL is Unicode text encoded in [UTF-8](http://en.wikipedia.org/wiki/UTF-8).
2015-01-08 22:05:17 +00:00
```
newline = /* the Unicode code point U+000A */ .
unicode_char = /* an arbitrary Unicode code point except newline */ .
```
## Letters and digits
Letters are the set of ASCII characters plus the underscore character _ (U+005F) is considered a letter.
Only decimal digits are supported.
```
letter = ascii_letter | "_" .
ascii_letter = "A" … "Z" | "a" … "z" .
digit = "0" … "9" .
2015-02-03 02:33:17 +00:00
```
2015-01-08 22:05:17 +00:00
## Identifiers
2015-10-13 23:54:48 +00:00
Identifiers are tokens which refer to database names, retention policy names, user names, measurement names, tag keys, and field keys.
2015-02-03 02:33:17 +00:00
The rules:
- double quoted identifiers can contain any unicode character other than a new line
- double quoted identifiers can contain escaped `"` characters (i.e., `\"`)
- unquoted identifiers must start with an upper or lowercase ASCII character or "_"
- unquoted identifiers may contain only ASCII letters, decimal digits, and "_"
2015-02-03 02:33:17 +00:00
2015-01-08 22:05:17 +00:00
```
identifier = unquoted_identifier | quoted_identifier .
unquoted_identifier = ( letter ) { letter | digit } .
2015-01-08 22:05:17 +00:00
quoted_identifier = `"` unicode_char { unicode_char } `"` .
```
2015-02-03 02:33:17 +00:00
#### Examples:
```
cpu
_cpu_stats
"1h"
"anything really"
"1_Crazy-1337.identifier>NAME👍"
2015-02-03 02:33:17 +00:00
```
2015-01-08 22:05:17 +00:00
## Keywords
```
ALL ALTER ANY AS ASC BEGIN
BY CREATE CONTINUOUS DATABASE DATABASES DEFAULT
2015-10-26 16:31:38 +00:00
DELETE DESC DESTINATIONS DIAGNOSTICS DISTINCT DROP
Add continuous query option for customizing resampling This makes the following syntax possible: CREATE CONTINUOUS QUERY mycq ON mydb RESAMPLE EVERY 1m FOR 1h BEGIN SELECT mean(value) INTO cpu_mean FROM cpu GROUP BY time(5m) END The RESAMPLE option customizes how often an interval will be sampled and the duration. The interval is customized with EVERY. Any intervals within the resampling duration on a multiple of the resample interval will be updated with the new results from the query. The duration is customized with FOR. This determines how long an interval will participate in resampling. Both options are optional. If RESAMPLE is in the syntax, at least one of the two needs to be given. The default for both is the interval of the continuous query. The service also improves tracking of the last run time and the logic of when a query for an interval should be run. When determining the oldest interval to run for a query, the continuous query service determines what would have been the optimal time to perform the next query based on the last run time. It then uses this time to determine the oldest interval that should be run using the resample duration and will resample all intervals between this time and the current time as opposed to potentially forgetting about the last run in an interval if the continuous query service gets delayed for some reason. This removes the previous config options for customizing continuous queries since they are no longer relevant and adds a new option of customizing the run interval. The run interval determines how often the continuous query service polls for when it should execute a query. This option defaults to 1s, but can be set to 1m if the least common factor of all continuous queries' intervals is a higher value (like 1m).
2015-12-18 20:32:05 +00:00
DURATION END EVERY EXISTS EXPLAIN FIELD
FOR FORCE FROM GRANT GRANTS GROUP
GROUPS IF IN INF INNER INSERT
INTO KEY KEYS LIMIT SHOW MEASUREMENT
MEASUREMENTS NOT OFFSET ON ORDER PASSWORD
POLICY POLICIES PRIVILEGES QUERIES QUERY READ
REPLICATION RESAMPLE RETENTION REVOKE SELECT SERIES
SERVER SERVERS SET SHARD SHARDS SLIMIT
SOFFSET STATS SUBSCRIPTION SUBSCRIPTIONS TAG TO
USER USERS VALUES WHERE WITH WRITE
2015-01-08 22:05:17 +00:00
```
## Literals
### Integers
2015-01-08 22:05:17 +00:00
InfluxQL supports decimal integer literals. Hexadecimal and octal literals are not currently supported.
2015-02-03 02:33:17 +00:00
2015-01-08 22:05:17 +00:00
```
2015-05-05 07:25:53 +00:00
int_lit = ( "1" … "9" ) { digit } .
```
### Floats
InfluxQL supports floating-point literals. Exponents are not currently supported.
```
float_lit = int_lit "." int_lit .
2015-01-08 22:05:17 +00:00
```
### Strings
String literals must be surrounded by single quotes. Strings may contain `'` characters as long as they are escaped (i.e., `\'`).
2015-02-03 02:33:17 +00:00
2015-01-08 22:05:17 +00:00
```
string_lit = `'` { unicode_char } `'` .
2015-01-08 22:05:17 +00:00
```
### Durations
Duration literals specify a length of time. An integer literal followed immediately (with no spaces) by a duration unit listed below is interpreted as a duration literal.
2015-02-03 02:33:17 +00:00
2015-08-27 12:38:16 +00:00
### Duration units
2015-02-03 02:33:17 +00:00
| Units | Meaning |
|--------|-----------------------------------------|
| u or µ | microseconds (1 millionth of a second) |
| ms | milliseconds (1 thousandth of a second) |
| s | second |
| m | minute |
| h | hour |
| d | day |
| w | week |
2015-01-08 22:05:17 +00:00
```
duration_lit = int_lit duration_unit .
2015-01-08 22:05:17 +00:00
duration_unit = "u" | "µ" | "s" | "h" | "d" | "w" | "ms" .
```
2015-02-03 02:33:17 +00:00
### Dates & Times
The date and time literal format is not specified in EBNF like the rest of this document. It is specified using Go's date / time parsing format, which is a reference date written in the format required by InfluxQL. The reference date time is:
2015-02-03 02:33:17 +00:00
InfluxQL reference date time: January 2nd, 2006 at 3:04:05 PM
2015-02-03 02:33:17 +00:00
```
time_lit = "2006-01-02 15:04:05.999999" | "2006-01-02" .
2015-02-03 02:33:17 +00:00
```
### Booleans
2015-02-03 02:33:17 +00:00
```
bool_lit = TRUE | FALSE .
```
### Regular Expressions
```
regex_lit = "/" { unicode_char } "/" .
```
2015-01-08 22:05:17 +00:00
## Queries
A query is composed of one or more statements separated by a semicolon.
```
query = statement { ";" statement } .
2015-01-08 22:05:17 +00:00
statement = alter_retention_policy_stmt |
2015-02-03 02:42:14 +00:00
create_continuous_query_stmt |
2015-01-08 22:05:17 +00:00
create_database_stmt |
create_retention_policy_stmt |
create_subscription_stmt |
create_user_stmt |
2015-01-08 22:05:17 +00:00
delete_stmt |
drop_continuous_query_stmt |
drop_database_stmt |
2015-02-03 04:27:09 +00:00
drop_measurement_stmt |
drop_retention_policy_stmt |
2015-01-08 22:05:17 +00:00
drop_series_stmt |
drop_subscription_stmt |
2015-01-08 22:05:17 +00:00
drop_user_stmt |
grant_stmt |
2015-01-26 03:40:50 +00:00
show_continuous_queries_stmt |
show_databases_stmt |
2015-02-03 02:33:17 +00:00
show_field_keys_stmt |
show_grants_stmt |
2015-01-26 03:40:50 +00:00
show_measurements_stmt |
show_retention_policies |
show_series_stmt |
show_shard_groups_stmt |
2015-08-27 12:38:16 +00:00
show_shards_stmt |
show_subscriptions_stmt|
2015-02-03 02:33:17 +00:00
show_tag_keys_stmt |
show_tag_values_stmt |
2015-01-26 03:40:50 +00:00
show_users_stmt |
2015-01-08 22:05:17 +00:00
revoke_stmt |
select_stmt .
```
## Statements
### ALTER RETENTION POLICY
```
alter_retention_policy_stmt = "ALTER RETENTION POLICY" policy_name on_clause
retention_policy_option
2015-01-08 22:05:17 +00:00
[ retention_policy_option ]
[ retention_policy_option ] .
```
#### Examples:
```sql
-- Set default retention policy for mydb to 1h.cpu.
ALTER RETENTION POLICY "1h.cpu" ON mydb DEFAULT;
-- Change duration and replication factor.
ALTER RETENTION POLICY policy1 ON somedb DURATION 1h REPLICATION 4
```
### CREATE CONTINUOUS QUERY
```
create_continuous_query_stmt = "CREATE CONTINUOUS QUERY" query_name on_clause
Add continuous query option for customizing resampling This makes the following syntax possible: CREATE CONTINUOUS QUERY mycq ON mydb RESAMPLE EVERY 1m FOR 1h BEGIN SELECT mean(value) INTO cpu_mean FROM cpu GROUP BY time(5m) END The RESAMPLE option customizes how often an interval will be sampled and the duration. The interval is customized with EVERY. Any intervals within the resampling duration on a multiple of the resample interval will be updated with the new results from the query. The duration is customized with FOR. This determines how long an interval will participate in resampling. Both options are optional. If RESAMPLE is in the syntax, at least one of the two needs to be given. The default for both is the interval of the continuous query. The service also improves tracking of the last run time and the logic of when a query for an interval should be run. When determining the oldest interval to run for a query, the continuous query service determines what would have been the optimal time to perform the next query based on the last run time. It then uses this time to determine the oldest interval that should be run using the resample duration and will resample all intervals between this time and the current time as opposed to potentially forgetting about the last run in an interval if the continuous query service gets delayed for some reason. This removes the previous config options for customizing continuous queries since they are no longer relevant and adds a new option of customizing the run interval. The run interval determines how often the continuous query service polls for when it should execute a query. This option defaults to 1s, but can be set to 1m if the least common factor of all continuous queries' intervals is a higher value (like 1m).
2015-12-18 20:32:05 +00:00
[ "RESAMPLE" resample_opts ]
2015-01-08 22:05:17 +00:00
"BEGIN" select_stmt "END" .
query_name = identifier .
Add continuous query option for customizing resampling This makes the following syntax possible: CREATE CONTINUOUS QUERY mycq ON mydb RESAMPLE EVERY 1m FOR 1h BEGIN SELECT mean(value) INTO cpu_mean FROM cpu GROUP BY time(5m) END The RESAMPLE option customizes how often an interval will be sampled and the duration. The interval is customized with EVERY. Any intervals within the resampling duration on a multiple of the resample interval will be updated with the new results from the query. The duration is customized with FOR. This determines how long an interval will participate in resampling. Both options are optional. If RESAMPLE is in the syntax, at least one of the two needs to be given. The default for both is the interval of the continuous query. The service also improves tracking of the last run time and the logic of when a query for an interval should be run. When determining the oldest interval to run for a query, the continuous query service determines what would have been the optimal time to perform the next query based on the last run time. It then uses this time to determine the oldest interval that should be run using the resample duration and will resample all intervals between this time and the current time as opposed to potentially forgetting about the last run in an interval if the continuous query service gets delayed for some reason. This removes the previous config options for customizing continuous queries since they are no longer relevant and adds a new option of customizing the run interval. The run interval determines how often the continuous query service polls for when it should execute a query. This option defaults to 1s, but can be set to 1m if the least common factor of all continuous queries' intervals is a higher value (like 1m).
2015-12-18 20:32:05 +00:00
resample_opts = (every_stmt for_stmt | every_stmt | for_stmt) .
every_stmt = "EVERY" duration_lit
for_stmt = "FOR" duration_lit
2015-01-08 22:05:17 +00:00
```
#### Examples:
```sql
2015-03-22 15:40:33 +00:00
-- selects from default retention policy and writes into 6_months retention policy
CREATE CONTINUOUS QUERY "10m_event_count"
2015-01-08 22:05:17 +00:00
ON db_name
BEGIN
SELECT count(value)
2015-03-22 15:40:33 +00:00
INTO "6_months".events
2015-01-08 22:05:17 +00:00
FROM events
GROUP BY time(10m)
END;
2015-03-22 15:40:33 +00:00
-- this selects from the output of one continuous query in one retention policy and outputs to another series in another retention policy
CREATE CONTINUOUS QUERY "1h_event_count"
2015-01-08 22:05:17 +00:00
ON db_name
BEGIN
SELECT sum(count) as count
2015-03-22 15:40:33 +00:00
INTO "2_years".events
FROM "6_months".events
2015-01-08 22:05:17 +00:00
GROUP BY time(1h)
END;
Add continuous query option for customizing resampling This makes the following syntax possible: CREATE CONTINUOUS QUERY mycq ON mydb RESAMPLE EVERY 1m FOR 1h BEGIN SELECT mean(value) INTO cpu_mean FROM cpu GROUP BY time(5m) END The RESAMPLE option customizes how often an interval will be sampled and the duration. The interval is customized with EVERY. Any intervals within the resampling duration on a multiple of the resample interval will be updated with the new results from the query. The duration is customized with FOR. This determines how long an interval will participate in resampling. Both options are optional. If RESAMPLE is in the syntax, at least one of the two needs to be given. The default for both is the interval of the continuous query. The service also improves tracking of the last run time and the logic of when a query for an interval should be run. When determining the oldest interval to run for a query, the continuous query service determines what would have been the optimal time to perform the next query based on the last run time. It then uses this time to determine the oldest interval that should be run using the resample duration and will resample all intervals between this time and the current time as opposed to potentially forgetting about the last run in an interval if the continuous query service gets delayed for some reason. This removes the previous config options for customizing continuous queries since they are no longer relevant and adds a new option of customizing the run interval. The run interval determines how often the continuous query service polls for when it should execute a query. This option defaults to 1s, but can be set to 1m if the least common factor of all continuous queries' intervals is a higher value (like 1m).
2015-12-18 20:32:05 +00:00
-- this customizes the resample interval so the interval is queried every 10s and intervals are resampled until 2m after their start time
-- when resample is used, at least one of "EVERY" or "FOR" must be used
CREATE CONTINUOUS QUERY "cpu_mean"
ON db_name
RESAMPLE EVERY 10s FOR 2m
BEGIN
SELECT mean(value)
INTO "cpu_mean"
FROM "cpu"
GROUP BY time(1m)
END;
2015-01-08 22:05:17 +00:00
```
### CREATE DATABASE
```
create_database_stmt = "CREATE DATABASE" db_name .
2015-01-08 22:05:17 +00:00
```
#### Example:
```sql
CREATE DATABASE foo
```
### CREATE RETENTION POLICY
```
create_retention_policy_stmt = "CREATE RETENTION POLICY" policy_name on_clause
retention_policy_duration
2015-01-08 22:05:17 +00:00
retention_policy_replication
[ "DEFAULT" ] .
```
#### Examples
```sql
-- Create a retention policy.
CREATE RETENTION POLICY "10m.events" ON somedb DURATION 10m REPLICATION 2;
-- Create a retention policy and set it as the default.
CREATE RETENTION POLICY "10m.events" ON somedb DURATION 10m REPLICATION 2 DEFAULT;
```
### CREATE SUBSCRIPTION
```
create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} .
```
#### Examples:
```sql
-- Create a SUBSCRIPTION on database 'mydb' and retention policy 'default' that send data to 'example.com:9090' via UDP.
CREATE SUBSCRIPTION sub0 ON "mydb"."default" DESTINATIONS ALL 'udp://example.com:9090' ;
-- Create a SUBSCRIPTION on database 'mydb' and retention policy 'default' that round robins the data to 'h1.example.com:9090' and 'h2.example.com:9090'.
CREATE SUBSCRIPTION sub0 ON "mydb"."default" DESTINATIONS ANY 'udp://h1.example.com:9090', 'udp://h2.example.com:9090';
```
2015-01-08 22:05:17 +00:00
### CREATE USER
```
create_user_stmt = "CREATE USER" user_name "WITH PASSWORD" password
[ "WITH ALL PRIVILEGES" ] .
2015-01-08 22:05:17 +00:00
```
#### Examples:
2015-01-08 22:05:17 +00:00
```sql
-- Create a normal database user.
2015-04-29 18:38:20 +00:00
CREATE USER jdoe WITH PASSWORD '1337password';
-- Create a cluster admin.
-- Note: Unlike the GRANT statement, the "PRIVILEGES" keyword is required here.
2015-04-29 18:38:20 +00:00
CREATE USER jdoe WITH PASSWORD '1337password' WITH ALL PRIVILEGES;
2015-01-08 22:05:17 +00:00
```
### DELETE
```
delete_stmt = "DELETE FROM" measurement where_clause .
2015-01-08 22:05:17 +00:00
```
#### Example:
```sql
-- delete data points from the cpu measurement where the region tag
-- equals 'uswest'
DELETE FROM cpu WHERE region = 'uswest';
```
2015-02-03 02:33:17 +00:00
### DROP CONTINUOUS QUERY
```
drop_continuous_query_stmt = "DROP CONTINUOUS QUERY" query_name on_clause .
```
2015-02-03 02:33:17 +00:00
#### Example:
```sql
2015-11-22 18:21:37 +00:00
DROP CONTINUOUS QUERY myquery ON mydb;
2015-02-03 02:33:17 +00:00
```
### DROP DATABASE
```
2015-02-03 02:33:17 +00:00
drop_database_stmt = "DROP DATABASE" db_name .
```
2015-02-03 02:33:17 +00:00
#### Example:
```sql
DROP DATABASE mydb;
```
2015-02-03 04:27:09 +00:00
### DROP MEASUREMENT
```
2015-11-22 18:21:37 +00:00
drop_measurement_stmt = "DROP MEASUREMENT" measurement_name .
2015-02-03 04:27:09 +00:00
```
#### Examples:
```sql
-- drop the cpu measurement
DROP MEASUREMENT cpu;
```
### DROP RETENTION POLICY
```
drop_retention_policy_stmt = "DROP RETENTION POLICY" policy_name on_clause .
```
#### Example:
```sql
-- drop the retention policy named 1h.cpu from mydb
DROP RETENTION POLICY "1h.cpu" ON mydb;
2015-01-08 22:05:17 +00:00
```
2015-02-03 02:33:17 +00:00
### DROP SERIES
```
drop_series_stmt = "DROP SERIES" ( from_clause | where_clause | from_clause where_clause ) .
2015-02-03 02:33:17 +00:00
```
#### Example:
```sql
```
### DROP SUBSCRIPTION
```
drop_subscription_stmt = "DROP SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy .
```
#### Example:
```sql
DROP SUBSCRIPTION sub0 ON "mydb"."default";
```
2015-02-03 02:33:17 +00:00
### DROP USER
```
drop_user_stmt = "DROP USER" user_name .
2015-02-03 02:33:17 +00:00
```
#### Example:
```sql
DROP USER jdoe;
2015-02-03 02:33:17 +00:00
```
2015-01-09 01:54:55 +00:00
### GRANT
2015-02-03 02:33:17 +00:00
NOTE: Users can be granted privileges on databases that do not exist.
2015-01-09 01:54:55 +00:00
```
grant_stmt = "GRANT" privilege [ on_clause ] to_clause .
2015-01-09 01:54:55 +00:00
```
#### Examples:
```sql
-- grant cluster admin privileges
GRANT ALL TO jdoe;
-- grant read access to a database
GRANT READ ON mydb TO jdoe;
```
2015-02-03 02:33:17 +00:00
### SHOW CONTINUOUS QUERIES
```
show_continuous_queries_stmt = "SHOW CONTINUOUS QUERIES" .
```
2015-02-03 02:33:17 +00:00
#### Example:
```sql
-- show all continuous queries
SHOW CONTINUOUS QUERIES;
```
2015-01-26 03:40:50 +00:00
### SHOW DATABASES
```
2015-01-26 03:40:50 +00:00
show_databases_stmt = "SHOW DATABASES" .
```
#### Example:
```sql
2015-01-26 03:40:50 +00:00
-- show all databases
SHOW DATABASES;
```
### SHOW FIELD KEYS
2015-02-03 02:33:17 +00:00
```
2015-02-16 20:30:58 +00:00
show_field_keys_stmt = "SHOW FIELD KEYS" [ from_clause ] .
```
2015-02-03 02:33:17 +00:00
#### Examples:
```sql
2015-02-16 20:30:58 +00:00
-- show field keys from all measurements
SHOW FIELD KEYS;
2015-02-03 02:33:17 +00:00
2015-02-16 20:30:58 +00:00
-- show field keys from specified measurement
SHOW FIELD KEYS FROM cpu;
2015-02-03 02:33:17 +00:00
```
### SHOW GRANTS
```
show_grants_stmt = "SHOW GRANTS FOR" user_name .
```
#### Example:
```sql
-- show grants for jdoe
SHOW GRANTS FOR jdoe;
```
2015-02-03 02:33:17 +00:00
### SHOW MEASUREMENTS
```
show_measurements_stmt = "SHOW MEASUREMENTS" [ with_measurement_clause ] [ where_clause ] [ limit_clause ] [ offset_clause ] .
```
2015-02-03 02:33:17 +00:00
```sql
-- show all measurements
SHOW MEASUREMENTS;
-- show measurements where region tag = 'uswest' AND host tag = 'serverA'
SHOW MEASUREMENTS WHERE region = 'uswest' AND host = 'serverA';
```
2015-01-26 03:40:50 +00:00
### SHOW RETENTION POLICIES
```
show_retention_policies = "SHOW RETENTION POLICIES" on_clause .
```
#### Example:
```sql
2015-01-26 03:40:50 +00:00
-- show all retention policies on a database
SHOW RETENTION POLICIES ON mydb;
```
2015-02-03 02:33:17 +00:00
### SHOW SERIES
```
show_series_stmt = "SHOW SERIES" [ from_clause ] [ where_clause ] [ limit_clause ] [ offset_clause ] .
2015-02-03 02:33:17 +00:00
```
#### Example:
```sql
```
2015-11-13 23:26:30 +00:00
### SHOW SHARD GROUPS
```
show_shard_groups_stmt = "SHOW SHARD GROUPS" .
```
#### Example:
```sql
SHOW SHARD GROUPS;
```
2015-08-27 12:38:16 +00:00
### SHOW SHARDS
```
show_shards_stmt = "SHOW SHARDS" .
```
#### Example:
```sql
SHOW SHARDS;
```
### SHOW SUBSCRIPTIONS
```
show_subscriptions_stmt = "SHOW SUBSCRIPTIONS" .
```
#### Example:
```sql
SHOW SUBSCRIPTIONS;
```
2015-02-03 02:33:17 +00:00
### SHOW TAG KEYS
```
2015-08-27 12:38:16 +00:00
show_tag_keys_stmt = "SHOW TAG KEYS" [ from_clause ] [ where_clause ] [ group_by_clause ]
2015-02-03 02:33:17 +00:00
[ limit_clause ] [ offset_clause ] .
```
#### Examples:
```sql
-- show all tag keys
SHOW TAG KEYS;
-- show all tag keys from the cpu measurement
SHOW TAG KEYS FROM cpu;
-- show all tag keys from the cpu measurement where the region key = 'uswest'
SHOW TAG KEYS FROM cpu WHERE region = 'uswest';
-- show all tag keys where the host key = 'serverA'
2015-02-03 02:33:17 +00:00
SHOW TAG KEYS WHERE host = 'serverA';
```
### SHOW TAG VALUES
```
2015-08-27 12:38:16 +00:00
show_tag_values_stmt = "SHOW TAG VALUES" [ from_clause ] with_tag_clause [ where_clause ]
2015-02-03 02:33:17 +00:00
[ group_by_clause ] [ limit_clause ] [ offset_clause ] .
```
#### Examples:
```sql
-- show all tag values across all measurements for the region tag
SHOW TAG VALUES WITH TAG = 'region';
-- show tag values from the cpu measurement for the region tag
SHOW TAG VALUES FROM cpu WITH KEY = 'region';
2015-02-03 02:33:17 +00:00
-- show tag values from the cpu measurement for region & host tag keys where service = 'redis'
SHOW TAG VALUES FROM cpu WITH KEY IN (region, host) WHERE service = 'redis';
2015-02-03 02:33:17 +00:00
```
2015-01-26 03:40:50 +00:00
### SHOW USERS
2015-01-14 16:53:17 +00:00
```
2015-01-26 03:40:50 +00:00
show_users_stmt = "SHOW USERS" .
2015-01-14 16:53:17 +00:00
```
#### Example:
```sql
2015-01-26 03:40:50 +00:00
-- show all users
SHOW USERS;
2015-01-14 16:53:17 +00:00
```
2015-02-03 02:33:17 +00:00
### REVOKE
```
revoke_stmt = "REVOKE" privilege [ on_clause ] "FROM" user_name .
2015-02-03 02:33:17 +00:00
```
#### Examples:
```sql
-- revoke cluster admin from jdoe
REVOKE ALL PRIVILEGES FROM jdoe;
-- revoke read privileges from jdoe on mydb
REVOKE READ ON mydb FROM jdoe;
```
### SELECT
```
2015-08-27 12:38:16 +00:00
select_stmt = "SELECT" fields from_clause [ into_clause ] [ where_clause ]
2015-02-03 02:33:17 +00:00
[ group_by_clause ] [ order_by_clause ] [ limit_clause ]
[ offset_clause ] [ slimit_clause ] [ soffset_clause ] .
2015-02-03 02:33:17 +00:00
```
#### Examples:
```sql
-- select mean value from the cpu measurement where region = 'uswest' grouped by 10 minute intervals
2015-03-12 01:12:42 +00:00
SELECT mean(value) FROM cpu WHERE region = 'uswest' GROUP BY time(10m) fill(0);
2015-11-22 18:21:37 +00:00
-- select from all measurements beginning with cpu into the same measurement name in the cpu_1h retention policy
SELECT mean(value) INTO cpu_1h.:MEASUREMENT FROM /cpu.*/
2015-02-03 02:33:17 +00:00
```
## Clauses
2015-01-08 22:05:17 +00:00
```
2015-02-03 02:33:17 +00:00
from_clause = "FROM" measurements .
group_by_clause = "GROUP BY" dimensions fill(fill_option).
2015-11-22 18:21:37 +00:00
into_clause = "INTO" ( measurement | back_ref ).
2015-01-08 22:05:17 +00:00
2015-02-03 02:33:17 +00:00
limit_clause = "LIMIT" int_lit .
2015-01-09 01:54:55 +00:00
2015-02-03 02:33:17 +00:00
offset_clause = "OFFSET" int_lit .
2015-01-09 01:54:55 +00:00
slimit_clause = "SLIMIT" int_lit .
soffset_clause = "SOFFSET" int_lit .
on_clause = "ON" db_name .
2015-02-03 02:33:17 +00:00
order_by_clause = "ORDER BY" sort_fields .
to_clause = "TO" user_name .
2015-02-03 02:33:17 +00:00
where_clause = "WHERE" expr .
with_measurement_clause = "WITH MEASUREMENT" ( "=" measurement | "=~" regex_lit ) .
with_tag_clause = "WITH KEY" ( "=" tag_key | "IN (" tag_keys ")" ) .
2015-01-08 22:05:17 +00:00
```
2015-02-03 02:33:17 +00:00
## Expressions
2015-01-08 22:05:17 +00:00
```
2015-02-03 02:33:17 +00:00
binary_op = "+" | "-" | "*" | "/" | "AND" | "OR" | "=" | "!=" | "<" |
"<=" | ">" | ">=" .
expr = unary_expr { binary_op unary_expr } .
2015-05-27 16:35:29 +00:00
unary_expr = "(" expr ")" | var_ref | time_lit | string_lit | int_lit |
float_lit | bool_lit | duration_lit | regex_lit .
2015-02-16 20:30:58 +00:00
```
2015-02-03 02:33:17 +00:00
## Other
2015-02-16 20:30:58 +00:00
```
alias = "AS" identifier .
2015-11-22 18:21:37 +00:00
back_ref = ( policy_name ".:MEASUREMENT" ) |
( db_name "." [ policy_name ] ".:MEASUREMENT" ) .
db_name = identifier .
dimension = expr .
dimensions = dimension { "," dimension } .
field_key = identifier .
2015-02-03 02:33:17 +00:00
field = expr [ alias ] .
fields = field { "," field } .
fill_option = "null" | "none" | "previous" | int_lit | float_lit .
host = string_lit .
2015-02-03 04:27:09 +00:00
measurement = measurement_name |
( policy_name "." measurement_name ) |
( db_name "." [ policy_name ] "." measurement_name ) .
2015-02-03 02:33:17 +00:00
measurements = measurement { "," measurement } .
2015-01-09 01:54:55 +00:00
2015-02-03 04:27:09 +00:00
measurement_name = identifier .
password = string_lit .
2015-01-09 01:54:55 +00:00
policy_name = identifier .
2015-01-09 01:54:55 +00:00
privilege = "ALL" [ "PRIVILEGES" ] | "READ" | "WRITE" .
2015-02-03 02:33:17 +00:00
query_name = identifier .
retention_policy = identifier .
retention_policy_option = retention_policy_duration |
retention_policy_replication |
"DEFAULT" .
retention_policy_duration = "DURATION" duration_lit .
retention_policy_replication = "REPLICATION" int_lit
2015-02-03 04:27:09 +00:00
series_id = int_lit .
2015-10-13 23:54:48 +00:00
sort_field = field_key [ ASC | DESC ] .
2015-02-03 02:33:17 +00:00
sort_fields = sort_field { "," sort_field } .
subscription_name = identifier .
tag_key = identifier .
tag_keys = tag_key { "," tag_key } .
2015-02-03 02:33:17 +00:00
user_name = identifier .
var_ref = measurement .
2015-01-08 22:05:17 +00:00
```