This is an automated email from the ASF dual-hosted git repository.
victoria pushed a commit to branch 30.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/30.0.0 by this push:
new 6bb5470bc76 Addition to subquery limit migration guide (#16671)
(#16686)
6bb5470bc76 is described below
commit 6bb5470bc768523afeabfae44ff79679836b11f4
Author: 317brian <[email protected]>
AuthorDate: Tue Jul 2 13:35:38 2024 -0700
Addition to subquery limit migration guide (#16671) (#16686)
Co-authored-by: Laksh Singla <[email protected]>
Co-authored-by: Victoria Lim <[email protected]>
Co-authored-by: Jill Osborne <[email protected]>
---
docs/release-info/migr-subquery-limit.md | 4 ++++
docs/release-info/migration-guide.md | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/docs/release-info/migr-subquery-limit.md
b/docs/release-info/migr-subquery-limit.md
index 853be50294d..6801aafdc7b 100644
--- a/docs/release-info/migr-subquery-limit.md
+++ b/docs/release-info/migr-subquery-limit.md
@@ -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.
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
See the following topics for more information:
diff --git a/docs/release-info/migration-guide.md
b/docs/release-info/migration-guide.md
index ca31fce327f..92053b83a11 100644
--- a/docs/release-info/migration-guide.md
+++ b/docs/release-info/migration-guide.md
@@ -28,7 +28,7 @@ In general, when we introduce new features and behaviors into
Apache Druid, we m
The guides in this section outline breaking changes introduced in Druid 25.0.0
and later. Each guide provides instructions to migrate to new features.
-## Migrate to arrays from multi-value dimensions
+## Migrate from multi-value dimensions to arrays
Druid now supports SQL-compliant array types. Whenever possible, you should
use the array type over multi-value dimensions. See [Migration guide: MVDs to
arrays](migr-mvd-array.md).
@@ -36,6 +36,6 @@ Druid now supports SQL-compliant array types. Whenever
possible, you should use
Druid encodes string columns into dictionaries for better compression.
Front-coded dictionary encoding reduces storage and improves performance by
optimizing for strings that share similar beginning substrings. See [Migration
guide: front-coded dictionaries](migr-front-coded-dict.md) for more information.
-## Migrate to `maxSubqueryBytes` from `maxSubqueryRows`
+## Migrate from `maxSubqueryRows` to `maxSubqueryBytes`
Druid allows you to set a byte-based limit on subquery size to prevent Brokers
from running out of memory when handling large subqueries. The byte-based
subquery limit overrides Druid's row-based subquery limit. We recommend that
you move towards using byte-based limits starting in Druid 30.0.0. See
[Migration guide: subquery limit](migr-subquery-limit.md) for more information.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
