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
Execution of ALTER queries on materialized views #1226
Comments
This feature would be very useful. I learned (via google groups search result) that the best way right now is:
These steps are not atomic and if 2. or 3. fail, then you might have a problem. It's also not trivial to block all running clients from accessing the relevant tables while this is happening. A full fletched ALTER on materialized views would solve these issues. |
@alexey-milovidov do you have a preference for alter materialized view query syntax? I might give it a try. |
The same issue is described here. |
The instructions work well on Ordinary database. But with Atomic database the syntax of |
Always create materialized views using the TO syntax (requires an existing storage table). detach table <materialized_view_name>;
rename table ".inner.<materialized_view_name>" to <storage_table>;
attach table <materialized_view_name>;
drop table <materialized_view_name>;
CREATE MATERIALIZED VIEW <materialized_view_name> to <storage_table>... |
Currently execution of ALTER queries on materialized views has not been fully developed.
(according to documentation)
It will be very convenient if materialized view supports:
The text was updated successfully, but these errors were encountered: