Addition to subquery limit migration guide (#16671)

Co-authored-by: Laksh Singla <lakshsingla@gmail.com>
Co-authored-by: Victoria Lim <vtlim@users.noreply.github.com>
This commit is contained in:
Jill Osborne 2024-07-01 22:22:47 +01:00 committed by GitHub
parent 34c80ee3de
commit bd49ecfd29
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 0 deletions

View File

@ -52,6 +52,10 @@ This property takes precedence over `maxSubqueryRows`.
You can set both `maxSubqueryRows` and `maxSubqueryBytes` at cluster level and override them in individual queries. You can set both `maxSubqueryRows` and `maxSubqueryBytes` at cluster level and override them in individual queries.
See [Overriding default query context values](../configuration#overriding-default-query-context-values) for more information. See [Overriding default query context values](../configuration#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](../configuration/index.md#metrics-monitors) for more information.
## Learn more ## Learn more
See the following topics for more information: See the following topics for more information: