hello-stephen opened a new pull request, #64706:
URL: https://github.com/apache/doris/pull/64706

   ## Summary
   - `GROUP BY`/`ORDER BY` on plain array/map/struct columns no longer throws 
(`CheckAfterRewrite` now only blocks Object/Variant/Varbinary types), 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 instead of relying on it implicitly resolving.
   - 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 — same class of stale-baseline issue.
   
   ## Test plan
   - [x] Ran `two_level_nestedtypes_with_s3data` and 
`three_level_nestedtypes_with_s3data` end-to-end with `-forceGenOut` on a 
branch-4.0 cluster — `All suites success.`
   - [x] Ran both suites on a master-branch cluster — 
`two_level_nestedtypes_with_s3data` passes. 
`three_level_nestedtypes_with_s3data` hits an unrelated master-only BE bug 
(`[NOT_IMPLEMENTED_ERROR] Method insert_many_dict_data is not supported for 
TINYINT`) on a plain, untouched `element_at` SELECT — pre-existing, out of 
scope for this PR.
   
   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]

Reply via email to