[fix](planner) should always execute projection plan #17885
Merged
Conversation
This file contains 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
github-actions
bot
added
the
area/planner
morrySnow
force-pushed
the
fix_insert_projection
branch
from
257e5a9 to
8ae8408
Compare
|
run buildall |
|
TeamCity pipeline, clickbench performance test result: |
morrySnow
force-pushed
the
fix_insert_projection
branch
from
8ae8408 to
ac16382
Compare
|
run buildall |
starocean999
approved these changes
Mar 22, 2023
github-actions
bot
added
the
approved
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
morningman
pushed a commit
that referenced
this pull request
Mar 28, 2023
1. should always execute projection plan, whatever the statement it is. 2. should always execute projection plan, since we only have vectorized engine now
gnehil
pushed a commit
to gnehil/doris
that referenced
this pull request
Apr 21, 2023
1. should always execute projection plan, whatever the statement it is. 2. should always execute projection plan, since we only have vectorized engine now
mongo360
pushed a commit
to mongo360/doris
that referenced
this pull request
Jul 12, 2023
1. should always execute projection plan, whatever the statement it is. 2. should always execute projection plan, since we only have vectorized engine now
SWJTU-ZhangLei
pushed a commit
to SWJTU-ZhangLei/incubator-doris
that referenced
this pull request
Jul 25, 2023
commit f5d6201 Author: morrySnow <[email protected]> Date: Wed Mar 22 10:53:15 2023 +0800 [fix](planner) should always execute projection plan (apache#17885) 1. should always execute projection plan, whatever the statement it is. 2. should always execute projection plan, since we only have vectorized engine now commit ad61c84 Author: mch_ucchi <[email protected]> Date: Mon Mar 27 17:50:52 2023 +0800 [fix](planner) fix conjunct planned on exchange node (apache#18042) sql like: select k5, k6, SUM(k3) AS k3 from ( select k5, date_format(k6, '%Y-%m-%d') as k6, count(distinct k3) as k3 from t group by k5, k6 ) AS temp where 1=1 group by k5, k6; will throw exception since conjuncts planned on exchange node, because exchange node cannot handle conjuncts, now we skip exchange node when planning conjuncts, which fixes the bug. notice: the bug occurs iff the conjunct is always true like 1=1 above.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Issue Number: close #xxx
Problem summary
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...