WITH clause
The with clauses allow you to give names to subquery which you can then reference. The syntax for a with clause is:Worked example
Given abids table:
And an
auctions table:
The following query uses CTEs to join bids with their auction items:
Each bid row is matched to its corresponding auction by joining
auction_id to id, producing one output row per bid with the item name attached.
SELECT clause
The select cause is a comma-separated list of expressions, with an optional alias. Column names must be unique.FROM clause
TheFROM clause specifies the primary source of data. It will be either a table name or subquery. The table name can be either a saved source, a table created in the WITH clause or a table created via CREATE TABLE and inserted into. Tables can be given aliases, but will default to their name as the alias for things like joins.
JOIN clause
TheJOIN clause allows you to join multiple tables together.
See the join documentation for more details.
WHERE clause
TheWHERE clause allows you to filter the data with a boolean condition. This predicate is applied to the incoming rows, so cannot include conditions on the resulting columns.
Worked example
Given anevents table:
The following query filters to only pageview events:
Only rows where
event_type = 'pageview' pass the filter. The click and purchase events are excluded.
GROUP BY clause
TheGROUP BY clause is used to compute aggregates over some set of fields. All GROUP BY queries will implicitly include a time window, and if the input doesn’t already have a time window, it should be specified as one of the grouping fields.
For example,
Worked example
Given abids table with events arriving over time:
The following query counts the number of bids and distinct auctions per 1-minute tumbling window:
The
tumble(interval '1 minute') creates fixed, non-overlapping 1-minute windows. All rows within each window are aggregated together. See the windows documentation for more on tumbling and other window types.
HAVING clause
The HAVING clause allows filtering on the result of aggregations (as opposed to WHERE, which filters on the inputs to the aggregation). For example:Worked example
Given the sameevents table:
The following query counts all events per user, then keeps only users with more than 1 event:
- alice has 2 events (pageview + purchase) - included
- bob has 2 events (click + pageview) - included
- charlie has 1 event (pageview) - excluded by the HAVING filter
UNNEST operator
TheUNNEST operator allows you to unnest arrays into multiple rows. This can be used as a normal scalar function with the following restrictions:
- It may only appear in the
SELECTclause - Only one array may be unnested per select statement For example,
Worked example
Given abids table:
The following query unnests a fixed array for each input row:
Each input row is expanded into multiple output rows - one for each element in the unnested array. The other columns are repeated for each expanded row.