[Fix](Nereids) Use correct column unique id when read data from non-base index.#15534
Merged
morrySnow merged 2 commits intoapache:masterfrom Jan 3, 2023
Merged
[Fix](Nereids) Use correct column unique id when read data from non-base index.#15534morrySnow merged 2 commits intoapache:masterfrom
morrySnow merged 2 commits intoapache:masterfrom
Conversation
github-actions
bot
added
area/nereids
area/planner
wangshuo128
force-pushed
the
mv-unique-id
branch
from
f1aaf70 to
b9a7838
Compare
Contributor
|
TeamCity pipeline, clickbench performance test result: |
wangshuo128
force-pushed
the
mv-unique-id
branch
from
c994682 to
c309239
Compare
15 tasks
wangshuo128
force-pushed
the
mv-unique-id
branch
from
c309239 to
e47904f
Compare
morrySnow
approved these changes
Jan 3, 2023
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
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
When light schema change is enabled by default, a column in OLAP scan is retrieved by column unique id instead of the column name. Columns with the same name would use different unique IDs among materialized indexes.
This PR ensures that the column in the OLAP scan node could use the correct column unique id.
Checklist(Required)
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...