3.0 KiB
| id | title | sidebar_label |
|---|---|---|
| migr-subquery-limit | Migration guide: Subquery limit | Subquery limit |
Druid now allows you to set a byte-based limit on subquery size, to prevent brokers from running out of memory when handling large subqueries. Druid uses subqueries as joins as well as in common table expressions, such as WITH.
The byte-based subquery limit overrides Druid's row-based subquery limit.
:::info We recommend that you move towards using byte-based limits starting in Druid 30.0. :::
For queries that generate a large number of rows (5 million or more), we recommend that you don't use maxSubqueryBytes from the outset.
You can increase maxSubqueryRows and then configure the byte-based limit if you find that Druid needs it to process the query.
Row-based subquery limit
Druid uses the maxSubqueryRows property to limit the number of rows Druid returns in a subquery.
Because this is a row-based limit, it doesn't restrict the overall size of the returned data.
The maxSubqueryRows property is set to 100,000 by default.
Enable a byte-based subquery limit
Set the optional property maxSubqueryBytes to set a maximum number of returned bytes.
This property takes precedence over maxSubqueryRows.
Usage considerations
You can set both maxSubqueryRows and maxSubqueryBytes at cluster level and override them in individual queries.
See Overriding default query context values for more information.
Make sure you enable the Broker monitor SubqueryCountStatsMonitor so that Druid emits metrics for subquery statistics.
To do this, add org.apache.druid.server.metrics.SubqueryCountStatsMonitor to the druid.monitoring.monitors property in your Broker's runtime.properties configuration file.
See Metrics monitors for more information.
Learn more
See the following topics for more information:
- Query context for information on setting query context parameters.
- Broker configuration reference for more information on
maxSubqueryRowsandmaxSubqueryBytes.