[fix](statistics)Fix select mv with specified partitions bug. #36817
Conversation
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
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
morrySnow
approved these changes
Jun 25, 2024
Contributor
|
run buildall |
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. |
TPC-H: Total hot run time: 39619 ms |
morningman
approved these changes
Jun 25, 2024
TPC-DS: Total hot run time: 173558 ms |
ClickBench: Total hot run time: 30.75 s |
Contributor
Author
|
run p0 |
Contributor
Author
|
run feut |
Contributor
Author
|
run external |
Contributor
Author
|
run p0 |
Jibing-Li
added a commit
to Jibing-Li/incubator-doris
that referenced
this pull request
Jun 28, 2024
…#36817) There is a bug of direct select mv with specified partitions. Planner will fail to find the mv column name. Because we need to create the LogicalOlapScan object using the given mv instead of the base table. ``` mysql> SELECT mv_id from part8 index mv1 partition p1; ERROR 1105 (HY000): errCode = 2, detailMessage = Unknown column 'mv_id' in 'table list' in PROJECT clause ``` This pr is to fix this.
Jibing-Li
added a commit
that referenced
this pull request
Jun 28, 2024
#36982) There is a bug of direct select mv with specified partitions. Planner will fail to find the mv column name. Because we need to create the LogicalOlapScan object using the given mv instead of the base table. ``` mysql> SELECT mv_id from part8 index mv1 partition p1; ERROR 1105 (HY000): errCode = 2, detailMessage = Unknown column 'mv_id' in 'table list' in PROJECT clause ``` This pr is to fix this. backport: #36817
dataroaring
pushed a commit
that referenced
this pull request
Jun 28, 2024
There is a bug of direct select mv with specified partitions. Planner will fail to find the mv column name. Because we need to create the LogicalOlapScan object using the given mv instead of the base table. ``` mysql> SELECT mv_id from part8 index mv1 partition p1; ERROR 1105 (HY000): errCode = 2, detailMessage = Unknown column 'mv_id' in 'table list' in PROJECT clause ``` This pr is to fix this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
There is a bug of direct select mv with specified partitions. Planner will fail to find the mv column name. Because we need to create the LogicalOlapScan object using the given mv instead of the base table.
This pr is to fix this.