hello-stephen opened a new pull request, #64709: URL: https://github.com/apache/doris/pull/64709
Cherry-picked from #64706 (master). Auto cherry-pick failed with a conflict: branch-4.0's copy of these two test files still uses `struct_element()` for struct field access, while master renamed it to `element_at()` in an unrelated earlier change. Resolved by taking master's `element_at()`-based content as-is — this exact content has been run end-to-end on a real branch-4.0 cluster with `-forceGenOut` and both suites pass (`All suites success.`), confirming branch-4.0's engine supports `element_at()` on struct the same way master does. ## Summary (from #64706) - `GROUP BY`/`ORDER BY` on plain array/map/struct columns no longer throws, so the old `errCode = 2 ... must use with specific function ... group by or order by` exception assertions in `two_level_nestedtypes_with_s3data.groovy` / `three_level_nestedtypes_with_s3data.groovy` are stale; removed. - `element_at()` on a struct returns an untyped result that `GROUP BY`/`ORDER BY` and functions like `map_keys()`/`size()` can't accept directly — the most-nested-column checks now `CAST` it to the concrete type at each point of use. - Struct `element_at()` out-of-bound access (`-1`/`0`/`1000`) no longer throws `the specified field index out of bound` either; those stale assertions are removed too. - Refreshes `CPUNetworkUtilization_order.out` (brown_p2) to match current output. ## Test plan - [x] Ran both suites end-to-end with `-forceGenOut` on a real branch-4.0 cluster — `All suites success.` Co-Authored-By: Claude Sonnet 4.6 <[email protected]> https://claude.ai/code/session_01EoF4rikuEzGPKT2ML2WtnM -- 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]
