[fix](nereids)do not push rf through cteAnchor#34742
Closed
englefly wants to merge 1 commit intoapache:branch-2.1from
Closed
[fix](nereids)do not push rf through cteAnchor#34742englefly wants to merge 1 commit intoapache:branch-2.1from
englefly wants to merge 1 commit intoapache:branch-2.1from
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
Contributor
|
Using an alternative approach to fix it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
pick from master #34744
Or_expansion rule create a CTEAnchor inside plan tree, and there are some columns above anchor sharing the same ExprId with columns under anchor. This mislead runtime pushdown visitor.
Solution:
when detect anchor inside plan tree, do not push rf through it.
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...