techdocsmith commented on code in PR #15902: URL: https://github.com/apache/druid/pull/15902#discussion_r1498401851
########## docs/querying/sql-window-functions.md: ########## @@ -88,40 +88,133 @@ You can use the OVER clause to treat other Druid aggregation functions as window Window functions support aliasing. -## Define a window with the OVER clause +## Window function syntax + +In general, Druid Window functions use the following syntax: + + +```sql +window_function() OVER ( + [PARTITION BY partitioning expression] + [ORDER BY order expression] + [[ROWS, RANGE] BETWEEN range start AND range end]) +FROM table +GROUP BY dimensions +``` + +```sql +window_function() OVER w +FROM table +WINDOW w AS ([PARTITION BY ] [ORDER BY] + [[ROWS, RANGE] BETWEEN range start AND range end] ) +GROUP BY dimensions +``` The OVER clause defines the query windows for window functions as follows: - PARTITION BY indicates the dimension that defines the rows within the window -- ORDER BY specifies the order of the rows within the windows. +- ORDER BY specifies the order of the rows within the windows Review Comment: ```suggestion - ORDER BY specifies the order of the rows within the windows An empty OVER clause or the absence of a PARTITION BY clause indicates that all data belongs to a single window. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
