clintropolis commented on a change in pull request #11157:
URL: https://github.com/apache/druid/pull/11157#discussion_r623722863



##########
File path: docs/querying/sql.md
##########
@@ -353,6 +353,10 @@ Only the COUNT aggregation can accept DISTINCT.
 |`ANY_VALUE(expr)`|Returns any value of `expr` including null. `expr` must be 
numeric. This aggregator can simplify and optimize the performance by returning 
the first encountered value (including null)|
 |`ANY_VALUE(expr, maxBytesPerString)`|Like `ANY_VALUE(expr)`, but for strings. 
The `maxBytesPerString` parameter determines how much aggregation space to 
allocate per string. Strings longer than this limit will be truncated. This 
parameter should be set as low as possible, since high values will lead to 
wasted memory.|
 |`GROUPING(expr, expr...)`|Returns a number to indicate which groupBy 
dimension is included in a row, when using `GROUPING SETS`. Refer to 
[additional documentation](aggregations.md#grouping-aggregator) on how to infer 
this number.|
+|`ARRAY_AGG(expr)`|Collects all values of `expr` into an ARRAY, including null 
values, with the default limit on aggregation size of 1024 bytes. `ORDER BY` on 
the `ARRAY_AGG` expression is not currently supported.|
+|`ARRAY_AGG(DISTINCT expr)`|Collects all distinct values of `expr` into an 
ARRAY, including null values, with the default limit on aggregation size of 
1024 bytes per aggregate. `ORDER BY` on the `ARRAY_AGG` expression is not 
currently supported.|
+|`ARRAY_AGG(expr, maxSizeBytes)`|Collects all values of `expr` into an ARRAY, 
including null values, with specified maximum byte size per aggregate. `ORDER 
BY` on the `ARRAY_AGG` expression is not currently supported.|
+|`ARRAY_AGG(DISTINCT expr, maxSizeBytes)`|Collects all distinct values of 
`expr` into an ARRAY, including null values, with specified maximum byte size 
per aggregate. `ORDER BY` on the `ARRAY_AGG` expression is not currently 
supported.|

Review comment:
       :+1: changed




-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to