mirror of
https://github.com/apache/druid.git
synced 2025-02-17 07:25:02 +00:00
Update documentation for exceptions to subquery limit. (#16295)
The true exception for groupBy is somewhat more narrow than the docs suggest.
This commit is contained in:
parent
6974498d98
commit
4285a5e2c6
@ -93,9 +93,9 @@ cannot exceed the [`druid.server.http.maxSubqueryRows`](../configuration/index.m
|
|||||||
[`druid.server.http.maxSubqueryBytes`](../configuration/index.md) if set. Otherwise, Druid throws a resource limit exceeded
|
[`druid.server.http.maxSubqueryBytes`](../configuration/index.md) if set. Otherwise, Druid throws a resource limit exceeded
|
||||||
exception.
|
exception.
|
||||||
|
|
||||||
There is one exception: if the outer query and all subqueries are the [groupBy](groupbyquery.md) type, then subquery
|
There is one exception: if the outer query is of type [`groupBy`](groupbyquery.md), and has a `dataSource` of type
|
||||||
results can be processed in a streaming fashion and the `druid.server.http.maxSubqueryRows` and `druid.server.http.maxSubqueryBytes`
|
`query` that is itself another `groupBy`, then subquery results can be processed in a streaming fashion. In this case
|
||||||
limits do not apply.
|
the `druid.server.http.maxSubqueryRows` and `druid.server.http.maxSubqueryBytes` limits do not apply.
|
||||||
|
|
||||||
### `join`
|
### `join`
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user