ektravel commented on code in PR #12549: URL: https://github.com/apache/druid/pull/12549#discussion_r1098965101
########## docs/querying/sql-data-types.md: ########## @@ -80,8 +82,42 @@ the `UNNEST` functionality available in some other SQL dialects. Refer to the do > they are handled in Druid SQL and in native queries. For example, > expressions involving multi-value dimensions may be > incorrectly optimized by the Druid SQL planner: `multi_val_dim = 'a' AND > multi_val_dim = 'b'` will be optimized to > `false`, even though it is possible for a single row to have both "a" and > "b" as values for `multi_val_dim`. The -> SQL behavior of multi-value dimensions will change in a future release to more closely align with their behavior -> in native queries. +> SQL behavior of multi-value dimensions may change in a future release to more closely align with their behavior +> in native queries, but the [multi-value string functions](./sql-multivalue-string-functions.md) should be able to provide +> nearly all possible native functionality. + +## Arrays +Multi-value dimensions may also be converted to standard SQL arrays, either by explicitly converting them with `MV_TO_ARRAY`, Review Comment: ```suggestion You can convert multi-value dimensions to standard SQL arrays explicitly by calling the `MV_TO_ARRAY` function or implicitly by passing them to the [array functions](./sql-array-functions.md). ``` Avoid passive voice whenever possible. -- 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]
