-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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.
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
[fix](mtmv) Fix rewrite wrongly when sync and async materialized view name is same #37311
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 39894 ms
|
@@ -72,7 +72,8 @@ Plan doGenerateScanPlan(CascadesContext cascadesContext) { | |||
@Override | |||
List<String> getMaterializationQualifier() { | |||
return ImmutableList.of(olapTable.getDatabase().getCatalog().getName(), | |||
ClusterNamespace.getNameFromFullName(olapTable.getDatabase().getFullName()), indexName); | |||
ClusterNamespace.getNameFromFullName(olapTable.getDatabase().getFullName()), | |||
olapTable.getName(), indexName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add some cases?
TPC-DS: Total hot run time: 168493 ms
|
ClickBench: Total hot run time: 31.3 s
|
run buildall |
TPC-H: Total hot run time: 39844 ms
|
TPC-DS: Total hot run time: 171834 ms
|
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
ClickBench: Total hot run time: 31.24 s
|
… name is same (#37311) ## Proposed changes This is brought by #33699 `AbstractMaterializedViewRule#isMaterializationValid` check would fail when sync and async materialized view name is same, because the Materialization valid check result is cached by name。this will cause the async materialized view check fail wrongly. This fix this by make sync materialized view name unique in every place.
Proposed changes
This is brought by #33699
AbstractMaterializedViewRule#isMaterializationValid
check would fail when sync and async materialized view name is same, because the Materialization valid check result is cached by name。this will cause the async materialized view check fail wrongly. This fix this by make sync materialized view name unique in every place.