Skip to content

branch-4.1: [fix](decimalv2) fix wrong result of decimalv2 avg #62346#62413

Merged
yiguolei merged 1 commit intobranch-4.1from
auto-pick-62346-branch-4.1
Apr 13, 2026
Merged

branch-4.1: [fix](decimalv2) fix wrong result of decimalv2 avg #62346#62413
yiguolei merged 1 commit intobranch-4.1from
auto-pick-62346-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #62346

### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #58666

Problem Summary:

When getting avg(decimalv2) result, DecimalV2 has fixed internal
scale=9, its arithmetic operators already handle scale correctly, so no
external multiplier is needed.


### 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 April 13, 2026 02:26
@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Apr 13, 2026

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?

@dataroaring dataroaring reopened this Apr 13, 2026
@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Apr 13, 2026

run buildall

@yiguolei
Copy link
Copy Markdown
Contributor

skip buildall

1 similar comment
@yiguolei
Copy link
Copy Markdown
Contributor

skip buildall

@yiguolei yiguolei merged commit 6e4e3d5 into branch-4.1 Apr 13, 2026
28 of 30 checks passed
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.

4 participants