Skip to content

branch-4.1: [fix](set operation) Use regular child output for set operation rules #64908#65071

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

branch-4.1: [fix](set operation) Use regular child output for set operation rules #64908#65071
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-64908-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #64908

…#64908)

### What problem does this PR solve?

Related PR: #24060, #27628

Problem Summary: Some Nereids rewrite rules mapped set operation outputs
to child outputs by list index. Set operations can carry regulator child
outputs whose order and cardinality differ from the child plan output,
so those rules could read past the child output or rewrite expressions
with the wrong child slot. This change makes one-row union merge and
distinct TopN/Limit pushdown build child mappings from regular child
outputs instead.

### Release note

Fix planner failures or incorrect set operation rewrites when regulated
child outputs differ from child plan outputs.
@github-actions github-actions Bot requested a review from yiguolei as a code owner July 1, 2026 06:09
@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

FE UT Coverage Report

Increment line coverage 100.00% (13/13) 🎉
Increment coverage report
Complete coverage report

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