Don't recreate mview for RisingWave

Author: VaggelisD

.circleci/continue_config.yml

@@ -311,9 +311,9 @@ workflows:
                 - fabric
                 - gcp-postgres
           filters:
-            branches:
-              only:
-                - main
+            # branches:
+            #   only:
+            #     - main
       - ui_style
       - ui_test
       - vscode_test

sqlmesh/core/snapshot/evaluator.py

@@ -2284,11 +2284,11 @@ def insert(
     ) -> None:
         snapshot = kwargs["snapshot"]
 
-        if (
-            not snapshot.is_materialized_view
-            and self.adapter.HAS_VIEW_BINDING
-            and self.adapter.table_exists(table_name)
-        ):
+        # For all engines that support materialized views (except RisingWave) we recreate it.
+        # This is because case if upstream tables were recreated (e.g FULL models), the mview would be invalidated as well.
+        # RisingWave is an exception as it doesn't support CREATE OR REPLACE, so upstream models don't recreate their physical tables.
+        force_view_replace = snapshot.is_materialized_view and not self.adapter.HAS_VIEW_BINDING
+        if not force_view_replace and self.adapter.table_exists(table_name):
             logger.info("Skipping creation of the view '%s'", table_name)
             return
 
@@ -2297,7 +2297,7 @@ def insert(
             table_name,
             query_or_df,
             model.columns_to_types,
-            replace=snapshot.is_materialized_view or not self.adapter.HAS_VIEW_BINDING,
+            replace=force_view_replace,
             materialized=self._is_materialized_view(model),
             view_properties=kwargs.get("physical_properties", model.physical_properties),
             table_description=model.description,