Skip to content

branch-4.0: [opt](nereids) rewrite PreferPushDownProject to slots before filter-join pushdown #61635#61714

Open
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-61635-branch-4.0
Open

branch-4.0: [opt](nereids) rewrite PreferPushDownProject to slots before filter-join pushdown #61635#61714
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-61635-branch-4.0

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #61635

…oin pushdown (#61635)

Push PreferPushDownProject expressions to the matching join child as
aliases and replace them with slots in filter predicates. This keeps OR
predicates above join while exposing nested-field access below join for
storage-level pruning acceleration.

Plan tree demo:

Before:
```
  LogicalFilter((match_any(info['context'], 'abc') OR r.k2 > 60))
    LogicalJoin(INNER)
      left:  LogicalOlapScan(student)
      right: LogicalOlapScan(score)
```

After:
```

  LogicalFilter((slot#x OR r.k2 > 60))
    LogicalJoin(INNER)
      left:  LogicalProject(student.*, match_any(info['context'], 'abc') AS slot#x)
                  LogicalOlapScan(student)
      right: LogicalOlapScan(score)
```
@github-actions github-actions bot requested a review from yiguolei as a code owner March 25, 2026 08:23
@Thearas
Copy link
Contributor

Thearas commented Mar 25, 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 Mar 25, 2026
@Thearas
Copy link
Contributor

Thearas commented Mar 25, 2026

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage 100.00% (11/11) 🎉
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.

4 participants