Skip to content

branch-2.1: [fix](Nereids) cse extract wrong expression from lambda expressions (#49166) #49942

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yiguolei merged 1 commit into from
Apr 10, 2025
Merged

branch-2.1: [fix](Nereids) cse extract wrong expression from lambda expressions (#49166) #49942

yiguolei merged 1 commit into from
Apr 10, 2025

Conversation

@924060929
Copy link
Contributor

@924060929 924060929 commented Apr 10, 2025

cherry pick from #49166

@morrySnow @924060929
[fix](Nereids) cse extract wrong expression from lambda expressions (a…
608660b 
…pache#49166)

### What problem does this PR solve?

Related PR: apache#33087

Problem Summary:

CSE should not extract ArrayItemSlot and ArrayItemReference. Because
they could not be computed out of Lambda expression.
NOTICE: currently, we could not extract common expression from Lambda,
because ArrayItemSlot in Lambda are not same.

(cherry picked from commit 9d4faa5)
@924060929 924060929 requested a review from yiguolei as a code owner April 10, 2025 05:25
@Thearas
Copy link
Contributor

Thearas commented Apr 10, 2025

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?

@924060929
Copy link
Contributor Author

924060929 commented Apr 10, 2025

run buildall

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Apr 10, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Apr 10, 2025

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

@github-actions
Copy link
Contributor

github-actions bot commented Apr 10, 2025

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit e4d0c67 into apache:branch-2.1 Apr 10, 2025
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

@morrySnow morrySnow morrySnow approved these changes

Assignees

No one assigned

Labels

approved Indicates 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.

4 participants

@924060929 @Thearas @yiguolei @morrySnow