Mryange opened a new pull request, #64913:
URL: https://github.com/apache/doris/pull/64913
### What problem does this PR solve?
Array aggregate functions such as `array_avg`, `array_sum`, `array_min`,
`array_max`, and `array_product` previously evaluated each array by creating
and driving the generic aggregate-function path. This added unnecessary per-row
aggregate state, arena, nullable wrapper, and virtual-call overhead for simple
array-local reductions.
Root cause: array aggregation reused the general aggregate-function
execution machinery even though these functions only need a small per-row
reduction state over the nested array data.
This change adds a direct `ColumnArrayView` based fast path with lightweight
`ArrayAggState` reducers for sum, avg, min, max, and product. DecimalV3
sum/avg/product keep using the FE-planned result type and scale, while ordinary
array-mapped functions now trust the FE return type instead of reconstructing a
BE-side aggregate function only for return-type checking.
Local optest result for `array/array_avg_arr` improved from about 1.685s to
0.85-0.91s in warm runs.
### Release note
None
### Check List (For Author)
- Test <!-- At least one of them must be included. -->
- [ ] Regression test
- [ ] Unit Test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason <!-- Add your reason? -->
- Behavior changed:
- [ ] No.
- [ ] Yes. <!-- Explain the behavior change -->
- Does this need documentation?
- [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
https://github.com/apache/doris-website/pull/1214 -->
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR should
merge into -->
--
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]