-
Notifications
You must be signed in to change notification settings - Fork 7
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
[materialized_view] why do not use swap instead of drop then create #49
Comments
I'm not using StarRocks (yet), but I'm watching this adapter really closely. Atomic swap sounds indeed a possibility to achieve what describe above, it will be amazing to have such feature in this dbt adapter. |
Same happens with regular views. They do drop&create, causing any dependent mat. view end up in broken and inactive state |
After changed materialized view(or called MV in rest of content), we will drop exist MV then create as follow code:
And I think there are better way to alter asynchronous MV because starrocks support atomic swap as this doc.
I will fork as internal project to use swap but also want to konw more ideas of community.
The text was updated successfully, but these errors were encountered: