Skip to content

branch-4.0: [fix](function)Fix array_apply being unable to handle LARGEINT. #61081 - #61105

Merged
yiguolei merged 1 commit into
branch-4.0from
auto-pick-61081-branch-4.0
Mar 7, 2026
Merged

branch-4.0: [fix](function)Fix array_apply being unable to handle LARGEINT. #61081#61105
yiguolei merged 1 commit into
branch-4.0from
auto-pick-61081-branch-4.0

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #61081

@MryangeYour Name
[fix](function)Fix array_apply being unable to handle LARGEINT. (#61081)
39d93f6
```sql
mysql> SELECT array_apply(int_array, '>', 2) FROM fn_test_nullsafe_array order by id;
ERROR 1105 (HY000): errCode = 2, detailMessage = (127.0.0.1)[INVALID_ARGUMENT][E33] array_apply only accept array with nested type which is uint/int/decimal/float/date but got : Nullable(LARGEINT)
```
now
```sql
mysql> SELECT array_apply(int_array, '>', 2) FROM fn_test_nullsafe_array order by id;
+--------------------------------+
| array_apply(int_array, '>', 2) |
+--------------------------------+
| [3, 4, 5] |
| [3, 5] |
| [3, 4] |
| [] |
| NULL |
+--------------------------------+
```
@github-actions
github-actionsBot requested a review from yiguolei as a code ownerMarch 6, 2026 07:37
@hello-stephen

hello-stephen commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaringdataroaring reopened this Mar 6, 2026
@hello-stephen

hello-stephen commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

hello-stephen commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/29) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage53.00% (19150/36135)
Line Coverage36.18% (178313/492844)
Region Coverage32.78% (138231/421642)
Branch Coverage33.78% (60025/177671)

@yiguolei

yiguolei commented Mar 7, 2026

Copy link
Copy Markdown
Contributor

skip buildall

@yiguolei
yiguolei merged commit e25019f into branch-4.0Mar 7, 2026
29 of 31 checks passed
@github-actions
github-actionsBot deleted the auto-pick-61081-branch-4.0 branch March 7, 2026 07:30
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguoleiyiguoleiyiguolei approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hello-stephen@yiguolei@dataroaring@Mryange