Skip to content

Fix: Model kind change should not be categorized as forward-only#2551

Merged
izeigerman merged 2 commits intomainfrom
fix-forward-only-when-changing-from-non-materialized
May 2, 2024
Merged

Fix: Model kind change should not be categorized as forward-only#2551
izeigerman merged 2 commits intomainfrom
fix-forward-only-when-changing-from-non-materialized

Conversation

@izeigerman
Copy link
Contributor

Before this fix when transitioning from a non-materialized kind like VIEW to a materialized incremental kind for which the forward_only flag is set, SQLMesh would categorized change as FORWARD_ONLY and try to reuse the existing physical table which is actually a view which can't be reused.

@izeigerman izeigerman requested a review from a team May 1, 2024 23:01
@izeigerman izeigerman changed the title Fix: Change from a non-materialized to a materialized kind should not be categorized as forward-only Fix: Model kind change should not be categorized as forward-only May 2, 2024
@izeigerman izeigerman force-pushed the fix-forward-only-when-changing-from-non-materialized branch from e7edea4 to 072618e Compare May 2, 2024 00:32
@izeigerman izeigerman merged commit c7b5ae8 into main May 2, 2024
@izeigerman izeigerman deleted the fix-forward-only-when-changing-from-non-materialized branch May 2, 2024 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants