Skip to content

branch-4.1: [fix](be) Use serialized hash keys for complex types #66777 - #66828

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66777-branch-4.1
Aug 18, 2026
Merged

branch-4.1: [fix](be) Use serialized hash keys for complex types #66777#66828
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66777-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #66777

### What problem does this PR solve?
Problem Summary: Multi-column hash keys could incorrectly classify
fixed-width complex types such as `STRUCT` as fixed keys. Because
`ColumnStruct` stores its fields in separate child columns, it cannot be
packed from a contiguous raw buffer. This change routes multi-column
keys containing complex types through the serialized-key path, fixing
`GROUP BY` and distinct aggregate failures involving fixed-width
`STRUCT` columns.
### 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

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

@hello-stephen

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage58.92% (25252/42856)
Line Coverage43.37% (256850/592188)
Region Coverage39.37% (203321/516411)
Branch Coverage40.88% (93767/229346)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage73.86% (30850/41766)
Line Coverage57.94% (340516/587738)
Region Coverage54.75% (283461/517717)
Branch Coverage55.69% (127568/229076)

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

Copy link
Copy Markdown
ContributorAuthor

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

@github-actions

Copy link
Copy Markdown
ContributorAuthor

PR approved by anyone and no changes requested.

@yiguolei
yiguolei merged commit 59bc3b5 into branch-4.1Aug 18, 2026
30 of 33 checks passed
@morrySnow
morrySnow deleted the auto-pick-66777-branch-4.1 branch August 20, 2026 03:58
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approvedIndicates a PR has been approved by one committer.reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@hello-stephen@yiguolei@Mryange