Skip to content

branch-4.1: [fix](be) Return null for TRY_CAST arithmetic overflow #67697 - #67985

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-67697-branch-4.1
Open

github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-67697-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #67697

Problem Summary: 
With enable_strict_cast=true, TRY_CAST of a DECIMAL(6,3) column
containing 123.456 to DECIMAL(4,2) fails the entire query with E-255.
TRY_CAST only classified INVALID_ARGUMENT as a recoverable conversion
failure, while decimal casts return ARITHMETIC_OVERFLOW_ERRROR.
Recognize arithmetic overflow in the shared batch and per-row error
classification so overflowing values become NULL and valid rows survive.
Child expression errors and ordinary CAST still propagate failures. Add
unit coverage for single-row and batch overflow with nullable and
non-nullable original cast results, plus child overflow propagation.


### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

### 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:
apache/doris-website#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 -->
@github-actions
github-actions Bot requested a review from yiguolei as a code owner September 15, 2026 02:59
@hello-stephen

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?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants