Currently, if user deploys their moose app to prod, we just create mvs if they don't exist in clickhouse yet. However, they should be able to delete the aggregation file, check-in that change to github, & deploy. When we deploy, we should just delete all materialized views and recreate them.
This unlocks a couple things. It allows them to clean up mvs they don't want anymore. It also allows them to update table versions specified in the mv. Deleting an mv does not delete the underlying tables, so this is a safe operation.
linear[bot]
commented
3 weeks ago
Currently, if user deploys their moose app to prod, we just create mvs if they don't exist in clickhouse yet. However, they should be able to delete the aggregation file, check-in that change to github, & deploy. When we deploy, we should just delete all materialized views and recreate them.
This unlocks a couple things. It allows them to clean up mvs they don't want anymore. It also allows them to update table versions specified in the mv. Deleting an mv does not delete the underlying tables, so this is a safe operation.