ektravel commented on code in PR #16516: URL: https://github.com/apache/druid/pull/16516#discussion_r1635450505
########## docs/release-info/migration-guide.md: ########## @@ -27,18 +27,15 @@ 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 and later. Each guide provides instructions to migrate to new features. -<!-- ## Migrate to arrays from multi-value dimensions -Druid now supports SQL-compliant array types. Whenever possible, you should use the array type over multi-value dimensions. See []()>. - ---> +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). ## Migrate to front-coded dictionary encoding 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` -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. See [Migration guide: subquery limit](migr-subquery-limit.md) for more information. \ No newline at end of file +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. See [Migration guide: subquery limit](migr-subquery-limit.md) for more information. Review Comment: ```suggestion 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. ``` -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
