Skip to content

Commit

Permalink
chore: query
Browse files Browse the repository at this point in the history
  • Loading branch information
discord9 committed Sep 5, 2024
1 parent 2501067 commit a50d9a4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/user-guide/continuous-aggregation/query.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ The query should have a `FROM` clause to identify the source table. As the join

`WHERE` and `HAVING` clauses are supported in the continuous aggregation query. They work as in a normal query. The `WHERE` clause filters the data before aggregation, and the `HAVING` clause filters the data after aggregation.

`DISTINCT` currently only work with `SELECT DISTINCT column1, column2,..` syntax. It is used to remove duplicate rows from the result set. Support for `SELECT count(DISTINCT column1, column2,..)` is not available yet, but it will be added in the future.
`DISTINCT` currently only work with `SELECT DISTINCT column1 ..` syntax. It is used to remove duplicate rows from the result set. Support for `SELECT count(DISTINCT column1) ...` is not available yet, but it will be added in the future.

`GROUP BY` clause works as in a normal query. It groups the data by the specified columns. One special thing is the time window functions `hop()` and `tumble()` described in [Define Time Window](./define-time-window.md) part. They are used in the `GROUP BY` clause to define the time window for the aggregation. Other expressions in `GROUP BY` can be either literal, column or scalar expressions.

Expand Down

0 comments on commit a50d9a4

Please sign in to comment.