Skip to content

branch-4.1: [fix](be) Fix TIMESTAMPTZ values in COALESCE #66689 - #67055

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66689-branch-4.1
Aug 25, 2026
Merged

branch-4.1: [fix](be) Fix TIMESTAMPTZ values in COALESCE #66689#67055
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66689-branch-4.1

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #66689

@MryangeYour Name
[fix](be) Fix TIMESTAMPTZ values in COALESCE (#66689)
fea1f80
COALESCE returned incorrect values for mixed NULL and non-NULL
TIMESTAMPTZ columns because its branchless accumulation buffer was
initialized with a non-zero date default. This change zero-initializes
the buffer and adds a regression case.
### 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 -->
@hello-stephen

hello-stephen commented Aug 24, 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?

@hello-stephen

hello-stephen commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

hello-stephen commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (1/1) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage74.16% (31174/42035)
Line Coverage58.39% (345713/592123)
Region Coverage55.17% (287967/521979)
Branch Coverage56.10% (129749/231269)

@yiguolei
yiguolei merged commit c9b8123 into branch-4.1Aug 25, 2026
30 of 33 checks passed
@github-actions

github-actionsBot commented Aug 25, 2026

Copy link
Copy Markdown
ContributorAuthor

PR approved by anyone and no changes requested.

@github-actionsgithub-actionsBot added the approved Indicates a PR has been approved by one committer. label Aug 25, 2026
@github-actions

github-actionsBot commented Aug 25, 2026

Copy link
Copy Markdown
ContributorAuthor

PR approved by at least one committer and no changes requested.

@morrySnow
morrySnow deleted the auto-pick-66689-branch-4.1 branch August 31, 2026 07:11
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

approvedIndicates a PR has been approved by one committer.reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hello-stephen@yiguolei@Mryange